Our New Tech Corner
Installing RedHat Enterprise Linux OpenStack v6.0 on RHEL7
1. First, we need to ensure that we have a single physical server that supports hardware virtualization, has a RHEL 7.1 minimal installation, one functional network interface (eno1 in this demonstration), and has subscriptions to RHEL Server and RHEL OpenStack. If you do not own the required licenses, you will need to purchase subscriptions before beginning or request an evaluation copy from Redhat.
2. Once the pre-requisites are satisfied in step one, we install a text-editor, net-tools for some network utilities that are excluded in the minimal install, and subscribe to the repos we need:
3. We then need to ensure all packages are up to date, disable the NetworkManager which conflicts with OSP, and reboot to apply the changes:
4. Once the server comes back online, we need to install the installer utility that we’ll use for the OSP all-in-one installation. In this case, we’ll use the packstack installation utility:
At this point, you’ll want to take a break as the packstack installer will take a while to install the OpenStack dependencies and services.
Note: When you run packstack –allinone, an answers configuration file is automatically generated with system defaults. If you want to customize these defaults before running packstack, first generate the answers file, then edit it, and afterwards run it as follows:
5. Once complete, we’ll need to do a little work to setup public and private networking for your instances. This guide assumes that you have one network interface (eno0) assigned with a statically routed CIDR subnet of same size.
First, we are going to connect to Neutron to clear out the default network config that was loaded:
6. Now we need to make some changes to your network interface configuration. Essentially, we are going to move it’s configuration to a new bridge (br-ex) interface that your instances will use to communicate outside the physical host, and map it back to the same eno1 physical interface.
First, open the configuration the eno1 interface configuration. Before making any changes, it’s helpful to copy and paste the contents of the file to a local text editor:
You want to remove the existing configuration and update this file to look like the following, assuming your interface is also eno1 (adjust the name accordingly):
Now, save your changes and create the bridge interface configuration:
Add the following configuration, updating my_host_ip, my_netmask, and my_host_gateway with the values retained in the last step from your ifcfg-eno1 before you changed it.
Save your configuration and reboot.
7. Once the server returns online, we’re ready to configure some sample networks that your instances will utilize. You may wish to setup a different network topology and you can reconfigure it later if you desire. In this case, we’re going to create a public network using a pre-assigned, statically routed public subnet. These addresses will be used as floating IPs in Neutron. We’ll also create a private network and assign it a subnet that Neutron will manage.
Now, to setup the aforementioned network topology:
In the above command, you’ll need to substitute the values given to you by your network administrator for your statically routed secondary subnet.
Start_usable_ip should be the first usable IP in your range
End_usable_ip should be the last usable IP in your range
Gateway_ip should be your default gateway
Network_IP/CIDR should be the network address, followed by your cidr subnet size.
Lastly, create a router in Neutron and configure it to complete the network topology:
8. You're now ready to start creating instances! Navigate to your Horizon dashboard utilizing your web browser. By default it is listening on port 80 using the ip of your br-ex interface.