 Not much anything that you'd like to become involved in an open source project. It means you want to contribute to Triple O, because it's an awesome project, within the umbrella space called OpenStack. And then you join the RDO community, which I'm a part of, for guidance feedback in this quarter. It means that you want to make a world a better place. A better place to start and help people all over the world to create something kick-ass awesome. The first context would sound awesome, but it's not bad. It's not bad. So I'm going to do what the keynote speaker said not to do, and ask you to follow me on Twitter. These are the three ways to kind of get in touch with the community and myself. This also introduces an element of interactivity during the talk that psychologists tell me is interesting, or at least seems interesting. So I invite you to send your comments, questions, and snag them on our Twitter. So, question time. Who knows what open source is? I think it's right here. That's where we're starting. Okay, no problem. Who knows what cloud computing is? OpenStack. It's pretty good. Who knows what RDO is? Exactly. It is Rain's Dynamic OpenStack, obviously. So we're going to talk about what OpenStack is. It can be a little bit daunting. It's not actually Rain's Dynamic OpenStack. I'll explain later. Triple O Quickstart is my project? No, it's the project that I happen to work on, and how to actually become an ATC, a contributor to an open source project. So, who am I? Ooh, I'm about to make your job hard. I'd like to walk. Sorry. Oh, great. There's a microphone. So, there's an owl. And I'll get into that later. It's actually the logo for Triple O. I am an RDO and Triple O developer of Angelus Seconds. I actually code on Triple O. I'm a Python programmer. I joined the project a year ago, and it took me about three months to figure out that everyone was just as overwhelmed as I was, because that's how big OpenStack is. I am at the end of the call. I'm at the FreeMailage IRC, channel's RDO and Triple O, and that is actually my email address, greenandrednet.com, and I put that up there, because not only do I love spam, but if you are having trouble with anything that you hear today on this talk, I actually want you to contact me and start the dialogue. There are all kinds of ways to get involved, and one of them is just saying, hey, I saw your pocket code days, and this part really confused me, and we ran out of questions, because we had technical issues, and I was full-time. So what is OpenStack? I love this picture. Isn't it pretty? Somebody smarter than me in designing built this. It implies that OpenStack is just three beautiful little projects packaged in little cubes. This says OpenStack dashboard, it's an interface that's so pretty and neat. It's definitely the marketing version, because the reality is kind of more like this. I don't know if you can actually see that, because of the awesomeness of the sun. Thank you, Sun. But it's actually four years old, even. It doesn't have all of the projects that are within OpenStack as an umbrella, and it's still this complicated and scary. The project I work on is triple O, not even on here. It's fine. It's fine. Because we're an installer, and this is just the main original big projects and how they interact. I would love to throw the challenge out to those of you watching later to update this picture. But I'm pretty sure it would just be a massive flying spaghetti monster who scribbles craziness and be even scarier. But I think there are neat designers out there. So what you need to know, take away from this, is that OpenStack is an umbrella project. It's massive. It's chaos. If you actually want to contribute, you kind of need to find a sub-project within OpenStack to contribute to. If you're good with hardware, I would send you to one project, or Ironic. If you're good with design, you could go the gamut of the projects. Everyone needs design, but specifically I would go to the dashboard interface. So don't be intimidated by OpenStack, although everyone is. Just think of it as an umbrella. So then what is Arteo? There was a joke for a long time because our developer advocate used to sell a company, his name was Rich, and then they hired Rain, and we would say it's Rich's distribution of OpenStack. And Rain's distribution actually doesn't stand for anything, because in the Linux world, oh yeah, I work for a Linux company, we like to mess with people. Maybe the recording should be paused. No. So Arteo doesn't actually stand for anything, except they always definitely openStack. But what it actually means is we just take all of OpenStack, that huge umbrella, and as soon as they release every six months their packages, we take them and make them all RBM packages, so that you can use them on Red Hat Enterprise Linux, Scientific Linux, CentOS, etc. But otherwise, it's exactly the same. So when people say what's the difference between OpenStack and Arteo, nothing, except it's RBM. Okay, so then the fun part, to me, and what is TripleO? It's OpenStack on OpenStack, and there were a few reasons why I've started. One of the my favorite reasons is what if just to see if it could work. And there's even OpenStack on OpenStack just to see what could happen. It's very slow, FYI. But it was to address cruft with utilities, with resources that are the underlying bits of the cloud. It was also done for simplicity's sake. And it was done so that if OpenStack releases every six months, and if you released a cloud for a developer a year ago, it would have been no, I'm not going to go there. It would have been one version. Six months later there's another version and they also want to test their out on both versions. Then with OpenStack and OpenStack you just go here, here's the latest version, instead of taking this one down or having to rebuild it. TripleO allows you to do that and how. So, originally if you wanted to have an OpenStack instance, just one, you just take OpenStack and run a series of commands. A lot of companies went okay, but let's say I want to be able to just press three buttons or have a lovely interface or I'm Amazon and I want to rent out several instances. Those companies all write their own versions and some of them are open source or proprietary. But all of them except TripleO use a new set of skills in order to deploy those actual versions of OpenStack. What TripleO does is I know how to deploy one instance on OpenStack therefore I can deploy tons of instances of OpenStack into the TripleO. It's exactly the same interface except it says TripleO instead of OpenStack. Does that make sense? So, I heard the recursive joke about the turtle. A professor was giving a talk about the solar system and the sun and planets and blue toy all the planets plus that other one. And he finished the talk and a little sweet person came on and said that's not correct. It's a nice talk. It's not correct. And he said really when is it correct in your world? And they said well obviously the world is a plate that is resting on a turtle traveling through space. And okay so then what is the turtle resting on? And they said this turtle is all the way down. This joke is used typically to explain recursion but it actually also explains below. It's OpenStack and then you always have to have OpenStack to deploy that OpenStack. One of the things that we do is we require that the under cloud the base turtle or owl have very specific components that are required. They're required to be able to manage resources to be able to recognize what it's working with to be able to recognize exactly what you're looking for to spin up. But the over cloud or multiple over clouds can be built of anything if an application developer needed a specific stack with a certain amount of space and processing. They can say okay I need XYZ and then the under cloud would go okay I have this hardware system that is exactly like the cloud you need here you go. Because if you had a person or a script that gave one piece of this hardware and another piece from Max then suddenly the cloud doesn't run as efficiently. So the under cloud does a lot of those demonstration tasks automatically 40. And now for a couple of details about the actual hardware. So you need a host machine and that host machine has to have at least 16 gig RAM for like 32 gig. That's a recent increase which kind of sucks but open stack just keeps getting bigger and keeps needing more space and you must be able to SSH the host machine as root with our main password and thank you to Jeremy for actually talking briefly about SSH and not getting the password. The host must be running a recent red cap based Linux distribution such as CentOS 7, REL 7 but currently only CentOS 7 is tested. This is actually often a non-starter for people the 32 gig part. I don't know about you but before I was an engineer actually on this project testing the script I did not just have a laptop or a desktop on my desk an extra 1.32 gig of processing power so right now what we are heavily doing is experimenting with putting the undercloud in one system and the processing the overclouds through another system because often people will have multiple smaller systems than the 32 gig. So right now if you go to the documentation for www.tripleo.org you can see that it's hardware specific but that is still pages and pages of commands of bash commands so if you're not familiar with bash that can be intimidating and if you're a human which I'm 95% sure of which you are thank you Karen you might do typos copy and paste can get boring you can still forget characters beginning with and even with your copy and pasting so one of the things that we are working on right now and that is actually starting to be released is the www.tripleo.org quick start script and it's three lines of bash commands which is much more reasonable than seven pages of bash commands and one of the other things to do is at conferences we get out these handy handy usb's that happen to have the scripts on them I only have this one sorry but if you need it over the stack summit and I'll look you up or email me directly and I will bail you on or you can curl down the latest version of the script now who here thinks that three lines of code in bash is easier than the seven pages would anyone prefer the seven pages because right back it's hiring so right now very much we are looking for people who will run these commands and if you have their own and would like to test that so if you would like to just leave the top right this second you can take these three lines of command see what happens and then email me at redhat.com and be like that didn't work or that worked awesome now what and just in case it didn't run perfectly now this slide is recording because we can't see it so the actual steps to becoming an ATC and these are very specific to triple O and to RDO but one of these steps can be used within any project with an open stack but also if you look at open source projects of any kind because there's open data there's open government there's frequent raspberry ties there's all kinds of open source projects out there and they're going to have some semblance of these projects to join the project ish okay so step one is for open stack which I know it starts with no it gets started by signing up as a community or a foundation member the difference is very very slight it just means that you'll vote if you're a foundation member whereas if you're a community member it means you're on vote and just no big deal for the board, for the foundation members if you don't be is for get hub still not matching if you don't already have a get hub account get one today and then download get seek, communicate or connect sign up for RDO and open stack developer and just haunt them just to kind of get a feel to the kind of communication going on get it on free node IRC and join RDO and triple L you can use webchat.freenode.net but it's kind of limited and then say hello to the community member call me Dia's documentation and I will say that I I earned my last two ATCs which by the way let me go in sidebar so there's open stack summit twice a year and it's very expensive for an individual I go as part of my company but if you were an individual developer you might not have $600 to shell out for it to get if you go fix a typo in open stack documentation any of the projects and it gets vetted and used which can happen in as little as one hour you get an ATC code to the next open stack site that completely is $600 I earned my last two ATCs in one day of work because I submitted one typo and it was immediately accepted and then one of the other typos took a few more weeks to go through and we had a release date and therefore I got the ATC code for the current release and the subsequent release which is $1,200 worth in one day that's why being an ATC is kind of cool so documentation should be your first step I don't care how good of a coder you are or what you do read the documentation go through it, follow it and see if it works and if it doesn't work get on my and then edit it you earn your ATC code so E is the installation which I just said follow the instructions ask questions and then F is Contribute it's the actual process of submitting the typo and open stack actually has a sandbox with a step by step tutorial of how to actually file a ticket for me the scary point was going from submitting the ticket in the sandbox which is if you mess up, who cares nothing happens and then actually submitting that first typo which was just a typo it was literally I'll never forget this um in branding when you say Red Hat Enterprise Living it's the very first time you write it it has to be written out and then call references after that you can say route and in the documentation they've not done that and so I just submitted that and it was instantly approved but actually submitting that first ticket was really scary because this was real and I knew it would be changed and so I just had an engineer in front go through those first steps with me and that's what I'm here to do for you get on IRC and we will do those last steps together and then you will be addicted and I'm sorry that it will become an obsession not really smart these are all of the references to the things that I've talked about you don't have to remember it's a thing it might emphasis on the might not for the perfect play and that's why you have my email address that's why you're on IRC and these are documentation for backup if you want to read through them first before you ask me questions but sometimes you just want to go straight to ask me questions it's awful alright I'll just read this so these are actual sets on how you can contribute which is very tiny on my screen as well so you can give feedback and update so you can submit an update code which is awesome you can attend conferences, meetups and events you can ask and answer questions on IRC mailing list askopenstack.org you can follow, tweet and tag at our neander or at rinleyander at rdocommunity and parentstripleo on social media you can vlog podcast your experiences, tweets and hacks or you can give a talk at code days on how to get tripleo atc thank you