Solve the network problem of the dock

[E liangshi Yiyou network] docker is an open-source application container engine that allows developers to package the content their applications and applications depend on into a portable container, then, you can publish the container to any popular Linux machine to achieve virtualization. Docker has completely released the power of virtualization. It makes application distribution, deployment, and management more efficient and easy, and relies on its own outstanding capabilities, docker has now become the darling of IT entrepreneurs and creators. Is docker perfect? The answer is no. For managers and developers, the network is still a pain point for docker. Managing the interaction and network between docker containers is always challenging.

To solve network problems, many companies have developed their own products to help developers use docker more conveniently. Serdar yegulalkaline recently shared an article on InfoWorld about five of the most important projects, including weave, kubernetes, coreos, flannel, pipework, and socketplane, at the same time, he believes that some of these projects may become part of docker in the future. Next let's take a look at these five projects.

WeaveDeveloped by Zett. Io, it can create a virtual network to connect docker containers deployed on multiple hosts. All the containers via weave are like being connected to the same network switch. The applications using the network do not need to configure port ing and links. External devices can access the services provided by application containers on the weave network, and existing internal systems can also be exposed to application containers. Weave Can penetrate the firewall and run on some connected networks. In addition, weave supports encryption, so you can connect to the host from an untrusted network. For more information about weave or relevant source code, click here.

KubernetesIt is an open-source project launched by Google for container management and orchestration. It allows users to easily manage, monitor, and control the deployment of containerized applications across container host clusters. Kubernete has a special networking concept similar to SDN: a service proxy is used to create an IP address that can be assigned to any number of containers, the front-end application or the user who uses the service calls the service only through this IP address, and does not need to care about other details. This kind of proxy solution is somewhat SDN-like, but it is not built on a typical SDN layer-2 mechanism. If you are interested, read the article Craig Matsumoto posted on sdncentral or click here to view the source code.

FlannelThe previous name is rudder. It is a Coverage Network tool designed by the coreos team for kubernetes. It aims to help each coreos host using kuberentes have a complete subnet. Kubernetes allocates an independent IP address for each pod, so that the containers in the same pod can be connected to each other. The existing coreos does not have this capability. To solve this problem, flannel sets a subnet for the host by creating a Coverage Network in the cluster. Click here to view the source code of the project.

PipeworkIt is a solution designed by an engineer of docker to allow containers to connect under "any complicated scenario. Pipework is a network function enhancement plug-in for docker. It uses cgroups and namespacpace. Click here to view the source code of the project.

SocketplaneThe goal is to focus only on the slogan "SDN to docker". Basically, there is no substantive work. The idea of this project is to use the same devops tool as docker to manage the virtual network of containers, and build a product equivalent to opendaylight/Open vswitch for docker. It sounds promising, but we won't be able to see any products before the First Quarter of 2015.

For the above project, Serdar yegulphosphatase also published a specific point of view in his article. He believes that weave is the best starting point because it solves most of the current problems through a straightforward method. Kubernetes is also a good starting point, but it may not be that easy to use. Flannel is better to be used with coreos, and it depends on kubernetes. For pipework, Serdar yegulpld considers it a temporary design scheme and is likely to be discarded. The final socketplane is basically just a look, don't expect too high. We recommend that you log on to the E-mentor Yiyou network tutorial.

Solve the network problem of the dock