Downloaded 34 times
![Configuration
Example config file (zk.conf): Group configuration = Instance + Flavor
{
"Properties": {
/* raw configuration */
}
}
{
"groups" : {
"my_zookeeper_nodes" : {
"Properties" : {
"Instance" : {
"Plugin": "instance-vagrant",
"Properties": {
"Box": "bento/ubuntu-16.04"
}
},
"Flavor" : {
"Plugin": "flavor-zookeeper",
"Properties": {
"type": "member",
"IPs": ["192.168.1.200", "192.168.1.201", "192.168.1.202"]
}
}
}
}
}
}](https://image.slidesharecdn.com/docker-from-dev-to-prod-oct-2016-oscon-london-161017135822/85/Oscon-London-2016-Docker-from-Development-to-Production-73-320.jpg)
Uploaded byPatrick Chanezon
Oscon London 2016 - Docker from Development to Production
The document is a presentation by Patrick Chanezon from Docker Inc. discussing the transition from development to production using Docker, emphasizing the cultural movement of DevOps which combines people, processes, and tools for continuous delivery. Key topics include the evolution of Docker's orchestration capabilities, the introduction of a container-as-a-service platform, and the importance of agility and collaboration in enterprise environments. The presentation also highlights various Docker features, such as orchestration built into version 1.12 and Infrakit for managing declarative, self-healing infrastructures.
More Related Content
Similar to Oscon London 2016 - Docker from Development to Production
Oscon London 2016 - Docker from Development to Production
- 1. Patrick Chanezon @chanezon, DockerInc. Docker from development to production London, October 2016
- 2. French Polyglot Platforms Software Plumber San Francisco DeveloperRelations @chanezon
- 3.
- 5.
- 6.
- 7.
- 10.
- 12. Low MTBIAMSH MTBIAMSH (MeanTime Between Idea And Making Stuff Happen)
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. Devops • Cultural movement •Inspired by agile methods • People, Processes & Tools • Continuous delivery • Infrastructure as code • Cross silo collaboration • Small iterations • Feedback loop, measurement Image from Patrick Debois http://www.slideshare.net/jedi4ever/devops-the-war-is-over-if-you-want-it http://www.slideshare.net/jedi4ever/devopsdays-downundervfinal
- 20.
- 21.
- 22. 28 https://blog.docker.com/2014/12/dockercon-europe-keynote-continuous-delivery-in-the-enterprise-by-henk-kolk-ing/ Henk Kolk, ING,DockerCon EU 2014 People, Processes, Products deployment time: 9 months -> 15 min 1500 deployments/week
- 23.
- 24. The world needs toolsof mass innovation
- 25. A programmable Internetwould be the ultimate tool of mass innovation
- 26. A commercial product, builton a development platform, built on infrastructure, built on standards. Docker is building a stack to program the Internet
- 27. Isolation using Linuxkernel features namespaces pid mnt net uts ipc user cgroups memory cpu blkio devices
- 28.
- 29.
- 30.
- 31. 1. Get outof the way The best tools… 2. Adapt to you 3. Make the powerful simple
- 32. Docker for MacDocker for Windows
- 33.
- 34. ng the bestway to orchestrate Docke Docker 1.12: now with orchestration built-in.
- 35. Swarm mode Service API Cryptographicnode identity Built-in routing mesh Docker 1.12: now with orchestration built-in.
- 36. Using the beta?You already have 1.12 installed. > docker swarm init > docker service create
- 37.
- 38. Deep integration withnative load-balancers, templates, SSH keys, ACLs, scaling groups, firewall rules… beta.docker.com
- 39. Distributed Application Bundle www.docker.com/dab Aportable format for multi-container applications
- 40.
- 41.
- 42. Cloud Zone 1 CloudZone 2 Data Center Development Center Headquarters Containerization: standard containers on a standardized container engine Orchestration: build and deploy complex systems easily Enterprise: Enable delivery and time to value across a large, complex, rapidly evolving enterprise The Global Enterprise Supply Chain
- 43. BUILD Development Environments SHIP Registry: SecureContent & Collaboration RUN Control Plane: Deploy, Orchestrate, Manage, Scale Networking Volumes MonitoringLoggingConfig MgtCI/CD IT Operations Developers IT Operations Docker CaaS Workflow
- 44. Docker Containers asa Service platform 44 BUILD Developer Workflows SHIP Registry Services RUN Management Docker for Mac and Windows Docker Trusted Registry Docker Universal Control Plane Docker Cloud Docker Container Engine Ecosystem Plugins and Integrations
- 45.
- 46. Docker UCP 1.1- DTR 2.0 • HA • Unified Auth • Compose deployment • UI to add nodes
- 47. Security scanning inDocker Cloud
- 48.
- 49.
- 50. 2013-05 2013-06 2013-07 2013-08 2013-09 2013-10 2013-11 2013-12 2014-01 1,000,000 0 2014-02 2014-03 2014-04 2014-05 2014-06 2014-07 2014-08 2014-09 2014-10 2014-11 2014-12 2015-01 2015-02 2015-03 2015-04 2015-05 2015-06 2015-07 2015-08 2015-09 2015-10 2015-11 2015-12 2016-01 ~ 2016-09 1,000,000,000 ~ 10,000,000 9,000,000 8,000,000 7,000,000 6,000,000 5,000,000 4,000,000 3,000,000 2,000,000 6,000,000,000 5,750,000,000 5,500,000,000 5,250,000,000 5,000,000,000 4,750,000,000 4.500,000,000 4,250,000,000 4,000,000,000 3,750,000,000 3,500,000,000 3,250,000,000 3,000,000,000 2,750,000,000 2,500,000,000 2,250,000,000 2,000,000,000 1,750,000,000 1,500,000,000 1,250,000,000 Notary runC • containerd • HyperKit, VPNKit, DataKit • SwarmKit • libcontainer • libnetwork • • Docker 1.8 : Docker Content Trust • Docker for Mac Docker for Windows • Docker 1.12 with built-in orchestration • Docker 0.9 : Pluggable execution • Docker 1.7 : Multi-Host Networking • Docker 1.11: OCI support
- 51. Notary “Let’s stop usingcurl|sh” Trusted collections for any content Transport-agnostic Reliable updates, proof of origin, resistant to untrusted transport, survivable key compromise Build on industry-leading standards and research
- 52. RunC The universal containerruntime https://runc.io
- 53. containerd A daemon tocontrol runC built for performance and density http://containerd.tools/
- 54.
- 55.
- 56. Docker for Macarchitecture (simplified)
- 57. Hypervisor Framework vmnet Framework Docker ContainerEngine Hypervisor Linux VPN Data Service Interface Client Libraries Admin GUI CLI Security Sandbox Docker for Mac internals
- 58.
- 59. Hypervisor Framework vmnet Framework Docker ContainerEngine Hyperkit Linux VPNKit DataKit Client Libraries Admin GUI CLI Security Sandbox Improving Docker with unikernel tech
- 60.
- 61. Problem: Managing Docker ondifferent infrastructure is difficult and not portable.
- 62. Consistent User Experience 62 Howdo we handle updates to a cluster??
- 63. Docker for AWS EBSELB Container Engine Storage plugin Infrastructure Management Network plugin Orchestration IAM CloudFormation EC2VPC Admin interface Linux User Applications / Services
- 64. Docker for AWS EBSELB Container Engine Storage plugin InfraKit Network plugin Orchestration IAM CloudFormation EC2VPC Admin interface Linux User Applications / Services
- 65. InfraKit A toolkit forbuilding declarative, self-healing infrastructure.
- 66. Declarative • JSON configurationfor desired infrastructure state: • Specification of instances — vm image, instance type, etc. • Group properties — size, logical identifiers, etc. • Design patterns encourage • encapsulation • composition • Config is input to all operations — system figures out what to do 66
- 67. Self-healing • Composed ofa set of active components / processes that • monitor infrastructure state • detect state divergence • take actions • Continuous monitoring and reconciliation — always on • No downtime — rolling update 67
- 68. Toolkit • Primitives formanaging collections of resources • create, scale, destroy • rolling update • Abstractions & Developer SPI • Group - manages collection of resources • Instance - describes the physical resource • Flavor - extra semantics for handling instances • A collection of executable, active components — plugins • Initially, Go daemons in the toolkit • Soon, easy management via Docker Plugins (runc)
- 69.
- 70. Instance Plugin • Spec:specification / model of an instance (e.g. vagrant, EC2): • Logical ID, Init, Tags, and attachment • Platform-specific properties • Methods: • /Instance.Validate • /Instance.Provision • /Instance.Destroy • /Instance.DescribeInstances • Examples: instance plugins for EC2, Azure VM, Vagrant, … 70
- 71. Flavor Plugin • Givesmore context about the group members: • Size, or list of Logical ID’s (e.g. IP addresses for ‘pets’) • Application-specific notions of ‘health’ Is the node not only present but also joined a swarm? • Methods: • /Flavor.Validate • /Flavor.Prepare • /Flavor.Healthy • Examples: flavor for Zookeeper members, Docker swarm nodes 71
- 72. Group Plugin • Mainentry point for user interaction: • Create, describe update, update, destroy • Config JSON is always the input • Composed of Instance and Flavor — mix and match to manage cattle (fungible) or pets (special) • Methods: • /Group.Watch • /Group.Unwatch • /Group.Inspect 72 • /Group.DescribeUpdate • /Group.Update • /Group.StopUpdate • /Group.Destroy
- 73. Configuration Example config file(zk.conf): Group configuration = Instance + Flavor { "Properties": { /* raw configuration */ } } { "groups" : { "my_zookeeper_nodes" : { "Properties" : { "Instance" : { "Plugin": "instance-vagrant", "Properties": { "Box": "bento/ubuntu-16.04" } }, "Flavor" : { "Plugin": "flavor-zookeeper", "Properties": { "type": "member", "IPs": ["192.168.1.200", "192.168.1.201", "192.168.1.202"] } } } } } }
- 74. Operations • Make surethe plugins are running: • infrakit/group &; infrakit/zookeeper &; infrakit/vagrant &; • “Watch” the group starts management: • infrakit/cli group watch zk.conf • Update the config, e.g. change size or add IP address • Describe changes before committing — infrakit/cli group describe zk.conf • Begin update — infrakit/cli group update zk.conf 74
- 75. Today 75 • InfraKit isjust getting started… only primitives for working with groups like clusters of hosts • But we have big plans • Improve group management strategies • More resource types — networking, load balancers, storage… • A cohesive framework for active management of infrastructure — physical, virtual, or containers
- 76. Get Involved • Helpdefine and implement new and interesting plugins • Instance plugins for different infrastructure providers • Flavor plugins for systems like etcd or mysql clusters • Group controller plugins — metrics-driven auto scaling and more • Help define interfaces and implement new infrastructure resource types — load balancers, networks and storage volume provisioners 76
- 77. More Info • Github: https://github.com/docker/infrakit •A quick tutorial: https://github.com/docker/infrakit/blob/master/docs/tutorial.m d 77
- 78.
- 79.
Editor's Notes
- #44 Local development environments Self service app images Build, Test, Deploy applications Define app behavior and infra needs Registry services for image storage, management and distribution IT Ops maintains library of secure base content Manage role based access to repos/images Management consoles Provision, manage infrastructure resources Monitor, manage, scale infrastructure and applications
- #63 Docker for Mac is super easy to use. It self-updates. But how to do you do that for other platforms??
- #64 Infrastructure management holds an interesting position — it has to prepare the environment for the container engine.
- #65 Infrastructure management sets up the environment for the container engine. It then collaborates with it to service the user’s needs.
- #69 integration in the future as Docker Plugins (as runc containers) goes back to initial goal of simplifying user experience through a common Docker plugin install experience
- #70 InfraKit can be used set up to run with leader election (e.g. integrated with Docker swarm mode) to achieve high availability. Multiple plugin sets are running as hot standby but only one is active (the leader).
- #71 no method to update !!— opinionated immutable infrastructure
- #72 Prepare modifies the Spec for the instance. It can inject additional init scripts, tags. Healthy goes beyond just presence — is a node present AND part of a swarm?
- #73 No operations to create: watching nodes that don’t exist —> will create them … declarative state explain cases for using each. why explicit is better than implicit (use unwatch / destroy example)
- #74 Simple patterns Compose them into a large configuration. Group is made up of Instance and Flavor
- #75 Note the config is used for all inputs. The system figures out what needs to be done. Only signals to system to start managing Docker plugins in a future implementation