 Hi, I'm Shamal Bayer with the Mitaka design series and with me today is Armando. Armando, can you please tell us a little bit about yourself? Hi there, thanks for having me. Yes, so I am Armando Mighiaccio. I am the project technical lead for the Neutron project in OpenStack for the Mitaka leads and I work for a Hulet Partner Enterprise and I'm based in Palo Alto. So I've been involved in OpenStack for quite a while, almost since the beginning and I've seen this project grow tremendously over the past five years. I started with Nova and doing hybrid by the work and then moved to Neutron later on where I've been focused since early 2013. I started as a core developer to grow into my involvement more and more, eventually culminating in getting the PPL for the project. Great. And now that it's been about a week since the design from Nintocchio, could you discuss what were some of the hot topics your team talked about and what decisions were reached in Tokyo? Sure. So in Tokyo, I think we had a very productive summit. Sometimes it's difficult to like spread the real balance between, you know, one is to be thought of and one, you know, would like to achieve. Time is always a constraint. We've over many areas. We talked about cutting edge technologies and topics like network function penetration as well as container networking support. And we also talked about advanced services by far away load balancers and without, you know, telling in too many details. We, you know, we, we, we started laying down the plan for Mitaka and how these, these features can, you know, can proceed and they've started, you know, off a while back. But yet, you know, yet more needs to be done. However, at the same time, no new feature is really useful if we don't, if you don't pay attention to, you know, to the stability and the performance of the current platform and the services, the core services that the platform must provide. And that requires a certain amount of, you know, housekeeping and certain amount of rigor and discipline in making sure that, you know, the platform is stable and reliable, it's performance and so on. And we talked about that quite a bit too. Got it. So that's a good segue, you know, performance reliability. What other user needs or problems came up in the design permit in Mitaka? Yes. Yes. Neutron has all other projects, you know, they have, we have many stakeholders. We have operators to think about, we have end users, we have developers too. But other than that, projects are also important. And, you know, cross-project interaction is also important. I'm thinking about projects like Noval Rhydonic, for instance. And all these, like stakeholders, persona or like entities, if you will, all they have different needs and striking a group balance so that you can prioritize these needs within the span of a single-recycle, which is also six months long. It's a really challenging effort. And in Mitaka, we like to make sure that we make progress on better operability and just the ability of the platform without compromising, you know, on richer capabilities too much. So, again, most of our efforts goes into improving operability and usability. And that's what users, you know, and stakeholders have been asking for. Got it. And I know there's going to be a tremendous amount of work being done in Mitaka, but if I was to ask, what would you say are top three priorities in terms of new features or enhancements to existing features that we can expect in Mitaka? Yeah. As I mentioned earlier, you know, NFV, Networking for Container Rangers are in the minds of many. And, you know, we've made quite a bit of progress over the past two or three years to enable these efforts to proceed. And more has to be done in order to better integrate with the core of the platform. Also, better protocol support, like IPv6 and, you know, BGP, so layer three is also important. You know, we're looking into those. While the, you know, the latter are more relevant to the core of the platform, like IPv6 and BGP being like somewhat native services of neutron, the former, you know, can evolve more autonomously. NFV and, you know, and container networking is something that's really been bootstrapped since the Liberty sample. And we've done so by, you know, by going down the path of allowing these efforts to innovate independently with the introduction, introduction of what we've all done, just from stadium. And this is because the concept helps us keeping the core of the platform focused. But yet, and we can enable smaller groups of folks to collaborate without, you know, being bottlenecked too much. And, you know, that seems to be working so far. Great. And the product work group has recently started using themes to kind of help users connect dots in terms of, you know, the direction of a project. So in terms of themes such as resiliency, scalability, manageability, modularity, or interoperability, what are some of the key, what's the key theme or themes that neutron will be pursuing in the process? So yeah, when we look at themes, and we think about, you know, scalability, since Juneau, this thing with the version of running was a key feature that was introduced by the platform. And now users are starting to get their hands on it. And that, you know, obviously finding finding issues that we're working hard to address all of them being, you know, being reports from the field. Residency is also another aspect that we, you know, we look at it very carefully. You know, neutron is all about data playing and making sure that, you know, users' workloads are connected without, you know, without disruption. And we also tend to pay attention to those by, to this aspect. Because again, there is no point in having workload if you can't reach it. As far as manageability is concerned, since last cycle, we implemented, you know, online database upgrades. And this is, you know, a stepping stone for enabling upgrades for minimal downtime. So that is a great help for operators to provide minimum disruption to their users. As far as modularity goes, this is yet another thing. As I mentioned earlier, we started off the journey of the neutron stadium since Kilo, the Kilo cycle. And this enabled us to develop software modules that can interact with one another in a more loosely coupled fashion. So I guess this is, you know, the very exact definition of modularity. And some of these modules interact with the core platform. And more needs to be done for the core platform to provide the services to integrate, you know, these various elements better, so that the end-to-end neutron system, you know, field operates like one. So again, yes needs to be done, but I think we're in a very good way after it is. And yeah, I mean, obviously, more can be done. And as soon as, you know, more things and more aspects drop on our radar, you know, we'll go and, you know, we'll be able to try to prioritize and take care of as many aspects as software development as we can. Awesome. Well, before we wrap up, is there anything else that you'd like to add that we can fully add? Well, developing new features to mix and looking into bleeding edge. It's an important aspect of any open source project that needs to be and stay on the forefront. But I strongly believe that that can only come without compromising, you know, what we built so far. There's really no point in presenting shiny new features if we have much more fundamental issues internally. And open stack and neutron in particular, it's all about the, it's all been about growth, right? And right now, we've got to perhaps change the image sure that there is a better balance between, you know, enabling new use cases, making sure that we can embrace more and more features. But at the same time, again, housekeeping and stability and reliability will need to also be given a serious thought. So I'd like to switch here and make sure that we have a better balance. Because again, you can only grow so much without imploding under your own weight. And obviously, any project is at risk of that. And again, it's a difficult bond to strike. And I hope we'll, you know, we'll think harder, we'll try to make sure that we, you know, we manage to, you know, appeal any, you know, any user that's out there. But at the same time, we don't support ones that we already built. Thank you so much, Armando. Amanda, you look forward to great things from Neutron and the Neutron Staying Project in Atlanta. Thank you.