openstack/placement
Code Issues Proposed changes
5acaa2eec7
placement/gate/perfload-nested-loader.sh

25 lines
723 B
Bash
Raw Normal View History

Nested provider performance testing This change duplicates the ideas started in with the placement-perfload job and builds on it to create a set of nested trees that can be exercised. In placement-perfload, placeload is used to create the providers. This proves to be cumbersome for nested topologies so this change starts a new model: Using parallel [1] plus instrumented gabbi to create nested topologies in a declarative fashion. gate/perfload-server.sh sets up placement db and starts a uwsgi server. gate/perfload-nested-loader.sh is called in the playbook to cause gabbi to create the nested topology described in gate/gabbits/nested-perfload.yaml. That topology is intentionally very naive right now but should be made more realisitc as we continue to develop nested features. There's some duplication between perfload.yaml and nested-perfload.yaml that will be cleared up in a followup. [1] https://www.gnu.org/software/parallel/ (although the version on ubuntu is a non-GPL clone) Story: 2005443 Task: 30487 Change-Id: I617161fde5b844d7f52dc766f85c1b9f1b139e4a
2019-06-17 15:47:36 +01:00
#!/bin/bash
set -a
HOST=$1
GABBIT=$2
# By default the placement server is set up with noauth2 authentication
# handling. If that is changed to keystone, a $TOKEN can be generated in
# the calling environment and used instead of the default 'admin'.
TOKEN=${TOKEN:-admin}
# These are the dynamic/unique values for individual resource providers
# that need to be set for each run a gabbi file. Values that are the same
# for all the resource providers (for example, traits and inventory) should
# be set in $GABBIT.
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-07-30 14:05:42 +01:00
CN1_UUID=$(uuidgen)
N0_UUID=$(uuidgen)
Nested provider performance testing This change duplicates the ideas started in with the placement-perfload job and builds on it to create a set of nested trees that can be exercised. In placement-perfload, placeload is used to create the providers. This proves to be cumbersome for nested topologies so this change starts a new model: Using parallel [1] plus instrumented gabbi to create nested topologies in a declarative fashion. gate/perfload-server.sh sets up placement db and starts a uwsgi server. gate/perfload-nested-loader.sh is called in the playbook to cause gabbi to create the nested topology described in gate/gabbits/nested-perfload.yaml. That topology is intentionally very naive right now but should be made more realisitc as we continue to develop nested features. There's some duplication between perfload.yaml and nested-perfload.yaml that will be cleared up in a followup. [1] https://www.gnu.org/software/parallel/ (although the version on ubuntu is a non-GPL clone) Story: 2005443 Task: 30487 Change-Id: I617161fde5b844d7f52dc766f85c1b9f1b139e4a
2019-06-17 15:47:36 +01:00
N1_UUID=$(uuidgen)
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-07-30 14:05:42 +01:00
FPGA0_0_UUID=$(uuidgen)
FPGA1_0_UUID=$(uuidgen)
FPGA1_1_UUID=$(uuidgen)
PGPU0_0_UUID=$(uuidgen)
Nested provider performance testing This change duplicates the ideas started in with the placement-perfload job and builds on it to create a set of nested trees that can be exercised. In placement-perfload, placeload is used to create the providers. This proves to be cumbersome for nested topologies so this change starts a new model: Using parallel [1] plus instrumented gabbi to create nested topologies in a declarative fashion. gate/perfload-server.sh sets up placement db and starts a uwsgi server. gate/perfload-nested-loader.sh is called in the playbook to cause gabbi to create the nested topology described in gate/gabbits/nested-perfload.yaml. That topology is intentionally very naive right now but should be made more realisitc as we continue to develop nested features. There's some duplication between perfload.yaml and nested-perfload.yaml that will be cleared up in a followup. [1] https://www.gnu.org/software/parallel/ (although the version on ubuntu is a non-GPL clone) Story: 2005443 Task: 30487 Change-Id: I617161fde5b844d7f52dc766f85c1b9f1b139e4a
2019-06-17 15:47:36 +01:00
# Run gabbi silently.
gabbi-run -q $HOST -- $GABBIT
Copy Permalink