 Okay, so I want to get started Today's lab is a little bit time-sensitive in the sense that We're gonna probably need every minute to get everything set up installed and get you to be able to step through operating a Open stack a little bit. So I don't want I don't want I don't want to run short. So I'm gonna get started now So first and foremost, thank you for coming. I know it's Thursday at 11 a.m I know everybody's tired ready to go home But I appreciate you coming out. I will try to make this as enjoyable as possible and Throw in as much information as we can in the next 90 minutes. Okay, so we're gonna be deploying OSA OSAD OSA, it's the same thing. They keep changing the name. It'll be a different name next week. Don't worry about it And we're also going to Operate OSA what I mean by that is we're gonna do some things that you would do as a cloud operator Everything that's out there now right open stack is usually about the user or the developer But what about the guy who actually has to run this thing? So we're gonna step through some scenarios that you would do as a cloud operator and demonstrate how you can use ansible To make your life a lot easier when stepping through those those instructions. Okay, so So getting started a little bit about me. I'm a cloud solution architect at rack space The division I work in is called RPC Which is specifically we I am in charge of building open stack clouds So we have a lot of private clouds at rack space, but I build only private clouds built at open stack That's some of my information there for free to hit me up on Twitter LinkedIn GitHub I have some stuff out there and get up as well as I have a blog that you can find some useful open stack information Over 17 years of IT. I am a New Yorker Funny story is I'm actually moving to Texas In two weeks, so I'm a New Yorker Texan at this point always been a cloud advocate and You know hybrid clouds are my favorite So I like doing private and public and there's some other information there I am a DJ and a motorcyclist, but I forgot to put that on there Okay Cool neither just some of the companies that I've had a chance to work for but we don't care about that stuff We want to learn about open stack So some quick ground rules and I goes, you know, you guys already know this but Turn your I'm not gonna ask you to turn your mobile phones off, but if it rings I now claim it I have an iPhone 5. I've been looking for a nice success. So anybody who has a new phone make sure you leave it on and let it ring Okay, asking questions is very important. So don't hesitate to ask questions If you have to have a side conversation or you need to take care of something for work I know we're all professionals here. Just please go outside so that we we can get a little keep focused here Again, we already know about the small groups And yes, this is where all the materials will be there. It's actually there now So you can go down there and to get up and take that take a look that that link will take you to get up So before we get started As I said those of you who have the student handout it has some information on there that that you'll need for the lab the student ID Instructions are how to connect to the deployment server and also the IP address of the open stack server You're gonna do so what we're gonna do today is we're gonna use a deployment server to deploy open stack to the open stack server Okay, so that's pretty much what you would do in the standard open stack build You would use some sort of deployment server to build your open stack environment Specifically with also you want to do that because when you bring down all those playbooks and build open stack using those playbooks It creates like a dynamic inventory on the deployment node So you want to have a server that has that that dynamic inventory so that you can keep doing things to your cloud It just makes things easier And again, we will be working with a command line in Ansible So if you're not familiar with that or you feel uncomfortable whoever hopefully your partner with can take on those those responsibilities But it's really easy stuff. So don't worry about it And again, we will be using the open stack client OSC to do some of the Ansible stuff Which is actually new the new client for open stack Okay, oh, I'm gonna put it again when you get to the lab stuff But yeah, it is when we get there's another slide to have to have the information again. Okay, take the pictures one two three all right So So if we're gonna start yes Yes, yes, that is lowcase YZZ capital a Zero and then the capital letter O Don't blame me for that. That's Google's fault. I have nothing to do with that. So deploying OSA If you're not familiar with what OSA is It's a combination of using Ansible to deploy open stack, right? It's to me is the easiest method that I found to deploy open stack in a sense that not just easy But it's also flexible and it is something you can use in an enterprise grade, right? So we're not talking about dev stack or or anything else We're talking about our true deployment of open stack whether it be on all in one or whether it be on a thousand no cluster that we like We did with the innovation center with Intel Same thing is what we use. So this is this kind of overview We're gonna prep the Ansible playbooks to install OSA. So there's some prep work you have to do before you can actually do the install You're gonna prep the open stack server as well Because you have to prep that server as well before you can do the install you have to do some networking stuff and install some Repositories that you need As well as then we're gonna kick off the OSA install and then while the OSA install is running because it will take some time to Run we're also gonna then start talk about OSA and learn a little bit more about it All right, so we're gonna do a double task So we're gonna kind of jump into the install get it running and then we're gonna step backward and learn more about OSA Okay All right, so this is what I need you to do anyone who has one of those lab sheets I need you to go to this URL in your browser and That will hold the steps or the instructions for the first part of the lab right so get to that URL Then after that you need to be able to connect to that lab environment server So if you're holding your student sheet, it's the environment that's at the top here the very first one and And you're gonna use the username and password that's on that sheet there If you don't have it, I'm sorry you you can't you can't do that So you're gonna have to just watch me do it when I when I go to do it, okay? Sorry, it's you need my environment to be able to do it Don't yell at me I apologize Yes, yeah, you'll just need to be able to create so if you have the capability of creating two cloud servers right now I Can probably include you in the lab I can push the playbooks that you need to set up those machines But basically outside of here all you need to do is set up two servers and then use those two servers to Execute the lab. All right. Does everybody have this URL up who has the lab sheets and have they connected to the lab environment? I need to show our hands. Is everybody ready because I'm gonna move. I'm gonna move. I'm gonna keep it going All right Can't access what is anybody else having a time time getting to that URL? It's case sensitive. I'll tell you you guys are really smart. It's the same thing. Yeah, this one goes directly to the Instructions for the lab the first one went to the main gut GitHub repository. Okay, so okay, so right now we're gonna jump right into it and like I said, we're gonna come back and and Talk about also a little bit So I'm gonna actually step through the lab as well right so that those of you who can't participate You can actually see what those who are doing it or what are they are doing? So you should have opened up this text file. That's called install osa lab that text And I'm going to connect to the Lab the deployment note you want to make this bigger right can't see it Better You can't see anything on the screen What oh It's mirroring me isn't it? Yes, it is. All right. That's not gonna work out. So let me talk. Hold on a second. Okay Watch my machine crash. Yep. Just did that's great. No, it literally did this crash Okay Yeah, it works. So hopefully you're stepping through the lab stepping through the instructions. You don't have to wait for me Eventually my machine will wake back up. Yes, please Yeah, this is so not gonna work out I Yes Okay, no problem. Is that better? Yes to cloud servers What's that in Butoo In Bluetooth 1404. What's that? I'm sorry again This is gonna be kilo Yes Once we get past this point when we do a deep dive I'll show you where you will define and get hub what tag to pull down and osa and depending on that tag It depends it will tell you what version of open stack you'll pull down Yes Yes, yeah, these are actually public IP address because these are actually we're running this on We're running this on public cloud Rackspace public cloud Yes So the first playbook you run in here is basically going to prep that server For open stack. So as you already know open stack requires NTP That's actually one of the most important functions that you have to have in place at the time of your servers are not Or accurate or not coordinated your open-stack cloud actually won't work very well So this playbook will install that prerequisite. It will also install some other app get Packages that are needed So hopefully you should be past this point, correct? So all right. So it is everybody running this set up everything already Set up everything if you completed to set up everything already then you you're I need to hire you like right now Oh Yeah, no that one is done, but you have to move on. There's another there's another the next step to do Yes, perfect spot on Yep, I'm a hire you now you got a job you want to work at Rackspace you get to work from home Same You don't actually have to go to an office Yes, so do you okay? So where are you right now? Okay, so you're on the deployment server It's already it should have the SSH key. So you actually don't have to use a username and password So yeah, so it was able to talk to it Yes, you have to wait. Yeah, that's why the instructions. It says you got to wait at least five minutes for the server to restart Yeah, doesn't yeah just because the machine came up doesn't mean that all the services are there for you to SSH to us You got to just give it a minute It's restarting so after you run that first playbook the server restarts So you got to give it a minute to come back up because what it has to do is is it has to go in and create some network? Bridges network bridges are a really big part of OSA as well That's how you can get your full deployment of neutron to work. That's how the containers communicate with each other So we'll go through that once we get past this install part in more detail But that's why the server had to be restarted, right? So server-wise again, we'll go over later, but I will I'll tell you right now So server-wise it needs to be running in boot to 1404 that is the operating system that OSA runs on right now They're working on adding more like sent OS, but right now it's in boot to 1404 Obviously the machine has to be around SSH NTP and there are network requirements There are three network bridges you have to create and again, I'll I'll go in a little bit more detail about it So though but those are the high-level prerequisites Commodity was that it's up to you see that's the part that OSA doesn't involve in it doesn't involve in laying down the OS Yes Yes, yes in this lab. I created it I created cloud servers running in boot to 1404 so that part we jump past that part Right nobody nobody likes building machines. So we jump past that part The playbook just did it for you the playbook did it for you and rebooted the machine So once the servers come back up all those bridges already created and done Yep, okay, so is everybody able to move on at this point have their servers come back up Mine is not up yet either you have a problem. I could do that for you. What student number are you? Seven seven you sure didn't reboot Okay, that's fair enough. I like your honesty, so let me take a look So seven is up. Yeah, I know it makes you feel like you've lost that machine, but believe it or not it's Yeah, this one is still down it hasn't come back up yet and you said four What's that? Yeah, all right. Well, that's fair enough. Let me dig deeper Yeah, so that's the only problem with network bridges is that Technically the cloud server doesn't want them or like them so it rejects it rejects rejects and then finally machine a boot up So it takes a lot longer than it would a normal server to reboot after you create those bridges. All right, so Yeah, five minutes That's what the what I generally do is wait five minutes. I know What's that? Yeah, you yeah, you got a so once you get the server rebooted and run the next step It'll actually bring down to get it'll bring down everything you need to run the playbooks So the playbook name is prep deploy dot YAML. Once you run that guy, you'll be able to do it Okay, so my server is back up now. So you guys service should be back up now, too Yeah, so you don't have to actually put a password in because the SSH keys are there So we're behaving like we're really dealing with cloud, right? We don't do usernames of passwords in cloud Is anybody having any issues? Looks like everybody's having issues by me Yes, okay Yeah, so if you're not connecting from that deployment server, then you're not gonna be able to get in Okay Yeah, so you did you do a pseudo SU when you were in the deployment server? You got to do pseudo SU you got to be you got to be the pseudo you got to be super pseudo It's important, right because you're using gonna use the root the credentials that are there for the root server for the Root on the deployment. No, you got to follow my instructions. It's very important. I Promise you it works. What do you get? I'm sorry. I couldn't hear you. Oh get hubs down. No, I'm just kidding Yeah Yeah, right. I don't know Okay, why did it not? Oh Okay, you do it You do it because I'm gonna wear the angle So just do this for a second and just click on it because it's right there Okay, all right got it Okay, so where is everybody I need to see playbooks running. It's very important to me, right? So I'll I'll show you when we step through the other instructions But what happens is inside of OSA this configuration files and in those configuration files You basically will can point it to whatever release you want to right? So it's I'll it'll make more sense what I showed to you. I know you uh, you asked me about that before Okay, is everybody running these playbooks We have to set this server up. Oh, that's not good. I should to place on one. No such follow directory Yeah, I'm not Huh That's OSA that's having a problem Try running it again. See what happens It may be Yeah They changed the repo on me. I hope not. Let's see if we get better results. I'll come back. Okay. Yes Yeah, but you have to move into this directory Yeah, yeah Okay, so the first thing I see is that you're running this on your machine, right? Yeah, you have to be on the deployment server Well, you don't have to be but I see so yeah, so you see the host file in there That would that's what you would be editing with the password with IP address of your all-in-one server Okay. Yeah, you have to update that Yes, is it running again sure long as it's in boot to 1404 But I wouldn't encourage you to use AWS You're running. Yeah, it's gonna take a while. All right. So this is where I'm gonna start talking again Since that's gonna take a while if you run if anyone have runs into any problem running the setup everything and it errors out on you Try running it again That's actually OSA that you pulled down and it's running in the repose the dynamic So something could have changed if you run into a problem. So just run it again and Hopefully it won't fail again. So if yours is running Great If it's not You can keep going at it, but I'm just gonna talk a little bit about OSA now. All right. So now that we have some time So OSA So just giving you some background around OSA and how it started and where you know how we got to where we are So back in November 2014 The community voted to accept OSA that it was called at the time The playbooks for OSA as a stack for a repository. So basically the open stack community embraced OSA and said, you know what? We'll stand behind this will stamp of approval. You can use this method to deploy open stack, right? So basically saying this is the way we're gonna use Ansible to deploy open stack And just so happened that racks based were major contributors to creating OSA But then next at the Vancouver Summit the community decided they wanted to take it to the next level, right? and Decided to continue the process of improving OSA and try to make it as easy as possible to deploy using open stack And then very late this year around fall OSA repository was actually moved out of stack for it and moved into the open stack repository So and now it was now rebranded as OSA instead So now these were this repository the things we were pulling down are actually coming right out of the open stack Repository so they're not in stack for us anymore. They are now officially part of open stack Okay, so that's just some of the background around OSA that's the link where you can get to the playbooks there on github So the things you need to know about Ansible. I mean OSA it and its feature and benefits I have Ansible as a feature of OSA because to me you're getting a two-in-one You're not only getting to deploy open stack, but you're also getting learn another really powerful tool called Ansible Another feature that's part of OSA is the fact that you are actually deploying your open stack services in containers And not Docker containers, but their original container system LSE containers And you may ask well Why would I want to deploy open stack services out of containers and make it much more complicated than what it already is? But the reality is is that by doing that you can actually do in place upgrades right by dropping in new containers running new Versions of open stack take take down the old containers do some database updates and boom you're in the next release So it's about portability. It's about flexibility, and that's why that was chosen to be the case You're using Linux bridge agent with OSA not OBS I repeat Linux bridge agent not OBS The reason behind that was is that at an enterprise scale OBS was not holding up to the challenge from a network perspective So Rackspace decided to roll back and go with Linux bridge something that's been around much longer than OBS And can withstand enterprise volume right so that's another thing you're getting with OSA You are getting a full neutron deployment with OSA. We're not talking about Nova networking We're talking about full neutron full L2 full L3 capabilities with OSA Because of being able to go back to that Linux bridge agent And of course it is prod ready right so what comes with OSA or the services that are prod ready with an open stack So what you may find is that OSA may not have the latest new service that was just launched at the summit There's a reason for that because those services need to be tested and trialed and beat up to make sure that it is production ready So know that if you deploy OSA you're getting the services that are production ready So you don't have to question whether or not those services are ready or not And the thing about OSA is as I mentioned before you can deploy it as an all-in-one You can deploy it as a fully distributed build for your enterprise a thousand nodes Ten nodes twenty nodes a hundred nodes. It doesn't matter. OSA is just that flexible, right? So you can go in either direction with it And that's what I like about it Right because if you use it as all-in-one or your on your machine in virtual box The same thing you use there is the same thing you can use to deploy it in your data center There is no different other than changing some configuration files So these are the high-level prerequisites under the cover stuff as a gentleman was asking about So again and boot to 14.04 is the operating system that is required at this time for OSA That is being worked on to add more right now. That is it SSH client NTP client as I said before time is very important and Python 2.7 or later most machines running Linux Linux kernel is going to have Python already So that's probably not even an issue The networking features so this again, and then we talked about the bridges and net and namespaces These are the bridges that need to be created in order for OSA to work now This is a probably the most complicated part of OSA is doing the networking part but there are a lot of examples out there on github as well as the The lab that we're stepping through today. There's a good example of how you can set up the networking on a cloud server As well, so there's a lot of good examples out there So don't let that part overwhelm you but just know that you go you will you do have to create network bridges for OSA to work right if you don't create all these bridges it actually won't the install won't run and you'll be like Why am I install? Why is not installing? Well, it's because those network bridges So that that's the thing the only tip that I would say is make sure your network is solid your network configuration is solid before you go to deploy OSA So here's some more under the cover stuff So also is basically broken down into four main playbooks one of those being optional the HA proxy Playbook is an optional playbook reason being is that with OSA you're it's intended to deploy with Multiple controllers in an active format active active format Meaning it's meant for you to have multiple controllers all being active at one time And that's accomplished because there is a low balance that put in front of those services You can use a physical load balancer like your f5s or what have you or you can use HA proxy if you decide to use HA proxy you can use that playbook to actually set up HA proxy for you So not only will install HA proxy, but it'll set up all the front end and back end stuff for HA proxy and configure everything for you So you actually don't even have to do anything, but run that playbook against your HA proxy server Okay, so out of all those four HA proxy one is the only optional one The other three are required or you can just do like we did today run the setup everything the setup everything YAML file will basically execute all four of those for you right so that's the thing about play Ansible is again you can tear playbooks inside of each other And basically make one call and it'll do everything you need it to do okay If you want to learn a little bit more about that if you go to this link here in the github repository It actually will show you all the playbooks that are available and it breaks it down by service It breaks it down by other features as well So you know something you can take a look at and again this my slide presentation is already up on github. So you have all this information Some more information about it So behind those playbooks are what I consider the most important thing which is your configuration files So there's four configuration files that you will have to open up and actually do something to an edit Before you deploy OSA and this is in the information that's in these files are specific to your environment Your eye your whatever cedar range is you're going to use however Infrastructure nodes you're going to use however compute nodes you're going to set up higher as cinder nodes You're going to set up whether or not you're going to put neutron on your control node Or whether you're going to have neutron separate all that stuff is configured in these files Your passwords you're going to use to set up my sequel rabbit the passwords You're going to use for your service accounts such as nova and keystone all that stuff and information It's stored amongst these four configuration files. So these files are your friends you want to make sure you get and you know very intimately acquainted with them and Again in this lab you can use examples that are already provided to kind of give you a springboard as well as in the github There's also examples of what those configuration files look like But these are the four configuration files that you will spend the most time with and if we have time I'll actually open those up and we can step through those a little bit So how is how's everybody installed going? It's right in the root of that github repository So if you're in the github repository So it's actually called os dash summit dash osa dash workshop PDF It's damaged Yeah, I don't know if it's gonna open up to great entire github. You may have to download it. Oh, okay Either way, I'll send out I can either tweet out a link or put up put it up in slide deck, whichever one But I can get it to you if it takes a while Yep, so So you had the same problem? all right, so I Was afraid of this so I've been testing out the Wi-Fi in this place since I got here on Sunday afternoon and I had a good days and I've had bad days and I Seem like we're having a bad day today. Yeah, I was able to build it I don't know how I'm building I've been building this environment every day since I've been here to make sure that it can be done But I can't do anything about the Wi-Fi. Unfortunately. Oh, so they changed something Cannot send to the remote holes make sure the hose is reachable SSH. It's just trying to install memcash Hmm Yeah, well So is everybody all stuck where I am right now? Yeah, oh Okay, you got further than me which Is concerning but okay, so have you guys tried to kick it off again? This is failing again Okay, I failed again. Yeah So yeah, so the issue that we are having is it has to do with connectivity between Us to the deployment. No to deployment. No to the open stack I know it looks like it's it's keys, but a lot of times it is because of the internet. I Know it doesn't make you feel good. It makes me doesn't make you feel good either Yeah, so you got the same exact error as I did in the exact same place. Let's try executed again. We'll see Yes Yeah, see he has to update this this file to the to be the do you have the handout? Yes, see so key is is if you didn't get in handout, then you don't know what server to connect to Okay, and only a certain amount of people. No You can but then they'll they'll be a Overriding each other Well, is there is there a duplicate handout somewhere that I can borrow for just a couple of minutes like can you buddy up with Somebody and I can borrow one for the back table. Well, I've you know what I'll do is maybe I'll spin up another server I Just give me a second. Oh, it probably will No, it definitely will no it shouldn't It shouldn't it won't change our Wi-Fi situation. Well, that's a good point. I'm not you know You got to remember this is a live repository that people make changes to so It's taking so long to get through these playbooks. Yeah, it's it's not even anywhere right now Yeah Yeah So, yeah, the problem is is that if Ansible can't get back the communication from that server in a timely manner It just drops it and says they can't talk to it Yeah, yeah, I didn't expect to have to do that but yeah Hopefully one person will get it completed Okay, good. I like cheating Yes, you try to get me in trouble, aren't you I don't know unfortunately. I don't know Whether or not that red hat is now brought Ansible will red hat maybe adopt Ansible Yeah You well, let's put it this way. You don't just buy companies for a hundred million dollars for no reason, right? So You can yeah, no exactly. All right, mine died again. So since What's that you guys are leaving sure One second. Yes So you got your lab built. Oh, excellent. Mm-hmm. It says no such directories found you're on the right place But you're using the IP that's there because that's a different IP. Yeah, but oh So you must be you must be using your own Yeah Yeah, so are you running OSA? Yeah, okay, and you you got the IP address of the utility container. Yeah, okay Okay Open up your command prompt again, do you mind just showing me the file the host file Okay And you're actually on that server right now if you do it like see that's LS that's fancy that's that's fancy LS yeah That's that's fancy. So yeah, it's there It all it's going to try to do is create a user using keystone Try it again, you don't mind And now you made a man Broke it you broke it Yeah, no it I Mean it obviously in probably better circumstances It'll all work out better But that playbook all it does is create users and it writes the username and password out to the screen It it's the simplest thing ever. I don't know why it would say no no file found. That's weird Eight well, it's the six flavor number six No Yeah, but that's exactly what we're doing. It's just we're not using those batch scripts. That's all oh I see I see what you mean I see what you mean Yeah, I'll try that Yeah, yeah that one actually you know what that's a good idea. Let me try that on it Yes Sure, yeah, you can do this one because they left it's okay No, but I I just realized the install is running from the server that it's installing on I'm just SSHing to that server as a cloud server. So it's not gonna We're not we're not running it from the deployment. No, we actually SSH into the server that we're deploying it on Dude, I've been doing this all week and it's been working in my hotel room Of course I get here and it bombs so it's a true failure, but this is what happens when You're dealing with cloud so I appreciate you guys still trying But I'm gonna put out a flag and probably say that you're probably not gonna make it Yeah, okay, so everybody is consistently failing at the same places so That's good. So let's take a second and talk about operating Ansible and then I'll give you back 30 minutes of your life I'm not gonna force you to hang out It's connectivity. It's connectivity. It's all connectivity Yeah, I know it will work. Yes. So thank you. It does work Once you have reasonable internet. Thank you. That was a good term. It does work. Trust me It does it really really does the lab is there. What I'm gonna do is I Will rebuild those servers so that you can start from the top again with the labs and I'll leave them there for a week Okay, so I'll give you a week You can go back in you can give it a go if you have the lab handout if you don't have the lab handout that I will build more servers and Just hit me up on Twitter and I'll give you some it I'll give you the information All right, so I'll give you a week to be able to connect back in and give it a go yes absolutely, I'll write a blog and Share more details about it Also put up the github information so that you'll have it but I'll give you guys a week to give it a go once you get home Trust me. It will work Yes, okay virtual box, right? Okay. Yeah, so my wonderful co-worker here. I also said, you know You can do this using virtual box of fusion as well if you want to do it from your laptop, right? You don't have to use a cloud server That is also a possibility. Okay. Yeah So I want to talk about operating OSA But the reality is is I won't be able to show it to you because no one has a cloud built to actually do it with you Probably got the closest So why use Ansible with open stack that's usually probably the biggest question that I get Why does the answer will make sense with open stack? So these are just some of the reasons why I have kind of fell in love with Ansible when dealing with open stack Ansible does not require any sort of agent only requires SSH and Python and actually really doesn't require Python But it requires SSH to be able to connect to the devices So you don't have any agents. You don't have to worry about chasing down configurations and things like that That's why I like Ansible. They're already modules in Ansible that work with open stack They actually just with a 2.0 release of Ansible. They actually have new modules to work with open stack directly. Yes So it kind of gives you a leg up, right? Those modules are already written and know how to communicate and work with open stack So you can use those modules in Ansible to be able to do what you need to do The playbooks are can be written to talk against the API's or the CLI open stack, right? So if you like dealing with the API and making curl requests Then you can use that or if you want to use the CLI directly You can write your playbooks to call the CLI directly as well, right? So you have three choices. You have the API CLI or the modules in Ansible to be able to communicate with open stack And then last but not least You know designing roles or writing playbooks is as simple as writing an email, right? It's written in YAML language very simple market language To me is you don't have to learn another programming language to be able to use Ansible And so it makes your life a lot easier in my opinion versus some of the other guys out there This is just like a visual view as to how I look at when dealing with open stack in Ansible You know, you're the cloud operator at the very top there and Basically through your DevOps team and you may be part of that DevOps team You can create series of playbooks and roles through Ansible and those playbooks and roles directly interface with your open stack cloud Right, so this is just a very simplistic view of what we kind of talked about you can call the API You can call the CLI of open stack It doesn't really matter right and this is just the easiest approach to me as to being able to manage my open stack clouds We can't do the second lab because you need the first lab to do the second lab. That's just how that works So sorry about that What the second lab was going to do is step you through some possible scenarios that you would see as a cloud operator So one of the scenarios was this guy right here So, you know, you have your marketing department who never talks to IT. They just go and do what they want to do And so they purchased some website and for this special campaign and decided that hey, you know now I need environments. I need environments for those developers to finish creating that website So they walk up to you and say hey, you know, I need 10 tenants 10 users And yeah, I need that right now. And by the way, you know, I need that like right now So, yeah, you can execute 10 commands or do you know open up horizon dashboard and do that 10 times or You can create an answer will playbook where you put in some parameters you execute one command and it's done in a minute So this is just one example of what we were going to do. So we were actually going to create 10 users 10 projects As well as assign the proper roles and have the passwords Dynamically created and written to the screen. So all you have to do is copy that block You can paste that right into an email and send it off, right? So just examples of showing how answer book and really simplify doing things as a cloud operator So that was one of the things again the playbooks there in github. You can do it on your own You can use them and download them and use them as you wish The other scenario was so now that the marketing department has gotten their tenants They've gone in there and they've lost their minds and started consuming all your resources, right? Because you didn't set the proper quotas For their for their tenant. So now you need to go back in and adjust that quota so that they don't keep consuming all your cloud Resources so the next set of playbooks will actually going to take three of the developers reset that quota To be 30 vcpu and give them an allowance to do 30 instances and then the rest of them It was gonna have 20 vcpu and 20 instances, right? And we were gonna all do that by just editing one variable file and Executing one answerable playbook and it would do all that for you So instead of going through horizon or making a multiple CLI calls We were actually able to do it in one command using ansible and again that playbook is there in github And then the last scenario was going to be so now that these developers have totally not lived up toward the marketing department Wanted they fired them all got rid of them So now you as the cloud operator you have to clean up that everything they left behind But before you do everything they said well We want you to back up at least one of the developers environments just in case they actually did some Work that we want to look at later on so the next scenario was is we're going to execute a playbook That was going to delete all the tenants delete all the users take snapshots of just one of the tenants Instances store those off and then get rid of everything else right again update one variable file Execute one playbook command and all that work would be done for you so those are just examples of How you can use ansible to make your life as a cloud operator a lot easier We can't do the lab. You can't go. Sorry Skipping towards to some of the tips and tricks so What I found when dealing with osa these are just some of the things that have made my life a lot easier So anyone familiar with github, you know that you can go in and deploy code by the branch or by the tag I would recommend highly recommend looking at the tags when looking at osa not just a branch The branch will say ice house Juno kilo and that's all great But if you actually look at the tags you'll realize that there's multiple revisions of those releases in between and they make updates to them So knowing exactly what you're deploying is actually very important with osa So my recommendation is is deploy using the tag so the tag we use for this lab today was 11.2.3 Right. There's actually 11.2.4 there right now, which is the latest so you can try that as well But that's just one of my suggestions Always go out and check the github repo to make sure that there were not new things added to the variables files because it's constantly improving Right, so you may have your variables files stored. You may have them already updated the way you like it But if they release a new A new variable in that variable file you don't have it in yours when you go to deploy it'll act deploy a new version It'll actually fail So there's just something to keep in mind make sure you go in and check the new versions and make sure your variables are Accurate triple checking that working. I can't say that a million times triple checking that working triple checking that working triple checking that working The bridges must be created. They must be working. They must be able to communicate with each other That's just how that works right so without that deployment will not be successful They're actually playbooks out on the github repository of OpenStack Ansible that will help you do cleanup Let's say for example you deploy it and you want to start over again Right there are actually playbooks out there that will kill all the containers clean up the machine and get you back to step one So just take a look at those playbooks use them Don't try and you know doing on your own deleting containers and things like that because what happens is is there are actually Placeholders and other configuration files that are stored off in another place that you don't know there So even though you've deleted that container when you go to run the install again It'll actually be looking for that container that you delete it right so it's best to use these playbooks to kind of clean up your environment There's also Galera health check playbooks out there that will help you check the health of your Galera cluster I know that's a It can be a pain point at times right but your Galera cluster needs to be in sync right so you have a successful open stack environment So there's playbooks out there to help you with that and last but not least if you don't know dash L for Ansible Dash L gives you the opportunity to focus that play that playbook run at a specific machine or a specific container So using dash L what Ansible is your friend when you want to just do a one machine So let's say for example, you want to add another compute node to your environment You can basically run the playbooks again But you just add dash L the name of that new compute node and it will only run the playbooks against that newest machine So that's just a tip and trick about Ansible dash L is your friend These are just some of the reference materials. So this is a really important stuff the osa install guide There's some additional instructions to that install guide that rack space has put together that you can also help to kind of supplement some really good Examples, there's a quick start all-in-one install Guide which is a very helpful It's uses a series of bad scripts to do exactly what we did But and probably a move a more simplified fashion and of course if you like to follow osa as far as news and updates This is a link there as well That shows you some of the newer things that they're doing one of the things that they're working on right now It's possibly an image-based deployment using osa So actually just pushing down an image that actually will run an open stack. So anyway, that's just some of the latest greatest stuff Thank you again. I severely apologize, but you know, this was always a 5050 risk using the Wi-Fi here Again, I will leave those servers there for a week I will reset them back so that you can start the lab from the top again and And if you didn't get a lab handout with a server Come up to me at the end and I'll take your name down or at least your Twitter handle or something And then I'll create some servers for you and get you set up. Okay. Thank you again guys. I appreciate it. All right And it does work. Yes