Deploying OpenStack in a Virtual Machine Environment Using OpenStack Deployment (TripleO) - Red Hat Customer Portal

5/9/2015

Deploying OpenStack in a Virtual Machine Environment Using OpenStack Deployment (tripleO) Red Hat Customer Portal

C USTO ME R PO RTAL Products & Services  Knowledgebase  Articles Environment Using OpenStack Deployment (tripleO)



Deploying OpenStack in a Virtual Machine

Deploying OpenStack in a Virtual Machine Environment Using OpenSta Deployment (tripleO) ( Updated April 24 2015 at 3:23 PM

Introduction These procedures are for installing OpenStack in a host machine using the OpenStack Deployment service. This can be used for testing and evaluating the provisioning, configuring, and operating of OpenStack components. This material is for proof-of-concept testing and not recommended for enterprise environments. This setup creates virtual machines within a host machine. It creates three (3) to five (5) virtual machines, depending on if you choose to deploy block and object storage nodes, consisting of 4GB of memory and 40GB of disk space each. The virtual machine disk files are thinly provisioned and will not take up the full 40GB initially.

Technology Preview OpenStack Deployment (tripleO) is included as a technology preview in Red Hat Enterprise Linux OpenStack Platform 6.0. For more information on the support scope for features marked as technology previews, refer to https://access.redhat.com/support/offerings/techpreview/.

Contents 1. Minimum System Requirements 2. Preparing the Host Machine https://access.redhat.com/articles/1320563

1/19

5/9/2015


2.1 Host Setup 2.2 Virtual Machine Creation

Minimum System Requirements The minimum system requirements for the host machine to follow this tutorial are: Red Hat Enterprise Linux 7 At least (1) quad core CPU 12GB free memory 120GB disk space 1 If you want to deviate from the tutorial or increase the scaling of one or more Overcloud nodes, you will need to ensure you have enough memory and disk space. See the Red Hat Enterprise Linux 7 Installation Guide (https://access.redhat.com/documentation/enUS/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/) for help with installing Red Hat Enterprise Linux 7. See the Red Hat Subscription Management (https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/) guides for help with registering a system to the Red Hat Content Delivery Network and enabling repositories. 1 Note that the default partitioning scheme will most likely not provide enough space to the partition containing the default path for libvirt image storage (/var/lib/libvirt/images). The easiest fix is to customize the partition layout at the time of install to provide at least 200 GB of space for that path.

Preparing the Host Machine If you are connecting to the host machine remotely using SSH, you will need to use the -t flag to force pseudo-tty allocation or enable notty via a $USER.notty file. Do not use the root user for executing any instack-undercloud scripts. Some programs of libguestfstools are not designed to work with the root user. All of the instack-undercloud scripts were developed and tested by using a normal user with sudo privileges. 1. Ensure the system is up-to-date. Run 'yum update' and reboot if a new kernel is installed. 2. Make sure the sshd service is installed and running: $ systemctl status sshd

https://access.redhat.com/articles/1320563

2/19

5/9/2015


3. The user performing all of the installation steps on the host machine needs to have sudo enabled. You can use an existing user or use the following commands to create a new user called stack with password-less sudo enabled. Do not run the rest of the steps in this guide as root. Note the use of -, -l, or --login with the su command: $ sudo useradd stack $ sudo passwd stack $ echo "stack ALL=(root) NOPASSWD:ALL" | sudo tee ‐a /etc/sudoers.d/stack $ sudo chmod 0440 /etc/sudoers.d/stack $ su ‐l stack

If you have previously used the host machine to test tripleO, then there is a risk of conflict with scripts previously installed. It is recommended to clean up from any previous tripleO tests by deleting ~/.cache/tripleo and making sure there is no $TRIPLEO_ROOT defined in your environment.

Host Setup These steps will setup your host machine with a virtual environment for testing the Overcloud deployment. For more information about the changes performed, see the FAQ. 1. Make sure you are logged in as the user you created above. $ whoami

2. Add export of LIBVIRT_DEFAULT_URI to your bashrc file. $ echo 'export LIBVIRT_DEFAULT_URI="qemu:///system"' >> ~/.bashrc

3. Enable the Red Hat OpenStack 6 repository The following sections assume your system was registered with Red Hat Subscription Management during installation as described in the Red Hat Enterprise Linux 7 Installation Guide (https://access.redhat.com/documentation/enUS/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/). For additional information, see Using and Configuring Red Hat Subscription Manager (https://access.redhat.com/documentation/enUS/Red_Hat_Subscription_Management/). However, if you have not yet registered the system, do so now. Enter the following command and follow the prompts to register the system:


3/19

5/9/2015


$ sudo subscription‐manager register $ sudo subscription‐manager list ‐‐available | less

Search for the word "OpenStack", note the pool ID at the bottom of the section where "OpenStack" was mentioned and then proceed as follows: $ sudo subscription‐manager attach ‐‐pool= $ sudo subscription‐manager repos ‐‐enable rhel‐7‐server‐openstack‐6.0‐rpms Repository 'rhel‐7‐server‐openstack‐6.0‐rpms' is enabled for this system.

1. Install the instack-undercloud package. $ sudo yum install ‐y instack‐undercloud

2. Download the Red Hat Enterprise Linux 7 KVM guest image, rhel-guest-image-7.020140930.0.x86_64.qcow2, from the Red Hat Customer Portal. The image is listed on this page: Product Downloads (https://access.redhat.com/downloads/content/69/ver=/rhel--7/7.0/x86_64/product-downloads). Ensure the file name is correct after downloading. Note that the links do expire, so reload the page before copying the link. 3. Configure your environment by replacing the values in [ ] with the appropriate ones for your environment. These are the settings needed to run instack-virt-setup: export DIB_LOCAL_IMAGE="[/path/to/]rhel-guest-image-7.0-20140930.0.x86_64.qcow2" export NODE_DIST="rhel7" export REG_METHOD=portal export REG_PASSWORD="[your password]" export REG_POOL_ID="[pool id]" export REG_REPOS="rhel-7-server-openstack-6.0-rpms,rhel-ha-for-rhel-7-server-rpms" export REG_USER="[your username]" export RHOS=1 Note that you can find some of the above information with the following command: sudo subscription‐manager list ‐‐consumed ‐‐pool‐only

1. Run the scripts to install required dependencies https://access.redhat.com/articles/1320563

4/19

5/9/2015


$ source /usr/libexec/openstack‐tripleo/devtest_variables.sh $ tripleo install‐dependencies $ tripleo set‐usergroup‐membership

The previous command has added the user to the libvirtd group, so we need to login to the new group $ newgrp libvirtd $ newgrp

Virtual Machine Creation 1. Verify that your user has been added to the libvirtd group. The command shown below should show the libvirtd group listed in the output. $ id | grep libvirtd

2. Run the script to setup your virtual environment. $ instack‐virt‐setup

When the script has completed successfully it will output the IP address of the "instack" virtual machine. Addresses for the Undercloud are assigned by the host machine, using DHCP, from the 192.168.122.0/24 range, but 192.168.122.1 is reserved for use by the host. Running virsh list --all will show that you now have one running virtual machine called "instack", and four called "baremetal_[0-3]" all shut off. The "instack" virtual machine runs a minimal install of Red Hat Enterprise Linux 7 and will be used to install the Undercloud on. You can login to the "instack" virtual machine by running: $ ssh ‐i .ssh/id_rsa_virt_power root@

The virtual machine contains a user "stack" that uses the password "stack" and is granted passwordless sudo privileges. Once logged in as root to the "instack" virtual machine, you can become the stack user as follows (note the use of -, -l, or --login): $ su ‐l stack


5/19

5/9/2015


The other virtual machines do not have an operating system installed yet but will eventually become part of the "Overcloud". You may also want to install virt-manager on the host as it can be very helpful if monitoring when the virtual machines for the Overcloud nodes are powered on and off. You can also use virt-manager to login to the console on the Overcloud nodes.

Deploying an OpenStack Undercloud with OpenStack Deployment (tripleO) Installing the Undercloud Make sure you are logged in as a non-root user (such as the stack user), on the node you want to install the Undercloud onto. $ whoami

Subscribe this system to the Red Hat Network using Red Hat Subscription Manager as described in the Red Hat Enterprise Linux 7 Installation Guide (https://access.redhat.com/documentation/enUS/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/). For additional information, see Using and Configuring Red Hat Subscription Manager (https://access.redhat.com/documentation/enUS/Red_Hat_Subscription_Management/). Repeat the procedure described in "Enable the Red Hat OpenStack 6 repository" above.

Install instack-undercloud $ sudo yum ‐y install instack‐undercloud

Once this script completes, you will have the follow files in /home/stack/: deploy-overcloudrc instack.answers instackenv.json

Create and edit your answers file. In this case, the instack.answers file has been created for you in the /home/stack/ directory, so you can skip this step. If required, copy the sample answers file into your home directory. The descriptions of the parameters that can be set are in the sample answers file itself.


6/19

5/9/2015


Confirm the answers file exists in the home directory If required, copy the sample answers file to your home directory $ cp /usr/share/instack‐undercloud/instack.answers.sample ~/instack.answers

The values in the answer file must be suitable for your environment. Check and replace them if required. In particular, check that the LOCAL_INTERFACE setting matches the Network Interface on the Undercloud used as the provisioning network to handle PXE boots.

Prerequisites for running instack-install-undercloud Prior to running instack-install-undercloud, Overcloud images must be download from the customer portal.

Downloading images from the customer portal Download the RHOS 6 Overcloud images from the following Red Hat Customer Portal link: Product Downloads (https://access.redhat.com/downloads/content/191/ver=6.0/rhel--7/6.0/x86_64/product-downloads). Ensure the file name is correct after downloading. Note that the links to the files do expire, so reload the page before copying the link. You should download the following files from the above link: deploy-ramdisk-ironic.tar discovery-ramdisk.tar overcloud-cinder-volume.tar overcloud-compute.tar overcloud-control.tar overcloud-swift-storage.tar Copy each of the downloaded files to the Undercloud and extract the individual image files from each tar file: $ scp /path‐to‐tar‐file root@:~/ $ tar xvf /path‐to‐tar‐file


7/19

5/9/2015


After extracting the image files from the tar files you should have the following image files: deploy-ramdisk-ironic.initramfs deploy-ramdisk-ironic.kernel discovery-ramdisk.initramfs discovery-ramdisk.kernel overcloud-cinder-volume.initrd overcloud-cinder-volume.qcow2 overcloud-cinder-volume.vmlinuz overcloud-compute.initrd overcloud-compute.qcow2 overcloud-compute.vmlinuz overcloud-control.initrd overcloud-control.qcow2 overcloud-control.vmlinuz overcloud-swift-storage.initrd overcloud-swift-storage.qcow2 overcloud-swift-storage.vmlinuz Copy each of the downloaded image files to the Undercloud. $ scp /path‐to‐image root@:~/

Run the script to install Undercloud. The script will produce a lot of output on the screen. It also logs to ~/.instack/install-undercloud.log. You should see instack-install-undercloud complete, along with the details about the stackrc file at the end of a successful run. $ instack‐install‐undercloud

Once the install script has run to completion, you should take note of the files /root/stackrc and /root/tripleo-undercloud-passwords. Both these files will be needed to interact with the installed Undercloud. Copy them to your home directory for ease of use later. https://access.redhat.com/articles/1320563

8/19

5/9/2015


$ sudo cp /root/tripleo‐undercloud‐passwords . $ sudo cp /root/stackrc .

If your install does not complete successfully, please see the FAQ for potential solutions.

Deploying an OpenStack Overcloud with OpenStack Deployment (tripleO) Addresses for the Overcloud machines will be assigned from the 192.0.2.0/24 range and the Undercloud will also have one interface with an address in this range to communicate with the Overcloud nodes.

Deploying an Overcloud Deploying the Overcloud via the Dashboard You can deploy the Overcloud either through the browser-based dashboard user interface using the Tuskar plugin, or via the Tuskar command-line interface.

Dashboard User Interface (Tuskar) If you want to deploy the Overcloud via the Dashboard user interface (UI) you will need to open up port 80 in the firewall so that you can access the Dashboard UI. On the Undercloud node, the "instack" virtual machine, enter the following command to open up port 80: $ sudo iptables ‐I INPUT ‐p tcp ‐‐dport 80 ‐j ACCEPT

The Dashboard UI will be at http://:80/dashboard (if connecting from the host) If the host machine is not the same system that you will be running the web browser from, you can use an SSH tunnel for connectivity. If required, configure the host as follows: If working from a remote system using an SSH tunnel, on the host do: $ sudo iptables ‐I INPUT ‐p tcp ‐‐dport 8080 ‐j ACCEPT $ ssh ‐g ‐N ‐L 8080::80 `hostname` &

where is the address of the Undercloud virtual machine to bind to, and "hostname" is the host name of the host machine. The Dashboard UI will be at http://:8080/dashboard (if using SSH tunnel). https://access.redhat.com/articles/1320563

9/19

5/9/2015


By default will be 192.168.122.1. When logging into the dashboard the default user and password are required. They can be found in the /root/stackrc file on the Undercloud node, OS_USERNAME and OS_PASSWORD. Once you have logged into the Dashboard UI use the Tuskar UI guide to continue deploying your Overcloud.

Using the Tuskar UI 1. Register nodes Start by registering nodes for your Overcloud. To do so, click on 'Register Nodes' in the left navigation. Once there, you will see two options for registering nodes in the top-right corner. The first is to input the relevant node information manually; click on the '+' icon to do so. The other is to upload a CSV file containing your node information; click on the Upload icon to do that instead. If you are using virtual nodes, you can generate the CSV file by running this script on your "instack" virtual machine:

$ curl ‐L ‐O https://raw.githubusercontent.com/openstack/tuskar‐ui/master/nodes.sh ./nodes

Both options lead to a node registration form where you can choose to have auto-discovery performed on the nodes to identify missing node attributes. To choose auto-discovery, ensure the box is checked on each node "Discover missing attributes". If you use the CSV file upload method, the auto discovery option should already be selected. If you use auto-discovery, your nodes will appear in the 'Maintenance' tab instead with the status 'Discovering'. Wait a few minutes, and the status will change to 'Discovered'; their attributes will appear as well. Now you can choose to 'Activate' these nodes, and they will appear in the 'Free' tab. After discovery is complete, refresh your browser to see the changes as the "Maintenance' page does not auto-update. If you choose not to use auto-discovery, fill in any missing node attributes and submit the form. Your nodes are now registered and viewable in the 'Free' tab. 2. Deploy the Overcloud You are now ready to deploy your Overcloud. Start by clicking on 'Overview' in the left navigation. From here, you can adjust the role count of your Overcloud as node availability permits. At a minimum, a controller node and a compute node must be specified. Also, please note that the number of controller nodes can only be increased by 2 at a time. Once you are satisfied, click on 'Deploy'. A popup will appear informing you of any autogenerated overcloud parameters; press 'Deploy'. Your Overcloud is now deploying. 3. Initialize the Overcloud https://access.redhat.com/articles/1320563

10/19

5/9/2015


After the Overcloud is deployed, you will still need to initialize Overcloud services. To do so simply click on the 'Initialize' button. A form will appear detailing various initialization parameters; the defaults will be sufficient. Press 'Initialize' to start the initialization process. Once this is complete, the 'Overview' page will show you the credentials needed to access Overcloud Horizon. The instack-undercloud package provides a test script, instack-deploy-overcloud that can be used to verify your environment. The following steps will guide you through using instack-deploy-overcloud. To deploy a production ready Overcloud, you should use the Tuskar CLI or OpenStack Dashboard UI. 1. While logged into the Undercloud node export the required variables into your shell in order to use the CLI tools for the Undercloud and Overcloud. If you copied the stackrc file into your home directory at the end of the Undercloud installation, simply source that file. Alternatively, you can use the following command directly to set the needed environment variables. $ command $(sudo cat /root/stackrc | xargs)

2. A file named deploy-overcloudrc is used to define the needed environment variables to deploy an Overcloud. For a virtual environment setup, this file has already been created under /home/stack/. There is a sample file included with instack-undercloud at /usr/share/instack-undercloud/deploy-baremetal-overcloudrc. Copy and edit the file as needed. For the NODES_JSON value, specify the path to the file that you created in the previous step. Example rc files containing values for the required variables can also be found in the FAQ. Note that the variables must be exported so that their values are picked up by instack-deploy-overcloud. $ source deploy‐overcloudrc

3. Deploy the Overcloud $ instack‐deploy‐overcloud

4. To further interact with the API services running in the Overcloud using the OpenStack CLI tools, you can run the following commands: export TE_DATAFILE=instackenv.json $ source /etc/tripleo/overcloudrc

If you run into issues and want to redeploy your Overcloud the first step is to delete it using the instructions in the FAQ. You should then be able to re-execute instack-prepare-for-overcloud and deploy the Overcloud again.


11/19

5/9/2015


Testing an OpenStack Overcloud with OpenStack Deployment (tripleO) 1. While logged into the Undercloud node export the required variables into your shell in order to use the CLI tools for the Undercloud and Overcloud. If you copied the stackrc file into your home directory at the end of the Undercloud installation, source that file. Alternatively, you can use the following command directly to set the needed environment variables. $ command $(sudo cat /root/stackrc | xargs)

2. Run the instack-test-overcloud script to launch an image on the Overcloud and wait until it can be pinged successfully $ instack‐test‐overcloud

The instack-test-overcloud script will test block storage by: Creating a new volume Attaching the volume to the Compute instance, and then Using ssh to log on to the instance and partition, format, and mount the volume The instack-test-overcloud script will test object storage by: Uploading a file with data to the node Testing the data content downloaded from the node

Frequently Asked Questions I got a "disk is in use" error when deploying the Overcloud If the Undercloud machine was installed using LVM, when deploying overcloud nodes, you may see an error related to the disk being "in use". The workaround for this error is to:

Modify /etc/lvm/lvm.conf to set use_lvmetad to be 0 # vi /etc/lvm/lvm.conf use_lvmetad=0

Disable and stop relevant services


12/19

5/9/2015


# systemctl stop lvm2‐lvmetad # systemctl stop lvm2‐lvmetad.socket # systemctl disable lvm2‐lvmetad.socket # systemctl stop lvm2‐lvmetad

Are there any example rc files for Overcloud deployment? Example rc files to source before deploying the overcloud are included as part of the instackundercloud package. Descriptions of the variables are below. Example deploy-overcloudrc file for deploying the overcloud on a virtual machine setup: /usr/share/instack‐undercloud/deploy‐virt‐overcloudrc

Example deploy-overcloudrc file for deploying the overcloud on a bare metal machine setup: /usr/share/instack‐undercloud/deploy‐baremetal‐overcloudrc

Descriptions of the variables in the rc files


13/19

5/9/2015


NODES_JSON: path to a file of the JSON representation of the baremetal nodes. Documented in th NeutronPublicInterface: Overcloud management interface name OVERCLOUD_LIBVIRT_TYPE: Overcloud libvirt type: qemu or kvm NETWORK_CIDR: Neutron network address in CIDR format FLOATING_IP_START: Start of floating IP addresses allocation FLOATING_IP_END: End of floating IP address allocation FLOATING_IP_CIDR: floating IP network address in CIDR format NEUTRON_NETWORK_TYPE: tenant network type: gre or vxlan NEUTRON_TUNNEL_TYPES: supported tenant network tunnel types: gre or vxlan or gre,vxlan COMPUTESCALE: # of overcloud compute nodes BLOCKSTORAGESCALE: # of overcloud block storage nodes SWIFTSTORAGESCALE: # of overcloud object storage nodes

What is the NODES_JSON file format? NODES_JSON in the deploy-overcloudrc file specifies a path to a JSON file and contains the data used to register nodes for baremetal provisioning. The JSON file should be in the following format. For the host machine (note that if you used instack-virt-setup the file has already been created for you automatically):


14/19

5/9/2015


{ "nodes": [ { "memory": "4072", "disk": "30", "arch": "x86_64", "pm_user": "stack", "pm_addr": "192.168.122.1", "pm_password": "contents of ssh private key go here", "pm_type": "pxe_ssh", "mac": [ "00:76:31:1f:f2:a0" ], "cpu": "1" }, { "memory": "4072", "disk": "30", "arch": "x86_64", "pm_user": "stack", "pm_addr": "192.168.122.1", "pm_password": "contents of ssh private key go here", "pm_type": "pxe_ssh", "mac": [ "00:76:31:1f:f2:a0" ], "cpu": "1" } ] }

How do I delete the Overcloud? There are delete scripts included with the instack-undercloud package If you want to delete an overcloud and reset the environment to a state where you can deploy another overcloud. These steps only work if you used instack-deploy-overcloud to deploy the overcloud. 1. While logged into the Undercloud node export the required variables into your shell in order to use the CLI tools for the Undercloud and overcloud. If you copied the stackrc file into your home directory at the end of the Undercloud installation, simply source that file. Alternatively, you can use the following command directly to set the needed environment variables. $ command $(sudo cat /root/stackrc | xargs)

2. Enter the following command to remove the overcloud: https://access.redhat.com/articles/1320563

15/19

5/9/2015


$ instack‐delete‐overcloud

How do I load new Overcloud images? If new images are made available for download, or you build new images, you will need to load them into glance on the Undercloud. You can follow these steps to do so. 1. While logged into the Undercloud node export the required variables into your shell in order to use the CLI tools for the Undercloud and Overcloud. If you copied the stackrc file into your home directory at the end of the Undercloud installation, simply source that file. Alternatively, you can use the following command directly to set the needed environment variables. $ command $(sudo cat /root/stackrc | xargs)

2. Use the following command to load new images. Pass the command whatever new image file you want loaded into glance. $ tripleo load‐image ‐d overcloud‐control.qcow2

How do I view the Undercloud Dashboard when using a remote host? If your host machine is a remote system, and not the same system that you are running your web browser from, you can create an SSH tunnel from the host to the "instack" virtual machine for connectivity. On the host enter the following: $ sudo iptables ‐I INPUT ‐p tcp ‐‐dport 8080 ‐j ACCEPT $ ssh ‐g ‐N ‐L 8080::80 `hostname` &

where is the address of the Undercloud virtual machine to bind to, and "hostname" is the host name of the host machine. Dashboard UI will be at http://:8080/dashboard (if using SSH tunnel) By default, the will be 192.168.122.1. Update appropriately for your environment. With the SSH tunnel created you can launch a browser on a system with connectivity to the host machine and go to http://:8080/dashboard and the dashboard should appear. If you need to connect remotely through the host machine, you can chain SSH tunnels as needed. When logging into the dashboard the default user and password are required. They can be found in the /root/stackrc file on the "instack" virtual machine, OS_USERNAME and OS_PASSWORD. https://access.redhat.com/articles/1320563

16/19

5/9/2015


What configuration changes does instack-virt-setup make to the host? The instack-virt-setup script makes configuration changes to the host to allow for using a full virtual environment for testing an Overcloud deployment. These changes include: Installs various packages such as openvswitch, libvirt, and qemu. Adds a new Open vSwitch bridge called brbm. Adds a new libvirt network also called brbm, which is configured to use the Open vSwitch bridge. Reconfigures libvirtd to set the domain socket group ownership to the libvirtd group. This allows for easier interaction with libvirtd on the host. Adds the user running instack-virt-setup to the libvirtd group.

How do I build Red Hat Enterprise Linux 7 Overcloud images? 1. Download the Red Hat Enterprise Linux 7 guest image, rhel-guest-image-7.020140930.0.x86_64.qcow2, from the Red Hat Customer Portal: Product Downloads (https://access.redhat.com/downloads/content/69/ver=/rhel---7/7.0/x86_64/productdownloads). Ensure the file name is correct after downloading. Note that the links do expire, so reload the page before copying the link. 2. Install instack-undercloud on the system to be used for the image builds. 3. Set the following environment variables in your shell, substituting appropriate values where necessary. In particular, any value wrapped in [] needs to be replaced with the appropriate value for your environment. export NODE_DIST="rhel7" 4. Choose from one of the two following methods to specify the guest cloud image: Specify a web server containing the RHEL guest cloud image export DIB_CLOUD_IMAGES="[http://server/path/containing/image]" Alternatively specify the file name of the RHEL guest cloud image export BASE_IMAGE_FILE=rhel-guest-image-7.0-20140930.0.x86_64.qcow2 export REG_METHOD=portal https://access.redhat.com/articles/1320563

17/19

5/9/2015


export REG_POOL_ID="[pool id]" export REG_PASSWORD="[your password]" export REG_USER="[your username]" export REG_REPOS="rhel-7-server-extras-rpms,rhel-ha-for-rhel-7-server-rpms,rhel-7server-optional-rpms" 5. Run the following command: $ instack‐build‐images

Note that you can find some of the above information with the following command: sudo subscription‐manager list ‐‐consumed ‐‐pool‐only

Article Type

General (https://access.redhat.com/search/#/?q=article_type:("General"))

Product(s) Red Hat Enterprise Linux OpenStack Platform (https://access.redhat.com/search/#/?q=product: ("Red+Hat+Enterprise+Linux+OpenStack+Platform")) Category

Install (https://access.redhat.com/search/#/?q=category:("Install"))

Comments Add new comment

Formatting Help

SUBMIT COMMENT


18/19

5/9/2015


Privacy Policy (http://www.redhat.com/en/about/privacy-policy) Customer Portal Terms of Use (https://access.redhat.com/help/terms/) All Policies and Guidelines (http://www.redhat.com/en/about/all-policies-guidelines) Copyright © 2015 Red Hat, Inc.


19/19

Deploying OpenStack in a Virtual Machine Environment Using OpenStack Deployment (TripleO) - Red Hat Customer Portal

Recommend Documents