 Hi, we are about to start. Can you please repeat your name? I don't want to pronounce it. Rain. Sorry? Rain. Rain. Like the weather? Yeah. Yeah. Okay, perfect. Yeah, it's my... Rain Leander, I'm an engineer with Red Hat. Yeah, I don't want to talk about it anymore, but I think it's better people talk about themselves than just the main, or if you want to. You can just say Rain. Yeah, okay, perfect. This is Rain. You can't say Rain. Sorry. Sorry. We've got Rain. And I will show you 10 minutes in advance and 5 minutes in advance that we are running every time. We can be a minute or two per time, but not more. Yeah, yeah. It's fine. Perfect. Hello, everybody. Just like I remind you that there is a white board in the D building. You can vote for a lightning ball this evening. And in the afternoon there will be spare tickets for evening party also in the D building. So don't forget it. And don't forget to provide feedback after every call. And now we have a talk about building your home drive cloud. And please welcome Rain. Hello. I'm Rain, like the weather. I am a software engineer with Red Hat. I work on the OpenStack Triple O project as well as the RDO manager project. And if you don't understand what those are, we're going to tell you today. So yay. One of the pieces of feedback I've received about this is it's very command line heavy in the installation. We're working on a script right now. So it's just two lines, but it's still command line. Last night someone said, why aren't you doing installing RPM and then do a GUI installation? And so as this talk is happening, I would love to hear if you are plus one about that idea or something else entirely that I'm not even going to touch on. Any kind of feedback like that I would love, love, love to hear. This is not a workshop because the actual building of the developers cloud using RDO manager takes much longer than 40 minutes. So what I'm going to do is give you a knowledge shop, an introduction about what OpenStack Triple O RDO manager is. So you kind of understand how it fits in the OpenStack family. And then I'm going to give you links to the documentation, which are pretty verbose, but very specific so that you can go installing your own cloud. Then I'm also going to give you a link to our quick start script, which is meant to replace the seven pages of verbose instructions. And I would love, love, love for you to tweet at me at Brain Stance because I used to dance. And tell me what this work was like for you, if it was way too complicated, if you were frustrated by the images because they're up on a separate server. Anything, send me your tweets. And also, I would love to hear any questions that we don't get to today. Feedback, et cetera, at my Twitter handle as well. First, I would like to know who in here is a developer. Cool. Do we have any end users in here? Don't be scared. Okay. Do we have any contributors, active contributors to OpenStack? One, one, hey. One, two, yes. And out of the three of you, is anyone a contributor to Triple O? Okay. Well, let me introduce you. So, Ardio Manager is an installation. It's a way to actually install your own cloud. It's very, very new. Well, OpenStack and cloud computing are very, very new. It's even very, very, very newer. And it finally works. Yay. But there are bugs, too. So, what we're doing is making a quick start. But in order to understand Ardio Manager, I feel like it helps to understand what's OpenStack, what's Triple O, what's Ardio, what's Ardio Manager. If you want to learn more, ArdioProject.org. So, what is OpenStack? It is an infrastructure as a service. And all that means is it's a base platform to put your platforms and then your applications on top of it. Why would you want to install your own cloud? Maybe you are already an installer for a company or already a developer for a company that builds applications on the cloud. But for whatever reason, you would like your own private under your desk version of the cloud. You might have really bad connectivity to your company's system around the world and want to limit that issue. So, you can just see it privately. You may want to see what it's like to test on a private system and then push out. And so, in that case, you probably want to work with OpenStack. No way. You definitely want to work with OpenStack. And OpenStack is a bunch of little projects under an umbrella. So, when I say OpenStack, I'm not talking about one little push-a-button and it's done, I'm talking about an umbrella. It's more like a bunch of sub-projects within a bigger. And this is the marketing version of OpenStack. It's very pretty. It looks like there's only three, four projects. If you count the dashboard, compute, networking, and storage, it's very, very misleading because even within the storage projects, there's three such as staff cluster. And so, what OpenStack actually looks like is more like this, which is a little intimidating, but if you're intimately about this, shut your eyes. I promise. Triple L makes it easier. You don't have to think about so much these details, which are even a little stressful for me. How does Triple L fit into all these projects? Well, it's not even on this page because it's the installer. And so, think of Triple L maybe being in one of the white spaces by itself. There are lots of projects, actually, that aren't included in here. These are just the main ones. And so, I say if this intimidates you, just think of OpenStack as an umbrella and then let it go. So then, what is OpenStack? Triple O. It's OpenStack on OpenStack. And there are two terms that are most important about that, and that is that you are building two clouds. And because there are two clouds, we named one brilliantly under-cloud, and the other one, brilliantly over-cloud, helps to visualize that. I don't like left-to-right visualization. I actually prefer under-to-over. But if someone wants to make that graphic for me, I would be incredibly grateful. This is the simple. And again, we have a more complex version, but if you don't want to be stressed, just shut your eyes. It's cool. Your under-cloud deploys monitors and whatnot, your over-cloud. And the reason you might choose to have this scenario is if you would like to use your under-cloud as your testing site. You build an app. You actually test it within your under-cloud and work out the bugs, work out any confusion between the resources. Let's say it works really well on a smaller system, but you put it on a larger flavor, which might have a specs for a larger system and suddenly your application explodes. You would test that all on your under-cloud, which is not where the public or your end-users access it. But once it works, you set it over to the over-cloud. If you don't like the names of these under-cloud and over-cloud, I've had some complaints. I would love suggestions, alternatives. It's open source, so, you know, we'll listen. The under-cloud is very specific in what the requirements are, whereas your over-cloud, the sky's the limit. So when you deploy your over-cloud, you would get more specific for what your application needs. Okay, so what is Spinal Stack? I haven't even said Spinal Stack yet today. Spinal Stack was a project that we adopted some of the philosophy for our new manager, and that's what I'm bringing up now, and it's kind of, if you're thinking of Open Stack and Triple O and RDO and RDO Manager as brother and sister, husband and wife, but not at the same time, you might think of Spinal Stack as a best friend that kind of influences a couple of aspects of RDO, RDO Manager. And these are the three points that we really liked about Spinal Stack. Automated health checks were already built in, which is a good thing because you would want to know if something was trailing. The resource matching, which is if I need X, Y, Z in my environment, it looks at the resources available and tries to get you something as close as possible instead of something that's really different but then giving you just the limit of that. And then the support for Red Hat, Red Hat developers kind of like that. So then what is RDO? And get ready for a little bit of data review. RDO is Open Stack, but it's only for Red Hat Enterprise Linux, CentOS, Fedora. So everything that Open Stack is trying to do build the scalability, instant access, etc., etc. It's the umbrella. And why do I specify RDO as well as RDO Manager is because sometimes people get the too confused as one thing. But RDO is the big project, the umbrella, whereas RDO Manager is the triple O equivalent within RDO. So again, get ready for more data review. RDO Manager is triple O, but for Red Hat Enterprise Linux and CentOS, why not Fedora? We haven't got that far. Oh, and Spinal Stack, yay, Cousin. So what are the specific environmental requirements for an RDO Manager? Oh, RDO is Red Hat Deployed Open Stack, RDO. The environmental requirements are the bare metal machine has to fix virtualization hardware extensions enabled at this time nested KVM which is with an avert is not supported. I'm sure you could get it to work if you want to hack on it a while, but it would get very, very slow. One quad core of CPU, one quad core of CPU, 12 gig free memory, 120 gig disk space, and that is because you're creating three virtual systems and each of them has their own requirements, which is four gigs of memory and 40 gigs of disk space. So as I said, this is only for REL and CentOS at this time. 7.1 for REL and 7.0 for CentOS. And now for the fun part. Installation by hand. I'm not doing a demo. I'm just going through the documentation a little bit. The link is way, way too long, so I employed Bitly. What I'm going to go over today is only the environment preparation and the installation of the undercloud, not the actual deployment. Because when you get to the deployment phase, that's going to get really, really specific based on what you are working on. In the future, if you're interested, please treat me and I will write up a specific document just for you. Yes, I just said that. Challenge thrown. So this is the link. It's a Fedora pages, Ardeo stuff, like really long link. First thing I would have you do is once you get to this site, narrow down your operating system and whatnot. This that I have outlined, just CentOS and just virtual is the simplest version. You are more than welcome to use REL, but then you have to add satellite or portal for your registration. Of course, you're allowed to use CEPH. Have fun with that. Go storage. And then bare metal is if you have three if you're installing on three systems, but then you have to be comfortable with the networking in between them and a couple of extra factors that frankly I just want to build a cloud and then start developing. So I limit. We already went over the requirements. Prepping the virtual environment so you would install CentOS. You would make sure SSHD is running. You would create a non-root user because if you have all these done with if you run these instructions as a root user, you might miss some error messages that root will just smash through and create anyway. And then you become that root user. You enable two repos. One of them is Apple and the other one is either CentOS or DeLorean. I can absolutely not speak to the DeLorean side of things. I've only ever tried with CentOS, but if you do that, please tweet at me. Let me know how it goes. And then you actually install Instac-undercloud. There's a couple of... There's just one extra... No, two extra steps that if you need to specialize in any way, you do that. And then Instac-vert setup. And that actually just builds your three-vert systems and whatnot. Then instead of going down and clicking next, which will take you off into how to prep a bare metal system, three bare metal systems, click on installing the overcloud. So then you SSH into the system you just prepped. As the non-root user, I cannot stress that enough because I've done that and you miss things. Again, enable the two repos and install Python Triple O Client. And then open stack-undercloud install. That's it. Then YumUpdate, I think. Yup, YumUpdate. Oh, and then open stack-overcloud-deploy templates. Now, the next bit about basic deployment, it goes into some detail. It's a lot of pages and way more than 40 minutes will allow. But that's basically it. It's pretty simple. So then we get to the installation by script, which used to be strictly on GitHub, but now it's working enough that we have put it on Ardio Project, which is exciting. And you run the script, which does everything I just said. It creates the non-root user. It preps your environment. It makes sure everything's running that should be. It goes out to the repos. It does all the packages. It does all the installation for you. So you only have to run one line of scripts. And then after that, deploy the basic overcloud. And again, if you want me to help you with that, let me know. These are the instructions, which I think are still a little bit for both. But it's basically one line. Lies. Lies. And it's four lines. But then you can go back to the original upstream docs. I really hate the Ardio Manager troubleshooting. It's like four things. And so much more could go wrong than those four things. And after that, I say to you, please get on IRC FreeNode, pound Ardio, and ping me, I'm Leanderthal, or any one of my friends that are also in there. I'm also at Rain's Dance, and if you would like to test that script, hack on that script and whatnot, please do. We are working on a documentation right now, and I would love to hear from you guys what you would like to see about building a basic cloud. And now I would love to hear your questions, comments, some landmarks. About anything, and apparently I get to reward you with a scarf if you have any questions. Or not. Any questions? Okay, let me ask you this. Would you, are you likely to use Ardio Manager to build your own cloud? Raise your hands. Okay. One guy. No. Why not? Actually, we have tons of time. I'm going to get you all comfortable talking. Turn to the person to your left or right and introduce yourself, tell them what you do, what you're programming languages. Two minutes. Come on, come on, talk. Come on, introduce yourself to someone you don't know. Obviously. Let's go. How's that going to do? How do I do this? How do you do this? How do you do this? How do you do this? How do you do this? How do you do this? How do you do this? How do I do this? Why is it so complicated? How do I do this? I'll start talking a little bit. And one of the comments is that the reason I won't do it is because I have to maintain it then. And that is totally valid. If you have the resources, someone else is maintaining the entire lab. Why should you have your own private one? kind of have to be an administrator, as well as a developer, validator. Great, why not install a broker's day? I mean, we have people, we have tax day, we have people from the United States, and now we have a lot of open wires. What are the reasons for it? I agree. There are millions of options. Maybe not a million. There are tons of options for installers. And so why would we use RDO Manager instead of the triple O? And the answer is that RDO Manager, if you want to get really specific in what you're under, in what your environment is, it's strictly for REL, it's strictly for CentOS, and theoretically, then, there are specifications that make it run more smoothly if you're using that environment. If you're not using that environment, go to triple O, awesome. Go to practice, that's what you're more comfortable with, or any of the other installers, frankly. Triple O and RDO Manager, as far as I know, are the only installers specifically being developed to do cloud managing and cloud scenario. If you don't need or want that scenario, if you just want your own single cloud, I love pecs, actually. My name is Ray, I'm an RDO Engineer, I love pecs. That was recorded, right? And there's tons of other options as well. And that's one of the beauties of installers is, if it doesn't work, you try another one, another version, that might work better for you. Apparently, I have zero loyalty. If the open select is still not available, I don't think you might have run. I have not worked with no pecs. Was there a chance for my application to run? Great question. So the question was, my laptop has a minimal hardware resource, and I need that for my application to run. Why should I then delegate another cute, actually rather large chunk of space just for OpenStack, specifically triple O RDO Manager? I would not run this on the same system that you are debbing your application. I don't do that. I have a laptop just for the cloud or the cloud. I use this laptop actually for my testing for applications and whatnot, and then when I'm ready to start testing it on the cloud, then I push it over to that system. So this specifically assumes, great word, that you have an extra piece of hardware. Any other questions? Then we are done a little bit early. Who asked the question, come up for a Skype if you don't already have one or you want an extra? Can you please upload the slides on the USB? Best, but whatever works. We have a special sticker for every speaker, so you can distinguish yourself. I don't have a use case. I like this without solutions, but I can justify to spend time on it. I feel like it's for also people who are new to contributing as well, so it's back and whatnot. And also there are very specific use cases where a person is so remote that their access to the lab is too delayed. But yeah, I agree. I also think it needs to be a lot simpler and mindless to maintain. And something that they're working on right now, as we speak, is live updates and the simplicity of maintaining. So it's coming. And you're in the Bruno office, shut up. I would love to replace the lab solution. We have Reven over and the server, the cluster is sitting in Bruno. The front end is Israel. Round trip to Amsterdam, actually. Yes, exactly. It's very slow. It's really slow. And when the VM is running... Just try OS1. Just try OS1. How long are you? What's the repeat? Two hours. So we have an internal cloud named OS1. You're not supposed to tell us that. You can have to keep this a secret. Well, you don't have a login for this. Why not? That I may use it when I can. So there might be in some future some cloud available somewhere. And that might be named blah blah blah. I don't know. Thanks for raising your hand. Thank you for your talk. Two side remarks like RGO stands for nothing. Yeah, I know. I've been aware. I saw your talk in Brussels and I just... So it's a repeat in question. What is it for? It actually stands for nothing. So we're doing like GNU basically. Well, maybe yes, maybe no. Nobody knows. I have no idea who came up with this name. And I have no idea who liked this name. Are there any plans to change it? I'm just gonna be like... I have no idea. The other thing is we are currently in the process of dropping Fedora. So we are not supporting Fedora at all. Okay, cool. Reasons? Well, I mean, it makes sense because they're upstream and it's a lot easier to make things stable after it's rel synced up. Well, it's a bit hard since Oversex is moving so fast and Rel and Santos is moving so slow. And we are pushing new changes so fast into the project. Maybe it's like we are trying to keep at least something stable as the base that might be an idea why we are just dropping Fedora. Yeah, yeah, yeah. It makes sense. So I would just drop the... No, I already have one. I know. You want mine? I know they are forcing you to hand out. Yeah, I know. Scarf. Scarf. Scarf. Yeah, yeah, yeah, you can use it for maintenance deployments. You'll notice... Yeah. Yes, technically it is the goal to install deploy maintain. But right now the stability is in the installer. Like, I can say installer and she would run into a lot less bugs. Get out. Hey boss. Hey boss. I kept running into this overtime and running out of time for questions. Maybe it's two times the time. So, like, I'm sure running out of time would be a good idea. I know. I feel like conferences are just about... What's your name? I feel like that's some kind of advice. Sure, we're exchanging information. I just want to get you out of there soon. Yeah, I was... Yeah, exactly. Yeah, I don't work for a lot of speakers. Hey, people. Thank you so much. Hello. I was just talking to you. Oops. Why can't I see it? Yeah. Yeah. Yeah. I'm not gonna put you out there. I'm just gonna take a picture of you. Yeah, yeah. I'm gonna put you out there. I'm gonna be... I'm gonna put you out there. I'm gonna be... We'll be there in a minute. I'm gonna be seeing you. I'm just gonna take a picture of you. Okay, okay. He's not talking to me right now. Maybe it's gonna be okay, but he won't stop reacting. No, he won't stop reacting. Let's try to miss it. What is this? I hope he won't have to take the whole thing off. No, but... I don't know much about him, but he doesn't speak Czech. I don't know. I don't know what to say. I don't know what to say. That's him. That's him. He has a stand-up. He has a stand-up. That's his technique. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. That's him. Thank you, thank you very much. Thank you very much. Thank you very much. So, hello everybody, there was change in schedule. Next presentation will be about network manager.