placement/gate
Chris Dent ed03085187 Add apache benchmark (ab) to end of perfload jobs
Start the process of reporting some concurrency numbers by including
a 500 x 10 'ab' run against the query URL used in each perfload job.

There's duplication removal that could be done here, but we leave
that until we've determined if this is working well.

The PLACEMENT_URL is updated to use 127.0.0.1 instead of localhost;
ab will attempt to use the IPV6 version of localhost if that's the
case, and we've not bound the placement server to that interface.

The timeout on the placement-nested-perfload job has been raised to
1 hour as the default 30 minutes is leading to a timeout. If that's
still not enough we'll explore lowering concurrency.

We will quite likely need to adapt the mysql configuration if we
intend to continue down this road.

Change-Id: Ic0bf2ab666dab546dd7b03955473c246fd0f380a
2019-08-06 09:18:44 +01:00
..
gabbits Implement a more complex nested-perfload topology 2019-08-06 09:18:39 +01:00
perfload-nested-loader.sh Implement a more complex nested-perfload topology 2019-08-06 09:18:39 +01:00
perfload-nested-runner.sh Add apache benchmark (ab) to end of perfload jobs 2019-08-06 09:18:44 +01:00
perfload-runner.sh Add apache benchmark (ab) to end of perfload jobs 2019-08-06 09:18:44 +01:00
perfload-server.sh Add apache benchmark (ab) to end of perfload jobs 2019-08-06 09:18:44 +01:00
README Nested provider performance testing 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.