When GRENADE_USE_EXTERNAL_DEVSTACK is set to True,
the initial steps performed by grenade are skipped, namely:
- grabbing and configuring the base and the target devstacks;
- running devstacks on the base target.
This change is required to allow a native Zuul v3 job to use
the existing workflow to setup and run devstack.
Change-Id: I232db8de05141849c81851dd29440959cb0d8533
We haven't gated on nova-network in a long time so this
removes mentions about testing with nova-network from
the docs. Also mention that this the list isn't exhaustive
since there are other grenade configurations like with
postgresql and heat, designate, etc.
Change-Id: Ia56486227688f0d7651594e9780d61d0fdccd660
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I53dcfcb704a6dbdc8772d275001475bc0b1ecf26
Every time I have to figure out where in the sequence
of upgrade events the per-release within-$base and
from-$base scripts run, I have to dig into the doc.
We have a pretty good document already on the sequence
of phases in a grenade run, but the upgrade section is
pretty fuzzy, and with no mention of when the per-release
scripts run relative to when new code is installed, which
is pretty important if you're going to write one of these
scripts.
So this adds some docs related to when those per-release
upgrade scripts happen relative to installing new code
during the upgrade.
Change-Id: Ic79cd10b2df5fa54a13f73cf49c8f73fa93e9381
Nova caught a few projects off guard with the fact that cells v2
and the placement service are going to be required in Ocata and
to upgrade to Ocata, deployment tooling needs to be potentially
changed in Newton to allow the upgrade. Within our QA/CI system
we handle things like this using Grenade, but we as developers
sometimes forget to communicate these types of major changes
to the various deployment projects in OpenStack, like TripleO.
Developers have gotten used to assuming that everyone reads and
understands the implications of the release notes, and we need
reminders of how to effectively communicate beyond those. This
patch tries to help fill some of that reminder gap.
Change-Id: Ia654b88309a9d2506766e21309317ad14d47099a
This fixes the formatting so that the descriptions of
each item are aligned properly with the bullet point.
Change-Id: I4cdf8848ae350bdc9fa10fe3c3676dda5a109627
The dependent patch here moves this code into ironic's tree as a grenade
plugin. Remove it from grenade's tree.
Change-Id: I659e3de5c64df798441798ff48ba5c9c0506585a
Depends-On: I8b065c60e9e06cd7fc10749c49bdf79d878fcc12
This commit fixes an internal pointer to a later section to actually
be a link, to make it clickable.
Change-Id: Idc4547f2850f062825998109a2743d04ea558c25
This commit adds basic docs building support to grenade. Previously
we just had rst files in the root of the repo and relied on github
or something else to render them. After this commit we'll support
sphinx built docs.
The next step after this is to add a docs publishing job to infra so
we'll have hosted grenade documentation like other projects.
Change-Id: I505c1d5e250d103b6e0f9da008f44d3ce28df94f
This attempts to bring README.rst into current reality. A few things
are simplified along the way. It also explains our theory of upgrade.
Change-Id: I2fbb457246a2faca8ac2405104e86885b93e8c48
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
This commit removes some unnecessary commented out codes and files they
are related to upgrade-packages. Upgrading package was part of the
original vision of Grenade. However the scope of upgrades was cut back
now. Because any package upgrades required should be handled in the
service that requires them as Dean Troyer said.
Change-Id: Ic1b6ee2e2b668c0c76c2a1425475651bf8a8bd73
With this patch grenade can be run either with nova-network or neutron.
Closes-bug: #1235149
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Change-Id: Ib35ee2b35155f3c7e86eef5c75f70da300fa99c7
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
This is to avoid confusion with DevStack's DEST which is set to
${STACK_ROOT}/$BASE_RELEASE in Grenade.
Change-Id: Ibc9b94bd51e7d5dd82ec45f23557923d2f38db96
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.
Brian Rosmaita