Use OS_REGION_NAME so that OCC ignore it properly

os-client-config will construct a cloud called "envvars" if the
environment has environment variables that start with OS_ and are not
OS_CLOUD and OS_REGION_NAME (those are singled out because they are
selectors) The convenience variable in our example code snippet here is
an OS_ var that is neither of those, so it causes the environment to
produce an invalid cloud config which then confuses the ansible
inventory which is trying to iterate over the all the clouds that
exist.

Change-Id: I65324bc2f3ca71dd4ada2f39f322ccc5f13d6897
This commit is contained in:
Monty Taylor 2016-09-15 16:24:08 -05:00 committed by Jeremy Stanley
parent f2ac215342
commit a05340b2f6
1 changed files with 4 additions and 4 deletions

View File

@ -24,25 +24,25 @@ To launch a node in the OpenStack CI account (production servers)::
. ~/launch-env/bin/activate
export OS_CLOUD=openstackci-rax
export OS_REGION=DFW
export OS_REGION_NAME=DFW
export FLAVOR="8 GB Performance"
export FQDN=servername01.openstack.org
cd /opt/system-config/production/launch/
./launch-node.py $FQDN --flavor "$FLAVOR" \
--cloud=$OS_CLOUD --region=$OS_REGION
--cloud=$OS_CLOUD --region=$OS_REGION_NAME
To launch a node in the OpenStack Jenkins account (slave nodes)::
. ~/launch-env/bin/activate
export OS_CLOUD=openstackjenkins-rax
export OS_REGION=DFW
export OS_REGION_NAME=DFW
export FQDN=slavename01.slave.openstack.org
openstack image list
export IMAGE='Ubuntu 12.04 LTS (Precise Pangolin) (PVHVM)'
openstack flavor list
export FLAVOR="8 GB Performance"
./launch-node.py $FQDN --image "$IMAGE" --flavor "$FLAVOR" \
--cloud=$OS_CLOUD --region=$OS_REGION
--cloud=$OS_CLOUD --region=$OS_REGION_NAME
Manually add the hostname to DNS (the launch script does not do so
automatically). Note that this example assumes you've already