Automated deployment with open source tools

1. AUTOMATED
DEPLOYMENT
with open-source tools
2017.03.12
Sardor Muminov

2. Who I am
● Backend software engineer
● IT systems engineer
● Open source enthusiast
● Python, Javascript and Rust (learning)
muminoff
muminoff

3. Software deployment is all of the activities that make a
software system available for use.
― Wikipedia

4. Manual deployments
● not consistent across environments
● slow, neither repeatable nor reliable
● require extensive documentation (often outdated)
● hinder collaboration (usually conducted by a few experts)

5. Why automated deployment?
● less error-prone and much more repeatable
● anyone in the team can deploy software
● engineers spend their time developing software
● deploying to somewhere new is not a headache
● you can release more frequently

6. Traditional workflow (FTP, SFTP, SCP)
FTP, SSH HTTP
Codebase
Local
Windows
macOS
Linux
Server
Directory
Web-server
Windows
macOS
Linux
Request
Browser
Mobile
API client

7. Traditional workflow (Git, SVN, Mercurial)
git push
Codebase
Local Server
Directory
Web-server
Request
Browser
Mobile
API client
HTTP
VCS
Repository
versions
git pull
Windows
macOS
Linux
Github
Gitlab
Self hosted
Windows
macOS
Linux

8. Automated workflow
VCS
commit
checkout
Build
Automation
poll for changes
www
Production
environment
Unit tests
test
Sandbox
environment
deploy
deploy
Developer

9. Open source automation tools
● Chef
● Puppet
● Salt
● Ansible
● Fabric

10. Chef
● Written in Ruby (client) / Erlang (server)
● Not-easy to learn and deploy
● Highly mature and works at massive scale
● Used by big companies
○ (e.g. Facebook, Microsoft, Bloomberg)

11. Puppet
● Written in Ruby
● Requires master (track infrastructure)
● Depends on agent
● Used by big companies
○ (e.g. RedHat, Microsoft)

12. Salt
● Written in Python
● Requires agent (minions)
● Depends on PyDSL and Python
● Used by big companies
○ (e.g. Pivotal, CloudFlare)

13. Ansible
● Written in Python
● Agent-less
● Supports any programming language
● Excellent security using SSH / SSH2
● Being used by companies:
○ NASA, Twitter, Attlasian
○ Evernote, RedHat, Cisco
○ EASports, GoPro, etc.

14. Fabric
● Written in Python
● Easy to learn, extend
● Programmatically integration
● Can be integrated with 3rd party tools

15. Summary
Benefits Manual deployment Automated deployment
Less time consumption ⚝ ◾
Less error prone ⚝ ◾
Repeatable ⚝ ◾
Collaboration ⚝ ◾

16. Continuous Delivery Vs. Continuous Deployment

17. Continuous Delivery Vs. Continuous Deployment

18. Example workflow (Ansible)
10.1.2.40
Ubuntu/xenial
10.1.2.41
CentOS/7
10.1.2.43
Debian/jessie
localhost
Docker
192.168.2.3
VMWare
Developer
Host
inventory
10.1.2.40
10.1.2.41
10.1.2.43
playbook

19. Example workflow (Ansible)
Developer
10.1.2.60
Server
deploy
$ git pull origin master
…
$ npm install
…
$ bower install
…
$ gulp run build
…
$ supervisorctl restart all
…
$ service nginx reload
…

20. Demo

21. References
1. https://en.wikipedia.org/wiki/Software_deployment
2. https://en.wikipedia.org/wiki/Software_release_life_cycle
3. https://en.wikipedia.org/wiki/Release_management
4. https://en.wikipedia.org/wiki/DevOps
5. https://en.wikipedia.org/wiki/Ansible_(software)
6. https://www.ansible.com
7. http://www.fabfile.org/

22. Thank you