 Greetings. Good morning. It's Lucina. We can get started with the CI Working Group meeting in just a few moments as there may be a few more folks who would like to join. All right. It's 10.05. We can get started. My name is Lucina Stricko and I've been doing project management for the CI Working Group and the CrossCloud CI team. I've posted the meeting agenda and notes for this call into the chat and also a copy of today's slide presentation has been shared in the chat window as well. I'll pass it over to Taylor if you'd like to introduce yourself and then we can popcorn. Introduce everyone on the call and get started. Thanks, Lucina. Yeah. I'm Taylor Carpenter and I provide a little bit of development and ops dev on the team and working with Denver. Denver, are you with us? Yeah. I'm here. Okay. Great. I'm going to go ahead and see if. Hey, Taylor. Dan just joined. I'm not sure who else we have and what you want to cover. Hello. Hello. Hi. I'm Shashi from Huawei. This is the first time I'm attending this bar group and I just want to get myself updated with this bar group basically. We have a downstream projects who use CI which is more or less based on Kubernetes testing for tools. So we are looking for some alternatives in that direction. I just want to get updated myself with the CNC of CI working group. Great. Welcome. Sure. Thanks. Dan, your audio was a little cut out as you came in. I couldn't quite hear everything. Was there something? No, I was just saying that I'm here, but I didn't have anything I needed to cover. Okay. No problem. Okay. Well, let's see. So happy to have anyone join that wants to listen and participate to see what's going on. So if anyone has something they would like to talk about, a topic specifically, the CI working group, there's a shared document with agenda notes, so feel free to add anything on here, maybe even for the next time when we prepare that and happy to have you join in on that. Thanks, guys, participating on some of the things that we're working on on the CrossCloud CI team. So I'll jump right into that. So the updates from the CrossCloud CI team and the project that we're working on. So for those of you that are there. Just before we dive in, could I just ask the Huawei folks, because they previously had had a site up CNCF dot build that was based on container ops. And I was just curious what the status of that was. Absolutely. I think I don't have much info about that, Dan, as of now. So I'll get to that probably next time. Okay. Okay. If maybe you could send an email to the CNCF CI mailing list, I'd love to hear it. If you guys have either discontinued the project or are taking it in a different direction or anything. Sure. Thanks. Awesome. Okay. So this is the current team, CrossCloud CI development, doing development. So Denver, some of y'all have maybe met previously, Watson has been doing API development and some front-end development, Josh Smith doing front-end dev, and then Lucina and myself who have met now. So this is current team and the meeting notes I talked about before, those are linked off of the CI working group GitHub page. So since last meeting, we have had a couple of demos and meetings with some folks, Camille. We went through the current status, hadn't had an update with her in nearly a year. It seems like it's been quite a while. That was good to catch up with her. We're going to be following up to get more of her feedback. Lucas, we had a meeting last week talking about QBedman and how ADM, how we could add that in as a potential plug-in for doing Kubernetes provisioning. The system now uses custom provisioning on all the clouds. So we had some feedback on where QBedman is right now, what type of support, and then some directions that are going. We also received a bunch of, I guess, more detailed specifications and what we could look into to see if it's going to work right now or if we need to have some further conversations. So that's on our list and then we'll be having some follow-up conversations with Lucas. From the cross-cloud software stack itself, from the CI system, the pipeline, as we've been increasing and moving towards the production release at the system, we've been working through, it's starting getting really rapid on resource usage. So we actually had to reach out to the cloud providers, get a bunch of that increased as we're pushing through all of the different environments and testing. And seeing that, that will tie in with some conversations, Dan, with some of the folks like for the IBM and Bluemix stuff that you're aware of. Blinkerd, as we're refactoring to work with the new system as it's split out, fixing some issues on some of the existing projects. We've had some items for upstream changes like core DNS. There was, I guess it was right at the end of the last, on the edge of the last meeting, there was upstream for Kubernetes that was fixed as well. And then on packet, there's been limitations with resolving resolution on the clusters because packet doesn't provide any type of DNS service or anything else internally. So we have a discovery cluster that works with the deploys and allows us to work around some issues with bootstrapping and other things. So that's in place and working. So packet was offline while we put that and it's back re-enabled and working as far as a test cloud provider. On the dashboard itself, the part of the 3AM scheduling is the client for triggering and controlling the back-end CI system and handling stuff like when is the new Kubernetes master build done and complete and ready to provision and then run through and collect all the status and stuff. So this is part of that. So the trigger client for doing all those pieces and then the next step, I'll get to in a minute on the 3AM. Integration tests, we've been doing a lot of integration tests across the whole system. So this is going from dashboard all the way down through the CI system and completed quite a few of those. And then as we're moving towards production D1O, there's a lot of bug fixes that we're working on, a lot of them are related to integration stuff like timeouts. So one of the items that we ran into was when you're doing a lot of deploys, app deploys and then running tests on top of each other and the state of the dashboard. So working through those sort of things. And this is really going to be affected more when we start increasing the number of times the dashboard is updated. It's seeing those and let's see. So then we get to in progress. Fluent D was a little bit higher on the priority list previously. It's been lower, but it was partially done. This year the builds were working. So the remaining items, there's a couple of remaining items to test, but the big thing was refactoring it to support the new app deploys. That's been completed and it's ready to test. So we'll be finishing that out and it'll be coming in the next couple of weeks or so. The last, some of the last items for V1O are the running the scheduled job. This is what runs at 3 a.m. and every day to do builds for all the active projects, do provisioning to all of the active clouds with the latest stable and head of Kubernetes. So this will be using the new trigger client and stepping through and running for each of the pieces. And then one thing that we need to update and work on is the related to all this will be clearing out all the resources. So after the 3 a.m. job, with all the work that we've done, there's quite a few pieces that we need to tie in to actually run and clear out those. Some of this ties in with development. How long do we want something F and available and then which ones do we want to be cleared out immediately? So that'll be probably post launch as far as V1O to complete that so pretty soon after. And let's see, I think that's it and then what's next? So the V1 release and we're looking at completing this, these items, targeting this week. So it's going to be this by end of week, I think we're going to be pretty comfortable with a launch. Want to talk with you, Dan, as well, to see how we want to do that and any items that you want to make sure are in there. And this is going to include a release 210 with the CI system. So this has a lot of the parts that are allows to do integration with other groups like ONAP for the build system itself. And it's working internally, so it'll be public on that. And then we can start working with other folks to take advantage of those parts. The back end API system integrated to that. And then the projects and clouds planning to have for that launch. So coming in the future. So we're planning on being at KubeCon and we have an intro that we would like to do that's pretty close to what we've done in the past, a little bit of updates with what's production launch. The deep dive we're hoping to focus more on working with projects as far as integration and then start getting feedback. We actually have a live working session for that, so getting ready for that. We'll be updating all the documentation across all the different repos to be able to help people to just step in and start how would they add their project, how could they contribute. So there's going to be a lot of that just after release. And then the next big focus is going to be on app supporting a some of the components, the master service orchestrator. We're planning on targeting that component and getting it running on all the active clouds and doing the integration with them. We have a couple of clouds, BlueMix should be coming online and then OpenStack is pretty close based on work that we've done with folks on that end. So that should be pretty soon after. And then we've got quite a few demos and discussions that we want to have. So the GitOps side, we've done some review on that. We're trying to write something up on how we're actually already using some of the processes and ideas that are being talked about from GitOps. And we'd love to talk more about that. And then it would be nice to get a, I think one of the requesters to have someone from that end talk as well. So let's see. We have quite a few other demos we need to catch up with on the storage working group. The packet plus arm was deferred. So try to follow back up with Ed and see if he's available yet. And then as I mentioned, OpenStack will be following back up with Chris Hodge once we retarget integrating the code that he wrote. So he wrote most of the OpenStack provisioning code and essentially we need to update it and pull it into the new release and then we'll follow up with him. Why do we need to update the code? I thought that he would update the OpenStack code after we release the 2.0. He could, I think most of it was pretty close and so we were going to go through and see. I think it would be if there's anything major, then maybe we push that back to him. It could be pretty minor. We merged his code into a branch that was pretty close to the current. So Denver and I were going to dig through that and see if it's pretty short to update and then deploy. If it is, then we'll do it. If not, then we'll push back to Chris and allow him to retarget. So some upcoming events that we're planning on attending in some fashion, the Mobile World Congress and helping with ONAP as Dan, Cross Community Infrastructure, the face-to-face network, CICD and ONS, North America and then coupon, which we're talking about before. Any questions, other questions? So I don't quite understand when you think the dashboard is going to be live. I think that we should be through getting all the, I guess, the production by fixes and everything else that we've been working on the last couple of weeks this week. So I think we'll be up and ready by end of week as far as those parts and probably want to check in and we'll have it running at 3 a.m., like actually by tomorrow we'll be running, going through and seeing what's the results, what's the results. Okay. I'm very eager to see that. Pretty close. Okay. If there's nothing else, if anyone have any other items they want to talk about outside of what we have here. So the next working group meeting is February 13th. This is where you can get involved as far as the CrossCloud CI or the CI working group. There's a CNCFCI public list, CNCFCI working group has information as well and this slide deck was shared in the channel and we'll add those to the notes as well. Thanks everyone. Okay. Thank you. See you all next time. Thank you. See you all.