Focal images do not provide 'python' anymore,
and this means that those scripts are broken
in that environment without this change.
And make sure the scripts are really py3 compatible
(fix a buffering issue)
Change-Id: I652e5d007d5a606f0fe89ac6b3ea76f765be1ae4
* Remove settings that openstackdocstheme now defaults to.
* Switch completly to openstackdocstheme to be in sync with
other OpenStack projects.
* Use sphinx-build.
* Change tools/generate-grenade-plugins-list.py to use opendev URLs.
Change-Id: Ic6dd19d8695f4d8db6655e7cac7a6eb7736cd4c1
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
This commit makes to generate a plugin list for the registry
document and, also fixes a python3 incompatibility and docs warnings
in generate-grenade-plugins-list.sh.
And this commit also removes doc/source/plugin-registry.rst because
it's generated by the script.
Change-Id: I391ca452f2e99e899ded8e4bcb5649a4511a7696
This commit adds an execution permission to
generate-grenade-plugins-list.sh for better UX and consistency.
Change-Id: Iaaf0c9041ed3febab28d9a95993173eb6f9e545d
This copies the devstack plugin detection code, to be executed
from a nearly identical periodic proposal job, generating a list
of plugins in the same format.
Change-Id: Ifac7833b03409a4c476b3c9f0f9900987b5ad177
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
javelin is obsoleted for direct use in grenade by the resource plugin
scripts, so remove the coupling and reference to it.
Change-Id: Ieaf63f0162f8d87a96058e941fb5b1f3e750dd2b
There is currently no grenade testing of Trove, and we are working
to move trove devstack support into a plugin. Remove the few
references to trove in this repo.
Change-Id: I7671a657be48cf9ae0211a51e4bc08867a231c73
Creating 2 surviving resources as m1.small and m1.medium means locking
up 6GB of ram in surviving guests, which is *way* too much to
consistently work.
Tune this back down to m1.tiny and m1.micro.
Closes-Bug: #1398074
Change-Id: Ia9d679d82ffae951273f62c7beee67007b2ad080
One server can be attached to multiple networks. This patch adds back
networks per server and if neutron is not enabled, networks are removed.
Change-Id: Ia65b92891419fde908423e9806fe7281c25c6378
Closes-Bug: 1392641
The current javelin config makes assumptions about what services
devstack has actually deployed and will fail if those assumptions
are not correct. We're now testing more than just the default devstack
topology. The list of resources grenade expects javelin to act on needs to
be flexible if we want it to support these non-standard configs. This adds
a tool to dynamically generate the javelin resources yaml depending on
what services devstack has deployed, using the existing resources.yaml
has a base.
Change-Id: Iaf9381e185d4875e6098fe5f3573b5bb61c01e33
this is part of the effort to make grenade summaries actually work
in the gate like we expect, so that the base case can take the
output out of the main console and into summary consoles for
readability.
Instead of duplicating the awk filter from devstack, create a new
python tool for this, which lets us have much greater control and
sanity in filtering out garbage that we don't care about.
Change-Id: I235a725b6ca8a02caddad9f5a1457f6461269d5b
Anand Bhat