 So, we'll try. Yeah. So, I was actually worried that he's not going to wait. So, welcome. So, that session is going to be about reactions. So, you may ask why we have a GIF reaction in OpenStack Summit? Because it's actually a funny way, like, to present OpenStack and how we, like, what's the reaction of a day-to-day-to-life of a contributor in GIF. So, first of all, hello. So, you're going to see a lot of GIF. It's going to be a lot, a lot of them. It's a... Here, it's a dog, but it doesn't mean anything in that case. But, at first, this is me. Same t-shirt, same thing. So, I'm not going to blah, blah, blah with myself because that's not really the point. Just saying that my day-to-day job is not doing GIF every day. I'm actually doing some other works and been involved with OpenStack for, like, really, really long time. And I've been reading a lot of, like, mailing lists and things since the last five years, I think. So, I actually quite have a good idea about how OpenStack works. So, this website is not just myself. I mean, it's actually a lot of people contributing, a lot of people doing things. So, thanks to everyone first. And I actually used different sources to use that. I actually read, like, another blog called Developed Action, which I've been using as well as for inspiration. So, I'll be honest with you. Oula. Okay. What? So, when I get the talk, when you get the talk accepted, I was surprised. So, we actually started, like, to propose, like, I started to propose, like, different talks. They're all, like, super serious talks about APIs, about things. And I get the thing, like, I get the email, like, approved. And I was, like, whoa. That's a, okay. So, but, and after a while, I was, like, what am I going to say? I mean, like, really, like, what am I going to say? Like, in GIF, like, there is a, well, there is a website. I'm not going to put it on the website and bunch of GIF. I need to make a, like, kind of a story as well. So, so, working more on it, I get more excited. I mean, there is, there is actually quite a stuff. You can actually talk and you can actually have a story saying enough in a funny way for people who's not aware how OpenStack works and what's the day-to-day of life and actually get to see a bit of it in a funny way as well. So, the website, the website is bunch of GIF, bunch together. It's been created, like, two years ago with Emilia and Flavio and other people that have been contributing. And we post there on the website. We're not trying to just be funny. I mean, it's, which is actually pretty hard to try to be funny. But we actually try to be helpful. So, we, we, we try, like, to pinpoint stuff. And maybe we actually had, we had, we had a funny thing. It's like, there was a one, one guy that was working on Event Let and a problem with concurrency. And he actually saw one of the GIFs that was proposed by Clay with, with, you need to have, like, a certain type, sleep zero. And he was like, what? Like, there's a problem with Event Let. Can you ping me with the other guy? So, he actually used that as an informative thing. And, but we, literally, like, it provided, like, Stefano, like, a nice lipstick on the, on his, on his newsletter to make, like, a funny image. So, the story of a new person wants to start no more about OpenStack. So, at first, he would be like, whoa. So, he, he would be like, like, that would be like, wow, there's a lot of information going on. And we all know that. I mean, we all feel the pain for those ones. And at time, he would be like, whoa, they see way too much. What should we do? But after a while, things start to make sense. So, start reading about the OpenStack manual. Especially, you need a military strategy, like, to, to understand OpenStack, you know. And you read more blogs on the PlanetOpenStack.org, which is, like, great technical information. And you start really to ask a clever question on mainly needs to ask OpenStack.org. And bit of peace, you're not starting to make sense. So, you get, like, everything plugged together. You have, like, the architecture, the high-level picture. And things, like, start to make sense. So, so reading the, one by four. Reading the main list can be hard. There is a lot to decipher. So, people who are participating in the main list knows that, I mean, there is quite a bit of stuff. So, you need to go to all those plus one emails that goes through, like, when there is a coordination with, like, 10 or 15 of them. And you're like, yeah, cool. You'll see there's a bit of heated discussions that goes on with people. I mean, it's all a nice and friendly way. But, yeah. So they get, well, it's not too bad. And especially you have the long-opinated email that goes on. So you get that. And you get that coming. Well, at least some people would get, like, a TLDR the first time. So that's good. The George Clooney would be happy. But mostly, it's a lot of people bringing great things, passing together. And at the end of the day, we build stuff. You know, we do stuff. We're pretty popular. So we do kind of thing. And so now, like, you read a bit. You read the main list. You get past through all that stuff. So now you're pumped up and you start to experiment with OpenStack. So you start downloading DevStack. DevStack is, like, the entry point for most people who want to try OpenStack. I mean, in a very, very easy way. So you go and you do, like, a git clone and things. So DevStack on paper is like that. So you get, like, a bunch of pieces plugged together. They get past through. And it's all nicely configured. They go to the right place. It's all nice. But sometimes, in reality, I mean, it's more like that. And I'm a DevStack developer, so I can talk about that. But, I mean, most of the time, they get pigs. Don't worry about it. So they get this thing. So if there is an error, I mean, if there is an error, you have to dig into the log to find the issues. And after, like, it shows up to you. Like, whoa, it's here finally. I finally find that issue. So it's great. But when DevStack will be successful, you'll be like, whoa. And you get as well success at the end. And you'll be like, whoa, say, don't, boom. That's nice. So you have your own little OpenStack that you can experiment with it. It feels good. You know, like, you have your thing. You'll like it. You know, like, it's just a good, good OpenStack, a good OpenStack environment that you can do stuff with it. So OpenStack is not really hard to see. Like, it's a lot of passing that goes on after to achieve, like, some gold at the end. And with a bunch of components. So those components, you have Keystone giving you access to a token, like, in a very clever way. It's actually how it works in a log, the thing. And OpenIt. You have Nova applying its secret source to schedule a VM on an app advisor. And you get a glance fetching the right image to boot and choose, like, which image I'm going to have and which image I'm going to pass through. And that thing is, like, it's usually nicely stored, like, in an object storage, like Swift, which is, like, at the right place. And a scene there is attaching the right block storage into the VM. So you get, like, block storage that gets through. And all that stuff goes to Vianutron. So I get to say, like, it was really hard to find a gif on Nutron. I mean, that's the thing. So try to imagine, like, a packet loss at the end. So it's more, like, UDP kind of thing, more than TCP, I'd say. Well, I could have said handshakes and things, but that was more too conceptual. So try to imagine, like, a link, but you lose some stuff between. Still pretty good of it. Still working. And you get Horizon. Horizon is the pretty face of OpenStack. It's what you show to everyone in your presentation or when you ask someone who wants to use it. And that's what's good. So when you think about improvements, you can think of a thing that you actually want to fix. So there is an improvement, but there's a lot of stuff that you want to do. So you need to watch that gif carefully. So the guy is, like, starting, like, to have, like, one little thing. I need to fix that. Oh, OK. That's the thing that I need to fix now. So I'm going to go and it goes in loop. So I need to watch. And it goes forever. So basically, like, there is always, like, things like to fix. So now it's like you find a bug. You find something to fix. You take your body armor on and you go have a mission, like, to fix that bug. So you fire your digital and you start coding. You probably want to look at your screen because that would be a good idea. Or you get those over the lines stuff anyway. But you start, like, a crazy coding session. You feel open tap. So you start your thing, but you see, like, your unit tests are not failing. So the go, the go, pass, pass, fail. So you need to, so you keep adjusting the code. So you start to adjust the code. You fire the pizza, the red bull and stuff, and you fix your code until it works. You make sure that it's as well PEP 8 or Flake 8 compliance, which is our code checking compliance. So that's the way, that's the best way to fix those ones. You just throw up the code. Yes, that's it. You try to avoid the most common mistake, like forgetting to sort the input line or things like that. And now it seems like TOX seems to pass. I mean, surprisingly, by luck, TOX gets all green. So you're all good. That's a lucky kid, man. So you're part of your patch and you're ready to submit for review. So that's, you think it's a masterpiece. You get it, like, really well done and everything. And I was like, I'm going to show it to everyone. Before you show it to everyone, you actually need to wait a little bit. You wait patiently until Zool picks up your patch to learn other things. So if it gets busy, you have to, so you're not trying to be so it's normal. You just wait. You can log into Zool. To see the progress, you get some progress bar. And since they introduced the progress bar like a year or two ago, now it's like you can just stay like that and watch the green thing until it's gone. It's gone. And this is where you have a failed thing again. So you're like, whoa, okay, I'm going to start again. So another crazy coding session. You reach, oh, okay, it's coming, it's coming, yep. And you reach it and receive it again. So you just like code, code, code like crazy until you get your thing fixed. But things, but things failed again for some unknown reason. Due of an infra issue. So you need to watch, whoa. That's pretty helpful. Well, it's not like that, like that all the time. You could try to keep it a recheck notebook to get Jenkins to recheck. So that's what you do like a lot of times. So you have on Garrett, you have a way to do that. And you just do recheck notebook and after you would retry. But it's actually something greater than that. So you keep your crime. You don't try to panic, not like that guy because he's a bit panicking on his keyboard. Okay, the refresh is a bit... So things like if there isn't an infra issue, you're sure going to see it on IRC. You'll see all the devs complaining, what's happening? Doesn't work? Doesn't work? Is that working or is that not? And you'll see it like there is something happening greater than just your code that's failing. So thankfully we have an awesome infra team that can help you. So that's the infra team. That's the infra team that is all coming. And those guys are awesome by the way because they work like 24 hours and they're always here and they're always helpful. I mean, I get to say. So it's a great thing for them. So the issues start to get fixed. It's like actually some kind of case people install that are going to explain in some way that gets dependencies caching and like magic. It gets all fixed. So okay, cool. Nice. So now Jenkins is happy. And has passed all the tests. So that's actually a very happy Jenkins. A little bit of issue in between but it's all good and nice. So we are going to call the core reviewer. So the core reviewer is on his way to review the code. So he's coming on the fix. So first of all, if you didn't have a unit test, if you're not going to like it, that's for sure. That's easy to throw this thing away. That's for sure. So sometimes you get some very unfortunate going to nitpick you. That's the nitpick Nazi team that's going to come over. Watch. That's not standard. This is not good enough. That's a pretty helpful thing. The worst problem is giving minus one for a minor phrasing change, especially that most people are not. So it's a bit like, whoa. For some issue, there's nothing to do with your patch. So we get a bit angry but not that much. So you reach it more until it gets right, especially like you try to walk with people until it's one way or another. And it goes forever like that. And not like you're going to get the plus one starting. So you get all the thumbs up. Yeah, you get like 1,000 plus one coming through and coming. So you're actually quite good into it. But you need that last plus two to get it approved. And that's some core developer waiting. Like that's the way I imagine on my review, is that what they were waiting for. So you ping them gently on ISC for review. Please, please. Sure. Thanks. Sometimes they're going to help you and fix the issue directly on your patch. So they're going to help you and going to do an iteration on your patch directly. I can do that. And they go until the fix. Sorry, I saw it after. So you finally get that final plus two approved. So your patch is approved. You're all good. You're really happy about it. So you first you make sure that it takes the reviewer. Don't scare them away. Don't try to be too much. But you just hope so it gets first to approve. But you just need to be sure that it's not going to last failed before the last checks. But it got all right. So finally you have merged your first two open stack. Well done. So we could talk more about the life of open stack. It's not just like the new contributor. It's a lot of stories. So some of them will be like more private jokes that people who contribute open stack would know. But that's some reaction. So sometimes when you agree about a feature to implement with open stack with order, you talk to orders, you get some weird faces. But we kind of agree between each other and we find a common ground. Or when you miss the deadline just before the end. Sorry about that guy. The deluge of CI emails when you send a review of a CI-backed project that you get true. Or when you try to convince the real manager to allow the feature to go in. So you're doing like the crazy dance. So some people ask me if I can do the dance. But I'm not going to. So that's the dance you need to do to cherry if you want like a new one. That's very nice. When you have to start to look over upgrading your open stack between releases, between one release to the other. So you look over your cloud and you're like, whoa, what did I do? Yeah, right? Maybe not. It's not always like that. We all know that. When you start SQL, it can be migration. So for the people who doesn't know SQL, you need to make sure for the upgrade of the database and make sure that you're not failing. So it's a very, very kind of tricky thing to do in a proper way. So it's a bit like those guys doing the upgrade. But there is one thing. Like when you enjoy co-authoring a patch with another fellow, you put co-authored by inside the open stack commit in the review. And you're like, whoa, flying. Well done. When you enjoy just helping another open stack user, he just thank you and you're just like, we are welcome. But whatever feeling you have at the end, like contributing to open stack is usually like an awesome experience. It's a lot of contributors with your documentator, translator that does a lot of things together. And there is a lot of things that's happening between the things. So at the end of the day, we still need to be very proud of what we do every day and bringing that platform all together. So more contribution appears on the open stack newsletter. So it's usually on Fridays. So that's when you receive the newsletter. It's usually before the weekend. And we're waiting for your submission to on Twitter, on the OS reactions whenever you can. So I'm not going to ask if there is any questions, because that would be surprising. But one thing we can do is someone have a reaction to share, like to everyone here. I mean, it's welcome to do it. But thanks for attending.