 Hi, I'm on video chat with Hongbin. Hongbin, can you please tell us a little bit about yourself and your OpenStack background? Yeah, sure. So my name is Hongbin Lu. I'm the project team for MADVM in the Newton release cycle. And I work for Huawei Technologies in Canada. I'm currently the software engineer. And yeah, that's about me. Fantastic. Can you tell a little bit about your project, Magnum, and what it does? Yeah, sure. So MADVM is OpenStack Container Infrastructure Management Service. It was created to bring the popular container technology to OpenStack. And in general, MADVM provides three kinds of features, which are summarized as the provisioning, and configuration, and the management. And for the provisioning, it provides a service to provision the different container objustration engines, which is referred as the COEs. And right now, the supporting COEs, Kubernetes, double swarm, and a patching resource. And for the configurations, so it provides a cell option for the user to configure the COEs. And Kubernetes, for example, is supported to configure it in an HA manner. And it has an option to configure it for the different networking options. And it can configure it for using the different storage options. And there's many more features. And for the management, it basically provides a service to manage infrastructure to run the COEs. So for example, you can use the Magnum API to add and remove NOAA instance to the Kubernetes classes. So that the capability of the cluster can scale up and scaled up at one time. And that's it for the Magnum in general. Fantastic. Thank you for that overview. The next question is, what are some of the hot topics for your team at the Austin Design Summit? And what were some of the decisions and outcomes that came up from these discussions? Yeah, so in the Design Summit, one of the hot topics is to discuss if Magnum should manage the containers or the Magnum should focus on managed container infrastructures. And so a point of view is that Magnum should manage the container as well. And because Magnum is originally the open stack container service, and another point of view is the Magnum should focus on managed container infrastructure, not the containers. And this is the very popular topic, very hot topics. And we have discussions, and finally we decide that the Magnum should focus on the managed container infrastructures. And for the management of the containers, we will create a new project to do the distrop, and Magnum is focused on the infrastructure use case. And yeah, that's it for the hot topic. Fantastic. So during Newton planning, what did you identify as user needs or problems that you're trying to solve in general? Yeah, so in the Newton, in the last cycle, and we identify a problem that is about what is blocking the adoption of the Magnum. And due to the feedback, it turned out that the hard dependency on other open stack services, such as Barbican, is the focus for the Magnum adoption. And that is because most of the users are willing to install Magnum, but they don't want to install Magnum and other new open stack services such as Barbican. And this is the feedback we are getting. So we are planning a solution, which is implement Barbican alternatives. That is doing the same function in the less secure manners. And for Barbican, it's more secure, but it's harder to configure. And so after this implementation, the user needs to choose which option they should use based on their requirements. But yeah, this will address the hard dependencies of the Magnum. Okay. Fantastic. And what are the top three priorities for new features or enhancements? Yeah. So the first feature is the container networks. So in this cycle, we are going to work with the curry teams to build a neutron integration to connect the container to the neutrons. And this will greatly improve the number of the containers. And the second feature is the iron integrations. And that is because most of the users is very interesting to run the container experimentals and not the VMs. So iron integration is very important. And the last one is the expandable architectures. So we are going to, we decide kind of refine the architecture of the Magnum to make it more possible so that the vendors can plug in their own distribution of customization of the Kubernetes and to Magnum. And that's the top priority in the Magnum. Okay. Yeah. Fantastic. Only a couple more questions that I have. One is around themes. So if you were to think about themes as scalability, resiliency, manageability, modularity, interoperability. So if you were to think of these five themes, what is the key theme or maybe more than one theme that your project aims to achieve with Newton time frame? I think a theme we need to focus is the interoperability. Okay. So most of the users are interested in the tie integrations between the container technologies and open steps. So interoperability is a theme that we are going to focus on. And maybe another one is the modularities. And that is because the vendor want to expand the Magnum to, to, or I should say they want to customize the deployment of the Kubernetes or Docker swarm or other COEs. So the modularities and extendability is also very important. Fantastic. Thank you. So interoperability and modularity as the top themes for Magnum and Newton time frame. And then just a last follow up would be what theme or themes do you project will be the priority for Ocata time frame for Magnum? Is it going to be the same or is there going to be a shift in what will be needed? Right now I think it's the same. Yeah, but I don't know too much about the features. Yes. It is more a guesswork, right? So you're saying most likely it'll be the same themes that will carry in Ocata time frame? Yeah. Okay. Fantastic. Thank you so much.