Since older devstack versions do not support glance in standalone mode,
make grenade configure the base and target for glance deployed with
uwsgi.
Change-Id: I9ac380aec2689277a2793a67b33b6f9ef8728003
Removed API_RATE_LIMIT per commit f617a2ddddf7d8f759ff3ca5d66a133b124eeb42.
Removed STACK_LOG in favor of LOGFILE as per devstack/stackrc#L845
Change-Id: I841757bd6ad4889fddcc626bed0de03731918fa5
Since cells v2 are required to start Ocata, grenade should not set
rabbit host to localhost. Otherwise cell mapping will contain
transport_url set to localhost and therefore subnode-2 will fail
connection to rabbit, e.g., when trying to start pre live migration
steps on contoller+compute node. This is beacause subnode-2 will
take cell mapping from the database and then transport_url from
cell mapping which points to localhost:5672 in such case.
Change-Id: I3d4d7b309e50f4e2970cda55aada02d68c4fa705
Related-Bug: #1649586
Recently, devstack-gate accidentally stopped setting these values and
there appeared to be no fallout. Looking closer, they appear to be
no longer used by Grenade. This removes them from sample localrcs
and docs.
Change-Id: I4d1ec41bac5a05241069963d1bcd2df4070f5ea2
in the gate we specify all the swift services directly, not the
old swift flag. We should mirror that back to grenade, as we now
really do depend on it.
Change-Id: Id0ddf92c0c2d02dd3fb86e408a84646e081944da
Smoke and Scenarios tests can offer a better coverage and also it's good to
centralize all tests in tempest.
Change-Id: Iacb60ab011d2c7d90885b339b3c8454bd3de8219
Partial-bug: #1023131
* change BASE_RELEASE and TARGET_RELEASE in grenaderc
* remove work-arounds from devstack.localrc.target
* remove upgrade steps from the upgrade-* scripts
* change references to release names in variables to BASE_ and TARGET_
* remove Javelin check from check-sanity, will return in verify-javelin
in https://review.openstack.org/#/c/26257/
Fixes bug 1175340
Change-Id: If1523c73ebefeaf3d3e3efdfbc053f47365d123a
Paths get stuffed in the database so rather than rewrite them
just leave the data in-place for both versions. This is how
real upgrades are likely to be done anyway...
Change-Id: I3610d93227b54d4c2f5c832478e7d23afe1bd173
Create top-level directories for each release and put devstack and
the project repos under that. data is still a top-level as it
will be processed for the upgrade.
Dan Smith