 Okay, hi everybody welcome to the open infrastructure community meeting a reminder that this is a quarterly meeting and this next one will be in September. So if you have questions along the way please throw them into the chat and we will try to address them if there is additional time. So let's get started the agenda. First up we've got the open stack foundation project updates from all of our premier projects and then secondarily we've got some event updates from our about the PTG open dev and the open infrastructure summit. So first up the open stack project updates. We'll start with open stack and speaking will be gone. Thanks Jimmy. Good morning everyone. Good morning from open stack side on the project updates. We have the three things to share. First is the project retirement. We did the time and for the two project one is Congress and one tricycle. The TC has retirement criteria now like PTL is one of them and we didn't have any PTL candidate for Congress and tricycle project in Victoria cycle and as per their development also not going active in your series cycle so we decided to retire these two Congress and tricycle project. So the retirement is completed and if there is any activity comes up they can continue the development under the open dev and they can reapply for the open stack official project. And other update on retirement is we did some process clarification on retirement also. And we found like there are many projects which were retired previously are not cleaned up properly. So the cleanup process is also ongoing in PC. Next is Victoria cycle goals. So we have selected the two goals for Victoria cycles. One is migrating CICD jobs to go into focal 2504 version. That goal is being started we are preparing the dev stack jobs first and then in parallel we will be testing the projects project CICD also once we confirm everything is working fine then we will move the dev stack and tempest so by default to the focal. Second is migrating the Zool legacy jobs to Zool V3 native and Toskey champion for this is driving the effort on that. The work in this is we have the legacy is we still have the legacy jobs in open stack and we are trying to move it to Zool V3 since many years but this cycle we are deciding to go with the goal community goal and if we can finish it it will be a big relief for in the term of the maintenance it will be a big relief for all the projects and even in for our team. So these are the two final goals and next cycle goals will be starting soon on the release site Milestone one is being done last week and if you have seen the Sony mail on or the mailing list in open stack that discuss. We have the like a recycle deadlines so each projects should follow those all those things all the Milestone guidelines and updates. On community updates has everyone knows we finish the virtual PTZ or first virtual PTZ for Victoria cycle, you can find all the etherpad here and we have the blocks also from candle on summary of TC and project site. And you have etherpads you can have the summary emails from projects on mailing list also. And it was overall it was great success and we discussed a lot of technical topics to be finished in Victoria cycle. And participation was much more than the physical PTZ so it's really great. Second big thing we did from community update wise is technical committee and user committee. So we must these two committee into a single governance body and the paths we link there is also merged in governance. So the technical committee, which has 11 members now, so they'll be serving as user committee also or you can say the user committee also is a part of that technical committee. We have the new charter also available to clarify like what are the responsibility and how we will, how we will go man plan these both communities to work together. So there's there and they did all this work and thanks to him. That's all from open stack site. If you have any question, yeah, you can address in chat. It's only addressing chat or can we ask. I'm not sure maybe for crime permit Jimmy. Because if you could put your questions in the chat, we will. I think we'll handle them at the end if we have time. Awesome. Hi everyone. Sorry, sunny side everyone. Thanks. As you might have heard of that open stack is turning this year and to celebrate years open stack on the birthday July 19 will be launching the campaign that includes many articles and blogs that are written from our committee members and ecosystem companies about 10 years and as another part of the birthday campaign we are planning to have a virtual celebration on July 16 with the community to celebrate the 10 years. So as more details, the details come up I will be sending an email about it to the open stack list. So please keep an eye on your email for more details on that committee meeting. And meanwhile, we are also launching the world world runs on open stack and this will be a series of case studies and interviews highlighting how open stack has impacted me things across the globe. If you are interested in submitting case study, please let me know and that's my email sunny at open stack org at the very bottom. So please, please reach out to me and and we can talk from there and another action item to participate in the 10 years open stack is that please share your top 10 favorite moments or top 10 favorite anything with open stack by clicking that bitfully link and yeah please share that with us before the birthday July 6 July 19 and yeah we'll be very excited to hear from you. Awesome. Thank you, sunny. Next up we've got airship Alex Hughes is going to be presenting. Hi, thanks. I'm one of the members of the airship technical committee and just want to share a few updates from the airship community what's happened since we last met and what we're working on going forward. After airship one success we wanted to take the lessons we learned and make airship more capable, more secure more resilient and most importantly more comfortable to operate. So what do I mean by more capable, but we will support more use cases expand the operational capabilities and add more supportive features. And to do all this we started developing airship to and split up some of these goals into milestones. Recently the airship community completed the alpha milestone and one of the great success stories of that was deploying airship to into a bare metal lab and demonstrating and then provisioning workflow. Anyone interested can track the progress and availability of our upcoming beta release in GitHub issues. And each month the technical committee provides a snapshot of this progress on our blog and in the newsletters. The airship community wouldn't have made the progress that it has without frequent conversations with operators and developers. So earlier this month we attended the virtual PTG and we had a few key takeaways. We had higher participation than we usually do for in person events. We made significant progress on secrets design deployment configurations we want to support, and the airship UI project, and there was also excellent cross team collaboration with Starling X ironic and the edge working group. During our discussions with Starling X. We gave an update on airship to and laid out the deprecation cycle for our motto. We also encouraged them to check out the flux helm operator and look forward to more discussions and opportunities to align Starling X and airships technical stacks in the future. The airship technical and working committees have been driving efforts to make airship secure out of the box to help us. We have adopted the formal vulnerability management process that's inspired by open sex process. This will be used to report and disclose vulnerabilities and coming soon will be more automated processes to help developers and share their code is free of security concerns with tools like bandit. And the resulting container images are free of CVEs with tools like Claire. The track call this work and facilitate collaboration across projects the airship community adopted GitHub issues. GitHub issues has proven an invaluable tool, and we now host weekly grooming calls to scope work and discuss design considerations for each item. This is a lot about the project but the community behind airship is essential. Governance is governance by community elected officials is one of the cornerstones of the four opens. And last year we held our first elections for the technical and working committees. Earlier this month we elected our second technical committee with leaders representing five different companies, Accenture, AT&T, Ericsson, Morantis and for the first time Dell. Dell's representation on the technical committee emphasizes the community's continued growth and commitment to diversity. And next month we'll be holding our elections for the second working committee term. We've also launched the airship user survey and this gives users and evaluating a running airship and opportunity to provide anonymous feedback to help influence the community and software direction. We'll present the results of this survey at the fall summit. So these are just a few of the highlights of what's going on in the airship community for some more frequent updates and encourage you all to check out the blogs on airship.org. We're looking forward to delivering a more comprehensive update and announcing the release of airship to at the fall summit. Until then, thank you and Jimmy I'll pass it back to you. Thanks Alex. Thanks for coming up. We've got Kata containers with Eric Ernst. Hey Jim, thanks. So, things continue to move forward with Tata. You know when we first started off there was a lot of excitement and, you know, just different new enabling to highlight. At this point, things are nicely boring. I would say we just last week had a couple of different releases around the 1.011 and just kind of some basic iterative fixing and slight enhancements. But I would say the majority of the community's focus at this point is around Tata 2.0. If doing a major release, it gives us a lot of flexibility to deprecate old things that, you know, we don't see as necessary anymore and then kind of make more major changes in order to be able to better enable our end users. So, a few different examples out of that that I've highlighted here is that we went ahead and rewrote the agent in Rust. And the reason to do this isn't because Rust is an awesome buzzword, but it is a bit more secure generally as a language, but it is a lot lighter weight. So the agent is something that would run closest to an end user's workload. So, you know, it is from a surface standpoint. Maybe on the more sensitive end and also since it's going to exist for every single pod that's created, you know, having this reduced in size as much as possible is a big improvement from a footprint for end users. And similarly, making kind of similar changes, I suppose, in Tata 2.0, so it's a lot of work for us, but we're kind of have a lot of good momentum. We had the PTG, we participated at the beginning of the month, and a lot of the discussion was around different features around Tata 2.0. We continue to have a pretty good mix of contributors and people very active in the project. It's a mix of some vendors. If you look at like ARM, I'm at Ampere now. I need to look at Intel. You know, that's a good core of the project, but pretty much everyone else is somebody trying to use it in production or manage, you know, a software offering in production. So it's, I think that that's been a pretty healthy balance. And I'm happy to see that we continue to hear more folks who are using Tata in production, but less about, you know, hand holding at this point, because the maturity of the project. Sometimes we just hear the new features being added from different people kind of detailing how they can customize Tata to meet their needs best, or just as a hey, heads up we're using it and it's been working well. So, you know, we I do have a link at the bottom of this for the Tata user survey. More or less the way that we're trying to get more formal information on production numbers and kind of deployment sizes, things like this, but I would say that, you know, we're continuing to get more and more people using Tata in production. And once we have 2.0 out there, you know, and we continue developing 2.0 I think we'll be able to be more splashy, I would say for a little bit but otherwise things things are boring and things are being used and continuing to iterate to be a better project. Awesome. Yep. Thank you. The boring is good. Yeah. All right. Awesome. Next up, we've got a new initiative from the open stack foundation. It's the open info labs. So we've got Michael Deitzman and bill burns up to talk about that. Hi, this is this is bill burns. Michael and I have been trying to help get this community going. It's a an effort to have a community centered around cloud operations. You know, not, not just open stack, but any, any particular cloud components that open source cloud components that people might want to use as a place where people can test code and production, publish complete reproducible stacks to make it easier for other folks, stand up clouds, you know, an existing and emerging workloads and so forth. Some of the things that have happened. It's really been gained traction over the last six months. And still building some of the things that we moved to get lab because we got feedback from cloud operators that the, the traditional setup that open dev was really not amenable to them. They're more used to get so it's actually moved to a get lab repository to make it embrace the operator community. We have an active discussion going on about monitoring needs for the cloud for people running open source clouds without trying to use proprietary cloud provider infrastructure, you know, they need to be able to monitor the usage of the cloud. And one of the efforts is kind of going on here is to develop some tooling to assist operators that would actually use AI. And so as AI ops is something that needs consistent monitoring to help manage the cloud. The mass open cloud in Massachusetts and the New England research cloud, both having their architectures defined as part of an open process in in the project up at open for labs. And NERC is a new cloud that's emerging and mass open cloud is undergoing a an evolution from its prior state. And then I run an initiative at Red Hat. I work for Red Hat called operate first and the idea there is that we were trying to get engineers at Red Hat and in the upstream projects to be more focused on operations and how their code functional code performs when it gets out into the cloud. And so we're part of this community and the operators within Red Hat that run clouds are really excited to have an upstream where they can contribute their tooling and reference architectures or whatever, and also share in community, just like we do for regular projects at Red Hat. So it's a great thing. And there's also a project Keras that has been proposed that addresses distributed compute and distributed storage together from another party. And the current idea of open info labs is that it's pretty wide open to embrace anything that touches upon operations and cloud operations in general. So that it's not being restricted to a particular thing. It may not actually produce a, you know, an open info labs release one or release two. It probably might be more ongoing with various tools and things to assist. There could be a prescription there for the latest open stack, you know, in use with, you know, projects X, Y and Z, and then it could be a prescription in there for the an older version of open stack with projects A, B and C, and you could have, you know, set up sale that don't have anything to do with open stack. Right. It's not limited to any one particular technologies. It's designed to be open and to provide the open source benefits to the operator community. So we have a link here and we're interested in any communications and efforts and with the chat channel on free node called open info labs where you can engage and also in the upstream get repo. So that's open info labs. We're looking to build the community. Great start so far and the more the merrier. So if anybody out there knows folks trying to stand up open source clouds struggling by rolling their own whatever. This is a great place to get people together to share their experiences and benefit from others. So thank you. Excellent. Thank you. And next up, Bruce Jones will be presenting for Starling X. Hello, thank you. I'm Bruce Jones on one of the Starling X TSC members. It's my pleasure to present to you today. So the biggest news from Starling X is we were just confirmed just a few weeks ago at the board of directors meeting for a full project. We're very, very pleased and grateful for the support of the foundation. We're working toward our 4.0 release right now. We release every six months were aligned with the cadence of the upstream open stock community. So our previous stable release right now is 3.0. It was released in January of 2020. We're very, very, very close to declaring milestone three for our July release. The gating factor is integrating the usury version of open stack. We're working toward that night and day right now. Hopefully we'll be declaring milestone three actually later today at our release planning meetings. So the work that we've gone that's gone into Starling X for this release is largely more about stability and less new features less major architectural changes than in the previous releases. And we are upgrading to the latest usury. We've upgraded to a more recent version of Kubernetes. And we've upgraded the kernel to 4.18. We're using CentOS as the source for our kernel and user space components. We've begun the process of implementing the code changes necessary to allow the underlying software platform to be updated in place. We're not currently supporting updates from three to four, but we're hoping to be able to enable upgrades from release four to release five. We've put in quite a bit of work as a community towards supporting FPGAs and in particular being able to manage those devices through their life cycle. We have some changes that have gone in for certificate management to improve that. We spent a great amount of time and effort updating our documentation, improving the documentation. And then we had Cata container support is now possible so you can now spin up Cata containers within the Starling X framework and manage those instances using Starling X. So we are seeing growth and interest from the user community. But we'd also very much encourage people to please take the survey and provide us with data as to your use of Starling X. Thank you very much. Awesome. Thank you, Bruce. Next up, Monty Taylor is going to speed talk you through Zool. Because we all know that I'm really good at talking quickly. Hey everybody, I'm Monty Taylor. I'm one of the Zool maintainers and you may know me from other things too. So the main thing that we want to talk about today is we have a big sort of exciting new thing coming in Zool and which is the Zool v4 and v5 releases. So we've been doing a lot of work to lay the groundwork for that recently. The result of this, the Zool v5 is going to be a more scalable and reliable. We're getting rid of the scheduler as a single point of failure and that'll be a scale out high available service component at that point. Zool v4 is a transition period to get us there. There's a couple of operator facing changes that have to be made by Zool operators. It's going to be really clear communicating these two people so that they could continue running without any downtime and without any issues. We don't want to surprise somebody with the new thing. So we rolled out in the in Zool v3 support for the things that are going to become mandatory in Zool v4 that will then allow us to roll out the schedule or feature. So those have all been landed in v3. We've made our final v3 release 319. And at this point, the operator should be able to roll out support for ensuring that they've got an SQL database. It's been optional this whole time. It's going to be mandatory in v4 or in the sort of ultimate state. We're not really running one, but technically we've allowed people to run without one. And so we wanted to be really clear about that that it was going to cease being an optional component. And similarly we rolled out support for the components all talking to the underlying zookeeper service over TLS and that's also going to be mandatory. And now we've we've added support for it so you can add support for that thing. So operators who are running need to get these, these two config things rolled out so that they can they can upgrade to v4 when when that's ready. And then over the v4 lifecycle will get all of the ha components sort of done in place, and then v5 should be the signal that everything is all now ha and scale out to be very exciting. So that should be a lot of that work is already in well in flight. We're just sort of being careful about how we how we landed and roll it out. Some other things that we did over this last this last since last we chatted with you. We added a new, a new pipeline manager called serial that was actually based on some of open devs experience in doing continuous continuous deployment of the open dev service using open devs tool. And there's there's some specific cases where you're running patches when changes land, but the jobs that you're running to deploy things have matches on them to limit so that you're only running some jobs when some files change, and you really need to run those in sequence. So the serial pipeline manager allows you to express that to make sure that you don't run old patches old production states after you run new production states which is usually a thing you don't want to do when you're rolling things out. We also added support for managing release jobs in tree. There's, there's weirdness with triggering things based on tags and knowing how those relate to branches. So we've actually added code and to be able to infer branch relationships with with tag commit so that those work as people expect them to. We've got better support for for streaming logs, if you're running your job content in in Kubernetes namespaces. So the live log streaming during a job run has traditionally been a thing that's only worked in the SSH based VMs and so we've got some a better experience for our Kubernetes users there. We've got a nice new shiny Google Compute Engine node pool driver, which is in production for for our friends in the Garrett community. And the GitLab driver is is rolling quite along. There's a bunch of patches in flight for it. It's, I wouldn't say it's finished, but it's, it's definitely been been cranking along and so we're really excited about that. And with that, I think I think I'm done. So thank you. And also just a reminder, almost, actually, I think all of the projects have a user survey up. So please, if you happen to be using one of these projects, please take the user survey. Next up, we will move to OpenStack Foundation events updates, starting with virtual PTG recap from KindleWaters. Hi, Jimmy. As a few of the previous speakers mentioned, we had the virtual PTG earlier this month. It was the first ever virtual project teams gathering. It was very successful with the largest ever participation we've ever had with over 700 registrations. And also the most diverse that we've ever had with diverse in gender countries and organizations. We had 44 teams meet with the largest sessions being triple O, Cinder, Starling X, OSF Edge Computing Group and Ironic. On average, there were about 25 people that would participate per session with the highest getting up to around 50 or maybe a little bit higher. We used a variety of tools. We use Zoom, MeetPad, IRC, EtherPad and PTG bots. A few of the key takeaways that we heard from teams, it was very productive. Of course, everyone would prefer to have it face to face, but this was a solid option and everyone seemed to get a lot done. Back to you, Jimmy. Thanks, Kendall. Next, we've got the OpenDev event series by Ashley Ferguson. Hey, this is Ashley Ferguson. So yeah, we are having an OpenDev event. Actually, the first one will be starting next week. We've done this event previously, but this time we will be doing it virtually in a series of three different virtual events. We'll be using Zoom for the first event. It's intended to be a discussion-oriented collaborative event that really will hit on some major topics within the open infrastructure community geared at sharing common architectures and collaborating around solutions to common challenges and problems that other people in the community seem to be facing. So it's definitely intended to go on just, you know, not during the event, but after the event in different meetings and working groups. We're hoping to have some deliverables come out of it eventually in the future. But like I said, it'll be three events in each event will be three days for just three hours a day. It's pretty easy to pay attention. And thank you to Platinum and Gold members for making it happen, as well as our awesome programming committee for each event. Registration is still open so you can register for the large-scale usage event that starts on Monday. And we also have registration open for the second two events, hardware automation and containers and production. And also, if you're interested in learning a little bit more about open-infra-labs, they will actually be sharing a little bit about their use case on Monday of this first event. So make sure to check that out if you're interested. Back to you, Jimmy. Thanks, Ashley. Next up, we've got Erin Disney. I don't think this one's mine. I'm next. Oh, sorry. Hi. So, yes, I'm going to provide an update on the open-stack days and open-infra days that traditionally happened during the June and July summer months and often into later in the year as well. And even this year, a lot have decided to either postpone until next year or transition to a virtual event. So we're creating an etherpad because as more and more virtual events happen and the foundation does its own virtual events, we're gaining a lot of knowledge around best practices and what we should do and what we shouldn't do. If you attended an event or helped organize one, please throw your best practices into that etherpad. We definitely want to gather as much community input as possible as we head into another round of events later this year. And then there are actually two that are still going to be happening this year that will be virtual. So the first is the first cloud operator days that is going to be held by the Tokyo event organizers. And then the second is the open-stack days that will be held on July 29th and through the 30th. And they're going to be focusing on real cloud operation and there's some categories here. And so if you're interested, I encourage you to check out the website. And I think that those will be recorded, but we can circle back with them on that as well. And then the open-infra days, China is going to be in mid-August. So if this is a website you've been checking in on for updates in that community, we will, that will be a redirect soon. And their theme is going to be intelligent open infrastructure. So these are going to be the two events that are put on by local organizers in the community this year, but we'll continue to update the community as more make their decisions on whether they're going to go virtual or potentially move into 2021. Back to you, Jimmy. Thanks, Allison. Was that your cat? Also, next we've got Aaron Disney. Yes, this is my side. We're super excited to be kicking off our content submission process for the summit this fall. The first up is the programming committee nominations. We are looking for volunteers. And that is actually already live. And you could submit, I believe Ashley sent the email earlier this week with the link to the mailing list. You can find it there. There's also a link here to nominate yourself or a friend. We also have call for presentations coming up very soon. We're launching that July 1 and you'll have about a month to get your sessions in. And then we're also working on sponsorship and all the other details to come. But if you have any questions, feel free to reach out to me or to summit at opensec.org in the meantime before we have more to announce. Excellent. Thank you, Aaron. The next up is me. So be sure to, wait, what, yeah, join the virtual events that are coming up. We've got Open Dev that is coming up on June 29. The first one, large scale usage of open infrastructure. And then two more open devs coming up this summer, all virtual, very exciting. And be sure to get involved in the 10 years of Open Sack campaign. Contact Sunny Sigh, sunny at opensack.org and tell us about your experience with Open Sack. And yes, if you have anything to contribute to Super User, the blogs, any other content that you can. Help us with please contact Alison Price. And I think I've been following along in the chat and I believe all the questions have been answered. However, if you have something that is in process, definitely feel free to take it to the mailing list. That's where everybody is, or IRC. But if there's any other questions, we're going to open it up right now. If we've missed anyone. All right. Thanks everybody. We'll see you in September. Thank you. Thanks. Thanks, everyone.