4 ms·

Kubernetes as an abstraction layer above clouds, whereas OpenStack is a cloud computing environment. Though, I heartily agree with "it's easy to get started wi

Kubernetes as an abstraction layer above clouds, whereas OpenStack is a cloud computing environment. Though, I heartily agree with "it's easy to get started with Kubernetes, and difficult to get started with AWS". When I tried looking at deploying an application to OpenStack (as an alternative to deploying to AWS), I was barely able to setup an OpenStack cloud environment on my computer. The most practical option was to use a public cloud which provided OpenStack APIs. Even with public clouds with OpenStack APIs.. my experience trying "compute VM with an internet-facing load-balancer in front" was that different public clouds required different setup for this. -- TBH, this surprised me. I understand that you can't just copy-paste Terraform code for AWS and have it work for GCP; but I had expected to be able to copy-paste Terraform code for one OpenStack cloud and have it work with another OpenStack cloud.

jetbalsa 4y ago
For your "local" deployment of openstack, look into "Devstack" -- For the cross openstack terraform, the only main issue I ran into was images for the VMs you are going to use are going to differ a bunch, same with networking. as everyone has their own take on how networking should work in their openstack.
nicolaslem 4y ago
The reason the network setups do not really match between public OpenStack cloud providers is that most of them significantly change that part of OpenStack. My knowledge is very outdated but I remember that the networking part had significant scalability issues that pushed every provider to introduce their secret sauce.
- jetbalsa 4y ago
  Yep, a "stock" openstack install will tend to use OVN or VLANs -- Most public clouds throw that out completely since they are going to use their existing methods for networking. its a shame, I've not found a public cloud that supports something like OVN.
  - hyperionplays 4y ago
    OneQode does.

jetbalsa 4y ago

For your "local" deployment of openstack, look into "Devstack" -- For the cross openstack terraform, the only main issue I ran into was images for the VMs you are going to use are going to differ a bunch, same with networking. as everyone has their own take on how networking should work in their openstack.

nicolaslem 4y ago

The reason the network setups do not really match between public OpenStack cloud providers is that most of them significantly change that part of OpenStack. My knowledge is very outdated but I remember that the networking part had significant scalability issues that pushed every provider to introduce their secret sauce.

jetbalsa 4y ago
Yep, a "stock" openstack install will tend to use OVN or VLANs -- Most public clouds throw that out completely since they are going to use their existing methods for networking. its a shame, I've not found a public cloud that supports something like OVN.
- hyperionplays 4y ago
  OneQode does.