![]() We cant run the full pingtest yet, so this adds some basic sanity checks which ensures some enabled services are working, and that we can create content that survives the upgrade process. For now this only handles the keystone service, we create/get a user before the upgrade, then get/delete it afterwards, which gives reasonable confidence keystone is running OK. Change-Id: I67c416d0407b54aab72b0e6a67b49f6b42f29709 |
||
---|---|---|
docs | ||
heat-templates | ||
scripts | ||
templates | ||
test-environments | ||
undercloud-configs | ||
.gitignore | ||
.gitreview | ||
README.md | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
testenv-client | ||
toci_gate_test.sh | ||
toci_instack_oooq.sh | ||
toci_instack_osinfra.sh | ||
toci_instack_ovb.sh | ||
tox.ini |
README.md
toci
Description
TripleO CI test framework.
Tools to help run CI jobs for TripleO. Includes things like:
- Shell scripts to help execute jobs on CI slave nodes (Jenkins slaves)
- A test environment broker framework which uses a client-server model to execute jobs on a remote bare metal machine in an isolated test environment (using VMs).
- Image elements to help build images for the test environment broker nodes.
- Heat templates to help deploy and maintain test environment nodes using an undercloud.
- Helper script(s) to generate CI status reports. (tox -ecireport -- -f)
OpenStack Infrastructure is deploying multiple jobs with different scenarios. OpenStack services are balanced between different scenarios because OpenStack Infastructure Jenkins slaves can not afford the load of running everything on the same node.
Service testing matrix
The CI testing matrix for all scenarios is defined in tripleo-heat-templates. This matrix describes the services that will run in each environment.