There are two main tools for testing a deployed cloud, Rally and Tempest.
I have been looking into verifying functionality in a private cloud once it has been created (using TripleO) and the documentation is, as usual, abysmal. Its the usual rabbit warren of developer docs, stuff relating to releases from 3 years back, blueprints which mention “the upcoming Havana release” etc etc.
So for reference (mine mostly), here are the steps to get OpenStack Tempest working on the RDO Mitaka stable release:
- Ensure you have a neutron network called “nova”
$ neutron net-create nova --router:external --provider:network_type flat --provider:physical_network datacentre
$ neutron subnet-create --name nova --enable_dhcp=False --allocation-pool=start=10.1.1.51,end=10.1.1.250 --gateway=10.1.1.1 nova 10.1.1.0/24
- Check that you have a role called “heat_stack_owner”. If not, create one:
$ openstack role create heat_stack_owner
- Create your tempest directory and change into it
$ mkdir ~/tempest && cd ~/tempest
- Initialize the directory by running
- Configure tempest
$ tools/config_tempest.py --deployer-input ~/tempest-deployer-input.conf \
--create identity.uri $OS_AUTH_URL identity.admin_password $OS_PASSWORD
- Run tempest (NOT with tools/run-tests.sh)
- Answer yes to the prompt to initialise your virtual environment. This will download required libraries etc.
Depending on environment the tests will take about an hour to run. So go make a brew and get ready to debug the failures. 🙂