Openstack Provider

[peyunco]

Is this a bug report or feature request?

• Feature Request

What should the feature do:

• Crossplane should be able to deploy or migrate workloads on Openstack cloud environment.

What is use case behind this feature:

• User can successfully deploy or migrate workloads to Openstack environments through the use of different Openstack services as authentication, compute, image, networking and storage.

Environment:

• N.A.

[kevinzs2048]

Any update on this?
If not, I can take over this task now.
We ( Linaro ) are using OpenStack deeply in a public cloud

[bassam]

@kevin-zhaoshuai we'd love your support here ! Please join the slack channel at https://slack.crossplane.io and we'd love to discuss further.

[hasheddan]

@kevinzs2048 are you still interested in helping out here?

[kevinzs2048]

@hasheddan Hi, I do not have time recently working on this. But will still pay attention on this topic.

[muvaf]

I have added this issue to Proposed column of the next release. I believe at least bootstrapping the provider repo and implement 1 small resource would be much of help to folks who'd like to contribute for specific managed resources.

[till]

I want to experiment with this as well. Not sure how much I can contribute, but will definitely try it if you have an example repository which implements something. :)

[prasek]

@till an example repo would be awesome! 👍

Are you using the native Open Stack APIs or the AWS compatibility APIs?

Also we're working on code generating resource controllers on top of the Terraform Providers #262. Are you using the OpenStack Terraform Provider today? If you give us the list of OpenStack resources you need we can prioritize them for code generation. We should be able to generate most of what's needed, but each resource will need a few annotations to assist the code generation, so if you're interested in helping with that and testing on OpenStack, it could help speed things along.
/cc @kevinzs2048 @kasey

[till]

@prasek We use OpenStack-APIs. Not aware of a compat layer (any info on that?).

And yes, we use the Terraform provider. I think my basic needs are described here: terraform-providers/terraform-provider-openstack#541

Essentially creating the network environment and attaching an instance to it:

• network
• subnet
• ports
• instance

[till]

I got so excited and forgot that we probably also need a router and a floating IP. But I can try to help too.

Is there anything to take a look at yet?

[till]

@prasek do you have anything I could hack on? The Terraform integration sounds great since we use Terraform already.

[till]

Leaving this here:
https://github.com/subhransusekhar/provider-openstack

Will experiment on the weekend.

[MPV]

In addition to @subhransusekhar (as mentioned above), it seems like @rochaporto has also started something recently, here: https://github.com/rochaporto/provider-openstack

[rochaporto]

Yes, i'm working on this. I'm particularly interested in instantiating kubernetes clusters (with Magnum) so will push that first.

[luebken]

With crossplane-contrib/terrajet we have created a tool that creates Crossplane providers with very low effort based of a Terraform provider. In this case, https://github.com/terraform-provider-openstack/terraform-provider-openstack/. If someone wants to take a look, please let me know, we are happy to assist.

[rochaporto]

Thanks for the update. We're about to restart this activity, definitely interested in some assistance to kick things off again.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[negz]

/fresh

[Dentrax]

Hey @rochaporto, still working on this? Any updates? 🤔

[rochaporto]

Hi @Dentrax . We're meeting today between different people to work out how to best progress with this. Will update the ticket soon.

[chriscowley]

@rochaporto What was the outcome of that meeting? Is there even a pre-alpha provider that people can start getting their hands dirty with ?

[ja-gooding]

Is there a reason this issue was closed?

[jbw976]

Good question @ja-gooding - I do still see demand for this and folks asking about it, so I'll re-open this issue :)

[jbw976]

/fresh

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 7 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[rimbi]

Hi All, our team needs an OpenStack provider. Given some guidance, we might allocate the effort to do the development.

[schlakob]

It looks like @martinnirtl recently has started working on a provider here: https://github.com/martinnirtl/provider-openstack
The provider is already available on the marketplace: https://marketplace.upbound.io/providers/martinnirtl/provider-openstack/v0.1.1

At the moment it only supports a simple compute InstanceV2, but since it is build on upjet it should be possible to add additional resources as well.

[rimbi]

We have also started one, although it's not public.

[negz]

I wanted to note that currently there are no plans for the maintainers of Crossplane to work on this provider. Our focus is on the "core" of Crossplane, rather than building providers.

That isn't to say we don't strongly support the creation of this provider. I'm sure it would be very useful. We'd be happy to create a repository under https://github.com/crossplane-contrib if anyone feels motivated to step up and maintain a provider for Openstack.

[rochaporto]

We're still interested on this, i think it's worth it to create the repo and iterate there.

[negz]

I had missed when I wrote my last comment that a couple of providers already exist for OpenStack. I'm happy to move one to crossplane-contrib if the owners are interested. It's also perfectly fine for them to remain where they are if that's what folks would prefer.

It seems like https://github.com/dusky-mate/provider-openstack is the most active and mature. Would it make sense for someone to open an issue there and see if they'd like to move to crossplane-contrib?

[martinnirtl]

Hi there!
think the owner of this repo is already on this issue.
@schlakob would you be up moving your provider-openstack to crossplane-contrib?

[schlakob]

Hi @negz @martinnirtl,
sure we would like to move the dusky-mate/provider-openstack to crossplane-contrib. Are there any special requirements, or is there a contact person we can get in touch with?

[negz]

@schlakob Sorry just saw this - let me get back to you ASAP.

[jbw976]

Awesome @schlakob!!! I can help you out with the process - essentially you can choose from one of the options described in crossplane/org#32.

Feel free to reach out to me directly on Crossplane Slack to discuss more if that's better for you 🙇

[jbw976]

@schlakob has generously transferred ownership of the provider-openstack repo over to the crossplane-contrib organization - folks are welcome to collaborate there in its new neutral community home! awesome!! 🙇‍♂️ 🤩

https://github.com/crossplane-contrib/provider-openstack

[schlakob]

Thanks to @jbw976 for helping with the transfer.

I'm looking forward to work together on the provider for Openstack. 💪

[negz]

I'm going to close this issue now that we have a repository for folks to collaborate on the OpenStack provider. Thanks!