Do you need OpenStack after Docker?

Docker from a new technology to a commercial model, the process of development is amazing, it is hot, but also to bring some confusion. This also brings some classmate's question and the comment: if uses the Docker again to use OpenStack to be suitable? This article comes from Helion HP cloud computing, in simple and simple analogy to OpenStack and Docker.

The following is the original text:

Solomon Hykes founded the Docker, never thought Docker would be popular and become the most popular cloud open source project after OpenStack. However, it has been said that Docker's friends rarely know their true meaning, many people are confused by various concepts, even the OpenStack and Docker analogy.

Related background of Docker

In simple terms, Docker provides a container for running programs, while ensuring that these containers are isolated from each other. The virtual machine has a similar function, but it creates a complete operating system stack through hypervisor.

Unlike virtual machines, Docker relies on Linux's own LXC (Linux containers) technology. LXC utilizes Linux to do memory, CPU, and network isolation for processes. Docker mirroring does not require a new operating system to be started, so it provides a lightweight way to package and run programs. And Docker can access the hardware directly, making it much faster I/O operations than the virtual secret.

Docker can run directly on the physical server, which raises questions: If the Docker has been used, is it necessary to use OpenStack?

Is it necessary to use OpenStack? Views are as follows:

This problem has no direct connection with OpenStack, or it can be set on other cloud platforms. Why do we compare Docker with OpenStack? The reason is: OpenStack is the most popular cloud platform in the private cloud environment, in the private cloud environment, we think that we can take Docker as another choice.

Misconceptions about hypervisor: Many KVM and Docker performance testing comparisons have nothing to do with OpenStack, because OpenStack is just a framework. In fact this performance test (whether KVM or Docker) is run under OpenStack, indicating that KVM and Docker can coexist. When using OpenStack to manage Docker situations, the argument between Docker and OpenStack is meaningless.

The cloud platform provides a complete management data center solution, as to what kind of hypervisor or container is just a small part of the cloud platform. Cloud platforms such as OpenStack include multiple tenant security, isolation, management, monitoring, storage, networking and other components. The management of cloud data centers requires a lot of service support, but it doesn't really matter whether it's Docker or KVM.

Docker is not a fully functional VM, and it has many serious flaws, such as security, Windows support, and therefore cannot be a complete replacement for KVM. Now the Docker community has been making up for these flaws, which, of course, can lead to a certain loss of performance.

The performance of the native hypervisor, the performance of the container, the performance of the application is different, and the contrast is meaningless.

Packaging the Docker container into a KVM mirror has little impact on the Docker operation. This architecture typically uses hypervisor to manage computing resources, while orchestration layer, such as heat, cloudify, and kubernetes, are used to manage hypervisor containers in Docker.

Summary

The proper way to treat OpenStack, KVM, and Docker should be: OpenStack for managing the entire data center, KVM and Docker as a complement, KVM for Multi-Tenant Computing resource management, Docker Container for packaged deployments of applications.