 Hey, I'm Mike Perez. I'm the development coordinator for the OpenStack Foundation, basically leading a variety of different cross-project initiatives within the OpenStack project itself. Great. Thank you for being here today. So can you expand a little bit more on what your role means from a cross-project coordination perspective? Yeah, specifically. So we have Ptls that are focused on a particular project, Sender, Nova, Neutron, and so on. My sort of view is all the projects. So I take feedback that comes from, you know, such working groups like Product Working Group, which are actual user feedback and taking that information to, you know, identify, okay, that particular thing makes sense in these projects and then trying to keep the communication going between those projects and helping them to achieve that. Otherwise, certain initiatives, like, it may only end up in, like, two projects, but it makes sense to be a cross-project, so we can't exactly advertise it as a feature then. Great. So how has the community addressed cross-project requirements so far? Yeah, so I would say it's something we're definitely working on for sure. And I think that's kind of why I'm switching sort of my initiative and why the OpenStack Foundation is having me help. And dedicate my time to that. So in particular, like, right now we have, you could take things like such as having multi-ten, or, sorry, hierarchy tenants inside of OpenStack. Right now there's only Sender that I'm aware of that actually implements this feature that Keystone has provided us. It would make sense for us to say to our users, hey, that feature to have projects within projects, to have that in Nova and Neutron and so on. So then it's not just, like, okay, a matrix of, like, Sender supports us and that's it. And so what changes are being made to help with this type of cross-project communication? Yeah, so right now I have been attending a variety of different design summit sessions and there are so many cross-project sessions that end up being double-booked, so I try to pick a handful of them. So in particular right now we have, you know, there's where Sender actually led in sort of the third-party CI and having that across all different vendors. So there's about 72 different vendors that we actually support behind this third-party CI. It's a great way in the project for us to actually have confidence in the quality of the drivers that we put out in a release and we recommend to our operators to use, which then ends up being a great experience for the users. We want to make that not just within Sender, but also across other projects. So one of the great things that came from this particular design summit is we have consensus across the vendors in Ironic. So bare metal vendors are all on board with working with us on supporting this idea. And, you know, there's other projects like Neutron where we want to bring this idea as well. It's been a thing that has been tried in the past and I think putting somebody like myself that is the dedicated resource to go ahead and help with that initiative, I think it's going to be great. Especially not coming, focusing on any particular feature in that project itself. And I would say, lastly, distributed lock management is a big thing. So a lot of projects itself have to support the ideas of HA or highly availability. And the idea is, for example, you want to have multiple open stack services to support whatever the thing is. So you take Sender, for example, you want multiple Sender services to talk the same back in storage. And if one of those services goes down, then you can't access your back in storage anymore to be able to create new volumes. So to have multiple of those. Problem is, there's issues with state and trying to keep state across all of those different services and making sure that they don't clobber each other and doing the same actions. So, but it's not just Sender that has that problem. It's also like projects like Heat and Ironic that also want this as well. So within the design summit session for Mitaka, we actually came to consensus on a solution so that we could bring that across. So it's not projects going off and doing their own thing. And then we make the operators lives a little scary because then they have to support Zookeeper and SED and console all these different kind of solutions. So coming to consensus has been a huge win. And so I think it's going to be a great experience going up back to the operators. Great. Well, congratulations on joining the OpenStack Foundation. And thank you for coming on Subruzor TV today. Yeah. Thank you.