 Yeah, thanks Arpin. So welcome everyone. Today we're going to talk about how the various projects under the Lynx Foundation Edge and networking are responding to user needs and how they're evolving the architecture and the software. I just wanted to put out this diagram out here and don't worry, I won't go into too much details and it won't be on the test as my sixth grade teacher used to say. But I just wanted to give you an idea of what projects we're talking about and what they're dealing with and here you see an kind of an end-to-end use case and you can see we're dealing with everything from the edge to the core, from orchestration to data playing, so really wide diversity of technologies in our projects. And as our projects in recent years are maturing and seeing deployment in production networks, what we're seeing is that, or what we're learning is two things. One is that we need to really be addressing the needs of our end users and respond to them and evolve our project to respond to them if you want to see more adoption. And two is that as you can see here, our projects are deployed in a kind of a side-by-side or part of a bigger picture. So we need to collaborate more closely between our project because this is the way our end users are using them, not as in a silo, but as a part of a larger end-to-end architecture. So we must work closely together within our projects and external projects and kind of evolve that and evolve that to the needs of our end users. And what we'll do today in our panel is we'll go into how it's really done and kind of some real-life examples of how we do that and how we benefit everyone, both the projects themselves and also the member companies in our organizations and of course our end users. So to help me with that, we have an esteemed panel today starting with Beth from Verizon who's also the TSC co-chair of the Anuket project. We were supposed to have Catherine, the leader of the TSC of the Honor Project. She's a bit under the weather, so she won't be able to join us today. That's probably live events, but we'll try to cover up for her. And Tina from Arm, who is the board chair of the Linux Foundation Edge, will join us as well. And myself, as R.P. said, the newly appointed CTO of the Linux Foundation Edge and Networking. So with that, I think it's not about slides, so I'll stop sharing and we'll dive directly into our questions. So first, I'd like to kind of first topic would be about how use cases and requirements come about and I want to ask where do those use cases come from and how exactly do they get translated into requirements for LF projects. So maybe starting with you, Tina, I know the LF Edge and Acreno have been responding to needs to support public edge and hybrid models. So what can you tell us about how these user requirements get translated into the project's architecture? Yeah, thank you, Renny and everyone. It's honor to be here to discuss with you. From my point of view, AI is the gross area for the public cloud and edge. And the AI inference is generally down on the edge. And the AI training is down on the cloud side. There should be reliable synchronization between cloud and edge. So in the LF Edge and our projects, it depends on the architecture, such as the container base, the cloud native. There is also a reliance on basic service, such as those of platform as a service to ensure the applications at the edge are deployed and wrong in line with the public and private clouds. In addition, how does the edge consider the differences between public and private clouds? For example, the public cloud multi tenant data privacy protection is certainly higher than the private cloud. LF Edge project considers security and privacy at the first place across 12 projects, including platform security and network security. In addition, device management on the edge is also very important. The public cloud edge interface blueprint family sets up a good example for public edge and hybrid cloud models through orchestrations. The AI Edge blueprint family supports all this implementation, including security monitoring at school and autonomous vehicle driving, including robot taxi and even the car in the airport and the federated machine learning for the edge applications. So this is my take. Thanks, Tina. And Beth, I know the Anuket community has dealt with the huge type of requirements from customers for kind of cloud-based, container-based architecture. What can you tell us about this? So Anuket is, I think, a little bit unique in the LF community as a project that started as a collaboration. It was started originally as a sort of a stealth project, if you will, CNTT that was a collaboration between the telcos and the vendors that support the telcos in building out infrastructure and supporting cloud-native types of workloads. So we early on identified that there was a gap and that there was a lot of projects that were working on tooling, let's say ONAC, of course, was working on management tools and orchestration of those workloads. And an LF Edge was working on and Ocreno was working on identifying various workloads, but what was missing was something to put those workloads on. And the telcos do build a lot of private clouds. And so it was important for us to make sure that the requirements that the telcos need to support those infrastructures was, in fact, reflected into the other projects. So CNTT was started and then just about a year ago, a year and a half ago now, it merged with OPNFE to form Anakit. And I have found that it has continued its mission of being very much focused on a collaboration between not only the the telco users of these services and the vendors who create these services, not just the infrastructure vendors such as Red Hat and Google and Microsoft Azure and Amazon, but also the vendors who produce the workloads. So Nokia and just to name a few, I guess Red Hat also fits into that category as well, Ericsson. So it's really a truly collaborative effort across many projects, not only within within the open source community, but also stretching into the vendors and the users of these services. And of course, Tina Acreno is also informing the Anakit requirements as well. Yeah, thanks. And again, Catherine is not here, but knowing the owner project, I know the owner project also had to respond to changing times or changing needs and two of the most central areas for these changes were first around the modularity of Onap itself, where users clearly told us that they need to see Onap being broken down into pieces that can be consumed separately in a more of a pick and choose model. And the other domain or area is where it's clear that our end users are adopting more of a cloud native technology and Onap is making steps towards supporting better this type of both the network function and also Onap itself becoming a more cloud native application, if you like. So I know you kind of, but you kind of alluded to that. But what can you say about the forces that are driving this collaboration across projects? Is it external forces from outside the communities, internal community drivers? What are you seeing in your community? I think it's both. So external forces, you know, as one of my co-workers used to say, if we adopt the, you know, internally within Verizon, adopt the etiquette reference model as our reference, you know, reference infrastructure, it will probably, you know, save 10% of our testing, which, you know, that's not an insignificant amount of testing. It's not like we're not going to test because all telephones are going to do that. But if we can, you know, sort of say to the vendors, you know, if you meet the etiquette assured program, and, you know, that means that there's a whole bunch of tests that have already been done. So we, you know, we can say, okay, you're good. So that's part part of it. I think the benefits for the vendors are that they don't have to build unique platforms for every single one of their, you know, their telco users and their customers. Again, synergy. We're not competing on our infrastructure. It's just not what we make our money at. So, and then of course, internally, you know, we also do etiquette works with GSMA as so the etiquette reference model gets turned into GSMA documentation. We're also working with other open source communities, open infra has the edge community edge working group, as well as the math and ONS and, you know, there's a lot going on across all of these communities. Yeah, it certainly sounds like a win win situation. Tina, what can you add from the edge perspective or what drives collaboration there? Yeah, in order to build this end to end solutions, we will need the more collaborations between various LF projects, especially with the LFN projects and the CNCF projects. For example, the edge integrates the LFN Tencent fabric for the private 5G LTE, integrates the LFN ONAC for the public cloud edge interface. It's later become the ENCO and integrated cloud native FIDO for integrated edge cloud, complies with the Anarchy for the 5G Max systems, including the 5G Max size for HD video, live streaming and cloud gaming. Also, the edge AI and automotive need more collaboration across the LF projects. LF edge uses many Kubernetes based technologies. For many versions, it's Kubernetes ready and ready for the development. Yeah, thanks, Tina. And I think we talked about prevention collaboration, almost ad nauseam, but how can you give our audience an idea of what are the mechanisms for that collaboration and how do we make people more aware of the benefits of this cross-project collaboration? Beth, maybe you can start by mentioning some of these mechanisms and platforms for collaboration. Sure. Well, there's a number of projects going on at the LFN level to do some reconciling across the tooling and documentation. So I've been working with a number of people. We've started the documentation evangelist group, and we're developing guidelines that will apply to documentation across all of the projects. It's not going to be, you have to do this, this, and this. But what we are recommending is, if it's a code type project, these are the types of documentation that we expect to see. If it's a documentation or security, not a security, a requirements document, then these are the types of documents you expect to see. So I think that will help go a long way toward driving collaboration across the projects. And of course, we meet regularly during the development day at workshops with the Onap community, with the LF edge community, with Acrena. So there are regular mechanisms to just collaborate on projects. And of course, there are people that cross the projects as well. Yeah. And Tina, any additional mechanisms in the edge community? Yeah. The participants jointly do one environment for two projects. That's what we do. Like some member companies, they do digital twins. And also the end to end showcase and super blueprints are good ideas. Like the 5G super blueprints you just mentioned. And there is also companies that want to do automotive energy or security end to end showcase on the edge and together with the other segments of the network. There are some business chains that involve a lot of project technologies, tech, the ASA, and going to the meetings are some of the same energy mechanism for demand and project planning. Yeah. And finally, I like to plug in some of something that is near and dear to my heart. We have a special task force that deal with specific topics. So recently we set up the under the LF networking, the security forum, where we have security experts from the different projects come in and share their best practices because security is of course top of mind concern for many of our projects. And it doesn't make sense for each project to reinvent the wheel and try to solve their security issues on their own just inside their project. So we're both working collaboratively. We started in the networking domain and we're extending it to edge. We're collaborating slowly with the open SSF project to learn from them how we can apply their best practices in our projects. But this area of security is one example of how we work cross-project when there are topics that are top of mind to many of our projects. And finally, is there any kind of specific call for actions from this forum to the broader community or to people in companies who are not yet members of our communities? What do you want people to do more or how you want to get people involved, Dina, if you can maybe start with you? Yeah, thanks. In order to create this end to end solutions, member companies need to invest more in two points. One is the integration of various projects you just mentioned and best mentioned. And also the second point, sharing use cases to the developer community is sometimes the suppliers and developers are two group of people they need to know each other. Okay, what are the real world use cases for us to implement? For example, we can call for you to do your own part to participate in the open source community. The intelligent work includes medical, food, accommodation, transport, smart cities, enterprise, energy and digital trustable. These use cases from end users bring requirements and the developers work on implementations and adoption of the LF projects and the suppliers bring the products deployed in production, receive the feedback and amend the ELF project. Connective vehicle blueprint was adopted by Tencent and was deployed in Winter Olympic. Feedback to the enhancement of release six of the LFJ criminal. And Google adopts and deprives FLEG for the OT. I think dynamic colleagues, Tom, just talk about this. And the super blueprints can be laid out for 5G, for automotive and for OT energy and you name it. So I hope this helps. Yeah, thanks. And we're almost out of time. So Beth, a few quick words of call for action. Yeah, get on board. You know, there's only upside. There's only benefits, not only to the community, but more importantly to your own companies. You know, as I mentioned, one of my co-workers said that we could easily save millions of dollars in testing just by adopting some of these solutions. And contributing the use cases and the requirements, that benefits everybody. Yeah, absolutely. And I'd just like to echo what she said. We're open communities. We don't bite. You're welcome to join in any form. If you weren't just listening at the beginning, you're free to do so and you're welcome to do so. We appreciate new eyes and new opinions. So thanks, everyone. As I said, we're almost out of time. Very insightful. And back to you, Arpit. Oh, thank you, Rani. I think you asked or answered all the questions that came through and I think really appreciate the insights, Tina, Beth and Rani. Thank you very much. And thank you for moving the communities forward in a collaborative manner. Thank you. Thank you for having us. Thank you.