placement/.zuul.yaml
Chris Dent 3ae8653338 Use a smaller base job for the perfload run
In this job we install placement by hand, based on the
instructions in
https://docs.openstack.org/placement/latest/contributor/quick-dev.html
and run the placeload command against it. This avoids a lot of node
set up time.

* mysql is installed, placement is installed, uwsgi is installed
* the database is synced
* the service started, via uwsgi, which run with 5 processs each
  with 25 threads, otherwise writing the resource providers is
  very slow and causes errors in placeload. It's an 8 core vm.
* placeload is called

A post.yaml is added to get the generated logs back to zuul.

Change-Id: I93875e3ce1f77fdb237e339b7b3e38abe3dad8f7
2018-11-30 15:00:57 +00:00

35 lines
1008 B
YAML

# Initial set of jobs that will be extended over time as
# we get things working.
- project:
templates:
- integrated-gate-py35
- publish-openstack-docs-pti
- openstack-cover-jobs
- openstack-lower-constraints-jobs
- openstack-python-jobs
- openstack-python35-jobs
- openstack-python36-jobs
check:
jobs:
- openstack-tox-functional
- openstack-tox-functional-py35
- openstack-tox-functional-py36
- placement-perfload:
voting: false
gate:
jobs:
- openstack-tox-functional
- openstack-tox-functional-py35
- openstack-tox-functional-py36
- job:
name: placement-perfload
parent: base
description: |
A simple node on which to run placement with the barest of configs and
make performance related tests against it.
required-projects:
- git.openstack.org/openstack/placement
run: playbooks/perfload.yaml
post-run: playbooks/post.yaml