All the steps I will be showing you are documented, and they can be
downloaded as a lab description. So don't try to take notes,
and just sit back and enjoy. Depending on your internet connection,
the whole process from start to end can take up to 2 hours and perhaps
a bit less. I will show you how to install Packstack Newton,
which is not available anymore on the RDO website, so a little bit of
tweaking is now required to do that, but it's possible without too much effort.
The first thing we need is obviously an operating system.
CentOS 7.3 fits Newton the best, and my recommendation is to install a
Minimal operating system. I'm picking up the ISO location,
and download the ISO to my virtual machine host.
And after that, I can install my system, let's just say that it is installed.
And I can log onto it. So this here is my totally new and fresh
CentOS 7.3 installation. The first thing we need to do is adapt the
repository files, they still contain pointers to repositories which
don't exist anymore, we have to tweak those a little bit.
The first is we cannot have the mirrorlist directive in there,
and instead, we will enable the baseurl directive.
Then finally we also have to tweak that baseurl directive a little
bit, and we have to do that for all the files in there.
That's the way it looks. Instead of the mirrorlist, we now have the baseurl enabled.
Before we do anything, let's ensure that we have an updated system.
And when that is done, we also have to ensure that neither the
firewall daemon nor Network Manager are running.
So we stop them, and we also disable them to ensure that they don't
start when the system runs. At this point, we can now install the
OpenStack Newton repository, that will be quick, it's just a few
repository files that have been installed here.
It's these three files that I'm talking about, we don't really need
the Ceph one, just the two others. We still have a base, a wrong base
URL in there, and we have to move it, we have to let it point to a
different repository, so we replace the mirror.centos with a
vault.centos URL. Oops, and then we can install Packstack.
That's going to take awhile, so let's just assume that it's done.
And we are now ready to run Packstack. Before we do that though,
let's ensure that our non-root user stack can become root without a password.
So we will enable the NOPASSWD option here.
And at this point, we can deploy the cloud with the Packstack command,
and a few additional options explained in the document with the instructions.
Note this log file here, this will be useful to follow the installation process.
It takes about an hour to install Packstack, it depends on how good
your internet connection is, and how fast your disks are.
Let's look at this log file, it contains a reference to another log
file, and it is there that we see what the deployment process is currently doing.
Alright, after an hour, I hope that you see this, Installation completed successfully.
Let me point out a few details here. The answerfile, that's the file
that contains all the options that we provided on the commandline and
quite a few options more. It will be useful to change certain aspects
of the cloud or to add hosts to the cloud, it's currently an all-in-one cloud.
The keystonerc file that is highlighted here, that's a file that
contains the credentials, they are needed to use OpenStack from the commandline.
If you want to access the GUI, you'll use this URL.
Credentials again can be found in the keystonerc file.
Finally, this remark here, you can ignore, there is no need at this
point to reboot the system. Let's run a few commands to test the
cloud, for this I go back to my home directory, and I'll source one of
those keystonerc files. Let's start with the demo one.
I will run a command that checks my credentials, token issue, and that looks good.
The next command I will run is as system administrator, and for that I
will source the keystonerc_admin file. And I will run a command that
checks on all the components of Nova, the compute service.
And as you can see, all components seem to be enabled and up.
This is indeed good news, our cloud seems to be in operation.
You may also want to check whether you can access the GUI,
and that seems to be the case here.
Before we conclude the demo, one step to make our Packstack machine a
bit more robust. OpenPack, or Packstack rather implements the
external network on an open vSwitch bridge named br-ex,
and the address on that bridge is not persistent, it will disappear
after a reboot. So let's make it persistent by creating an ifconfig
file for this bridge. The important parameters here are the IP
address, which we got from the IP command earlier, and the prefix,
which we also have from that command. And now our system or the
external network will survive a reboot. What if you forget to explore
this IP address? You can find it in the answer file under this
configuration parameter here. That is the IP address range of our
external network, and the bridge just needs the first address from
that range, which will be 225 in this case.
Now it's your turn, download the lab description, install Packstack,
and follow the lab instructions to discover your cloud, and have fun.