Continuous integration with Docker and Ansible

Transcript

1. Continuous integration with Docker and Ansible Dmitriy Slupytskyi
2. About project • 70+ repositories • 10+ microservices • 4+ technologies (golang, php, ruby, nodejs) • 65 build and deploy scripts
3. Docker Virtual Machines Containers
4. Why Docker? • Easily to manager containers • Build specify environment for project • Isolated workspace • Package it and be portable • Replicable - lower barrier to entry for new environments, teams • No “dependence hell”
5. Deployment process Start Clone Build Push Deploy Test
6. Jenkins CloudBees Docker Build and Publish plugin
7. Build • Use Dockerfile • Keep layers to minimum • Use tags for version control • Use .dockerignore
 (the same syntax as .gitignore) • One container per service • Manage output • GNU Make is optional Just for presentation, 
 make better one
 for your services
8. Build
9. Test
10. Private Docker registry • Version 0.9.1 (version 2 required docker version 1.6.0 and higher) • Nginx + LDAP authentication
 (https://hub.docker.com/r/h3nrik/nginx-ldap/) • Dockerized
11. Ansible • Inventory • Playbooks • Tasks • Modules
12. • docker-py (<=1.1.0) • docker module
 (http://docs.ansible.com/ansible/docker_module.html) • docker-compose
13. docker-compose
 https://docs.docker.com/compose/
15. Deploy
16. Jenkins + Ansible plugin
17. Logspout
 (https://hub.docker.com/r/gliderlabs/logspout/)
18. Papertrail
20. Profit • easily to update and maintenance images • Dockerfile • portability • isolated • logspout
21. • docker registry timeout • ansible freezes • time to build
22. Developers
23. Pros • Logs • Build specify environment for target service • Service management (start, stop, restart) • Manage environment variables (one container for few environments)
24. Cons • SSH • Time to build (can be depends on various factor, for example docker cache) • Jenkins plugin exit with 0, even if fails, that bring up misunderstanding • Unmounted volumes