Dockercon 2017 EU Recap

Editor's Notes

• #6: Talk about Docker Platform today.. It sits on the infrastructure which is below and application on the top.. Its Container Platform Its independent layer..You have developers and operators using the same interface and same workflow..from development to production great supply chain is available today
• #7: Principles: Docker should never lock you in anything.. Whatevr you choose in terms of application.. Number is 2 - Everything around Docker is built on Open Architecture, Open Modular in nature.. Swap components...Docker adapts to you.. Simplicity: Docker has to be simple.. Common misconception - We think More Complex something is , more powerful.. More Powerful system is More Simpler..
• #8: Lets talk about Under the Hood.. Docker Platform is like a stack with various layers.. First layer at the bottom is Containerd.. Container runtime.. where container magic happens.. containerd is an industry-standard core container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.. containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users. containerd includes a daemon exposing gRPC API over a local UNIX socket. The API is a low-level one designed for higher layers to wrap and extend. It also includes a barebone CLI (ctr) designed specifically for development and debugging purpose. It uses runC to run containers according to the OCI specification. The code can be found on GitHub, and here are the contribution guidelines. containerd is based on the Docker Engine’s core container runtime to benefit from its maturity and existing contributors. Thats where roots of Docker are.. You package up everything into magic containerd Over fewyears m, there has been lot of iteration on this layer.. Stable set of open standard..OCI.. OCI standard..industry standard...Containerd..Its running on 100,1000 of nodes By far widely adopted Container runtime..rock solid Some of largest technology company is all building it Developed by Consortium of large.. Foundation of Docker Platform Next, On top of containerd, is an orchestration layer Swarm => Orchestration ties your all individual machines together which runs container runtime. into a single distributed system.It allows you to deploy application not on one machine at a time but into a whole system. Makes your application distributed. To take advantage of these layers, as a developer you need tools, you need environment which can build, package your application taht takes advantage of your environment, we have CE edition - Docker for MAc, Windows..Familiar CLI, Familiar tools Now you want to go to prodcution...we provide set of management tools called Docker EE..familiar
• #9: As we develop Orchestration platform, we have really simple model for improvement. We follow various steps: We Listen. We Improve. We Repeat.. Swarm is docker inbuilt orchestrator..
• #10: This is how the stack look like... Two orchestrator at the same level.. The same 4 layers..two orchestrators ...integrated at the same level..same user experience.. We give you best of all.. Best Enterprise Service using Docker EE You get all Developer tool like widely adopted ones through Docker CE All running on industry standard runtime called containerd. and now you get 2 orchestrator integrated.. ITS NOT A FORK.. NOT A WRAPPER... Not a half integration This is real kubernetes sitting next to real swarm
• #11: We extended K8s with API extension so that it recognizes compose file and converts it on the fly to kubernetes native resources. We made a choice to use K8s functionality but we still like Docker tools Some has operational concerns.. From Developer to operator.. Developer expereicne in D4M and D4W Every Developer who gets D4w and D4W will also use Kubernetes
• #12: Reasons why Kubernetes - 1. Huge Community Support 2. K8s communitu has strong connections to Docker Community 3. K8s community came out within Docker community. 4. You will see that audience who attends K8s Meetup ..most of them do attend Docker Meetup too 5. Lot of same people...they go to same Meetup..use the same tool..we follow the same engineering principle..same language
• #13: So if you are developer and you are using Docker, the workflow look like this – You have D4M, D4W…Docker CLI Using Docker build, docker compose tie development loop If your production is in Swarm, then you can test locally on Swarm because there is already swarm built-in If your production is in Kubernetes, there is lot of work involved. Coz you need to translate files, compose, kubernetes ..you need to negotiate that sorts of tools Ofcourse its possible to do it but not smooth as how Swarm does that..
• #14: We are fixing it. Next version of Docker version, we have same tools..same versions, upstream K8s. You don’t have to learn any new tool.
• #15: My Compose file analyze it and converted it into pods Creating replicas sets Docker added stack command as the first class citizen to Kubernetes
• #16: The whole idea is not to mess up with the orchestrator. Both Swarm and K8s will not track usage of other Orchestrator. Resource contention issues One Orchestrator for production workload One API serves one and other Docker compose – use for either orchestrator Docker compose will be used for kubernetes… Its Stack deploy command Compose YAML or CL we are talking about.. We are still working on CLI… Docker stack deploy will be able to target kubernetes or docker swarm Based on definition inside Compose file, it will bring up K8s.. You can use overall K8s ecosystems.. Eseential full K8s API is exposed in the stack. Lot of time what that interface look like. Started with Docker EE.. Kube with Docker EE…we made it part of installation process.. Swarm Masters will also be K8s master.. Cluster Management => Swarm Cluster Orchestration => K8s Docker for Mac and Docker for Windows Why K8s is pretty greedy? For Dekstop 1 Infrakit and Hyperkit VM – its running on containers on top of that.. Optional feature.. Memory and CPU in fact.. If you are using already kube,
• #20: So Docker Inc. started interlocking with partners and enterprise customer and they found that there are number of traditional legacy application which has been there for past many years. Based on feedback from customer, Docker started a new programme called MTA POC Program. So the programme was for consulting partner. They do consultant for 5 days.. and stay for 25 days online. So programmme last for a month Where they send consultant to enterprise, COmprises Java and .NET they convert them to container and then start deploying to modern infrastructure We have Infarstrcuture Partners. Responsible for deploying Docker EE into their infra like HPE, Cisco..Microsoft for Azure Then we provide license of Docker EE in order to try that too..
• #21: One of feedback we got is Portability...On-premises...On Hybrid Agility - That has been adopted by many enterprises. 3rd Priority - Docker EE has many features which takes care of security TBD Innovation Challenge: Typically 80% of their budget is taken into maintenance while 20% is for Innovation.
• #22: One of the feedback we received from Enterprise is Portability ..where they want to run both on-premises as well as cloud environment
• #23: Second Priority is Agility. That has been priority from many enterprises
• #26: MTA POC Partners Accenture Cisco.. This PoC increase Portability Docker EE on-premises on Cloud.. Agility...2x faster Security...Aplications as you add more layers.. One attraction is we can reduce cost by 50%... Benefits of density of workload to run on this infra..
• #27: The way the modernization of journey works.. Start with existing app You dont need source code for it We give us some tools which converts it into Docker EE based container Then we can put this into Ci-CD system Once these are containerized, you can add business values in the form of new microservices ..starting to refactor monolithic application Different from other approaches: 6-months project to refactor monolithic.. With MTA programme..its much more contonous..you can add value to bit by bit..
• #29: Slide:1 Docker is building a complete platform for developers and operations team. Building microservices to build traditional application as well as deploy 3rd Party application. Typically you have CI-CD Infrastructure where you can benefit from Docker Content Trust and sustaining in Docker Trusted Registry. Then there is control planes For operation that enable to run containers in secure, on premises, on virtualization One of feedback we got is Portability...On-premises...On Hybrid Agility - That has been adopted by many enterprises. 3rd Priority - Docker EE has many features which takes care of security TBD Innovation Challenge: Typically 80% of their budget is taken into maintenance while 20% is for Innovation. So Docker Inc. started interlocking with partners and enterprise customer and they found that there are number of traditional legacy application which has been there for past many years. Based on feedback from customer, Docker started a new programme called MTA POC Program. So the programme was for consulting partner. They do consultant for 5 days.. and stay for 25 days online. So programmme last for a month Where they send consultant to enterprise, COmprises Java and .NET they convert them to container and then start deploying to modern infarstructure We have Infarstrcuture Partners. Responsible for deploying Docker EE into their infra like HPE, Cisco..Microsoft for Azure Then we provide license of Docker EE in order to try that too.. MTA POC Partners Accenture Cisco.. This PoC increase Portability Docker EE on-premises on Cloud.. Agility...2x faster Security...Aplications as you add more layers.. One attraction is we can reduce cost by 50%... Benefits of density of workload to run on this infra.. =================================== The way the modernization of journey works.. Start with existing app You dont need source code for it We give us some tools which converts it into Docker EE based container Then we can put this into Ci-CD system Once these are containerized, you can add business values in the form of new microservices ..starting to refactor monolithic application Different from other approaches: 6-months project to refactor monolithic.. With MTA programme..its much more contonous..you can add value to bit by bit.. ========================================== If there is anything new which comes additional to existing programme, how they are going to cope up with that.. 2 types of partners: - Whole programe last for months.. https://blog.docker.com/2017/10/modernizing-applications-poc-production-docker-enterprise-edition/ https://www.youtube.com/watch?v=yb0yNtHqTlg&t=331s Solomon Hykes: Slide: Docker Platform in a Nutshell Let me talk about Docker Platform today.. It sits on the infrastructure which is below and application on the top.. Its Container Platform Its independent layer..You have developers and operators using the same interface and same workflow..from development to production great supply chain is available today Principles: Docker should never lock you in anything.. Whatevr you choose in terms of application.. Number is 2 - Everything around Docker is built on Open Architecture, Open Modular in nature.. Swap components...Docker adapts to you.. Simplicity: Docker has to be simple.. Common misconception - We think More Complex something is , more powerful.. More Powerful system is More Simpler.. Lets talk about Under the Hood.. Docker Platform is like a stack with various layers.. First layer at the bottom is Containerd.. Container runtime.. where container magic happens.. Thats where roots of Docker are.. You package up everything into magic containerd Over fewyears m, there has been lot of iteration on this layer.. Stable set of open standard..OCI.. OCI standard..industry standard...Containerd..Its running on 100,1000 of nodes By far widely adopted Container runtime..rock solid Some of largest technology company is all building it Developed by Consortium of large.. Foundation of Docker Platform Next, On top of containerd, is an orchestration layer Swarm => Orchestration ties your all individual machines together which runs container runtime. into a single distributed system.It allows you to deploy application not on one machine at a time but into a whole system. Makes your application distributed. To take advantage of these layers, as a developer you need tools, you need environment which can build, package your application taht takes advantage of your environment, we have CE edition - Docker for MAc, Windows..Familiar CLI, Familiar tools Now you want to go to prodcution...we provide set of management tools called Docker EE..familiar As we develop taht platform, we have really simple model for improvement. We follow various steps: We Listen. We Improve. We Repeat.. In the process we saw areas where there has been talk.. Specificaly not every Swarm is docker inbuilt orchestrator..Docker want orchestrator seamlessly integrated.. To achieve that we built custom orchestrator.... We cant bring other orchestrator..same level of integration is difficult.you dont get seamless integration Different team uses different orchestrator...and now you have silos... That dilemna has been on mind.. THIS IS REALLY A BIG STEP.. In next version of Docker..we have Swarm and K8s out of box.. This is how the stack look like... Two orchestrator at the same level.. The same 4 layers..two orchestrators ...integrated at the same level..same user experience.. We give you best of all.. Best Enterprise Service using Docker EE You get all Developer tool like widely adopted ones through Docker CE All running on industry standard runtime called containerd. and now you get 2 orchestrator integrated.. ITS NOT A FORK.. NOT A WRAPPER... Not a half integration This is real kubernetes sitting next to real swarm 100% upstream...compliance Reasons why Kubernetes - 1. Huge Community Support 2. K8s communitu has strong connections to Docker Community 3. K8s community came out within Docker community. 4. You will see that audience who attends K8s Meetup ..most of them do attend Docker Meetup too 5. Lot of same people...they go to same Meetup..use the same tool..we follow the same engineering principle..same language