1 year with Docker
Download as PPTX, PDF1 like1,072 views
This document summarizes John Fiedler's presentation on his company's one year experience using Docker in production. It outlines their timeline of Docker use cases from 2013-2014 including for development environments, continuous deployment, and zero downtime deployments. It describes where they do and do not use Docker for persistent storage, middleware, tools/scripts/jobs, and web/monitoring/logging applications. It also details the operational standards they use like updating, monitoring, logging and security. Finally, it notes issues they encountered with device mapper, private registries, security concerns, and container types.
1 year with Docker
- 1. Title of slide to go here Now in production for 1 year by John Fiedler @johnfiedler
- 2. Agenda ● Timeline - Use Cases of Docker ● Where we do/don’t deploy docker in production ● Operational standards we use ● Things we’ve run into
- 3. Timeline of Use Cases over the year 2013 2014 2014 2014Q3-Q4Q4 Q1 Q2 Dev Environment Continuous Deployment in Teamcity Web Zero Downtime Deployments Full Stack Container Azkaban DockerMe Craft CMS Main Website Beanstalk Why Docker, Why Not Chef? Integrations Batch Jobs Mesos DockerCon 2014 Dev/ Ops CLI
- 4. Where we use / don’t use Docker Persistent Storage Middleware / Integrations / Internal Tools / Scripts / Jobs / Batch Process Web Monitoring Logging Security Dev Environment Ops Environment CI / CD Fully Somewhat No Create Deploy Run Operate Dockerized
- 5. Where we use / don’t use Docker Dev Environment Ops Environment Create ● Vagrant ● Shell Scripts ● Cassandra ● Redis ● Elasticsearch ● Kafka ● Chef Zero ● Knife ● git / repo ● Berkshelf ● AWS CLI’s ● Fabric ● MongoDB ● FoundationDB ● Voldemort ● Statsd ● Test Kitchen ● Scripts ● Spiceweasel ● More (coming soon) Fully Somewhat NoDockerized
- 6. Where we use / don’t use Docker CI / CD Fully Somewhat No Deploy Dockerized ● Teamcity Server ● Agents (used to be) now autoscaling cloud agents ● Docker Private Registry (Replaced Quay.io) ● Production Web code ○ Java ● Corp Web code ○ PHP ● Integrations ○ Python ● Dockerme branch web servers ○ Java ● Internal tools ○ Ruby/Python
- 7. Where we use / don’t use Docker Web Fully Somewhat No Run Dockerized webapp:v1 webapp:v2 hipache redis Ubuntu deployed with Chef deploy_if_new.sh
- 8. Where we use / don’t use Docker Middleware / Integrations / Internal Tools / Scripts / Jobs / Batch Process Fully Somewhat No Run Dockerized ● Cron Scheduling ● Health Checks ● Port / Server Discovery ● Grid computing ● Microservices ● SOA ● Lots of innovation needed ○ Where is vSphere for Docker?
- 9. Where we use / don’t use Docker Persistent Storage Fully Somewhat No Run Dockerized ● We don’t use Docker here ● Weird ownership issues ● Using more DB as a service ● Flocker is interesting ● Swarm/Mesos/CoreOS/Kubernet es/EC2 Container Service ● 2015 this will be solved
- 10. Operational Standards Update Monitoring Logging Security Fully Somewhat No Operate Dockerized ● All Containers log to the Host ● Host logs get picked up by Sumo ● Beanstalk logs to S3 > Sumo ● Chef deploys log rotate ● App Metrics (statsd) ● Service Metrics (datadog) ● Host Metrics (datadog) ● Docker Metrics (datadog) ● shell scripts (web deploy) ● Teamcity (beanstalk) ● Chef’s Docker cookbook ● Mesos deploy Update / Deploy / Orchestration Monitoring Logging Security ● Low container to host ratio ● Teamcity/Mesos deploys continous updates ● Scanlogd container
- 11. Issues we’ve found DEVICE MAPPER!!!! Registry ● Private registry issues ○ Quay.io ■ Private (everything from CI/CD) ■ DockerHub (Open sourced) Security ● Containers have an OS.. (shellshock,GHOST) ○ libs, OS, bugs, vulnerabilities, still exist ● Root ● Mesos/Authentication ● Keys... Container types ● Light weight stuff is great ○ Ops scripts ● Full stack is hard to migrate off ○ Azkaban