Guidance on Provider donation

[Rohit Yadav]

All,

We've been working on a CAPI provider and are interested in getting it
donated under CNCF/CAPI SIG.

I’d like some guidance on how we get started with that process.

Also, any advice on:
- specific steps and process of the donation under CNCF
- how some of our authors and contributors would be granted commit
access to the donated repo under CAPI SIG and
- integration with its bot/tooling and CI/CD system (or with our CI/CD system)
- get invited to join slack (the link isn't allowing us to join slack,
and we don't have a @get-an-invite-at.slack.kubernetes.io)

Would be greatly appreciated.

Thanks and regards.

[Ihor Dvoretskyi]

Rohit, which provider are you referring to?

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-cluster...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CANLSSBWUTBjgO5Vym5RogG95jUmKaVRBcDqoB2KC3OrZihjT1A%40mail.gmail.com.

[Rohit Yadav]

Ihor,

Thanks for replying, this is a new CAPI provider that is being
developed for an IaaS cloud platform. At this stage, we're trying to
understand the process of donating this provider to the SIG, as I see
many other IaaS CAPI providers part of the
https://github.com/kubernetes-sigs/?q=cluster-api-provider

Regards.

[Benjamin Elder]

> - specific steps and process of the donation under CNCF

Cluster API Providers are typically owned by this SIG under Kubernetes, rather than the CNCF directly.

The process to create or migrate a repo into the project involves an issue here:
https://github.com/kubernetes/org/issues/new/choose

But first approval from the SIG that will own it is required as mentioned in the "Repository creation/migration" issue template (so, it might be helpful to start sharing more specific details with this SIG). 

The repo must also meet requirements around licensing and adopt the CNCF's CLA system. More details on that are here https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-donated-repositories

> - how some of our authors and contributors would be granted commit
> access to the donated repo under CAPI SIG and

https://github.com/kubernetes/community/blob/master/community-membership.md

> - integration with its bot/tooling and CI/CD system (or with our CI/CD system)

https://github.com/kubernetes/org/issues/new/choose has an "integrations" template, the GitHub management subproject has to approve integrations with third party systems.

SIG Testing runs Kubernetes's own CI system, most CAPI repos use this, though some projects use built-in github actions.
In order to integrate the project's CI with an IaaS platform (if that route is taken), preferably resources to run on this platform are provided through CNCF => SIG K8s Infra.

> - get invited to join slack (the link isn't allowing us to join slack,
> and we don't have a  @get-an-invite-at.slack.kubernetes.io)

slack.k8s.io is the "get an invite" link, (from https://github.com/kubernetes/community/blob/144461e6e1f1dc5048bf1cdd78ce38c91c978831/communication/README.md#slack and other places)

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CANLSSBV81AuiDimEi%3DKJkpF7164Q-NzLMNAMgUYTyfqQm5L6JQ%40mail.gmail.com.

[Davanum Srinivas]

+1 to all that Ben said here.

Also if you are able to share the name of the IaaS, it would help gauge interest in the SIG/community. Also would be useful is a link to an existing repository as well.

-- Dims

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CAOZRXm9a7O1qMyzPL6nfVzkq-dyGzc8C_OgUXFyKnYtRjy%3DPFA%40mail.gmail.com.

--

Davanum Srinivas :: https://twitter.com/dims

[Rohit Yadav]

Thank you Ihor, Alex, Benjamin, Dims for replying and explaining the process.

The CAPI provider is for opensource Apache CloudStack,
http://cloudstack.apache.org, and we've used the Apache Public License
v2. I'm a committer and PMC member of the Apache CloudStack project.

During the course of development and testing, a few of my colleagues
and collaborators have already signed the ICLA due to requirements for
getting our pull requests merged to add the support for CentOS7,
RHEL/RockyLinux 8 qemu images in
https://github.com/kubernetes-sigs/image-builder

Regards.

[Giles Sirett]

I'm working with Rohit on this. The platform he IaaS mentions is Apache Cloudstack. This is a CAPI provider for Apache Cloudstack

[Alexandr Demicev]

Hi Rohit,

You can join weekly CAPI office hours https://github.com/kubernetes-sigs/cluster-api#-community-discussion-contribution-and-support and present the provider to a wider audience and there is also a sig-cluster-lifecycle meeting where you can discuss new repository https://github.com/kubernetes/community/blob/master/sig-cluster-lifecycle/README.md#meetings.
Some information you may find useful -  https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md

Alex.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CANLSSBV81AuiDimEi%3DKJkpF7164Q-NzLMNAMgUYTyfqQm5L6JQ%40mail.gmail.com.

[Rohit Yadav]

Thanks Alex, we'll put together a proposal and join the next office hours meeting.

Regards.

[Rohit Yadav]

All,

We've put together a proposal draft here: https://docs.google.com/document/d/1wIuOJx8boaHyqmlUlNy6VJqua7r9TxPc05YaZWEF-AE/edit# and added agenda for tomorrow's weekly CAPI office hours to present the provider.

The work is a joint collaboration between AWS (https://aws.amazon.com) and ShapeBlue (https://www.shapeblue.com). The repository is here: https://github.com/aws/cluster-api-provider-cloudstack

Regards.

[David Jumani]

Hi,

I've worked with Rohit and others in AWS and ShapeBlue on creating CAPI for CloudStack.

As part of this initiative, we've already added support for Rocky Linux 8 to the image-builder repo.

We've also created CAPI VM template images for CloudStack based on the image-builder repo which are available at http://download.cloudstack.org/templates/capi/ for KVM, XenServer and VMware which are the three main hypervisors supported by CloudStack. We will also be raising a PR on the image-builder repo adding support for CloudStack compatible images.
There's also a talk on CAPI for CloudStack which would include a demo at the CloudStack European User Group - A virtual get together for the European CloudStack Community but open to everyone (https://events.hubilo.com/cloudstack-european-user-group/register) if anyone is interested in knowing more about CAPI and CloudStack.
And earlier this month, CloudStack has released its latest LTS version, CloudStack 4.16.1.0 (http://docs.cloudstack.apache.org/en/latest/releasenotes/about.html#what-s-new-in-release), compatible with the CAPI provider that has been created.
Thanks everyone for your support and guidance on this and looking forward to getting it donated!

- David