Install Openstack Ocata on CentOS using RDO

today I'm going to do a demonstration on how to install the latest version of OpenStack I've made a couple of these videos in the past but I recently did it with the Academy lease and PAC stack which is the all-in-one OpenStack installer from the RTO project is a lot simpler now is that it was always simple and I was doing it the hard way so I did want to re-record it just for the new release and to show how there are some shortcuts especially when it comes to the network setup so here's a refresh as this video like just like in the previous ones we're going to start with the RTO install pax pack Quick Start Guide so we're going to just jump right in here so the first step so there's actually some steps before this that we need to do we need to disable firewall D and network manager so we can do that and then we're going to enable the more basic network service and it's because the dynamic nature of network manager doesn't play well with Neutron where the basic network service just kind of does a one-shot configuration of the server of the network at the beginning and doesn't interfere after that I also have SELinux disabled which I haven't tried with it on the policies might actually match but this has always been a pain point in the past and because I am doing an all-in-one at home and it's really just for development purposes I run it with selinux disabled just to avoid pain points because when you hit those things sometimes it's pretty hard to figure out what's going on so in order to do that you can do get enforce zero to take effect immediately and then if you go into Etsy sicilus a linux config you can change this selinux variable to either disabled or permissive and once we do that one thing that I did during install so this is that this is a fresh CentOS 7 3 minimal install is what I have here I haven't done anything else to it but I what I did do during the install is set up a static IP address on the ethernet interface so I can show you what that looks like so you should set up your network file to look something like this with your Ethernet device this your idea will be different but you do want to set um where is it here I'm looking for something in particular I'm not synced we got boot proto nothing brute proto none and then you gotta specify the IP address the site or prefix gateway DNS things like that so these are appropriate for my network and you need to you need to do this ahead of time and you also want to take note of what your Ethernet interface name is because we're going to use it later in the pack static configuration so after we do that I'm going to reboot this real quick just to make sure that SC Linux is disabled persistently and that our network service configures the network interfaces rather than network manager you can probably just stop Network managers and start Network but doing this make sure that you've done the persistent configuration properly and it doesn't take very long so the machine is coming back up here you may have noticed that I've also already configure for my network I've configured this machine with a DNS name OpenStack that's also something that I did during this in the Installer and you don't necessarily have to do that it just makes it cleaner alright so we're back into OpenStack and make sure that our interfaces are configured properly and they are so now we're going to start in the M on the M QuickStart here so we'll do the environment we will put these in there alright and then we're going to go through this the rel instructions we're going to do this and toss instructions here so it installed the repository for our kata alright and then we will I did from a local mirror here that's fully up-to-date with my installation so that's not going to do anything so we're just going to install packs back from here hopefully it won't take too long so if you're unfamiliar with pack stack pack stack is a tuffet based installer for opens back and so it and it makes the process of deploying all the OpenStack components and linking all together fairly straightforward alright so that we've done that the QuickStart says to do pack stack all in one and really the older one installs more than I like so I like to change the settings on this so I'm going to show you how to do that so if you do pack stack gin and serve file and say equals answer text then it will dump all the configuration variables out to this answers file and you can go in and change them which basically controls how packs the packs effect and cellar works so the first change I like to do for an all-in-one is change these config and change the config service workers from processor count which on my machine is twelve it is way more than I need for my setup I change it to one and then I go through and for me I just like to be able to download images and then start them up easily I don't really care about them have any persistent block storage or I don't care about Swift or heat because I'm not deploying complex templates or anything like that so really the setup that I'm right here is basically just glance Nova and Neutron along with Verizon which is the dashboard and Keystone which is required it's the identity service for open Zak so I kind of do a basic install but this will let you get you know just download cue cow two images from wherever and start them up in a virtualized environment so I'm going to say no to the cinder install glances the image store we do need that Nova is compute Neutron is network Verizon yes Swift is the object store and that Swift really does have a lot of components and probably should be a separate thing if you're deploying it in a production environment in an all-in-one it doesn't make a whole lot of sense and it's pretty resource intensive selamat errors don't care about metering or telemetry or meatery metering as a service as you can see there are quite a few sub projects here but we didn't want that we do with the client to install no Nagios okay so that's good so basically the config underscore things are all the main components of OpenStack and whether you want to install them or not up at the top and then there's one other thing we need to change and that is the bridge I phases so this right here with the way I'm going to set it up set it up in videos past I've created an external network and then you've had an internal network and then there's netting and bridging between the two of them and things like that but yet has set up floating IPs and for every instance that you start if you want external access to it yet the configure a floating IP when really for what for my needs really all I wanted to do was start up a VM and it be immediately available in a external network I always configured floating IP s with them and that was just one extra step and so since then I've realized there's a way to put your instances right on your external network and this is the way to do it so if you look here a config new toronto vs bridge mappings you have x net to the external bridge you can map this x that to a actual Ethernet interface on your machine so that's what I'm going to be doing here so I'm going to map the external bridge to np0 s 25 and so that is the name of my interface here so if I send back in took that one more time in p0 x-15 I typed it right ok and then we also need to note this that this is the default here but X net we're going to need this when we are configuring our external network in horizon after the installation so keep that in mind so after we do that that it's all set up paternity out so we just need to do pack stack answer file equals plane type answered tht and then that will start the installation so this takes a little while I'm going to cut and come back when it's done ok so that finished so now it you know again gives us our IP address so we can connect to the horizon dashboard on so we'll do that next we're going to need something out of here we need the Installer creates these Keystone RC files one for the demo user one to the admin user we're going to log in as the admin user and the password that it generated is right here here's it will be different so put that in admin and now we're into our opens back installation so there's some cleanup things well there's some things the Installer puts in that I like to clean up before I start putting instances in here one of them is the demo tenant and project so I delete the demo project and then I delete the demo user and the go ahead and change the password on the admin user so that I don't have to go put to that keys down admin file every time so just change some that is something that you can easily remember if I can type it twice and then how to login with that in your password after that okay and if we go into the admin tab here the flavors that it preloads are typically too big for what I use it for like this right here I mean that's a flavor I'm never going to use right there so I like to clear these out and just make a couple of flavors that are appropriate for the machine I've got this installed on so we'll call this in one small we'll say two CPUs two gigs of RAM a 10 gigabyte disk and that'll be good if we go under images here the it preload the Cirrus image and I never use that so due to some permissions configuration and horizon even as the admin user not allowed to delete that so a little key for that is if you source the Keystone RC admin file will change their password so let's check let's update our password in this file first and you'll see my password it's super secure here opens back and then we'll source that and then we'll run the OpenStack client we can do image list let me see the Cirrus image there we used to image delete Cirrus okay put that if we go here and refresh our serious image is gone the networks we need to clear out the routers first it creates a demo router and an external network which isn't going to be appropriate for your network most likely so we'll start from scratch on this stuff delete the routers delete the networks okay and then we're going to create a new network we're going to call it external and we're going to make it part of the admin project and then we're going to the network type here we're going to say flat and this is where over here in our answers file if you remember we this x net right here this is where it comes in so we need to name our flat network this so we're going to call it extent there and this is going to be shared among the projects and external so we'll do that then we can go create our subnet for this external Network so the sudden that this will be different for you you will follow the same process but depending on what side or network you're on and things like that you'll upman what your gateway is what your DNS server is you'll have to do different things so this will this is the one for me that's in the room blank their network address subnet name external you can call this whatever you want the gateway IP for my network is this if we go here we are going to want to enable DHCP and it's going to actually assign us addresses that are appropriate for the external network since we're it weren't a Flatwood network here and so you need to create a pool that is if you have a DHCP server on your primary subnet you need to choose a set of IP addresses that are outside the DHCP range of that DHCP server on your subnet so for me this is a set of addresses that isn't on that my DHCP server will never assign and this is the DNS server provided network so we'll create that ok so now because we're doing with a flat external network we don't worry about floating IPS at all which is for at least in my workflow very nice since I want all the instances I start up to be accessible in the external network anyway so let's go into the project here if we go into images we don't have any images I think I have one downloaded let's see um yes so that will do 426 alpha share and we will or this is a beta image actually put that in there Q count to set them in with this size create the image all right we're also going to need to add our key pair so I have an existing one you can hit create key pair and will generate one for you and you can say the private part onto your drive and use that when your ss-18 into these instances I'm going to import mine so meaning come over here get a new hope new tab mint and then this will be so the key that I use so put that in here Yuki okay the next thing we need to do is set up our security groups so by default all ingress is blocked except from other instances so we're going to and I don't use ipv6 songs be clear those rules out too so we're going to delete both the ipv6 rules and the ingress rule for ipv4 and recreate it we're going to add a rule go to other protocol and leave all this blank and that will that basically is a rule that will let in all ipv4 traffic on all protocols so that's that's letting everything in and out again this is not a secure setup but this is very nice if you want to just be able to start instances than be immediately accessible on the external network and all the reports be accessible okay so if we come to compute now and we go to images then we can launch this we'll call it test we're going to get one flavor source image will be here and the network we've only got one so it adds it automatically which is the external Network and we'll launch it and if we did everything right this should work all right and it started up so if we go in here we should see the instance booting up and we do which is great cloud and it should be installing our key and setting everything up so let's see if we can log into this thing in fairly short order we go back to instances you can see that I've got my external IP address here so I should just immediately connect to it using the Fedora user so if I say Fedora at that address see what it's doing here oh I did forget a step alright here we'll try this a we'll do this again won't take long to correct so clouding it was not getting an IP address and the reason it wasn't is because you have to change one setting in the new drunk config file for allowing the DHCP metadata to pass properly so we are going to come back over here and go to SC Neutron and we're going to go into DHCP agent I and I and we're looking for a setting let me remind myself of what it is enable isolated metadata so isolated here and so it's set to false we want to change it to true then after we do that we need to control restart see if I can type this in write neutron DHCP agent will cause the neutron DHCP agent to pick up on our changes to the ini file there all right so let's try to start this instance again test okay so let's watch the logs we should see cloud in it configure this IP address this time I guess there's all our IP configuration so now we should be able to get into this instance so I think it got the same IP address that we had before so let's try that again and there we go we're in and we have that public IP IP configured on the zero inside the instance and we can get to the outside no problem so there we go so that you know no matter of ten 50 minutes you can set up your own OpenStack all in one and with this the networking is largely taken care of by the Installer and the you have to mess with floating IP is because you're dealing with a flat network on the external and no firewall rules so I find this very helpful for development when I just need to quickly spin up a machine and have full access to it immediately on the external network so hopefully this was helpful

Channel: Seth Jennings

Views: 17,438

Rating: 4.9106145 out of 5

Keywords: openstack, centos, cloud, linux, virtualization, rdo, redhat

Id: Udtr1zJhcrw

Length: 22min 1sec (1321 seconds)

Published: Tue Jun 27 2017