Adam Lawson wrote: > [...] > I've been an OpenStack architect for at least 5+ years now and work with > many large Fortune 100 IT shops. OpenStack in the enterprise is being > used to orchestrate virtual machines. Despite the additional > capabilities OpenStack is trying to accommodate, that's basically it. At > scale, that's what they're doing. Not many are orchestrating bare metal > that I've seen or heard. And they are exploring K8s and Docker Swarm to > orchestrate containers. They aren't looking at OpenStack to do that.
I have to disagree. We have evidence that some of the largest Kubernetes deployments in the world happen on top of an OpenStack infrastructure, and hopefully some of those will talk about it in Boston. I feel like you fall in the common trap of thinking that both technologies are competing, while one is designed for infrastructure providers and the other for application deployers. Sure, you can be a Kubernetes-only shop if you're small enough or have Google-like discipline (and a lot of those shops, unsurprisingly, were present in Berlin), but most companies have to offer a wider array of infrastructure services for their developers. That's where OpenStack, an open infrastructure stack, comes in. Giving the infrastructure provider a framework to offer multiple options to application developers and operators. -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev