Zaqar's team is in the process of moving devstack's zaqar code into a
plugin. This patch changes the gate job to make it consume such plugin.
The plugin already landed in Zaqar's code base as per
I38c6cf71e2ae73f60e4494d853fee5796aa1f0f8
Change-Id: If5c91ebe136017cea2eeecf62a580d050e49617d
Zaqar's gate is current;y installing more services than it needs. This
patch sets the `ENABLED_SERVICES` var to what's really required for
zaqar to be deployed.
Change-Id: Ia7d3a2a5ed2ebb29b1a4f99c00cac4d024bcdddc
Sicne we've enabled `DEVSTACK_GATE_INSTALL_TESTONLY`, it is not
necessary to manually install test-requirements. This patch removes that
step from the job.
Change-Id: I90edb168ccf17700b741158790c7f19576e9a80d
A new redis drier was recently added to Zaqar. The team would like to
have a test job that checks *all* patches against this driver as well.
This patch adds such job to the infrastructure configs. It's based on
the already existing job but it enables redis by setting `ZAQAR_BACKEND`
in the gate environment.
The patch adds jobs for Zaqar, tempest experimental and devstack
experimental.
This patch depends on: I97629a303c55ee098e3bfbc534bfb05ccab94649
Change-Id: Icb260f27e01d024fe98cf03f68a7285ec4bb3b71
We'd like to test every patch submitted for zaqarclient against a live
running zaqar server. This patch adds a new zaqarclient job that
installs zaqar and runs the client functional tests.
This job has, temporarily, been made non-voting until we're sure it
works as expected. This is a prevention to avoid blocking the client
patches on a broken job. Once it works as expected, I'll add the job to
the gate pipeline and make it voting.
Change-Id: Ia5b47bfc02b2c53ccbc2a73729961a9d5fdd9b6d