Feature request: Adding OpenStack as supported IaaS

[voelzmo]

A few questions arise when trying to map AWS concepts such as VPC, subnet, and ELB to OpenStack:

• VPC might best map to private network or even OpenStack project
• AWS subnet is either an OpenStack subnet or a private network – depending on the above choice
• ELB might map to neutron LBaaS or you'd require CF to be installed with an HAProxy instead

Not sure what else I might be missing here? What do you think?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/134609655

The labels on this github issue will be updated when the story is started.

[evanfarrar]

Hey @voelzmo we are currently focused on adding our second ever IaaS, GCP, but will look at other IaaS after that is complete.

[voelzmo]

Thanks, @evanfarrar. Feel free to reach out once you consider OpenStack, so we can talk about a few concepts and how to match those.

[lexsys27]

cf-deployment recently announced Open Stack support.

Any updates from the bbl side?

[voelzmo]

@lexsys27 Our team has contributed the OpenStack support to cf-deployment, and we will look at bbl integration soon. Right now, we have a few other things as top priorities, but this is definitely on our list.

You can already get some of the convenience by relying on the terraform templates linked in the OpenStack README.

Hope that helps for now.

[genevieve]

Hey Marco! As openstack is now wired up in bbl, I am going to close this issue in favor of new issues or PRs regarding additional functionality (like actually making networks!)