Summary
Building and managing servers is a challenging task. Configuration management tools provide a framework for handling the various tasks involved, but many of them require learning a specific syntax and toolchain. PyInfra is a configuration management framework that embraces the familiarity of Pure Python, allowing you to build your own integrations easily and package it all up using the same tools that you rely on for your applications. In this episode Nick Barrett explains why he built it, how it is implemented, and the ways that you can start using it today. He also shares his vision for the future of the project and you can get involved. If you are tired of writing mountains of YAML to set up your servers then give PyInfra a try today.
Announcements
- Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
- When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With the launch of their managed Kubernetes platform it’s easy to get started with the next generation of deployment and scaling, powered by the battle tested Linode platform, including simple pricing, node balancers, 40Gbit networking, dedicated CPU and GPU instances, and worldwide data centers. Go to pythonpodcast.com/linode and get a $60 credit to try out a Kubernetes cluster of your own. And don’t forget to thank them for their continued support of this show!
- This portion of Podcast.__init__ is brought to you by Datadog. Do you have an app in production that is slower than you like? Is its performance all over the place (sometimes fast, sometimes slow)? Do you know why? With Datadog, you will. You can troubleshoot your app’s performance with Datadog’s end-to-end tracing and in one click correlate those Python traces with related logs and metrics. Use their detailed flame graphs to identify bottlenecks and latency in that app of yours. Start tracking the performance of your apps with a free trial at datadog.com/pythonpodcast. If you sign up for a trial and install the agent, Datadog will send you a free t-shirt.
- You listen to this show to learn and stay up to date with the ways that Python is being used, including the latest in machine learning and data analysis. For more opportunities to stay up to date, gain new skills, and learn from your peers there are a growing number of virtual events that you can attend from the comfort and safety of your home. Go to pythonpodcast.com/conferences to check out the upcoming events being offered by our partners and get registered today!
- Your host as usual is Tobias Macey and today I’m interviewing Nick Barrett about PyInfra, a pure Python framework for agentless configuration management
Interview
- Introductions
- How did you get introduced to Python?
- Can you start by describing what PyInfra is and its origin story?
- There are a number of options for configuration management of various levels of complexity and language options. What are the features of PyInfra that might lead someone to choose it over other systems?
- What do you see as the major pain points in dealing with infrastructure today?
- For someone who is using PyInfra to manage their servers, what is the workflow for building and testing deployments?
- How do you handle enforcement of idempotency in the operations being performed?
- Can you describe how PyInfra is implemented?
- How has its design or focus evolved since you first began working on it?
- What are some of the initial assumptions that you had at the outset which have been challenged or updated as it has grown?
- The library of available operations seems to have a good baseline for deploying and managing services. What is involved in extending or adding operations to PyInfra?
- With the focus of the project being on its use of pure Python and the easy integration of external libraries, how do you handle execution of python functions on remote hosts that requires external dependencies?
- What are some of the other options for interfacing with or extending PyInfra?
- What are some of the edge cases or points of confusion that users of PyInfra should be aware of?
- What has been the community response from developers who first encounter and trial PyInfra?
- What have you found to be the most interesting, unexpected, or challenging aspects of building and maintaining PyInfra?
- When is PyInfra the wrong choice for managing infrastructure?
- What do you have planned for the future of the project?
Keep In Touch
Picks
Links
- PyInfra
- Oxygem
- WordPress
- Lua
- Gary’s Mod
- Java
- Ansible
- SaltStack
- Chef
- Puppet
- EC2
- Boto 3
- Hashicorp Vault
- Vagrant
- Docker
- Testinfra
- Dockerfile
- Idempotence
- Nginx
- POSIX
- gevent
- Jinja2
- Click
- Zero Tier
- BSD
- AST Module
- RedBaron
The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA