 Hi and welcome to the PTL Design Series Interviews for the Newton Cycle. I'm Kenny Johnston from the OpenStack Innovation Center. I'm here with Jesse Petorius from the OpenStack Ansible Project. Jesse, could you introduce yourself and give a little bit of your background with OpenStack? Hi, I'm Jesse Petorius. I'm the project team lead for OpenStack Ansible Project in the OpenStack Newton Cycle. I work for Rackspace in the UK as a software developer and I've been working with OpenStack for around three years I think. Great. Can you tell us a little bit about OpenStack Ansible, what it does, who uses it? OpenStack Ansible was created to deploy OpenStack for production environments and targets make sure that builds are repeatable, highly available, and that deployers can build directly from source. It has a variety of consumers, Rackspace being one of the largest consumers, but there are some others who are reflected in our core contributor team. Awesome. Speaking of that kind of feedback between operators and core contributors, can you tell us a little bit about during your Newton planning in Austin, how you guys incorporated user and operator feedback into what you're planning on working on during the Newton cycle? So, most of our core contributors are actually operators. So, ahead of the summit, we actually chatted about what the needs were for the next cycle. Some of the big ones coming up were adding Ubuntu 16.04 support and also adding Ansible 2.1 support. And that was mainly just to provide the transition into the newer technology that's been available. We also held an open feedback session, which was broader for people who are just generally interested in the project or kind of following the way the project's developing. And we got some good feedback from people who tried to evaluate that around improving that part of the process as well. Very cool. Can you give us some insight into what the top three priorities for OpenStack Ansible are during the Newton cycle? So, while we did a heck of a lot of work in the last cycle to improve the documentation, it's turned out that the install guide is now a bit too much like a configuration reference guide. So, one of the big moves we're trying to make in this cycle is to keep the details but also provide a much simpler install flow for a new starter. So, that's one of the big things. The other two priorities are the new platform support for Ubuntu and the update of Ansible 2.0, version 2.1. Great. That's awesome. So, OpenStack as a whole across the projects have identified some core themes like scalability, resiliency, manageability, modularity, and interoperability. I'm wondering if you could speak to how the work that the OpenStack Ansible team is doing during the Newton cycle maps to those themes. So, being at a employment project, we've been working pretty hard to get the scalability, resiliency, and modularity into the project over the last, well, we've been working on this since Icehouse. So, the project code base is quite mature already in that respect. So, the focus for this cycle is much more around manageability in terms of the technology base. It's adding the extra technology support, improving the documentation, and as we do every cycle also including new service technologies into the integrated build that we provide. That's awesome. That's great to hear. So, looking into your crystal ball for the Okada cycle, what would you, what themes would you see carrying forward into that cycle and upcoming cycles? I think manageability is still going to be the biggest focus. Upgrades are a big busy problem within the OpenStack stable. For us, upgrades are okay, but they could be better. We have a fully managed upgrade already, but we'd like to do it a little differently. So, I think that's going to be a continued development process. We are also doing a little bit of work to get Red Hat platform support. That seems to be taking shape. If we don't finish it in this cycle, we hope to do it in the next. Awesome. That's really helpful. Well, thank you, Jesse, for taking the time to give us some insight into the Austin design discussions and meeting in Okada releases for OpenStack Ansible. And we'll talk to you again soon. Thank you.