DockerCon SF 2015: Enabling Microservices @Orbitz
13 likes6,018 views
The presentation discusses transitioning from a monolithic architecture to microservices at Orbitz, emphasizing the use of Docker and automated deployment pipelines for over 500 applications. It details the continuous delivery process, including testing, deployment, and health checks, while also highlighting the tools used such as Jenkins and Ansible. The key takeaway is the importance of creating a flexible and automated deployment platform that reduces human intervention in the release process.
DockerCon SF 2015: Enabling Microservices @Orbitz
- 1. Enabling Microservices @Orbitz Steve Hoffman @bacoboy Rick Fast @tortiepoint Senior Principal Engineers
- 5. Agenda • Brief Architecture Overview/History • From Monolithic to Services to Microservices with Docker • Automated Pipelines • Questions
- 7. #dockercon 2000 Yes, we are STILL hiring! @OrbitzTalent
- 10. #dockercon 2000
- 16. #dockercon 2004
- 18. #dockercon 2012 • Multiple Brands • Websites • Webservices • Multiple Backends • 500+ apps / thousands of instances • Deployments Daily (sometimes more) 2015
- 20. #dockercon Different Provisioning Tools DEV OPS Application Platform!=
- 21. #dockercon A New Experiment • Microservices? • Decompose single “service” into the actual 40+ sub-services - Any change to sub-service was a deployment of many • Could it be a simple Spring Boot App in Docker (12 factor?) • Backward compatible with existing service infrastructure. • Code to Production w/o help from other Humans
- 22. #dockercon The Docker Slave aka “The Rickbot” App App App
- 26. #dockercon
- 27. #dockercon
- 37. A Little More Background
- 38. #dockercon
- 40. #dockercon Editorial Module • A Continuously Deployed Microservice • www.orbitz.com - (scroll down)
- 42. #dockercon Orbitz Content Orchestration Service Content (Solr) Editorial Module Search Module Hotel Module Hotel Team Search Team Content Team
- 45. #dockercon Pre-Continuous Delivery 1.2-BETA-20150401-113002 Test Discard Test Discard 1.2-BETA-20150402-093002 Build Build And so on…
- 46. #dockercon Pre-Continuous Delivery 1.2-BETA-20150401-113002 Test Discard Test Discard 1.2-BETA-20150402-093002 Build Build Test Deploy 1.2 Build
- 47. Continuous Delivery with Jenkins, Docker, and Ansible (And then Marathon)
- 48. #dockercon Yo rfast-mbp:git rfast$ yo microservice _-----_ | | .--------------------------. |--(o)--| | Welcome to the kickass | `---------´ | Microservice | ( _´U`_ ) | generator! | /___A___ '--------------------------' | ~ | __'.___.'__ ´ ` |° ´ Y ` ? Enter the name of your service. (E.G. "my-service")
- 53. Jenkins Pipeline
- 55. #dockercon Pipeline (Simplified) build unit test publish deploy dev acceptance tests deploy qa deploy staging open RFC deploy prod close RFC
- 57. #dockercon Build if(…) { x ++; } 1.2 Merge 1.2. editorial-module.jar ./gradlew build {BUILD_NUMBER}
- 59. #dockercon Build 1.2 Merge editorial-module.jar FROM orbitz/java-8 ADD build/editorial-module.jar /opt/orbitz CWD /opt/orbitz CMD java -jar editorial-module.jar if(…) { x ++; } 171.2.
- 60. #dockercon Build 1.2 Merge editorial-module.jar orbitz/editorial-module:1.2.17 if(…) { x ++; } 171.2.
- 62. #dockercon Deploy - hosts: dev - tasks: - name: find previous images docker_facts: image=orbitz/{{application}} register: previous - name: deploy new image docker: image=orbitz/{{application}}:{{version}} … - name: wait for service wait_for: port={{port}} … - name: check health endpoint uri: url="http://{{fqdn}}:{{port}}/health" … - name: kill old image docker: {{previous}} git pull playbook.yml (abridged)
- 63. #dockercon host-001 host-002 host-003 host-004 host-005 - hosts: dev
- 73. #dockercon How to handle failure?
- 74. #dockercon What happens when a VM is moved?
- 75. #dockercon What if I need to add capacity?
- 76. #dockercon Deploy (Second Attempt) - hosts: dev - tasks: - name: find previous images docker_facts: image=orbitz/{{application}} register: previous - name: deploy new image docker: image=orbitz/{{application}}:{{version}} … - name: wait for service wait_for: port={{port}} … - name: check health endpoint uri: url="http://{{fqdn}}:{{port}}/health" … - name: kill old image docker: {{previous}} git pull playbook.yml (abridged)
- 77. #dockercon Deploy (Second Attempt) - hosts: dev - tasks: - name: find previous images docker_facts: image=orbitz/{{application}} register: previous - name: deploy new image docker: image=orbitz/{{application}}:{{version}} … - name: wait for service wait_for: port={{port}} … - name: check health endpoint uri: url="http://{{fqdn}}:{{port}}/health" … - name: kill old image git pull playbook.yml (abridged) - hosts: localhost - tasks: - name: marathon deploy marathon: image=orbitz/{{application}}:{{version}} instances=3
- 78. #dockercon Deploy (Second Attempt) New host setup
- 79. #dockercon Deploy (Second Attempt) Mesos Agent New host setup 1.2.16
- 80. #dockercon Deploy (Second Attempt) - tasks: marathon: … playbook.yml 1.2.16 1.2.16 1.2.16
- 81. #dockercon Deploy (Second Attempt) - tasks: marathon: … 1.2.16 1.2.16 1.2.16
- 82. #dockercon Deploy (Second Attempt) - tasks: marathon: … PUT /apps/editorial-module { “image”: “orbitz/editorial-module:1.2.17” … } 1.2.16 1.2.16 1.2.16
- 83. #dockercon Deploy (Second Attempt) PUT /apps/editorial-module { “image”: “orbitz/editorial-module:1.2.17” … } - tasks: marathon: … 1.2.16 1.2.16 1.2.16 app = GET /v2/apps/editorial-module if not app then deploy_id = POST /v2/apps { “image”: “orbitz/editorial-module:1.2.17”, “id”: “editorial-module” } else deploy_id = PUT /v2/apps/editorial-module { “image”: “orbitz/editorial-module:1.2.17” } end if while GET /v2/deployments contains deploy_id // still deploying end // deploy complete
- 84. #dockercon Deploy (Second Attempt) - tasks: marathon: … PUT /apps/editorial-module { “image”: “orbitz/editorial-module:1.2.17” … } 1.2.16 1.2.16 1.2.16
- 85. #dockercon Deploy (Second Attempt) - tasks: marathon: … 1.2.16 1.2.16 1.2.16
- 86. #dockercon Deploy (Second Attempt) - tasks: marathon: … 1.2.16 1.2.16 1.2.16 1.2.17 1.2.17 1.2.17
- 87. #dockercon Deploy (Second Attempt) - tasks: marathon: … /health 1.2.16 1.2.16 1.2.16 1.2.17 1.2.17 1.2.17
- 88. #dockercon Deploy (Second Attempt) - tasks: marathon: … /health 200 OK 200 OK 200 OK 1.2.16 1.2.16 1.2.16 1.2.17 1.2.17 1.2.17
- 89. #dockercon - tasks: marathon: … 1.2.17 1.2.17 1.2.17
- 90. #dockercon And off to the next environment… 1.2.17 1.2.17 1.2.17
- 102. #dockercon What’s inside the containers? • Spring Boot • Dropwizard Metrics (formerly Coda Hale, Yammer) • Consul Registration/Discovery • Logstash + Logback • Swagger • Hystrix • Retrofit + Consul OrbitzWorldwide/consul-client
- 103. #dockercon –You “Why didn’t you use {{.x}}?”
- 104. #dockercon Keeping an eye on… Kubernetes Amazon Elastic Container Service Docker Swarm
- 105. #dockercon Summary • Create a shared platform for docker deployments using shared and app-specific “localhost” helpers — this was ours, yours SHOULD look different — adapt to change, don’t fight it. • Take people out of the release process - Docker - repeatable applications - Chef - repeatable infrastructure — Environment aware - Jenkins - repeatable releases • Delineate configuration concerns: - Known at Compile time — Bake into Docker image - Known at Boot time — Bake into Playbook/Launcher - parameter to Docker run - Changes Anytime — Externalize (consul K/V, etcd, zookeeper)