Today I decided to set-up a new OpenStack environment to run some tests and provide a training on it.
This blog post will cover “OpenStack – Icehouse Deployment Via Packstack”.

There are several ways to deploy a OpenStack environment with a single-node or a multi-node:

1. Packstack – Quickest and easiest way to deploy a single-node or multi-node OpenStack lab on any RHEL distribution
2. Devstack – Mainly used for development, requires more time then packstack
3. Juju – Very time-consuming setup but very stable, Ubuntu only.
4. The manual way, most time-consuming, recommended for production environments.
   Detail can be found here.

In my scenario I deployed 4 CentOS 6.4 64bit VMs with each having 2x2vCPUs, 4GB memory, 2x NIC cards (one for MGMT, one for iSCSI – no MPIO).
After you completed the CentOS 6.4 installation, follow the steps below:

1. Shell

   Install the RDO repositories [root@TS-Training-OS-01 ~]# <strong>sudo yum install -y http://rdo.fedorapeople.org/rdo-release.rpm</strong>

   1 2	Install the RDO repositories [root@TS-Training-OS-01 ~]# <strong>sudo yum install -y http://rdo.fedorapeople.org/rdo-release.rpm</strong>

2. Shell

   Install openstack-packstack [root@TS-Training-OS-01 ~]# <strong>yum install -y openstack-packstack</strong>

   1 2	Install openstack-packstack [root@TS-Training-OS-01 ~]# <strong>yum install -y openstack-packstack</strong>

3. Shell

   Verify that packstack has successfully been installed [root@TS-Training-OS-01 ~]# <strong>which packstack</strong> /usr/bin/packstack

   1 2 3

   Verify that packstack has successfully been installed [root@TS-Training-OS-01 ~]# <strong>which packstack</strong> /usr/bin/packstack

4. Shell

   Use packstack to deploy OpenStack. Syntax - <em>$ packstack --install-hosts=Controller_Address,Node_addresses </em>[root@TS-Training-OS-01 ~# <strong>packstack --install-hosts=10.18.48.50,10.18.48.51,10.18.48.52,10.18.48.53</strong> In my scenario 10.18.48.50 will be used as the controller and .51, .52 and .53 will be used as NOVA compute nodes.

   1 2 3

   Use packstack to deploy OpenStack. Syntax - <em>$ packstack --install-hosts=Controller_Address,Node_addresses </em>[root@TS-Training-OS-01 ~# <strong>packstack --install-hosts=10.18.48.50,10.18.48.51,10.18.48.52,10.18.48.53</strong> In my scenario 10.18.48.50 will be used as the controller and .51, .52 and .53 will be used as NOVA compute nodes.

5. Shell

   Once the installation has been completed, you'll see the following output on your CLI: <strong>**** Installation completed successfully ******</strong> Additional information: * A new answerfile was created in: /root/packstack-answers-20140908-134351.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be a problem for some OpenStack components. * File /root/keystonerc_admin has been created on OpenStack client host 10.18.48.50. To use the command line tools you need to source the file. * To access the OpenStack Dashboard browse to http://10.18.48.50/dashboard . Please, find your login credentials stored in the keystonerc_admin in your home directory. * To use Nagios, browse to http://10.18.48.50/nagios username: nagiosadmin, password: some_random_password * Because of the kernel update the host 10.18.48.50 requires reboot. * Because of the kernel update the host 10.18.48.51 requires reboot. * Because of the kernel update the host 10.18.48.52 requires reboot. * Because of the kernel update the host 10.18.48.53 requires reboot. * The installation log file is available at: /var/tmp/packstack/20140908-134351-aEbkHs/openstack-setup.log * The generated manifests are available at: /var/tmp/packstack/20140908-134351-aEbkHs/manifests

   1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

   Once the installation has been completed, you'll see the following output on your CLI: <strong>**** Installation completed successfully ******</strong>   Additional information: * A new answerfile was created in: /root/packstack-answers-20140908-134351.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be a problem for some OpenStack components. * File /root/keystonerc_admin has been created on OpenStack client host 10.18.48.50. To use the command line tools you need to source the file. * To access the OpenStack Dashboard browse to http://10.18.48.50/dashboard . Please, find your login credentials stored in the keystonerc_admin in your home directory. * To use Nagios, browse to http://10.18.48.50/nagios username: nagiosadmin, password: some_random_password * Because of the kernel update the host 10.18.48.50 requires reboot. * Because of the kernel update the host 10.18.48.51 requires reboot. * Because of the kernel update the host 10.18.48.52 requires reboot. * Because of the kernel update the host 10.18.48.53 requires reboot. * The installation log file is available at: /var/tmp/packstack/20140908-134351-aEbkHs/openstack-setup.log * The generated manifests are available at: /var/tmp/packstack/20140908-134351-aEbkHs/manifests

6. Shell

   Reboot all hosts to apply the kernel updates.

   1	Reboot all hosts to apply the kernel updates.

7. Shell

   You can now access Horizon (dashboard) via the IP-address of your controller node, in this scenario http://10.18.48.50/dashboard

   1	You can now access Horizon (dashboard) via the IP-address of your controller node, in this scenario http://10.18.48.50/dashboard

8. Shell

   If you prefer the CLI, SSH to the controller node and source the keystonerc_admin file to become keystone_admin.

   1	If you prefer the CLI, SSH to the controller node and source the keystonerc_admin file to become keystone_admin.

   
   
   Shell

   [root@TS-Training-OS-01 ~]#<strong> source keystonerc_admin </strong>[root@TS-Training-OS-01 ~(keystone_admin)]#<strong> You are KEYSTONE_ADMIN now!!!</strong>

   1 2	[root@TS-Training-OS-01 ~]#<strong> source keystonerc_admin </strong>[root@TS-Training-OS-01 ~(keystone_admin)]#<strong> You are KEYSTONE_ADMIN now!!!</strong>

The initial install of OpenStack via packstack has been completed and you can start to configure it via CLI or using Horizon.