3 ms·

Drawing comparison between OpenStack and K8s is also invalid IMO... they operate at different levels of abstraction. You can use K8s with OpenStack as a cloud p

by brtknr 8y ago

Drawing comparison between OpenStack and K8s is also invalid IMO... they operate at different levels of abstraction. You can use K8s with OpenStack as a cloud provider as with any other cloud provider. K8s is intended to abstract away the infrastructure that lies underneath and give you a consistent way to deploy services across different cloud providers.

jrudolph 8y ago
The point made by OP is not so much about the technology but about drawing parallels between the history of and hopes held for both projects. Both OpenStack and K8s were/are hyped as solutions to reduce vendor lock-in, although they do so in different ways. The parallels between the two are startling, i.e. at the beginning of OpenStack vendors tried to differentiate themselves by solving distribution/installation and plug-ins/integrations. How many K8s distros/installers are out there right now? Countless... [0] provides an interesting angle to the discussion that vendors trying their best to differentiate themselves is what ultimately led to the demise of OpenStack. I'm so far optimistic the same won't happen to K8s. Google is investing into K8s as a vehicle to gravitate workloads to GCP, but in order to do so it has to maintain some level of compatibility to other cloud vendors. 0: https://aeva.online/2019/03/what-happened-to-openstack/ https://aeva.online/2019/03/what-happened-to-openstack/
majewsky 8y ago
In fact, my team does Kubernetes on OpenStack on Kubernetes. :) It's OpenStack on Kubernetes because we deploy the OpenStack components on a baremetal Kubernetes cluster (with actual payloads running in VMware), and it's Kubernetes on OpenStack because we have an addon service that allows customers to spin up Kubernetes on the VMware VMs created by OpenStack. We also dogfood this because the baremetal Kubernetes cluster is not large enough to hold all our internal services.
- jrudolph 8y ago
  So you're running VIO / vmWare integrated OpenStack?
  - majewsky 8y ago
    No. We started with our efforts before VIO was a thing. You can see what we're doing at https://github.com/sapcc https://github.com/sapcc, though admittedly that org is quite busy and I don't know every part of it myself.

by brtknr 8y ago

jrudolph 8y ago

The point made by OP is not so much about the technology but about drawing parallels between the history of and hopes held for both projects. Both OpenStack and K8s were/are hyped as solutions to reduce vendor lock-in, although they do so in different ways. The parallels between the two are startling, i.e. at the beginning of OpenStack vendors tried to differentiate themselves by solving distribution/installation and plug-ins/integrations. How many K8s distros/installers are out there right now? Countless... [0] provides an interesting angle to the discussion that vendors trying their best to differentiate themselves is what ultimately led to the demise of OpenStack. I'm so far optimistic the same won't happen to K8s. Google is investing into K8s as a vehicle to gravitate workloads to GCP, but in order to do so it has to maintain some level of compatibility to other cloud vendors. 0: https://aeva.online/2019/03/what-happened-to-openstack/ https://aeva.online/2019/03/what-happened-to-openstack/

majewsky 8y ago

In fact, my team does Kubernetes on OpenStack on Kubernetes. :) It's OpenStack on Kubernetes because we deploy the OpenStack components on a baremetal Kubernetes cluster (with actual payloads running in VMware), and it's Kubernetes on OpenStack because we have an addon service that allows customers to spin up Kubernetes on the VMware VMs created by OpenStack. We also dogfood this because the baremetal Kubernetes cluster is not large enough to hold all our internal services.

jrudolph 8y ago
So you're running VIO / vmWare integrated OpenStack?
- majewsky 8y ago
  No. We started with our efforts before VIO was a thing. You can see what we're doing at https://github.com/sapcc https://github.com/sapcc, though admittedly that org is quite busy and I don't know every part of it myself.