Chris Dent 07d7749cff Implement a more complex nested-perfload topology
This changes gabbits/nested-perfload.yaml to create a tree of
providers based on one of the compute nodes in the NUMANetworkFixture
used in the functional tests. For the time being only one type of
compute node is created (of which there will be 1000 instances).
Room is left for future expansion as requirements expand.

The resulting hierarchy has 7 resource providers.

The allocation candidates query is:

GET /allocation_candidates?
    resources=DISK_GB:10&
    required=COMPUTE_VOLUME_MULTI_ATTACH&
    resources_COMPUTE=VCPU:1,MEMORY_MB:256&
    required_COMPUTE=CUSTOM_FOO&
    resources_FPGA=FPGA:1&
    group_policy=none&
    same_subtree=_COMPUTE,_FPGA

This is a step in the right direction but is not yet a complete
exercising of all the nested functionality. It is, however, more
complex than prior, notably testing 'same_subtree'. We should
continue to iterate to get it doing more.

Change-Id: I67d8091b464cd7b875b37766f52818a5a2faa780
Story: 2005443
Task: 35669
2019-08-06 09:18:39 +01:00
..
2019-06-20 12:37:28 +01:00

This directory contains files used by the OpenStack infra test system. They are
really only relevant within the scope of the OpenStack infra system and are not
expected to be useful to anyone else.

These files are a mixture of:

* Hooks and other scripts to be used by the OpenStack infra test system. These
  scripts may be called by certain jobs at important times to do extra testing,
  setup, run services, etc.

* "gabbits" are test files to be used with some of the jobs described in
  .zuul.yaml and playbooks. When changes are made in the gabbits or playbooks
  it is quite likely that queries in the playbooks or the assertions in the
  gabbits will need to be updated.