@CloudMix #11 (Study Meeting about Containers) Docker on Mesos with OpenVNet
The Topics of Today Let's enhance Mesos and Marathon to integrate them with OpenVNet, which gives docker-containers* network isolation and virtual network functions. * in this case, the targets are “system containers”.
Here are docker containers run under mesos. “What are you talking about?”
“What are you talking about?” I made patches which let containers run on arbitrary virtual networks like below. You can apply some network functions there. DNS DHCP Security Group
Before that, what is Docker Networking like? ▷ Basically, it works on a single host ▷ It takes advantage of Linux Networking functions ▷ Services are exposed with ports About Docker Networking
Recent trends ▷ Tools like flannel, weave have appeared that can work with container managers like kubernetes. ▷ socketplane Since Docker acquired them recently, socketplane could be the standard networking function of it.
Recent trends Docker seems to aim to build a platform. However, the fact Docker itself is getting a little fat makes some people feel down.
Otoh, in the field of SDN... They have been around for some time. ▷ edge-overlay networking ▷ network function virtualization on distributed edges ▷ to support containers (btw, what does “support” mean in this case?) ▷ a de facto standard networking api (Neutron?)
OpenVNet? An open source software which builds overlaid networks and gives them virtual network functions. It's been developed by Axsh* co., LTD. Mainly. OpenVNet: ▷ was spinned-out from wakame-vdc ▷ builds virtual networks with MAC2MAC and GRE tunnels ▷ gives network functions like security groups, dns, dhcp * http://axsh.co/
Something similar to this ▷ VMWare NSX ▷ midonet ▷ OpenContrail ▷ OpenDaylight OpenDOVE(how is it going?), VTN etc.
▷ Various kind of tools related to docker networking have come ▷ However, the networking products from SDN field can realize more complex and powerful network environment. ▷ Why don't you integrate them with Mesos/Marathon/Docker? The main subject of today
Demo Let's build the environment like below with json request for marathon, and “Scale” button. eth0 10.0.100.0/24 DHCP eth0 10.0.100.0/24 DHCP eth1 192.168.0.0/24 DHCP The same IP range (isolated)
Conslusion Frankly speaking, if wakame-vdc suppoted Docker, you didn't need to enhance like this ..? ▷ Maybe, you're right. ▷ However, I've learned a lot in the process of researches or source code reading of Mesos and Marathon.