 Hi Mike, thank you for coming on SupervisorTV. Can you please tell us a little bit about yourself? Yeah, so I've been working on the Cinder project for some time. Some people know that for me. I'm also thinking on IRC. So, you know, I was former P.T.L. for the Cinder project in Liberty and the Keele release. And then right now I'm focusing on cross-project efforts and forming a team around that. And I have also recently joined the T.C., the technical committee. Great. So when you say you're working on cross-projects, can you please tell us a little bit more about what that means? Yeah, so really common thing and people kind of think like, oh, like you merged the projects together or something like that. And it's more like, you know, there are projects that are affected by certain issues inside of certain issues or certain features that they can benefit from. And the problem is that in typical cases when OpenSec was originally formed, we sort of did this whole silo thing where projects would go off into their own solution and eventually people would come up with, you know, coming sort of to the same path but in the end for the users and the operators that are ultimately going to consume whatever sort of features, they would end up with a completely different interface across project. Quotas is a good example of that right now. I myself, as being, you know, part of this project since, you know, for a while, every single time that I have to change quotas for between Cinder and Nova, I always have to look at the help usage every time. Yep. So to enable this type of collaboration in the community, what changes are being made to processes to help foster cross-project collaboration? Yeah. So originally, right, so cross-project team originally I think was like, you know, maybe at the most like maybe five people that would show up to this meeting and that, you know, maybe had an interest in it for different reasons or whatnot. But, you know, like when you look at OpenSec today, right, with the BigTent, like we have 50 plus projects at this point, right? And so getting collaboration across all those projects, five people that is not representing all of those teams, right? So in order to, you know, actually make progress in that area, we need like real people that are coming from those projects that understand those projects and understand how they work and then as well as, you know, having an interest in this sort of cross-project problem. And whether or not, you know, whatever the initiative is that is affecting the projects, the fact that they can actually know somebody in their project that can, you know, bring knowledge to that issue and actually bring a representative. So right now we have now a team of, you know, representing all these BigTent projects and they, you know, we come together and we come together only when, you know, there's an affected issue for, you know, the set of cross-pro, we call them cross-project spec-lasons, right? And so these people will come together and we review a specification that affects them and they come into agreement and once that is agreed upon across the team, it could then, that solution, whatever it may be, can be rolled out. So an example of going back to the quotas issue, right? We can, you know, we can, for example, come up with the interface of what that should look like and then once we have an agreement across that, you know, that ultimately will end up being beneficial for the end user with a consistent interface between RESTful interfaces as well as clients. Makes sense. So it sounds like, you know, there's a tremendous amount of growth in the level of participation and activity for these types of cross-project conditions overall, which is awesome. So besides quotas, what are some of the other important cross-project discussions taking place at this summit in particular? Right. So like right now, like as we saw from Mark Collier's keynote message, right, we have OpenStack Client, okay, and that is something that, you know, we came together as agreement in this group to, like right now, there is a Cinder client, there's a Nova client and so on, right? And it would be great to just have a client that gives you an interface of the resources that you're wanting to actually interact with, right? I shouldn't know that I need a Cinder in order to do a volume. I shouldn't need to know what a Cloud Kitty is to do the thing that it does, right? Instead, I should be able to just say, hey, server add or, you know, sorry, server create or volume create. And that's the neat thing about this interface, right, is it's the resource and it's a set of consistent verbs to interact with those resources. And that right there is like hugely beneficial going back to the quota issue where I myself can say, I want to do OpenStack, you know, so the command will look something like OpenStack quota set and then I can say dash dash whatever the resources, volume, instances, vCPUs, memory, whatever it may be, I just say it right there and that, you know, saves me time as a contributor to this project to not have to dig through the help usage. It's just a much better user experience. And going along with that as well, right, we want to keep that consistency going so there's also standardizing on the service catalog. Okay, so, and with this particular initiative, right, we have right now where if you go to, you know, a variety of OpenStack public clouds and you're wanting to actually consume like say for like the compute service or the volume service, that is not what it is today. It is whatever that the public cloud wants to actually define that resource as, it could be whatever they want in the service catalog. Us coming together and saying every single project now is going to be represented by a service so that, again, once again, you don't need to know about these code names. You don't have to be lost in the 50 plus projects and whatever trying to figure out what this name means to what service. And then, you know, it's interesting that it took us a while to get to this point and realizing that, but I mean we're getting there now and, you know, this is going to ultimately benefit operators in the end. I completely agree. It sounds like, you know, there's a lot of standardization efforts going on on different fronts. And anytime we can make things intuitive through standardization or, you know, classified work, you know, life is good. So thank you so much for sharing that and thank you for joining us on Supervisor TV. Yeah, thank you.