A Talk at the 5th Ansible Meetup in Zurich on the 24th of August 2017 (http://meetu.ps/38f7DB) by Anton Ovchinnikov (MoneyPark AG)

1. Ansistrano
Ansible for application deployments
Anton Ovchinnikov
Ansible Zurich Meetup, 24.08.17

2. Who the hell
➔ Anton Ovchinnikov
➔ DevOps @
tonyo@fastmail.com
https://tonyo.info/
https://github.com/rev112
We’re hiring Python and frontend devs!

3. ● Provisioning
● Configuration Management
● Continuous Delivery
● ...
Why Ansible?

4. ● Provisioning
● Configuration Management
● Continuous Delivery
● ...
Why Ansible?
+ Deployment

5. Goals
➔ Automate deployment steps
➔ Minimize downtime
➔ Preserve consistent state during deploys
➔ Be able to rollback quickly

6. Database migrations?
BTW, what about...

7. Database migrations?
BTW, what about...
Let’s forget about them for now ;(

8. (~2006)
“A remote server automation and deployment
tool written in Ruby”

9. Ansistrano
=
+

10. Ansistrano
2 Ansible roles
➔ carlosbuenosvinos.ansistrano-deploy
https://github.com/ansistrano/deploy
➔ carlosbuenosvinos.ansistrano-rollback
https://github.com/ansistrano/rollback

11. Does anybody care?

12. Main ideas
1. Deploy to a new release directory
2. Run all the preparations
a. Install requirements
b. Build static assets
c. ...
3. Switch symlink to the new release

13. Main ideas: rollback
Rollback: switch the symlink back

14. Directory structure

15. Flexible hook approach

16. Example playbook: deploy
(From https://github.com/ansistrano/ansistrano.com)

17. Example playbook: rollback
(From https://github.com/ansistrano/ansistrano.com)

18. Features
● Deploy hooks
● Release cleanup
● Several code deployment strategies
○ git/svn/hg
○ rsync/scp
○ S3
● Shared files and directories

19. Things to keep in mind
● Check mode: not really
● Working directory is changed (surprise!)
uwsgi:
--hook-post-fork chdir:{{ project_dir }}
● Anonymous stats