 Thank you for joining us. This joint LF Networking LF Edge webinar is actually the third in an existing series of LF Edge webinars and represents the inaugural LF Ging webinar. So welcome. Today's speakers include Arpit Joshapora, the general manager of Networking Edge and IoT here at the Linux Foundation, and Heather Kerpsi, the VP of Community and Ecosystem Development. Just a couple of housekeeping items. Before we get started, attendees will be muted during the presentation. However, there is an open Q&A window, so please feel free to type in your questions at any time. We have reserved time after the presentation to address those questions. And some of the questions may be answered in real time via typed responses from a team of staff and cost here at the Linux Foundation. So without further ado, I will go ahead and turn the time over to Arpit. Thank you, Jill, and good morning, good evening. Thank you for joining. I'm going to cover three very important topics for Networking Edge. The first is all focused around the new normal. But at the same time, I want to highlight all the progress that has happened. And then focus all the attention on what we need to do as a community in 2020 and beyond and what to expect from the Linux Foundation Networking and Edge communities. So without anything, any further ado, let me just start off by going into the first part, which is we are here and we acknowledge the reality and the new normal. We are here as a community working together. But the thing that we have to realize is the work we do now is more important than ever before. As we are in quarantine and stay home and kind of work to meet a common goal, you can see the stats that are getting published by majority of our carriers globally, whether it's the traffic patterns, the workload changes, gaming, VPN videos, et cetera. My favorite, obviously, is the fact that the voice minutes have gone up. Kids now cannot complain that it's just for parents to talk on the phone. But at the same time, I think what's more important is transactions have gone up, upstreams have gone up, and in this extraordinary period of history, not only it's the traffic patterns and the workload, but Forbes puts it very well. The telecom industry is proving essential in the response. So how do we do, what do we do is clearly very important to not just us, but the world as a whole. And in this battle, the two key technologies identified, obviously, 5G and Edge, not counting today's existing networks that have stayed up very well, thanks to all of the hard work that this community and a large global population have done. But what I want to point out here is that as we look ahead, there are industries and markets and applications that are going to come up and that have already started showing up, whether it's in the health care area, whether it's in the engineering area, manufacturing area, or in any of these areas where edge computing and lower latency through 5G is extremely important as a lot more IoT devices come up. And we have to embrace the change of open ecosystem that externalized innovation. And again, I want to call out for calling it very well. And this is the new world we are in. So what we wanted to do here was to show you what we are doing and what our projects are doing and what we as a community are doing. I am just representing all the hard work from all of you here so that people can understand and see the progress. For those of you who have not been familiar with Linux Foundation and just heard about us, here's a 20-second overview. We're much more than Linux, obviously. We create shared investment and search software that allow some of the world's greatest markets and problems to be solved, whether it's in security, networking, cloud, automotive, blockchain, Edge, web, AI, film, et cetera, et cetera. And we are host to over 240 projects. And the biggest thing is we bring almost 40,000 developers together in the variety of these projects. So today, we'll be focusing obviously on networking and Edge. But at the same time, there's a lot more beyond that that is important to our ecosystem. So what are we doing to support our community? There are three things I want to highlight. One is there are things that are getting done at the Linux Foundation level in terms of initiatives. For example, our Open Networking and Edge Summit in April has now moved to fall, obviously, for travel restrictions and things like that. We are expanding training. There are several training courses, both free and have extended discounting for some of this training. Keep in mind, training is counter-cyclical. And we need to take advantage of retooling ourselves as individuals during these tough times. So Linux Foundation is stepping up its work on training. Obviously, there's a training website you can get to. And then, of course, on mentorship, as companies cannot physically hire, we have a virtual mentorship program that we not only expanded but restarted with over 12 internships this summer. And the most important and to me the most exciting is there's a lot more new projects coming in on networking and communications that give us the ability to provide a lot more value to our community. So that's at the Linux Foundation level. At the LF Edge and LF networking level, as you are already on. And again, by the way, I want to thank you for your tremendous response on today's webinar. There's a huge community of participants here. So thank you. But this webinar series is one of many and we'll continue doing that. Several webinars have been completed. We even did an EdgeX virtual hackathon, which is quite interesting. There's a lot of training that's going on. If you're new to Edge and AI and IoT. And then on the networking side, there are several courses, several free, several discounted, whether it's SDN, whether it's 5G, or whether it's just DevOps training for a network engineer. All of these courses, along with certification on projects like ONAP, they're all coming on. And one of the things that we just did last week in real time was we just completed a set of virtual LFN technical meetings, which really brings developer community together. And instead of me talking about it, I would like to welcome Heather, who kind of was the architect behind this meetings and logistics. So just give us a flavor on what happened, how things went, what did you folks do as developers came together virtually across LFN. Thanks, Arpit, and hello to everyone. As Arpit said, when we decided to postpone the in-person ONES LA, the developer community and technical community felt that they still needed to get together, even if virtually, to advance the important work that we're doing. And so last week, we held our very first virtual developer event, and it was quite successful and went very well. We welcomed participants from ONAP, CNTT, and OPNFV to come together for a three-day virtual event and in sort of the quote-unquote shared accessible time zones available. We had more than 500 people registered and 370 attendees. One really cool thing about these events, too, is that we did have a number of first-time attendees who were able to attend because of the accessibility of the virtual event. We were able to do a lot of collaboration and move the work forward. To be honest, we weren't really sure how a virtual event would work for a really high-touched, high-collaboration type of environment, but it went really well. The community stepped up. We had really good and interesting content and discussions. Great job of everyone pulling together to figure it out as a collaborative community. And I really could not be more pleased with how it went. So far, on our survey results, we've got more than 83% sort of saying that they thought the event merited a four or five, both in terms of content and in the overall event itself, which I think is great. And we have an upcoming event in June. And so I really recommend for everyone on the call who's technical or for your technical teams that you work with, that you encourage them to participate, both in the planning of that event and in the participation and presentation of discussion and material. Developers coming together is how we get our work done as an open-source community. And it was really great to see all the smiling faces that I love to see at events, even if it was only through Zoom video. So it's really great that we're still able to do this. And I'll turn it back over to you, Arpit. Thank you, Heather. And this has clearly made us all realize that as engineers, work is the greatest form of distraction. And I think that's what we have seen here in the events. And I'll show you some stats on the community progress as there's a lot more participation and contribution in these tough times. So thank you for keeping it up. With that said, and with that background, let me move into some of the great work that the community has done and what we are announcing today. So there are three big, major announcements in terms of press releases, which I wanted to highlight. The first one, obviously, is around LF Networking, which really has accelerated its focus on 5G, Edge, and cloud-native readiness as projects expand, community expands. In reference to that, obviously, there is a new project that I'll talk about that has come to the Lenox Foundation. And obviously, over time, it'll be going through its lifecycle management to LF Networking. And so we're really excited about that. I'll talk about that in a bit. The second big announcement is the fact that all of the telcos and service providers, as they come together, they have stepped up the focus on cloud-native in parallel to what we are already doing as the number one challenge that the team wants to solve is interoperability and deployment. And so this is all the work that CNTT is doing with LFN, JSMA, all the compliance and verification work that's happening in OVP and OPNFV, which we'll talk about in a bit, as the phase two of these projects launch focused on the cloud-native aspects. And then finally, the press release that highlights the LF Edge expansion with, obviously, new projects, new members, and, more importantly, in the deployment milestones, as these projects reach a level of maturity where people are starting to use it in real time, in real networks. And, obviously, we are welcoming crowd-ring, federated, wireless, blue, moray, tensor, warrior, and H3 to the LF Edge community. So let me walk through a couple of new projects and then the community itself. The first project that now is part of LF, our Linux foundation, is called XGVilla. XGVilla is an open-source cloud-native pass, our platform as a service for applications and XNFs for a lack of better work. It's, again, used to accelerate the design development for telco-related services. The great work that came from the seed contributions coming from China Mobile and a set of global ecosystem partners, but working very closely with a set of open standards, all of the open-source work that has gone on in both Kubernetes and Onap, as well as kind of the CI CD work that will happen, blueprint work that will happen in OPNF, the Acreno, and the CNCF organization. So we're very excited to welcome this project to the Linux foundation. For those of you who want to participate in it, just go to the XGVilla website and just click the Subscribe button. Obviously, it stands for Sale in Latin, and it's also Constellation. The second project I want to welcome is for LF Edge. And this is a very exciting project called Open Horizon. Obviously, the seed contribution is from IBM. But more importantly, it's a project that's an application and meta-delivery management platform. Now, there's a lot of words and a lot of acronyms here, but for those of you who understand this, it's a very simple policy mechanism to secure and deliver these workloads to a whole set of heterogeneous edge nodes. And that's kind of a simplistic way of saying it. But the real value is really, you can actually do these and model this across just a single device or a whole bunch of nodes, even 10,000 or greater. The good news with these projects and specifically Open Horizon is it has been collaborating already with the rest of the LF Edge projects, whether it's a Jix Foundry, our Glossary project, or our Home Edge project. So we welcome these two projects under the umbrella. And really excited. And if you want to participate again, please go to the web page and join. As far as the two communities are concerned, LF Networking, again, for those of you who are not familiar with LF Networking, it hosts some of the top networking projects, almost eight out of 10 globally. And it kind of focuses on a lot of things for the networking stack, both telecom, service providers, and enterprise. We saw a pretty good member growth, obviously, even in tough times. So thank you very much to all the new members that are joining in. Clearly, the share of voices is gone up year over year. But the thing that I'm really very excited about is the deployments and the commercial products. There's a huge support of projects like ONAP, OPNFV, Open Daylight, et cetera, that have moved into the commercial deployment in real time. And some of the traffic handling that you saw that, at least in the US, AT&T, was able to do, for example, was directly a result of the network automation that they have put in. And then if you look at training, just a networking-specific training, 28,000 enrollments, so really, really positive. Please do take a look and upskill yourself. These are really good courses that have really helped our engineers to take their skills to the next level. And then, obviously, with a metric that I personally look at almost every week, and that's the developer engagement, here's just one example, which is an ONAP high-velocity project just from sort of January through now. And you can see the steady increase as the Frankfurt release is cooking, if you may. Pardon my analogy, but that's kind of food and staying home is all we are doing along with work. Anyway, so this is really good news here on the LF Networking. If you go to the LF Edge community, we have got a similar picture here, 25% new member increase year over year, lots of project in the pipeline as the unified Edge community comes together to help solve the most important problem in the Edge, which is how to bring a life cycle and unify the cloud markets and the telecom markets and the cloud Edge and the IoT markets, et cetera, through simple frameworks that can work across the stack. It is moving into deployments and then obviously, as seen by either downloads, so Edge X Foundry, for example, had 4.3 million downloads and a Crano has crossed 14 blueprints which are really a path to deployment. Developers have seen a lot of increase also in all the projects and code participation has seen an increase. So again, please keep it up. As I said, work and contribution to open source is the greatest form of distraction in these tough times and we are seeing that with the metrics. So with that said, let me focus on what to expect in 2020 and beyond. Let's start off with LF Networking and LF Edge in terms of standards and projects. For those of you who have been part of the community for over three years now, I presented a version of this stack diagram almost three years ago at ONS. It used to be called ONS at that time and it was a lot more complicated. It was a lot more projects and what we are starting to see in networking is some of the critical projects are shaping up well with the growth in community. Obviously, the green ones are what Lennox Foundation, Lennox Foundation Networking Post and then of course, Kubernetes and CNCF is LF which we collaborate and then of course, OpenStack is right there. And we're starting to see a lot more collaboration with the open hardware organizations, specifically OpenRAN, OpenComputet, et cetera. And then the standards that have stepped up in this end-to-end solutions are also moving very, very quickly. From an edge perspective, this is obviously an important slide to make sure that people understand that not everything is edge. Edge is defined by proximity, responsiveness and mobility and we have projects like State of the Edge now as part of LF Edge and the Glossary Project that have really defined and laid out what the different types of terminologies and edge functions are. But the good news is all of these verticals are very active to take advantage of the edge compute infrastructure and applications that are coming up in our LF Edge project. So what are they now and what are the use cases? And I think this is a very important part of the presentation because I wanna make sure that we take a step back and look at it from a big picture perspective. You've seen this diagram before, some of you may have the mobile residential, small business and enterprise who have data centers, et cetera, bring into an access network, into an edge and into a core cloud, right? Classic left to right. And some of these projects they are focusing on, right? Whether it's Oran at the access part of the telecom network or a home edge from an edge perspective, the residential, its constrained environment on Fledge or Eve, and then moving up the stack here. We host projects at the Linux Foundation and we work with the community to come up with software that can go into products that can be deployed and people like you who are on the call and a lot more can make money out of it, invest and then the cycle repeats itself. You've seen this cycle from our executive director Jim Zemlin all the time. And so I wanna make sure that you realize that every project follows the cycle. And I'm pleased to report we are in the deployment and profit phase as a lot of contracts are being awarded for vendors and system integrators that are participating in open source projects like ONAP or others, right? So first of all, let me show you how we view the use cases. And these are real problems that open source projects are solving. So this is the edge use cases, okay? I'm gonna start from the left and go to the right. Start off with a very simple anomaly detection and home surveillance. Those are the big use cases that the home edge project is focusing on. You go down, this is the on-prem edge virtualization engine, right, IIoT and this is DevOps at scale, really for on-prem devices and the key here is they may or may not have full connectivity, right? They could be partial, they could be intermittent but how do you make sure that the IIoT device scales and works there from a software perspective? That's Eve. Move up a step, Fledge, right? One of the LF edge projects. Again, focusing on predictive maintenance, condition-based monitoring, whether it's turbines, transformers, pumps, et cetera. In the press release today, you saw Google and sort of the TensorFlow ML application and there's some cool use cases on race cars and things that have come up with edge applications and Fledge. And then if you look at the top two, they are, again, stage three projects, EdgeX Foundry and Acreno. EdgeX Foundry, as I said, 4.3 million downloads but again, the focus is on an IIoT framework and now you can use it for building automation, for using it for industrial process controls. You can even use it for smart city water. Retail is a big use case that has been pushed and promoted in the EdgeX Foundry land. Very, very important. And then Acreno, for those of you who are not familiar with that project, brings two very important things. It brings a set of Telcom or Telco Edge solutions and blueprints, whether it's Radio Edge Cloud, Network Cloud, et cetera, which is basically saying, how do I put software in a base station or a smart central office that will be automated and connected end to end for enabling edge applications? And then it also brings vertical edge application blueprints like a connected vehicle or an augmented reality classroom that can be used these days for amplifying the experience. And then of course, it has the enterprise edge cloud automation blueprints with Kubernetes or with private LTE, et cetera. So a lot of good progress has been made on blueprints on the LF Edge side. Clearly, take a look at these. They're all documented under the wiki and we'll get to the points there. A quick note on the blueprints. How do you enable deployment of use cases? How do you enable faster deployment? And that's what this is showing, right? Which is it's a declarative configuration. It's basically saying, I have this use case. I'm gonna integrate this and I'm gonna automate the testing and scripting of those stacks and products and configurations. And I'm gonna open source it. So basically we're moving the interoperability and the testing in open land, if you may. So it's not just open source software, it's also open interoperability that a crane of focus is on, both at the device edge level and the infrastructure edge level end to end. Very, very important. Now let's get to networking. And let's get to LF networking where we are now seeing a set of use cases across the horizon on everything starting from the left to right. Let me talk about Oran. So as you may know, Oran is an alliance and Linux Foundation formed a partnership with Oran. Sometime back, we are hosting a project called Oran SC. Since we like acronyms, we keep them, keep on using them. SC stands for software community. So it's not very innovative, but it's very easy to remember. So we are hosting Oran SC and their focus is very simple. 5G, on app end to end network slicing, quality of experience optimization and getting white box or disaggregated hardware working in context of the life cycle management. That's the software releases have come out. Then if you look at ONAP, which is again with one of the largest projects we have in LF networking, there are concepts of blueprints and use cases. It could be 5G, network slicing, cross cloud VPN for global data centers, zero touch provisioning, close loop automation, voice over LTE, voice over IMS or virtual IMS, virtual CPE, and very cool nomadic broadband, so and many more. These are actual use cases and solutions that are tested and manifest itself as blueprints. And then all the supporting software below is all scaled to support that. Then you look at OPNFE, clearly we have shaped the community and the community has stepped up to work very collaboratively with CNTT and GSMA to allow for standardized NFVI, VNF, CNF, NFVI onboarding to provide reference implementation, compliance and verification. And then of course we are collaborating outside ONAP, outside LF networking into the LF AI community where you see a project called Accumals. And this is actually a very interesting state here because network has tremendous amount of intelligence and frameworks like Accumals allow you to do real-time video analytics use case, allow you to do federated training or just do straight integration with 5G or an ONAP and kind of bring all of that to a more intelligent network, intelligent and automated network as we would say. And then of course at the bottom the couple of most important open stack in Kubernetes, this is where the multi-cloud and the hybrid deployment of telecom services come in and extreme collaboration is happening as we speak. So how does LF networking enable faster deployment? Just like a cranial and blueprints is doing it for LF edge, the whole OVP program is doing it for LF networking. And for those of you are not familiar with how this works, on the left you see the stack. So infrastructure, NFVI, the virtual infrastructure manager, WIM as we call it, the orchestrator and VNFs, right? Different vendors, different Mano solutions, different life cycle management, different onboarding. What the CNTT phase one has done through GSMA specification projects are the first phase has been published with open stack as a WIM and all the onboarding guidelines have been integrated and now OVNFV and OVP, they're all doing the testing and scripting and all that stuff. Today's announcement also includes the start and launch of the phase two work that is going on in the community. That includes the phase two of CNTT which is focusing on cloud native. And that is in collaboration with the CNCF work that has happened. Plus there is a project. So ONAP has a work stream started called ONAP cloud native which again, the TSC chair, Catherine is leading. That is also happening in the Viki if you wanna join and participate on that. And as we move to phase two, how do you get to a hybrid VNF and CNF environment and how do you get to faster deployment? So very, very exciting things happening in the land of LF networking to speed up deployment. Remember, that's kind of our main goal here. And so if you look at the summary of what we have just discussed and what's happening in 2020 across open networking and Edge. The most important today, it's kind of picked up in the last six months is really the deployment focus. So projects are mature now. How do you deploy it? How do you enable use cases through solutions and blueprints? Both LF networking and LF Edge are really, really focusing on that. And our vendors, system integrators and our end users have stepped up to help on that, right? Through the developer community. The second important thing that I want to highlight is the markets are intersecting. And what I mean by that is because of 5G, because of network automation and because of edge computing, the various classic mindset we had, oh, this is telecom and this is enterprise and this is cloud and things like that. You're starting to see the lines blur and the biggest benefits are coming from the open source community as these projects do interoperability through working group, through blueprints, right? And as I showed, and whether that could be Kubernetes and its solutions or Hyperledger from a blockchain perspective as they focus on the telco use cases which require trust, right? So there are white papers on both sides that have come on. So we're encouraging and accelerating cross-domain technology collaboration and you will see a whole bunch of white papers coming out, whether it's on deployment, whether it's on consumption, whether it's on guides, et cetera, et cetera. So don't miss out on those things to educate yourself and obviously contribute. And then as we said in the press release, there's a heavy focus on cloud native primarily to sort of make sure that we have a hybrid deployment as we move the cloud and the telecom networks together both at the core and the edge level, okay? So again, that is a quick summary of what we wanted to talk about. We wanted to leave plenty of time for question and answers. So I think as Jill said, put question answers in your Q&A window and we will answer live on the Zoom call. But more importantly, here's a call to action since you all joined the webinar, I would like you to get a Linux foundation ID, there's a link, visit the Wikis, both networking and Edge, and then just join the workflows that are relevant to you, right? Whether it's project meetings or events like this or writing documentation, putting in requirements, answering questions, building software, providing feedback, all right? If nothing else, just talk about what you're doing, right? People, you will be surprised that you're not the only one with the problem. It's the same problems all over the place. And this is why open source has gone to a level that we would not have imagined, which is all the problems in software, which again, I hate to use the word plumbing, but in the stack, in the plumbing layer of the software are all common, they are non-differentiated and we don't wanna solve it 10 different ways. And that's where LF Edge and LF Networking is focused on. And then have the vendors differentiate on top, keep the onboarding simple, keep consistency and things like that. And then of course, there are upcoming webinars, May 12th, how LF Networking provides the building blocks, some good, and then of course, we will announce these future dates, very interesting topics. Please don't forget to sign up. With that, here's the Twitter handler and the wikis. I am going to open it up for questions. Jill, if you can please read out the questions since I can't see the Q and A. Yeah, so we did get one question in. How do CNTT and OVP, how can they be leveraged with LF Edge? That's a good question. So there are two ways to do that. The, as you know, CNTT and GSMA, the way we have collaborated or set up the collaboration. And just remember this, right? LF and Linux Foundation, we do software and we collaborate with the specifications bodies and SDOs as we call it, whether it's SC, GSMA and all that. So the setup is already there in place. Whether it's for Etsy's MEC initiatives or for GSMA focusing on some of the edge work that they are doing. The first one, obviously, is to make sure that as the specifications and as documents are created, they are brought into the LF Edge community through the TAC and through the governing bodies that we have set up for that particular domain. And then Acreno probably is going to be the project by which it will kind of collaborate and work together because that's focusing on those blueprints and solutions together. So that's kind of the high level answer. We can take specific answers through an email, obviously. What else? I wanted to open it up to see if Heather might have some additional comments on that one. I know she works very closely with CNTT. Sure. Yeah, I was just going to say that within CNTT, in terms of the two sort of high level work streams, the VM and OpenStack based one and the Cloud Native one, CNTT is looking at sort of edge considerations for the common NFVI and certainly doing that in concert with LF Edge. And I know there are certainly a large number of common members between Acreno and CNTT, for example. So CNTT is looking at sort of the edge as an extension sort of of the core as well. And so I think that there's a lot of work for all of us to do in conjunction. But as we start getting requirements into RC documents, obviously that's the way that things can get translated into OVP and OPNF. And keep in mind, the telecom edge, which, again, we are talking about here, is one of the many markets, if you may, that LF Edge addresses. There is a whole Cloud Edge. There is a whole enterprise sort of mindset and an IoT mindset that is kind of getting unified like at a horizontal level in the manifest. So yeah, that's good question. Thank you. What else? Are these frameworks architect independent? What type of license are they under? These frameworks that we talk about, specifically, all the projects, all the licenses are on the project specific web pages. Most of them are on the Apache 2 license. And then, of course, Creative Commons on the specification side. They're all open source friendly licenses as you would have guessed. Great. So another one coming in, it looks like the Cloud Native World, Networking World, and Edge Computing World are all colliding. Can you comment about strategic collaboration across CNCS, LFN, and LF Edge? Absolutely. And we have been saying this for quite some time now. We need to make sure that we follow the principles of what I call the best practices of open source, which is upstream and downstream. We do not want to redo work that has happened either in the Kubernetes community or in the OpenStack community or in the various projects of LF Edge. And so conceptually, that is the driving principles by which collaborations happen. And so if Kubernetes is viewed as an upstream community, which is part of CNCS, then downstream is a Crano. And give you an example, QBedge, as a project that is part of CNCS, is submitted a blueprint under a Crano, for example. So that relationship happens. The governance structures that we help enable the collaboration is all around working groups, special interest groups, subcommittees. I mean, I'm loosely using these terms because everyone uses a slightly different word. But the concept is, within a project, a group of people get together and VLF help create either a receiver list or a wiki page to help collaborate on that. We've also started seeing formal coordinators that are assigned. For example, ONAP has assigned a formal coordinator to work with CNCS and Kubernetes for moving to cloud native. So many, many things happening. Once you participate in the community, it'll be easy. I know I'm giving you so many high-level answers, but there is very, very specific ways collaboration happens. But the key is these umbrellas and these projects, each are autonomous and separate because they solve a specific area or use case. But together, they are much stronger because they bring the use cases to life. Next. Great, thanks, Arpit. Any collaboration with ONF and BBF? Yes, so ONF, I think last year or maybe even two years ago, we had already announced. And I think you may have seen a couple of years ago or maybe last year, CORD and ONAP had proven interoperability. So that's already happened, if you may. There is also work going on in the ORAN-SC community where the controllers and softwares are getting used. And so that's on that side. On the BBF side, we have not set up a formal agreement, but if there are specific use cases that you would like me to personally approach them. I mean, we have the management and leadership at BBF and we do communicate. We have not seen a request yet on, hey, you should do this to set it up. But I'd be happy to take that on. Other questions? OK, great. Are there any cloud providers actively participating in LF edge to line with and interoperate with edge clouds that support proximity-sensitive applications? OK, so I will answer that question very, very strongly because if you look at the ecosystem on LF edge, it consists of, I would say, silicon-independent players. So ARM, Intel, Qualcomm, et cetera. It has several of these telecom players, obviously, you know, AT&T and Equinex and NTT and others. But it has very strong support from the cloud players. Specifically, we've got Tencent and Baidu and some of the largest of the large cloud that are using, in fact, the connected car blueprint is coming from a cloud to an edge perspective. There's a project called Baidu that has been contributed by the cloud companies, and that's exactly what is focusing, that is one of the big projects for focusing on those applications. And then from a public cloud perspective, if you look at the US market, we are seeing complementary AWS work with Ajax Foundry and the same with the Azure cloud as well. So we're seeing that as solutions and interoperability as these markets come together. Great, thank you. Next question, how complementary are ONAP and Open Source MANO? They are actually quite complementary, and we have said that several times. ONAP is about 31 projects, sub-projects, I should say, and it's a full stack that includes MANO as one of the pieces, but it also includes closed-loop automation, network analytics, design tools, external APIs with the SDOs, TM Forum, MEP, et cetera. And it's kind of the entire solution, if you may. And MANO itself is one of the pieces. And I think, as you may know, OSM is focusing primarily on the MANO front. And so if you look at it, it's a subset. ONAP is kind of 31 projects, and MANO is one of them. Great, so this next one is for Heather. What is CNTT phase two expected to be completed? And CNTT identified the focus for phase three? So just really quickly, phase two is not necessarily a term we use in CNTT. We have the R1 set of work streams and the R2, which is a set of work streams, the first one being open stack and VM, the second being Kubernetes and container focused. And the best way to answer that is that we have a roadmap of things that we begin to see developing. And we are expecting some first releases in the, I assume when you say phase two, you mean the Kubernetes container-based work stream, that we are expecting to have some things published in September for that. But if you would like to see a roadmap slide on that, if you want to ping me, I can point you to that. Also, I would expect that we'll be doing a deep dive webinar on the topic of CNTT later in our webinar series, too, where we can dig into that information. But basically, that technical space is also certainly evolving rather rapidly. And so we want to stay in touch with the evolution of that technical ecosystem as it continues to mature and develop. Great. Thanks, Heather. Ray, if you'd like more information on that, just contact me and we can set up some time to go over more details. OK, next question. What all container network functions will come near Edge in 5G? Edge should be lightweighted with minimum number of computes. What is the best practice for Edge architecture designing? That's a loaded question. I would say definitely look at the use cases that Edge is producing. You're absolutely right that Edge is not one kind of place. There's a physical location, anything from what we call devices, which is microcontrollers, sensors to gateways to on-prem quote data centers, moving into the other side of the last mile, which is base stations and smart central offices. Basically, in the 20 milliseconds of less latency. And I think the general demarc point is about 100 kilometers or less. Each location and each industry, if you may, have specific requirements on memory and compute and what they can allow. And they have specific requirements on the hardening because of connectivity issues and things like that. So there's no one answer on how much is allowed or whether it's lightweight. If you have a six rack server that you can fit it into a smart central office that is in the heart of a windmill farm, guess what? You can fit a lot of things in. If you're in a remote location in a farm somewhere where you get intermittent connectivity, 256 meg may be the limit. And yes, that might be not. In fact, even containers may be an overweight. You may need an RTOS with that. So answer varies. Please look up the suggestions that the LFH community has provided for you to deploy these things in various use cases with the appropriate software and the appropriate memory and the software that comes with it. OK, this one is for Heather. Which NFVI and VNF vendors are actively engaged with CNTT? So all of the major NEPs are actively involved. In fact, we've got some work stream chairs from folks like Nokia and Intel. Red Hat is also involved. And then we've also got some, especially on the cloud native side, some smaller innovative players like Matrix and Lutsa, who are very active. So there is a quite vibrant representation from the vendor community. And I would add, Heather, on the receiving side, this is a specification side, on the receiving side in terms of OPNFV and the code, all the top 10 vendors. I was going. All the top 10 vendors are participating. Yeah, and I was going to say, also with CNTT and OPNFV's collaboration, really beginning to accelerate all of the traditional folks who've been active in development in OPNFV are participating as well. So we're really building that relationship, I think, in a very healthy, sustainable fashion between the engineers and the architects and deployment operations folks who are generating the requirements. So there's a lot of really good work there. And it is very much a partnership between the operators and the vendors. Cool, thank you. Couple of more, maybe, Jill? I don't know how much time we have. Yeah, we've just got a few minutes left. Can you say more about the collaboration between the Oran Alliance and Linux Foundation as it relates to the Oran software community that you mentioned? It seems like the RAN is still proprietary for the most part. How is this work going? Sure. So again, for those of you who are familiar with how the structure is, obviously Oran Alliance is kind of the Alliance. And what we have done with the Linux Foundation and Oran Alliance is we are formally supporting them with the software community. So that's the project OranSC that is hosted by the LF. So we get the specifications and the requirements and the guidance and the direction from the Oran Alliance. And the software community works to create the code that is part of the RAN, whether it's CUDU, all the apps, desegregation. There's a lot happening. The first release is already out. So take a look at it on the OranSC page and see what is missing. And again, I always say on any of open source projects, it's all about duocracy. So if you, and I think Heather may have coined that term, but you come in and you work and then you will be heard. We are not like, it's not like, hey, I'm giving you requirements or I'm solving a problem for you. We're all solving problems together. So if there's specific things on OranSC that you want to see, participate and just go with that. And you will be surprised on how helpful these developers are. Other, maybe one more? Sure, yeah. Is LF Edge supporting Kubernetes? So there are multiple blueprints. I mean, that is a very big question. There are multiple blueprints. I think I talked about a few of the enterprise blueprint. There's a blueprint that includes the network cloud, which pulls an open stack, for example. Then there is a blueprint which has no open stack and only Kubernetes. And you can take a look at that as well for those deployments. And then there's hybrid blueprints. And then there is blueprints that come from, and again, these are all under a Cranos Viki. So take a look at that. Short answer is yes. And containers and Kubernetes are a very important piece of the Edge ecosystem. Any final burning urgent ones or should we wrap? I think we should wrap. There were a couple of questions about some vendor-specific contributions that I don't know that we are in the best position to answer. But I think this was a good overview of questions. So thank you, everybody. Any last words from you, Arpit or Heather? I think I really appreciate everybody hanging in there and participating. Please stay safe. And as we said, participate. Work and open source contribution is the best form of distraction in today's times. And hopefully we'll see you in the future in one of the next webinars or as a TSC participant. Thank you. Great. And as a reminder, the recording of the presentation and the slides themselves will be available shortly. And we will be sending an email with links to both of those assets to all of our attendees. So if you missed something, you want to go back. You will have access to the content. Thank you. All right.