By default, the packstack installer uses either a volume group named cinder-volumes or a loopback device as back end for the Cinder block storage service. For professional purposes, this is not enough; the usual requirement is to have a redundant storage back end. If you have an existing Red Hat Storage service, you might want to use one of the GlusterFS volumes as back end for the block devices your virtual machines use in the Red Hat Enterprise Linux OpenStack Platform cloud.
Before starting the configuration, you must remove all existing Cinder volumes, or you will run into problems. To figure out if there are any existing volumes with your current Cinder setup issue:
If there are any volumes listed, delete them with:
cinder delete volumename
Now that you have a cleaned-up Cinder setup, you can configure the back end to exclusively use the Red Hat Storage GlusterFS volume(s).
Start off by installing the GlusterFS-fuse package on the Cinder host, available in the Red Hat Storage Native Client repository from Red Hat Network.
To install Red Hat Enterprise Linux OpenStack Platform manually can be an odious task, but packstack can assist in making the installation much easier and consistent. Normally, packstack is run from the controller node, which can either be a physical machine or a virtual machine.
Start by installing the machine with the latest Red Hat Enterprise Linux. Subscribe to the Red Hat OpenStack channel, as well as any other channels desired.
Next, install the openstack-packstack package using yum: ~]$ sudo yum install openstack-packstack
As root, use packstack to generate an answer file: ~]# packstack –gen-answer-file ~/answers.txt Continue reading →
With OpenShift Enterprise by Red Hat®, developers can now produce and support more applications faster. Implementing proper workflow processes across your organization lets you cut development time even further and work toward a true continuous deployment model.
Faster app deployment, higher-quality software
Through continuous integration, you can make sure your organization gets the full benefits of OpenShift Enterprise. Not only will you deploy applications quicker, your software quality will improve.
In this webinar demo, Red Hat Consulting walks through the steps for streamlining your development process so you can reduce deployment time by: Continue reading →
If you’re maintaining multiple Red Hat Enterprise Linux systems (or equivalent offsets like CentOS or Scientific Linux) your administration work with the particular hosts will gain in a routine. Because even the best administrator might forget something it would be advantageously to have a central software and configuration management solution. Chef and Puppet are two very mighty and popular mangement tools for this application. Depending on your system landscape and needs these tools might also be oversized though – Red Hat Package Manager (RPM) can emerge as a functional alternative in this case.
It is often forgotten that RPM can be used for sharing own software and configurations as well. If you’re not managing huge system landscapes with uncontrolled growth of software and want to have a easy-to-use solution, you might want to have a look at RPM.
I’m myself using RPM to maintain my whole Red Hat Enterprise Linux system landscape – this article will show you how easy RPM can be used to simplify system management.