 I think Google pushed for, like, there's a control order that kind of thing that we deal with. I just don't think there's ever thought of, like, we're going to have to solve another problem in front of this. We're going to have to solve another problem in front of this. So, I'm going to close it. Well, there's no provision until the application, actually. Because there's a little bit of freeing. We're going to do something about it. So, nothing that... Honestly, it's kind of like a conservation of resources, too. We may have a user that creates a really bunch of lines. You never hear about it. You know, because they never know what's going on in the application. They didn't tell you, actually. I mean, there's no reason to have that life cycle in different ways. You find them immediately. That way, you realize, actually, that you need it before you find it. Now, I'll do the other thing I can think of is the slight increase in provisioning time. Where you have to wait for volume to bind and bring up the application. So, maybe it's going to take 25 minutes for provisioning to occur. And maybe it's going to occur during the application to bring it up. Which, I mean, also suck any minutes out of the internet, so... Yeah, so... Maybe it's okay to like... I mean, does it... Does it even take all that long to provision, especially... It depends, I mean... Or something we don't... If it's... If you're talking about, like, a sand or something, maybe you actually... I mean, it does take a long time. It does take a long time. I mean... Are you making a fee up on the start clause? Whether this... Whether this gets back immediately upon... Submitting a claim or when the application... Well, I could see... Good afternoon ladies and gentlemen. I would like to introduce Neil Smith and his link often with Special Desk. Neil writes at Red Hat and does stuff like this for a living. So, let's hear it for him. Okay. So, I'm Neil Smith. I'm part of Jen's team in P&T at Red Hat. I work with a couple teams on AOS, the container storage team, and the scalability team. And I also work on the composer team in RHEL. What's the AOS team? The atomic open-shift team. And these guys are more... They're all cube guys, and then... So, as well, Kubernetes as well. So, who knows what lean is? Has anybody heard of the word lean? A few of you? So, has anybody heard of Toyota? Okay, so... Toyota, at one time, was almost broke. And they didn't have enough money to buy their material at, like, a normal car maker. And they came up with, just in time, ways of manufacturing. And that's sort of the basis of the lean philosophy. And that sort of started it, went into something else, called Kaizen, which is about continuous improvement. So, some people, whenever you're, like, sort of a lean evangelist, you apologize for the terminology, because it sort of gets attached to eliminating waste. But it's really about consistently improving and getting things as quickly as possible from the beginning to the end and to the customer, so you can make money. Or you can do it in many different ways. Hospitals use a lot of lean technologies to try to eliminate a lot of the waste so that they can get people in and out of the hospital and taken care of faster than sometimes they used to. So anyway, so lean copy is a way that we can run some meetings. People have been to meetings where two people start blah, blah, blah and for a long time, nobody else cares about what they're saying. And it's a waste of time for most of the people. It's a way to democratically run a meeting so that your interest keeps going and you're, you know, kept engaged through the meeting. It's using something as everybody know what a Kanban board is, basic Kanban board, so you structure the meeting in a to-do, doing, and done way of running the meeting. What we'll do first is find out what we're sort of interested in. I have several speakers here. Brad from Container Storage and he knows Kubernetes really well and containers. He knows other things that you can ask him about, but you might not want to. So Russian nesting dolls. We have Matthew Miller from Fedora. Allison Matlock, who's Matlack, who's a DevOps Agile Transformation person. We have Matt Nassim, who's our Rel Evangelist and knows Linux really well and also likes Process as well. We have Harold, a QE expert and also figured out how to get QE and process-wise, you know, getting QE done within the sprint, you know, real definition of done stuff working so we can talk about that. And Amanda, DevOps, open-source community stuff. So we'll split into groups if you're really technical, maybe with some of these guys or if you just want to do Process, we can all just talk about it, but it's good with groups of seven, sort of, you know, just like normal team size, right? So the first thing that happens, we'll split up. The next thing that happens, you guys are going to get some posties and depending on your group, you'll pick up some subjects that you're interested in talking about in that group. You're going to say, I don't even know what DevOps is. I'm very interested in that. Could we talk about that for a bit? Or we're trying to do the specific thing in DevOps. We can't make it work. Has anybody had experience in that? Let's talk about that. These are the things I tried. And in technical world, you guys will do something... Kubernetes storage. Yes. Very exciting. Can I amend my expertise because the DevOps community is something else. Oh, okay, what is it? Container builds, at least pipeline, tooling around R and secondary stuff. Oh, cool. Okay. So, that sounds great. Okay, so then we... So we do the voting. I mean, do the subjects. Then those go into our backlog, which is the to-do area. And then, since it's all Democratic, everybody gets two votes and they'll put their votes on those post-it notes. Then we'll look at the post-it notes and then most votes goes on the top. And we put that one into doing. One of the team members then will have a phone, get their timer out, and put a five-minute timer on it. We talk about that subject for five minutes. After five minutes, everybody votes. And they say, I don't want to talk about this or I'm mad about it or I do not want to talk about this anymore. And you follow the Democratic voting. And then if you decide to keep talking, go great, but if you don't, your moves are done and you're done. How do you pick the next topic? Then it's the next priority list. So you just keep going from the most voted to the next most voted to the... How do you come up with the priority list? You vote. Why don't we show how many things we have to come up with? So everybody gets like three minutes to write a few subjects that they'd like to talk about. Then everybody, the whole group, then votes on that whole list. What about things that are tight for votes? Then you just sort of put one on top of the other one. You know what I mean? Like normally you'll get like something with five votes, something, two things with three votes. So you don't really care about that. And then a bunch of twos and then nothings, right? So that's sort of how it often works. We're already seeing the technical people needle the process. So this is more container storage people if anybody wants to join that area. You guys probably don't want to be in this thing because... Oh yeah, you can. So then if you want to you can join that eight. There's other four there. Any other people want to... Does anybody want to talk about like DevOps, agile transformation stuff? Okay, why don't you guys take the back corner there. Get in a group. Any other... Anybody else vocal about like wanting to talk about Linux or REL or... What I'm talking about is we can do that. So this makes me work really hard. No, and you can talk about it. If you want to talk about what is the best thing you can check to see back, yeah, that is fine. Oh, I mean, check for public. For what you used to use the best thing that it was... All right. You guys don't have post-its? Okay. What would you guys like to do? Post-its. Post-its. Oh! Sorry. Yeah, I know. So... Okay, so groups, I'm assuming right now, you guys are all right and dead. Some questions or subjects you would like to talk about. I'll give you another two minutes to do that. And then we'll start the meeting. Are you waiting for discussion? They said we had too many times. Any questions or topics you want to ask? Any questions or questions? I'm just going to leave it at that. Good morning. Good morning. We thought you went to the background. Good morning. I love you. Hey, Dan. Now everybody's here. No, that's relevant. We need to talk. We need to talk. All right. No, no, no. We're just talking about technology. Dan. Tech. What are you doing here? I'm here for you. Q&A. Action. National Transformation. And you? Let me do this for you. Can you do that for Dan? Ha ha ha. Is this funny? Yeah. Is this funny? Yeah. Is this funny? Yeah. Is this funny? Yeah. Right. Just make it confusing. Action. All right. So we're here to talk about brand new technology. But we're going to talk about brand new technology. So we're going to talk about brand new technology. So you'll just realize that you've been doing a lot of stuff. Right. So you can take a moment here to write down anything you want to talk about. Want to know more about technology. So all of you have a two-boat teach. Container people. Just container people have very experienced problems with technology developers. I don't know if you've had that. It doesn't matter which doctor it is. All of our speakers. That's true. So that should be a good decision. You guys should be smart. That's funny. Yeah. That's funny. Yeah. So you guys should give Dan a chance to write an idea. Yeah. Okay. Let's talk about it. And then you can pick somebody who's going to be the five-minute timer person. So make sure you guys pick somebody who's the five-minute timer person. Okay. We do have a like for the next couple of minutes. Okay. Okay. I'm here for those of you who already have finished. So Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. Dan. You guys, did you guys vote? Okay. Each person gets two votes. And so sometimes you need to raise them up loud because you can't create a different person or anything like that. And also if they don't make any sense, let's start with Brad. And then you just, prior to that, just put your vote on. I'll be right to watch, right? All right. All right, so we've got... Yeah, wait. I don't know what I'm saying. I don't know what I'm saying. I don't know what I'm saying. I don't know what I'm saying. I don't know what I'm saying. I don't know what I'm saying. I don't know how any please to leave and comment. I don't know what I'm saying. All right. So when we have some- Go ahead and give a vote. Sh Were you going to get him- I don't know if they. Don't get me. I'm going to take this. Because I can'tción and it's bad. I think that is So literally, size as mass, inertia as mass. Inertia as mass. How are we going to deal with this? All right. So that's going to be a strike for a location besides pertinent and dystopian narratives. And just to be district of writing down anything. Yes? We raise two votes on the vote. And then you just vote on two dots on each vote. Two dots you get and put a dot on the third one. So you like to put one on the dot, the other on the dot. I'm just going to say to my names. Yes? You can't eat your stuff. All right. Hold up. Give me one. All right. I'll throw one more. Fill with it. Is there any interest in talking about here? Mine. Mine. I've been worried about where. All right, can we start talking? Now we take the next question. I just want to make sure that it's normal and that there's room for discussion. And I'll be sure to tell you who will say that this is right and why I don't agree. Maybe not even the story. I don't know. Sorry, people can't hear me. I just want to make sure that it's normal. All right. All right, let's head off to those two votes. I know that this is right. All right, now I'm going to put this on the line. You guys are slowest. All right. I'm going to put this on the line. It's not a race vote. But if we have to do that, we can try and do it. And you can... Don't have to go in order. I'm going to put it on the line. All right. I'm going to put this on the line. I'm going to put this on the line. I'm going to put this on the line. I'm going to put this on the line. I'm going to start already. We need to clap. We need to do it right. Make something win. I'm going to put this on the line. I'm going to put this on the line. I'm going to put this on the line. you just put them in order. We're missing one. I think no. So we do order them to do book. Yeah. And you only have to do like, hold probably the ones and the twos. I mean, the threes and twos. Or maybe some of them. Don't even worry about those other ones. Yeah. So then just, you can just put that three right up to doing. That's going to be the first thing you're going to talk about. All right. So welcome to this discussion of assistant managers. Who wrote this for them? All right. So we get to start off. I'll start the camera as soon as we start talking. Yeah. So we think there should be support. We don't reply to the person that needs this. We're going to get one strap. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. All right. Yeah. Yeah. Yeah. Woo! Sorry. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. So all right. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much. Thank you very much.