 Hey, Alex. Hello. How are you? Good. It's good to see you, man. Yeah, see you here. Right on. And I think we'll be spending some time like in the next hour or two today as well with the CNS day content planning. So you thought, I hope you missed me, Alex, because it looks like you're gonna get a lot of me now. We love you. You are best. How's that? How's everything going for you, Alex? Oh, no, all good. All good. Super busy, but all good. Are you getting ramped up for Amsterdam? Yeah. It's always super busy. There's always a lot of, let's say, motivation that comes along in time for KubeCon. This is the gist. I get a whole lot done right around the two months before KubeCon, let's say. I know. It's like, and then you have like projects, like in project review requests six weeks before, you know. Yeah. I wonder what's driving that? Are the meeting notes linked from the RICO? Or you just put it in the chat, Alex? Yeah, so I put the Meteor agenda there. Afternoon. Evening, depending on time zone, everyone. So I just posted the agenda in the chat window. We have a fairly long set of agenda items to cover today. So I think we won't hang around and we can get right through it. So the first thing on the agenda is the Rook project. So the Rook project was introduced as a CNCF project probably 18 months ago now, 24 months ago. Yeah, January 18th. And it started off as Sandbox progressed to incubation and then the Rook projects are looking to upgrades to a graduated project. So I've invited Jared and I see there's Travis here on the call as well from the Rook team to kind of give us an update on the status and what we are going to expect from the due diligence process that we need to just cover off from the SIG to get the project over the line. Cool. All right, Alex. Thank you very much. Let me go ahead and share my screen so I can just walk through a couple of things real quick if you don't mind. So just to put things into perspective, I don't think we're yet at the stage where you have a formal presentation or a formal PR yet, right? So this is the pre-work. Yes, exactly. Can you see the slide deck here now? We can. Okay, awesome. And actually the first slide here, Alex, is about what the expectations are for today. So we went through the process for going from Sandbox to incubation last year over a year ago and we did the whole formal presentation to the TOC and writing up all the due diligence and a pull request to the TOC repo, all the criteria steps. We went through that whole thing and we're in the middle of that right now for graduation, the graduation criteria. So after talking to our, you know, CNCF liaisons, Amy and Chris and a check, you know, one of the things that we learned is necessary as a step this time for graduation is to talk to the SIG and get the review and diligence done by the SIG here. So we wanted to just go ahead and get the conversation started today. We are not ready for a full proposal, but we want to go ahead and figure out where do we have gaps, where are some obstacles and things that we should be concerned about. And, you know, what are the next steps that we need to need to work through? So the goal, the hopeful goal here is that we would be able to finish the graduation process and all the diligence and have a vote by the TOC before we've gone and answered down, which is at the very end of March. So that's the hopeful timeframe we have here. And so the quick introduction about Rook, we'll go to this quickly here, is that the whole Rook project here was started about three years ago and it is a cloud-native storage orchestrator. So what that means is that it has a lot of automation and through custom controllers and CRDs within Kubernetes that automates a whole bunch of storage management and deployments, operational tasks. And it started off as being a operator specifically for CEP, distributed storage system. And around the time of getting transitioning from sandbox to incubation, we went ahead and started an effort on a framework to allow other storage providers and solutions to be part of the Rook project and to get the benefits of orchestration and automatic management in Kubernetes environments. So as Alex was saying, we got accepted into the sandbox stage in January of 2018. It was the first storage project to be accepted into the CNCF and at that time our sponsor was Ben Heineman. And then we went to the incubation stage in September of 2018. And so for this next stage graduation, we have a proposal. We're going to be talking to Saad more about that for Saad and his new, one of his first tasks as being a new TOC member is to hopefully sponsor the Rook project. So hopefully and Kubernetes, Saad's on the call. Yes, he is. I saw that. And I've got a meeting scheduled with Jared later today. Yep, so we'll be chatting. And thanks for all your effort and support over the years Saad, for sure. So let's go ahead and call it real quick. Some of the things we know are to-dos right now, things we have not done. So submitting the diligence poll request and official proposal to the TOC repo, that is going to be all written up and submitted formally. We have a list of production users and adopters of the Rook project. We need to finalize that and flesh that out a little bit more. We have a couple of governance updates that Travis will be walking through in a second. And we are updating or implementing our security disclosure process. So we have a poll request that's almost done with that. So that should be done soon. And we also know that we need to do our core infrastructure initiative, best practice badge, like 80% through that. And so we need to finish that off as well. So those are the things we know we have not done, the gaps we're aware of. And just a quick walk through before I head it over. Sorry, just a quick one. The security audit, that's being completed, but you just need to cover off the results and stuff. Yes. So the security audit is completely done. And we did that with the trail of bits. They also did one of the upstream Kubernetes security audits. So that's fully completed all of the issues were identified in the, I think that's on one critical issue that has been since fixed and patched and released. And the full write up of that is published and available. I think we need to link it from the repo. So it's more available in public, but that's done. This year is just a security disclosure process of if someone in the wild finds the security bug, how do they responsibly disclose it? And what is our process around that? So the audit is done, but then the process for finding new security bugs and disclosing them is the thing that's not done yet. Perfect. Yep. And then real quick, some numbers on a slide here. So on the left is what our stats were for the project in the community at the incubation acceptance stage. And then on the right is where we are current day. So, you know, container downloads is another 10x from sandbox to incubation was 10x from like 1 million to 10 million and then now 10 million to 100 million. So the project continues to grow in popularity with GitHub stars. We have a lot more releases where, you know, doing a lot more agile release process there to get more fixes out contributed a lot of most most everything is at least to 2x to 3x growth since the incubation phase. So you know, the community still expresses interest and, you know, they're gaining more adopters and the project continues to grow pretty healthily with both contributors commits and usage as well. So I'll hand it off to Travis to talk about some of the actual accomplishment in work. Yep, the real work we're getting down here. So since since incubation, we've definitely had a lot of a lot going on in the project. We have basically a quarterly cadence as far as getting releases out. So from vo.9 up to 1.2 was our latest release in December. You know, some of the major things going in, like edgafast, Cassandra, NFS operators are all new back in the O.9 release, UGBI-DB in 1.1. So up to six storage providers now in Rook. There are a couple others in early phases of called a PR open right now for Apache Ozone, which is a possibility. But anyway, stored providers and making it available for others has been a journey. Two of those, SF and edgafast have been declared stable as far as the CRDs and supportability. Like Jared said, we've completed the security audit. We don't really have time to dive into all the features of all the operators, but maybe one dimension is CSI drivers for both SF and edgafast have been implemented and consider those stable and lots of other features. But we really will miss the flex volume driver. Are you sure? No. It'll be around for a while, but CSI is definitely the future. And then we've been collecting our production adopters. A lot of them, probably, I think Jared, you said 60% of the people who surveyed don't want to publicize what company they're from. So there are a lot more than this list, but here are some of them that said we could publish their names. So we are following up with them to get quotes and things for how they're using Rook and how big their clusters are and things. Also, I guess, missed in this list, there are products based on Rook and production. We haven't collected those stats either. I know at least Red Hat and Sousa and maybe others are building on it. So that's another avenue. But we didn't query those users, just the upstream people. And I think that's about it. What did I miss, Jared? No, I think that's really what we wanted to share today here. And we know there's a busy agenda today, so we don't want to take up too much time. But if there's any obvious feedback or we can follow up in other channels, like on the mailing list, or you can email us directly, and we can talk about what are the things we really need to focus on and worry about such that we'll have good chances of proceeding with our next steps for the graduation. Jared, I think this is perfect. This is kind of like the textbook process that you follow through sandbox and incubation graduation. I don't personally see any major stumbling blocks. What I can say is that, you know, just the nature of the TOC's busyness before KubeCon, you should try and get those last checkbox items wrapped up in the next week because practically it takes a couple of weeks before there's a TOC meeting and then they vote, and people are out of office. It can take up to a month just to get that process completed. So it sounds like you've got most of the checkboxes checked, and it sounds like you really know what's going on here. But just leave enough time for the bureaucracy to take shape. Yeah, that sounds great, Quentin. Thank you very much for that advice there. Brilliant. Okay, so I think the follow-up item then will be to if you finish off those checkbox items and the security order, etc., and finish off the presentation, then maybe at the next SIG meeting we can do the formal presentation and have that recording, and then we can put together the docs for the SIG box. Alex, your voice is fading in and out. Oh, sorry. Can you hear me better now? Yeah, much better. Thanks. Okay, sorry. So I was just saying, so the next steps is if we finish off those checkboxes and then have a proper formal presentation in the next SIG meeting, then we can have that recording, plus the due diligence doc, and our recommendation for the TOC votes for the next, for the early, early March, I guess that would make it. Yeah, that sounds great, Alex, and we'll follow up on all that. And we'd love to be on the agenda to do the proper presentation proposal next SIG meeting. Awesome. All right. Thank you. So we'll put you on there. Should we assign somebody from the SIG to do the kind of formal review? Yes, we are great in needs to allocate someone. I'm guessing that's not going to be you now, right? Because you're on this thing. Right, that would be of interest, yep. Yeah, I'll just be clear. I don't think there is a conflict of interest there. I think you can represent the TOC and the SIG, and by the way, congratulations on. So I wouldn't personally worry too much about that unless there's some major concerns that this seems like a very straightforward graduation process to me. Just to be clear, the majority of the due diligence happens in the migration to immigrate to, what is the word I've just lost? Incubation. That's the one. So unless there have been major regression since then, it's mostly getting this badge, getting the security order done, making sure that you have enough contributors, enough maintainers from different companies, etc., most of which it seems you've done. You're just getting the final reports together. So we can get somebody else to do the due diligence, but the due diligence is essentially making sure that all those things have actually been done. It sounds like they have, so there's not much to do. Okay, that makes sense. I just don't want there to be any question or my double involvement potentially derailing this. So I think it would be safer just to have someone else do it. Yeah, we can do that. Before we, one last item just before we move on from Rook, are there any particular reservations that anyone on the call has that we haven't done the due process here? Seems to me like we have. Okay, thanks. I think we're good. Okay, so I added in, so just moving on to the next item on the agenda. So the Harbor Project, at the last meeting we put in links for the different PRs and the DD docs and Saad was allocated to do an overview with them. With the project, has that gone ahead? I have not gotten a chance to follow up on that. That's still a to-do for me. Okay. So this is, this is Michael from the Harbor team. I mean, the, what we've done with Sea Grantime and I put a link there is, they, you know, they're also as busy as everybody else. And they've asked me to create a PR that basically kind of drives some of the due diligence that the SIG was supposed to do. And that PR essentially is just one file that kind of puts all the checks and balances that the SIG is supposed to do. And they were going to just go through it really quickly and verify it. They, that we've done what we're supposed to and answer in those 10 questions. Saad, we really appreciate it. If we have some time to look at it, we're really trying to at least get a decision from the TOC if we're going to graduate before Cubicon and we've been on hold now for like almost four months. So it'd be good if we can actually get the process moving a little bit. Yeah, I'll try to find some time in the next couple weeks. Thank you. I'll reach out to you on Slack. Thank you. Do you want me to create a similar document like what I did for SIG Runtime where all you have to do is with your good with it, you just merge the PR? Yeah, that would work. Okay, I can do this. I'll do this and pink you. Perfect. And just shoot me an email. My email is on GitHub. That'll be my way to track this. You prefer email or the Slack? I do email. The email. Okay, I'll try to find your email. All right. Thanks, Michael. Awesome. Okay, so then just an update to the team. We completed the review of the Dragonfly project. We submitted... Lex, you're fading away again. Oh, no. Can you hear me now? A little bit better. Sorry about that. So we completed the review for the Dragonfly project. We submitted a couple of queries to the team. They've provided the replies this week, which is great. And I think going through the replies, this covers off the queries I had anyway. So I am going to give this a thumbs up and put an addendum in the DD that we covered this off. And we can have that closed off from a SIG review point of view. Okay. Then, moving on, this week, we had... No, late last week, sorry. We had the SIG chairs and TOC meeting where we covered off the process and templates for SIG project reviews. The good news is that this is now being agreed. We have the process which Liz had been driving, which is covered in the slide deck, and she has created a PR to update the existing criteria and process on the TOC GitHub. Erin's templates, which is basically a merge of templates we already had in the SIG storage together with the templates in SIG apps has been combined. And we put it into the issue 344, which is linked there. And that template was agreed on too. So this needs to be finally converted to... The issue just needs to be converted to a PR so it can get approved. But I think we now have a proper easy to follow process and set of templates that we can use for sandbox incubation projects. So I think this is a really good milestone between the TOC and the SIG. Thank you everyone for the work involved to get us to this point. Okay. Next point. So we have two sets of edits, which we're looking to merge into the landscape document. So the first being the database update stock, which Sugu had written. I've made some changes and asked for a review. Sugu and Quinton have put in their comments, which all look great to me. So I'm just going to add that into the document. It would be great if anybody else who has comments would have a quick look at that database update document, which is now being outstanding for a little while, but we would love to close this off. So assuming there aren't any more updates by the end of this week, I'll look to merge this into our landscape white paper. Similarly, Jing had an action to update the orchestration and management interfaces section to reflect the current state of the market. Given that over the last 18 months since we published the white paper, there have been sort of a number of changes around CSI and things like that. So there's a link to the updated doc that she has refreshed in the link attached on the agenda as well. And she has also sent it out as an email. It would be really great if people could review that. It looks good to me. And again, assuming there are no major review points this week, I'll look to merge that into the landscape documents. And what this will give us will then be a landscape document, which is sort of refreshed for 2020 with the database updates and will become sort of our 2.0 white paper, which we will then look to publish and publicize and market, etc., in the run up to in the run up to KubeCon. Any comments or questions on that? So this is so good. That optional section, we are going to use that content for the use case document, right? That's correct. So we're going to move that optional content into the use cases and I'll cover that in a little bit. Sounds good. I think that was the person complaining about that previously. But now that Alex's table is in there, I'm very happy to move the optional stuff to the other doc. Awesome. All right. So it sounds like we have agreement there. Jing, did you want to add anything around the management and orchestration updates that you shared out? No, just if someone could review it and add comments. That would be great. Great. Okay. And then we have the performance and benchmarking paper. So the author team met last week and we, no, the week before last now, and agreed on some of the work that we needed to do and started with the updates. We've, Paul Sobi has joined the sort of the white paper team and he's contributed a large chunk of content around the common pitfalls and considerations. So we've kind of got four or five pages there of new content, which is progress. And the rest of the team are working on some of the other benchmark tool documentation. Also, I'm following up with Josh after the TOC call. He mentioned that there were some other tools that we may look to consider that he had been working with as part of the Kubernetes benchmarking performance SIG and we'll probably look to see if there is some commonality or some overlap that we can include in here too. So again, looking for some feedback or points, we're all specifically, we're kind of interested in, are we missing anything obvious? Or if there are overlaps that you are aware of with other documents or other initiatives, it would be kind of good to point them out so that we can put the appropriate references in there. But otherwise, we continue to work on the DOC with a name of having a draft available to share before KubeCon. Any questions on that document? I just had a quick look at it. It looks fantastic, Alex. I think this is going to be a huge benefit to the community in general. I can take a look at it in the next week or so and give you some comments, but superficially it looks very well headed in the right direction. Brilliant. Thank you. All right. So any other things on that or can we move on? Wow, we're going through this agenda pretty quick. So the use case documents. So just to recap on this, the use case documents is something we wanted to work on and has also been the subject of sort of end user feedback. So following on from the content we provided in the landscape white paper, we agreed to put some use case information together to kind of show some of the best practice considerations for specific sets of use cases. And we've had a lot of deliberations. Louise had put together a template, which we had discussed quite a bit. And following some of the feedback, we kind of sort of regrouped and tried to figure out a way forward. So Louise, Erin and myself met last week and we agreed a couple of steps to move forward. So first off, we're going to move the current template, which is in GitHub, to a Google doc to make it a little easier to collaborate. We're going to change the focus of the template so that rather than being specific product use cases, they will be focused on use case categories rather than the specific product. And this is to sort of address concerns of creating unfair bias or showing preference to any particular project or vendor or whatever else. So specifically, we had a bit of a think and again, this is kind of open to debate, but we kind of thought, okay, which categories do we want to have templates drawn up for? And we put together databases, message queues, instrumentation. So to cover things like, say, Prometheus or Thanos use cases, key value stores and object stores. The template that we have currently is pretty good, but we're going to add in we're going to add in a table that will cover the storage attributes from the storage landscape documents. So the availability, consistency, durability, performance, scalability, etc. And we will also add in, we will also add in a sample of the options, similar to the content that Sugarhead put together in the database document. So the options section from the database document. And that will form the basis of the new template. So I'd really love to hear your thoughts on this. Are we heading in the right direction? Are there any, you know, serious objections to this idea? If not, I'll pull together to Google Doc and send it out for review in terms of a template. And then hopefully maybe we can, assuming we can get agreement on the templates, we can move forward with that template and create, you know, the first category. And sort of just make sure that the template works. Thoughts, comments, violent objections. Yeah, I totally agree, Alex. I think that's pretty much a feedback I gave you guys a while back. So I'm totally supportive of what you just proposed. Violent agreements. Well, that's cool. Okay. So in that case, I'll proceed with that. I'll get a Google Doc circulated in time for the next meeting. And maybe we can spend some time at the next meeting to review the template. And then finally, the last thing I had on the agenda was there is some logistics and tidying up that we'd like to do on the repo. So we'd like to have, we'd like to update the repo with things like the list of projects that we're covering and their current status and their current sort of category, whether they're sandbox or incubation or graduation. And maybe put some links to the projects and that sort of thing as well to get some publicity there and to cover projects that have recently been introduced to the CNCF like TribalFS and Longhorn, for example. So I'm happy to do that. But if anybody else wants to volunteer to do a PR, to add that list to the CIG repo, I could do it some help save on time. Alex, I'll take that up. I'll do it. Awesome. Thanks, Karen. I'll just put that down. Okay, so unless anybody has any other agenda items, we've actually gone through a fairly large agenda in a record amount of time. So you can get 25 minutes back. Thank you. Asad, I want to head and create the PR already and send you an email. Perfect. I'll take a look at that. Thank you. Thanks, Michael. No problem. All right. Take care, everyone. All right. Thanks, everyone. Have a good day. Good to see you guys. Bye. See you. Bye.