nova/playbooks/legacy/nova-grenade-multinode
Matt Riedemann 8cb6f07444 Drop neutron-grenade-multinode job
We were running the voting neutron-grenade-multinode job in the
check queue on nova changes but were not running it in the gate
queue.

We run the nova-grenade-multinode job in both check and gate queues.

The major differences between those jobs are that the neutron
job runs the tempest smoke tests during the grenade run on the
old and new side of the grenade environment and the nova job would
not run smoke tests but ran a select few live migration and
resize/cold migration tests via the post-test hook script, and would
run those with an lvm/local storage/block migration and ceph/shared
storage setup.

This change makes the nova-grenade-multinode job run smoke tests
like the neutron-grenade-multinode job was so we can drop the
neutron-grenade-multinode job from running on nova changes in the
check queue and save a few nodes.

Note that neutron-grenade-multinode ran all smoke tests but this
change makes nova-grenade-multinode run a subset of smoke tests for
only the ones that involve compute. This is in order to keep the
execution time of the job down by not testing non-compute API things
that nova changes don't care about, e.g. keystone, swift, cinder, etc
smoke tests.

[1] https://zuul.opendev.org/t/openstack/build/377affdf97b04022a321087352e1cc4c/log/logs/grenade.sh.txt.gz#41965

Change-Id: Icac785eec824da5146efe0ea8ecd01383f18398e
2019-11-19 15:52:26 +00:00
..
post.yaml Rename the nova-grenade-live-migration job to nova-grenade-multinode 2019-08-30 15:35:46 -04:00
run.yaml Drop neutron-grenade-multinode job 2019-11-19 15:52:26 +00:00