devtest

(There are detailed instructions available below, the overview and configuration sections provide background information).

Overview:

• Define a VM that is your seed node
• Define N VMs to pretend to be your cluster
• Create a seed VM
• Create an undercloud
• Create an overcloud
• Deploy a sample workload in the overcloud
• Add environment variables to be included to ~/.devtestrc, e.g. http_proxy
• Go to town testing deployments on them.
• For troubleshooting see Troubleshooting tips
• For generic deployment information see Deploying TripleO

This document is extracted from devtest.sh, our automated bring-up story for CI/experimentation.

Stability Warning

Note that every effort is made to keep the published set of these instructions updated for use with only the master branches of the TripleO projects. There is NO guaranteed stability in master. There is also no guaranteed stable upgrade path from release to release or from one stable branch to a later stable branch. The stable branches are a point in time and make no guarantee about deploying older or newer branches of OpenStack projects correctly.

If you wish to use the stable branches, you should instead checkout and clone the stable branch of tripleo-incubator you want, and then build the instructions yourself via:

git clone https://git.openstack.org/openstack/tripleo-incubator
cd tripleo-incubator
git checkout <stable-branch>
tox -evenv python setup.py build_sphinx
# View doc/build/html/devtest.html in your browser and proceed from there

Next Steps:

When run as a standalone script, devtest.sh runs the following commands to configure the devtest environment, bootstrap a seed, deploy under and overclouds. Many of these commands are also part of our documentation. Readers may choose to either run the commands given here, or instead follow the documentation for each command and walk through it step by step to see what is going on. This choice can be made on a case by case basis - for instance, if bootstrapping is not interesting, run that as devtest does, then step into the undercloud setup for granular details of bringing up a baremetal cloud.

1. See devtest_variables for documentation:

   source $(dirname $0)/devtest_variables.sh

2. See devtest_setup for documentation. $CONTINUE should be set to ‘–trash-my-machine’ to have it execute unattended.

   $(dirname $0)/devtest_setup.sh $CONTINUE

3. See devtest_testenv for documentation. Note that you can make your test environment just once and reuse it thereafter. TE_DATAFILE should specify where you want your test environment JSON file created. (A default value is set in devtest_variables.sh).

   devtest_testenv.sh $TE_DATAFILE

4. See devtest_ramdisk for documentation:

   devtest_ramdisk.sh
   

5. See devtest_seed for documentation:

   devtest_seed.sh
   

6. See devtest_undercloud for documentation:

   export no_proxy=${no_proxy:-},192.0.2.1
   source $TRIPLEO_ROOT/tripleo-incubator/seedrc
   devtest_undercloud.sh $TE_DATAFILE

7. See devtest_overcloud for documentation:

   export no_proxy=$no_proxy,$(os-apply-config --type raw -m $TE_DATAFILE --key undercloud.endpointhost)
   source $TRIPLEO_ROOT/tripleo-incubator/undercloudrc
   source devtest_overcloud.sh

8. See devtest_end for documentation:

   devtest_end.sh