By day, Stefano does devops at yola.com. Architecting systems, fighting fires, and handling special projects. Responsible for a large chunk of the deployment system and related developer tools.
Elsewhere, he's a Debian Developer, mostly working on Python-related things, he maintains PyPy in Debian, and a handful of Python apps and libraries. Historically, also active in the Ubuntu world, as a Release Team member, core-dev & MOTU.
Accepted Talks:
How do we get work from a developer's laptop to a production server? How do we do this repeatedly? How do we avoid releasing bad patches? How do we get changes out as fast as possible? And what happens to requests during a deploy? If you want continuous deployment, you have to solve these problems.
How do you handle configuration, so that the same code can run in multiple environment? From a developers laptop, to QA environments, to production. What about the quirks of each machine in production?
This talk will look at the path Yola took, with Jenkins, yoconfigurator, yodeploy. It's by no means a complete solution, but it's good enough that I rarely find myself working on it, these days.
We will cover the pros and cons of each path one can take. The whole platform architecture is really affected by this. We can talk about: Bare hardware, virtualization, containerization, build systems, linux distributions packages, language package ecosystems, configuration management systems, notifications, secret distribution, and much more.
