Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

blog.docker.com

Post reply on HN
Print view View original

31–40 of 80 posts

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#31

Post by lobster_johnson »

ninkendo wrote: post #24

How is the multi-host networking implemented? Is there a dependency on a service discovery system? What service discovery system? Or are they using portable IP addresses? How are those implemented? Overlay networks? BGP? Or is it doing some crazy IPTables rules with NAT? Will it work with existing service discovery systems? What happens if a container I'm linked to goes down and comes up on another host? Do I get tra…

According this [1] blog post, networking is pluggable, and the current "overlay driver" uses an overlay network via VXLAN tunneling. The driver sets up the tunnels automatically for you.

[1] https://blog.docker.com/2015/06/networking-receives-an-upgra...

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#33

Post by zenlikethat »

lobster_johnson wrote: post #28
sytse wrote: post #16

What is the difference between Compose, Swarm, Tutum and Kubernetes? To me looks like you can use each of them to compose a set of containers to run an app.

Swarm and Kubernetes are definitely competitors. Swarm is a container manager that automatically starts and stops containers in a cluster using a scheduling algorithm. It implements the Docker API, so it actually acts as a facade that aggregates all the hosts in the pool. So you talk to it just like you would with a single-host Docker install, but when you tell Swarm to start a given container, it will schedule it so…

FWIW, it's possible to specify Swarm filters using Compose which Swarm can use to know it should colocate containers on the same node ("affinity"): https://github.com/docker/swarm/tree/master/scheduler/filter...

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#34

Post by DannoHung »

jacques_chester wrote: post #20
amalag wrote: post #15

I am really trying to figure out the ecosystem. I did some stuff with a single server but now as we need to move it to multiple servers we have Rancher, Weave, and so many others (kubernetes?). And now docker has integrated multihost networking so I am really not sure how to proceed.

I'm biased: use a full PaaS. I like Cloud Foundry because I've worked on it. OpenShift is another alternative.

Pretty sure openshift v3 is built on top of kubernetes

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#35

Post by Estragon »

mikegcoleman wrote: post #21
sytse wrote: post #16

What is the difference between Compose, Swarm, Tutum and Kubernetes? To me looks like you can use each of them to compose a set of containers to run an app.

I won't comment on Kubernetes because I'm not qualified to do so. Compose: Multi-container orchestration. You define an application stack via a compose file including links between containers (web front end links to a database). When you run docker compose up on that file, compose stands up the containers in the right order to deal with dependencies. Swarm: Represents a cluster of Docker Hosts as a single entity. Wil…

If tutum is primarily a gui on top of a bunch of open source products, it doesn't sound like much of a business plan.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#36

Post by dcosson »

I don't quite understand the swarm & compose workflow for production. I'd rather use a declarative language to specify what the systems look like, potentially with auto-scaling, health checks to replace containers if they go down, etc. I don't want to run one-off commands to launch containers based on local instead of centrally stored configuration, run one-off commands to launch the underlying hosts and to scale to more instances (which then isn't persisted anywhere), etc.

I feel like I'm just not understanding the "docker approved" approach. Which is surprising because docker itself is so great.

The networking stuff seems interesting though, I'm very curious how the rest of the ecosystem will evolve to take advantage of it or not.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#37

Post by m_mueller »

cpuguy83 wrote: post #12
m_mueller wrote: post #11

What's the relation between Docker Swarm and Hipache? Is Hipache discontinued? Is Swarm built on it? Is it compatible? Also, is it possible to make Swarm answer to the same client IP with the same backend server during a 'session'? This is very important for database applications where the sync after each write may take some time and you don't want the UI to show different states from different servers until the syst…

Hipache is a reverse proxy, swarm is for managing/scheduling a cluster of docker engines.

Well, when I think of a cluster I think of load balancing and failover - for which you can use a reverse proxy such as Hipache. So I don't quite understand how this is not related. The way I understand Swarm, it could be just a higher level abstraction built on top of that?

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#38

Post by ghayes »

trout wrote: post #30
ninkendo wrote: post #24

How is the multi-host networking implemented? Is there a dependency on a service discovery system? What service discovery system? Or are they using portable IP addresses? How are those implemented? Overlay networks? BGP? Or is it doing some crazy IPTables rules with NAT? Will it work with existing service discovery systems? What happens if a container I'm linked to goes down and comes up on another host? Do I get tra…

This link is basically what Socketplane was working on when they got acquired: https://github.com/docker/docker/issues/8951 Basically integrating OVS APIs into Docker so it could use more mature networking code as well as VXLAN forwarding. VXLAN is basically IP encapsulation (a 16-bit ID) that the networking industry has standardized on. It more or less allows for L2 over L3 links. I like to think of it as the next S…

Could you explain this to someone not as familiar with networking?

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#39

Post by willyyr »

Great to see this. I've been missing Docker Compose on windows. Playing around with swarm for some time now I was hoping for it to become production ready. Does anyone know if swarm can now reschedule failed containers to another host? Couldn't find this detail in the blog post about it.

Re: Announcing Docker 1.9: Production-Ready Swarm and Multi-Host Networking

#40

Post by olalonde »

jacques_chester wrote: post #20
amalag wrote: post #15

I am really trying to figure out the ecosystem. I did some stuff with a single server but now as we need to move it to multiple servers we have Rancher, Weave, and so many others (kubernetes?). And now docker has integrated multihost networking so I am really not sure how to proceed.

I'm biased: use a full PaaS. I like Cloud Foundry because I've worked on it. OpenShift is another alternative.

I've been using Deis (http://deis.io/) which is built on top of Docker and inspired by Heroku. I think it's a bit more "lightweight" than Cloud Foundry but really pleased so far. I had a few issues but the Deis team was always quick to help and fix bugs.
Post reply on HN