This document discusses Python and DevOps. It introduces Ahmed Bessifi and his work with Python, Flask, Puppet, Docker, and Jenkins. It then discusses what DevOps is for, including ensuring better application development, continuous integration and deployment, and monitoring. Docker and its concepts of images and containers are explained. DevOps uses cases like development environments, continuous integration, and continuous delivery are covered. Finally, it discusses using Docker for development environments, continuous integration with Jenkins for Python projects, and DevOps workflows.

1. Python & DevOps
@pyfest 2015
Python & DevOps
@pyfest 2015
Python & DevOps
@pyfest 2015

2. Ahmed Bessifi @github/abessifi
DevOps Engineer @IMDEV
- Python, Flask, Puppet, Docker, Jenkins
Open source
- Author : Pyatta, repmgr-puppet
- Contributor : LWP, RQ, PoWA
- Member : Debian, openVswitch, metaflask

3. And you ?

4. DevOps !

5. Mixed Martial DevOps

8. DevOps, what is it for ?
- Ensure better development of the application.
- Continuous integration and deployment.
- Ensure that the application is working as expected
(monitoring, high availability, etc).

9. DevOps, what is it ?

10. DevOps, how to do it ?

11. What's all the fuss about ?

12. Docker :
“... an open platform for developers and
sysadmins to build, ship and run distributed
applications.”
https://www.docker.com/whatisdocker

13. Docker : Concepts
Images
A read only collection of “layers” joined together
via a union File System.
Containers
An instance of an image on which one or more
processes are running or have exited.

14. Docker : Use cases
- Development environments
- Application deployment
- Continuous integration
- Continuous delivery
- Platform-as-a-Service (PaaS)

15. +

16. Development
Environments

17. Dev Env : Components
- OS
- System libraries
- Python dependencies
- Database, cache, etc

18. Dev Env : Problems
- Constantly change
- Never truly consistent
- Miscommunication (Ops vs Devs)

19. Dev Env : Docker !
- Just write a Dockerfile !
- Easy to change and share
- 100 % isolated
- Always consistent
- Production ready

20. Continuous Integration

21. Why we write tests ?!

22. Python testing libs/frameworks :
●
- Pytest, Nose : Unittesting library (less boilerplate).
- Mock : easily create fakes for testing.
- WebTest : req/resp testing for WSGI web apps.
- Selenium : browser automation (web).

23. Why using CI ?
“A CI system improves the productivity of a
development team by automating various
things.”

24. Jenkins for Python :
- Run builds (pytest, tox, etc).
- Perform pep8 and Pyflakes checks.
- Display xUnit, coverage reports.
- Generate and publish docs.
- Build python/deb package(s).

25. DevOps in action
“workflow”

27. Thank you !
'' We build software for people
who build software ''
<Codiak>
about.me/abessifi
github.com/abessifi