3 ms·

I'm not sold on the title of this article. It isn't about Docker Orchestration at all (an example of an article about orchestration would be https://blog.docker

by ecaron 11y ago

I'm not sold on the title of this article. It isn't about Docker Orchestration at all (an example of an article about orchestration would be https://blog.docker.com/2015/02/orchestrating-docker-with-machine-swarm-and-compose/ https://blog.docker.com/2015/02/orchestrating-docker-with-ma...) This article is just about the problems that warrant implementing an orchestration solution. It is only at the end that they hint about talking about how orchestration is actually accomplished in a "Next time we'll talk about..." teaser

josephjacks 11y ago
I think the article provides some great foundational perspectives on how HA/service discovery/port mgmt and so on were handled in the "pre-containers" era of VMs with a look into how these challenges are somewhat re-imagined in this current world of containers (predominantly Docker). I'm looking forward to the follow-on post about why they chose Kubernetes and how that solution works for them.
dang 11y ago
Ok, let's use your phrase. Title changed from "Docker Orchestration". If someone suggests a better title, we can change it again.
erez-rabih 11y ago
Thanks for the comment ecaron. As this is the first post of a series, I wanted to present the problems we're dealing with when running Docker containers on production. It was also important for me to specifically touch the major shift of mind and new challenges that Docker has brought to our production infrastructure. As I see it orchestrating Docker isn't about a certain tool or a framework. It is an abstract problem that is being solved in many different ways/frameworks. That's why I do think that Docker orchestration is an appropriate title for the article, but I can see where you're coming from :) The next post in the series is going to be much more specific to ECS and Kubernetes.
- joepvd 11y ago
  Thanks for the write-up, this is really helpful to get the big picture. Looking forward to your next posts.

by ecaron 11y ago

josephjacks 11y ago

I think the article provides some great foundational perspectives on how HA/service discovery/port mgmt and so on were handled in the "pre-containers" era of VMs with a look into how these challenges are somewhat re-imagined in this current world of containers (predominantly Docker). I'm looking forward to the follow-on post about why they chose Kubernetes and how that solution works for them.

dang 11y ago

Ok, let's use your phrase. Title changed from "Docker Orchestration". If someone suggests a better title, we can change it again.

erez-rabih 11y ago

Thanks for the comment ecaron. As this is the first post of a series, I wanted to present the problems we're dealing with when running Docker containers on production. It was also important for me to specifically touch the major shift of mind and new challenges that Docker has brought to our production infrastructure. As I see it orchestrating Docker isn't about a certain tool or a framework. It is an abstract problem that is being solved in many different ways/frameworks. That's why I do think that Docker orchestration is an appropriate title for the article, but I can see where you're coming from :) The next post in the series is going to be much more specific to ECS and Kubernetes.

joepvd 11y ago
Thanks for the write-up, this is really helpful to get the big picture. Looking forward to your next posts.