The Watcher multinode experimental job is currently not working due
to the fact that the DEVSTACK_PROJECT_FROM_GIT variable is actually
shared by both the primary node and the subnodes. Therefore, I removed
it from the multinode job to let the Watcher plugin deal with this
using 'is_service_enabled' to detect whether we are on the primary
node or not.
Change-Id: I292d109c89c9f07b1440a215d6c50b9243df9abe
The Watcher multinode experimental job is currently not working
due to the fact that both the Watcher and Ceilometer plugins are
enabled onto the subnodes. Hence, this changeset introduces the new
DEVSTACK_SUBNODE_CONFIG variable to avoid the enabling of plugins
that only are meant to be activated on the primary node.
Change-Id: I6aea168a5d2ad61ed4ad36b25de8faeee044c543
Following https://review.openstack.org/#/c/274068/, I have an issue
with the "gate-watcher-dsvm-multinode-nv" job which is currently
failing when trying to deploy the subnodes.
The declaration of ENABLED_SERVICES as it is currently the case seem
to be the cause of it as it installs the list of services on both
the controller node and its subnodes.
This patchset hence removes the declaration of these services.
Change-Id: I92a6d9a2b03dfb1560031f2dd790c53863519187
Related-Bug: #1538606
With change Iff5e96bd80b8f165ccc7d6be09b53208613571eb, we do not need
to pass DEVSTACK_GATE_TIMEOUT anymore to devstack-gate, instead the
value from the build-timeout wrapper is passed.
Remove DEVSTACK_GATE_TIMEOUT for jenkins/jobs/[n-z]*.yaml
Increase timeout for all non-grenade jobs by 5 mins since
Iea866e4cc40e149e598f35e010ec855937bdf9ae will use a 10 minute buffer
and the internal timeout should stay the same. The grenade jobs already
have 10 mins of buffer, so no need adjust the timeout.
Adjust timeout for gate-rally-dsvm-cue-{broker},
the removed variable in builder devstack-cue-rally-gate was 100,
so set timeout to 110.
Change-Id: I623fff029fb2e0acdbe2bf93a13af02547062a71
As we want to create a Horizon plugin for Watcher, (see
blueprint watcher-ui), we want to set up a new project for it.
Partially Implements: blueprint watcher-ui
Change-Id: I52a1b1948f369852dea4d2569ef4361ce3253305
As we are now trying to make some live migration within Tempest
scenarios, we would like to make our Tempest job run on a multinode
DevStack so that it doesn't skip them.
Change-Id: I1d42d61cf842a4aa44a40da7a840335e45000855
Related-Bug: #1538606
As specified in
http://docs.openstack.org/developer/tempest/plugin.html, the
name of the tempest tests package should be of the format
'{{name}}_tempest_plugin'. So this patchset is here to enforce
this rule.
Change-Id: I93b3e39f1f83a04a25da1bcb97e6d6ec12c1df14
As of I8bf7cbaa7015bb61656ab90ccc8f944aaeebb095, Nova
removed the n-obj service, so we should cleanup
Change-Id: I5e681c8c7031dd7f04ec9d77914c9da051a64822
As we are currently trying to setup functional tests using tempest
in Watcher, we want to add a new gate which will run them against
our new patchsets.
Partially Implements: blueprint tempest-basic-set-up
Change-Id: I4d299959e16afc042870ac09b420be90d9595974