<commit_before>---
title: Deploying an RDO Overcloud with Instack
authors: bnemec, ccrouch, jomara, rbrady, rlandy, rwsu, slagle, tzumainn
wiki_title: Deploying an RDO Overcloud with Instack
wiki_revision_count: 84
wiki_last_updated: 2014-11-17
---

# Deploying an RDO Overcloud with Instack

[ ← Deploying RDO using Instack](Deploying RDO using Instack)

Now that you have a working undercloud, let's deploy an overcloud. Note that deploy-overcloud can be configured for individual environments via environment variables. The variables you can set are documented in the [Instack FAQ](http://openstack.redhat.com/Instack_FAQ#Are_there_any_example_rc_files_for_Overcloud_deployment.3F). For their default values, see the instack-deploy-overcloud\* scripts.

## Preparing for the Overcloud

1. While logged into the undercloud node export the required variables into your shell before running the instack-\* scripts that interact with the undercloud and overcloud:

      command $(sudo cat /root/stackrc | xargs)

2. Run the prepare-for-overcloud script to get setup. This script will download approximately 2.5GB of images from [here](http://repos.fedorapeople.org/repos/openstack-m/tripleo-images-rdo-icehouse/). It will avoid re-downloading images if they already exist in the current working directory. If you want to force a redownload of the images, delete them first.

      instack-prepare-for-overcloud

3. Create a deploy-overcloudrc script to set variable values you'll need to deploy the overcloud. Example rc files containing values for the required variables can be found in the [Instack FAQ](http://openstack.redhat.com/Instack_FAQ#Are_there_any_example_rc_files_for_Overcloud_deployment.3F). Note that the variables must be exported so that their values are picked up by instack-deploy-overcloud. Most of the example values will work as-is if you've been using the defaults up until now, except for the following:

*   In a virtualized deployment the MACS variable will need to be set to the space separated values you gathered during the steps to [setup your virtual machines](http://openstack.redhat.com/Deploying_RDO_to_a_Virtual_Machine_Environment_using_RDO_via_Instack#Virtual_Machine_Creation).
*   Similarly in a bare metal deployment the MACS variable will need to be set to the MAC address of the NIC that will PXE boot, for each host you want to deploy the overcloud to. The PM_\* variables need to be set with corresponding IPMI information. All these values should have been collected during the steps to [setup the bare metal environment](http://openstack.redhat.com/Deploying_RDO_on_a_Baremetal_Environment_using_Instack#Networking).

If you want to deploy more or fewer compute, block storage or object storage nodes in your overcloud then update the appropriate \*SCALE variable in the rc file. If you increase these numbers you will need to make sure that sufficient virtual machines or bare metal hosts are available.

## Deploying the Overcloud

You can deploy the overcloud **either** through the Horizon web interface using the tuskar plugin **or** via the command line

### Tuskar Web UI Deployment

If you want to deploy the Overcloud via the UI you will need to open up port 80 in iptables so that you can access the Web UI. On the instack VM enter the following:

    sudo iptables -I INPUT -p tcp --dport 80 -j ACCEPT

Note that if your virt host is not the same host that you'll be running the web browser from, you can use an ssh tunnel for connectivity. See this [FAQ](http://openstack.redhat.com/Instack_FAQ#How_do_I_view_the_Undercloud_Dashboard_when_using_a_remote_virt_host.3F) for more information.<commit_msg>Tuskar Web UI Deployment<commit_after>---
title: Deploying an RDO Overcloud with Instack
authors: bnemec, ccrouch, jomara, rbrady, rlandy, rwsu, slagle, tzumainn
wiki_title: Deploying an RDO Overcloud with Instack
wiki_revision_count: 84
wiki_last_updated: 2014-11-17
---

# Deploying an RDO Overcloud with Instack

[ ← Deploying RDO using Instack](Deploying RDO using Instack)

Now that you have a working undercloud, let's deploy an overcloud. Note that deploy-overcloud can be configured for individual environments via environment variables. The variables you can set are documented in the [Instack FAQ](http://openstack.redhat.com/Instack_FAQ#Are_there_any_example_rc_files_for_Overcloud_deployment.3F). For their default values, see the instack-deploy-overcloud\* scripts.

## Preparing for the Overcloud

1. While logged into the undercloud node export the required variables into your shell before running the instack-\* scripts that interact with the undercloud and overcloud:

      command $(sudo cat /root/stackrc | xargs)

2. Run the prepare-for-overcloud script to get setup. This script will download approximately 2.5GB of images from [here](http://repos.fedorapeople.org/repos/openstack-m/tripleo-images-rdo-icehouse/). It will avoid re-downloading images if they already exist in the current working directory. If you want to force a redownload of the images, delete them first.

      instack-prepare-for-overcloud

3. Create a deploy-overcloudrc script to set variable values you'll need to deploy the overcloud. Example rc files containing values for the required variables can be found in the [Instack FAQ](http://openstack.redhat.com/Instack_FAQ#Are_there_any_example_rc_files_for_Overcloud_deployment.3F). Note that the variables must be exported so that their values are picked up by instack-deploy-overcloud. Most of the example values will work as-is if you've been using the defaults up until now, except for the following:

*   In a virtualized deployment the MACS variable will need to be set to the space separated values you gathered during the steps to [setup your virtual machines](http://openstack.redhat.com/Deploying_RDO_to_a_Virtual_Machine_Environment_using_RDO_via_Instack#Virtual_Machine_Creation).
*   Similarly in a bare metal deployment the MACS variable will need to be set to the MAC address of the NIC that will PXE boot, for each host you want to deploy the overcloud to. The PM_\* variables need to be set with corresponding IPMI information. All these values should have been collected during the steps to [setup the bare metal environment](http://openstack.redhat.com/Deploying_RDO_on_a_Baremetal_Environment_using_Instack#Networking).

If you want to deploy more or fewer compute, block storage or object storage nodes in your overcloud then update the appropriate \*SCALE variable in the rc file. If you increase these numbers you will need to make sure that sufficient virtual machines or bare metal hosts are available.

## Deploying the Overcloud

You can deploy the overcloud **either** through the Horizon web interface using the tuskar plugin **or** via the command line

### Tuskar Web UI Deployment

If you want to deploy the Overcloud via the UI you will need to open up port 80 on the undercloud node in iptables so that you can access the Web UI. On the instack VM enter the following:

    sudo iptables -I INPUT -p tcp --dport 80 -j ACCEPT

Note that if your virt host is not the same host that you'll be running the web browser from, you can use an ssh tunnel for connectivity. See this [FAQ](http://openstack.redhat.com/Instack_FAQ#How_do_I_view_the_Undercloud_Dashboard_when_using_a_remote_virt_host.3F) for more information.
{'fraction_non_alphanumeric': 0.05221648082676095, 'fraction_numerical': 0.005983138428066358, 'mean_word_length': 4.912379421221865, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 6, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2144089', 'n_tokens_mistral': 2063, 'n_tokens_neox': 1986, 'n_words': 958}