Docker容器集成方案1.pptx

Docker容器集成方案;OPEN CONTAINER Initiative –OCI (formerly OCP) ;Docker ;Docker Toolbox;Lightweight runtime robust tooling that builds and runs your Docker containers. Runs on Linux to create the operating environment for your distributed applications. The in-host daemon communicates with the Docker client to execute commands to build, ship and run containers.;Cloud hosted service from Docker that provides registry capabilities for public and private content. Manage Users Organizations Docker Subscription Repo Plans Automated Builds Triggers, WebHooks Links;Automated Docker Provisioning Single command Docker setup Single command Swarm setup Creates Hosts on most major virtualization hypervisors and in cloud service providers space;;Docker CAAS – Container as a Service;;Primary design pattern and focus of Docker was the non-persistent use of Graph Drivers (–storage-driver) Docker uses drivers based on Kernel FS modules that enable use of layered Docker images to create a Read/Write Union File System that serves as primary storage for a container The persistent part of the design pattern for containers typically comes from using Volumes that are first attached to a Linux OS and then to a specific Container. Accomplished via: Kernel storage modules, SCSI NFS ; Docker 1.7 was the first release that adds Volume plugin functionality in “experimental phase” Docker 1.8 included volume plugins, allowing you to back Docker volumes by any third-party storage system, i.e. Ability for Storage Partner ecosystem to integrate their storage with Docker Docker 1.9 allows an orchestration system to setup volumes as needed, separate from the container lifecycle. This integrates with the plugin system. The plugin system worries about provisioning the actual storage to provide to Docker, the volume API is the user-facing side that drives those plugins.;Docker now has volume APIs so you can manage the entire lifecycle of a volume Volume plugin functionality allows Docker to request th