VScaler: Using Tempest to validate the OpenStack deployment

Run from within Kolla

Docker Images Exist?

Check and make sure the images are built for tempest and rally

[root@house-vscaler ~]# docker images | grep tempest
10.10.10.1:5000/kolla/centos-binary-tempest                       4.0.3               6b5ff759b887        8 weeks ago         667MB

Enable Tempest in the globals.yml file

enable_rally: "yes"
enable_tempest: "yes"

# then down towards the bottom

tempest_image_id: 9f3cae72-56b0-4957-9536-d2c01ce88d64 # (Image ID of cirros from: openstack image list)
tempest_flavor_ref_id: 3 # (openstack flavor list - medium)
tempest_public_network_id: 42eee1c7-475e-43a1-9c1a-3bc583a0cce8 # (openstack network list - public or ext-net)
tempest_floating_network_name: ext-net # name of publci net)

Reconfigure OpenStack

kolla-ansible -i ~/kolla-deploy/multinode reconfigure

# By the end - go to a controller node and check the container is there
[root@controller01-enp2s0 ~]# docker ps | grep temp
da12f9034786        10.10.10.1:4000/kolla/centos-binary-tempest:4.0.3                     "kolla_start"       6 minutes ago       Up 6 minutes                            tempest

Drop into the tempest container

# on the controller
docker exec -it -u root tempest bash
# edit the /etc/tempest/tempest.conf file 
tempest init

# once you have done the init you'll be dropped to the default run locaiton: /usr/share/openstack-tempest-*
(tempest)[root@controller01-enp2s0 openstack-tempest-*]# pwd
/usr/share/openstack-tempest-*
(tempest)[root@controller01-enp2s0 openstack-tempest-*]# ls
etc  logs  tempest_lock
(tempest)[root@controller01-enp2s0 openstack-tempest-*]# 

# Then for a full run
tempest run

Run the min requirements

From: https://www.openstack.org/brand/interop/

# Get the min tests list: 
curl -O  https://refstack.openstack.org/api/v1/guidelines/2016.08/tests?type=required

Running Manually

Notes from running within a Centos VM (on vScaler) pointed towards the external / public endpoints