The openstack-nova-volume service requires an LVM Volume Group called nova-volumes to exist. We simply create this using a loopback sparse disk image.

+

Now copy the keystonerc file created by the install script above to your home directory, so that it can be easily sourced to provide the credentials used by the various OpenStack command line utilities.

The OpenStack dashboard is the official web user interface for OpenStack. It should mostly work out of the box, as long as keystone has been configured properly.

−

−

* Install the dashboard

−

$> sudo yum install openstack-dashboard

−

−

* Make sure httpd is running

−

$> sudo service httpd restart

−

$> sudo chkconfig httpd on

−

−

* If selinux is enabled, you will have to allow httpd to access other network services (the dashboard talks to the http API of the other OpenStack services)

−

$> sudo setsebool -P httpd_can_network_connect=on

−

−

The dashboard should then be accessed with a web browser at http://localhost/dashboard . Account and password should be

−

what you configured for the keystone setup.

−

−

−

−

To open up the firewall ports for HTTP:

−

$> sudo lokkit -p http:tcp

−

$> sudo lokkit -p https:tcp

−

−

== Configure swift with keystone ==

−

These are the minimal steps required to setup a swift installation on RHEL which keystone authentication, this wouldn't be considered a working swift system but at the very least will provide you with a working swift API to test clients against, most notibly it doesn't include replication, multiple zones and loadbalancing

−

−

Ensure the keystone env variables are still setup from the previous steps

If you use the Chrome browser, kill it before embarking on this section, as it has been [https://bugzilla.redhat.com/show_bug.cgi?id=727925 known] to cause the lvcreate command to fail with 'incorrect semaphore state' errors.

If you use the Chrome browser, kill it before embarking on this section, as it has been [https://bugzilla.redhat.com/show_bug.cgi?id=727925 known] to cause the lvcreate command to fail with 'incorrect semaphore state' errors.

+

+

Note when setting up volumes in production, make sure you don't put your volume nodes on the same network as your guests

+

when using the default volume driver, as all the iscsi targets are discoverable and accessible without any security.

Install and Setup OpenStack on a single node

Now copy the keystonerc file created by the install script above to your home directory, so that it can be easily sourced to provide the credentials used by the various OpenStack command line utilities.

sudo cp /root/keystonerc ~

Installing within a VM

If you are testing OpenStack in a virtual machine nova needs to be configured
to use qemu without KVM and hardware virtualization.
Note nested virtualization will be the much slower TCG variety, and you should provide lots of memory to the top level guest,
as the openstack created guests default to 2GM RAM with no overcommit.
Note openstack-demo-install does this automatically:

Nova Network Setup

NB the network range here, should *not* be the one used on your existing physical network. It should be a range dedicated for the network that OpenStack will configure. So if 10.0.0.0/24 clashes with your local network, pick another range

Register an Image

To run an instance, you are going to need an image. There are prebuilt Fedora 17 JEOS (Just Enough OS) images that can be downloaded.
Note this will download a 250MB image (without a progress bar)

Volumes

If you use the Chrome browser, kill it before embarking on this section, as it has been known to cause the lvcreate command to fail with 'incorrect semaphore state' errors.

Note when setting up volumes in production, make sure you don't put your volume nodes on the same network as your guests
when using the default volume driver, as all the iscsi targets are discoverable and accessible without any security.

You should also make sure that openstack-nova-consoleauth has been started on the controller node:

$ controller> sudo /etc/init.d/openstack-nova-consoleauth restart

After restarting nova services on both nodes the newly created machines will run the qemu-kvm with a parameter -vnc compute_fqdn:display_number.
Then after starting the novncproxy and connecting to the dashboard it will discover the host and point to the novncproxy with the appropriate values and connect to the VM.

Note ensure than the iptables entries for VNC ports (5900+DISPLAYNUMBER) are allowed.

Migrate and Resize

This is implemented currently by transferring the images between compute nodes over ssh.
Therefore currently you need to make these adjustments on each compute node to allow that.

Now everything should be running as before, except the VMs are launched either on controller or node. You will only be able to ping/ssh to vm's from the controller node.

Manual Setup of MySQL

As of openstack-nova-2011.3-9.el6 and openstack-nova-2011.3-8.fc16, openstack-nova is now set up to use MySQL by default. If you're updating an older installation or prefer to set up MySQL manually instead of using the openstack-nova-db-setup script, this section shows how to do it.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.