Lesson Learned from Using Docker Swarm at Pronto
10 likes1,152 views
This document discusses Docker Swarm and microservices at Pronto, including how they have set up Docker Swarm, their continuous integration and deployment processes, lessons learned, and future plans. Their build pipeline involves separate pipelines for each service that includes checks, static analysis, unit tests, building, pushing to a registry, and deploying. They use Docker images versioning and tagging for continuous delivery and rolling updates. Monitoring, log centralization, improved versioning, and more integration tests are planned.
Lesson Learned from Using Docker Swarm at Pronto
- 1. USING DOCKER SWARM AT PRONTO L E S S O N L E A R N E D F R O M www.prontotools.io K A N O U I V I R A C H
- 2. K A N O U I V I R A C H A B O U T M E Research & Development Engineer
- 3. D O C K E R S WA R M
- 6. M I C R O S E R V I C E S https://www.nginx.com/blog/introduction-to-microservices/
- 7. . . H O W W E ’ V E S E T U P. .
- 9. docker swarm init docker network create -d overlay --subnet=192.168.0.0/24 simplesat
- 10. docker service create --name survey --network simplesat survey:stable docker service update --image survey:live survey
- 11. docker swarm join --token SWMTKN-1-0nqrebfaz7qc6deimizh4tfqa vfq5pam1qt08alxots8w5x9fv-8ii4ina9 fm640am99z1tbpfvl 192.168.65.2:2377 docker swarm join-token manager To add a worker to swarm To add a manager to swarm
- 12. O U R B U I L D P I P E L I N E L O O K S L I K E
- 13. Check-In BUILD PIPELINE FOR SERVICE 1 BUILD PIPELINE FOR SERVICE 2 BUILD PIPELINE FOR SERVICE 3 BUILD PIPELINE FOR SERVICE 4
- 15. C O N T I N U O U S I N T E G R AT I O N P R O C E S S
- 16. Check - In Static Analysis Unit Tests Build & Push Push Deploy Production Pull Deploy Dev Pull
- 17. – I N S P I R E D B Y Y E L P Docker Images Versioning for Continuous Delivery
- 18. docker build -t ${package}:${GIT_COMMIT} docker tag ${package}:${GIT_COMMIT} ${package}:unstable During the first docker build
- 19. docker tag ${package}:${GIT_COMMIT} ${package}:stable docker push ${package}:${GIT_COMMIT} docker push ${package}:stable After the tests pass
- 20. docker tag ${package}:${GIT_COMMIT} ${package}:live docker push ${package}:live After deployment succeeds
- 21. . . W H AT W E ’ V E L E A R N E D . . http://bocabraincenter.com/conditions/learning-disabilities/
- 22. Follow the practices • One process per one container • Use an appropriate base image (official base image)
- 23. S E R V I C E N A M E I N T H E C O D E ! SURVEY_API_URL = 'http://survey:8000/api/'
- 24. R O L L I N G U P D AT E S F… C O O L F E AT U R E ! I S Effortless with Blue-Green Deployment
- 25. – E A S Y T O M A I N TA I N Keep services in one single repository
- 26. Environment variables – ALLOW US TO HAVE SAME IMAGE ON ALL KINDS OF SERVERS
- 27. D O C K E R S WA R M couldn’t automatically pull images from private registry when update a service
- 28. --with-registry-auth Ex. docker service update --with-registry-auth --image simplesat-gateway:cc01ef0c gateway
- 29. (A bit) complex command
- 30. . . W H AT W E P L A N . . https://unsplash.com/photos/CkH1Hh8kllA
- 31. Monitoring
- 35. Questions?