How we use Ansible to set things up in our CI environment

1. Ansible in our CI
Dharmit Shah
@dharm1t

2. Who am I?
➔Co-organizer of Ansible Ahmedabad & Docker Ahmedabad
➔Software Engineer @ Red Hat
➔Work on Ansible, CentOS, Docker, Vagrant, Jenkins, etc.
➔I ❤ automation

3. Continuous Integration
As said by Martin Fowler (ThoughtWorks):
➔Software development practice
➔Team members integrate their work frequently (~daily)
➔Verified by an automated build (including test)
➔Detect integration errors as quickly as possible
➔Leads to reduced integration problems

4. How do we use it?
➔Code commit to GitHub
➔Jenkins polls the repo
➔Build gets triggered if polling detects a change
➔Build process takes ~20 minutes (more on that later)
➔Docker image is pushed upon successful build

5. Tools involved
➔Jenkins (CentOS CI)
➔Vagrant
➔Ansible
➔CentOS
➔Docker

6. CentOS CI
➔CI infra for open source projects
➔Build your code on top of CentOS
➔200+ systems with awesome hardware configs!
➔Intel Xeon 2.5 GHz, 500 GiB SSD, 32 GiB RAM, ~200 Mbps
➔Physical box & root access

7. Ansible Roles
➔ansible, ansible-playbook and now Roles
➔Abstraction to organize playbooks
➔Imagine having multiple playbooks for different purposes
➔Recommended directory structure (aka Framework)

9. Walkthrough!
https://github.com/dharmit/adb-ci-ansible/tree/kontinuity/

10. Thank you!