Check that function calls look like ^function foo {$ in bash8, and fix
all existing failures of that check. Add a note to HACKING.rst
Change-Id: Ic19eecb39e0b20273d1bcd551a42fe400d54e938
Oslo has adopted 4 libraries that were previously on
stackforge, so we can now install them from source.
Change-Id: I6b6e20a7884b47ade466fc38641a5ac1a5f3e146
oslo.rootwrap recently graduated but was not made part of the
devstack-gate. This change is part of a series of changes affecting
devstack-gate, config and devstack which will collectively fix this:
https://review.openstack.org/#/q/status:open+topic:rootwrap-gate,n,z
This should probably be merged once the config and devstack-gate changes
are in, so that it can be self-testing.
Change-Id: I7b1332c8004845a0dd76e27d871370d41d4524ac
Address miscellaneous issues with Markdown formatting in comments which
are consumed by shocco when generating the online documentation.
Change-Id: I953075cdbddbf1f119c6c7e35f039e2e54b79078
This enables commit If92073be5a431840701c952a194e63a7c452c9ca
for cleaning up potentially installed older oslo.config. Here are
its original details.
If the user had oslo.config installed prior to us setting up the
oslo.config out of git they can get themselves into this very funny
situation where pip doesn't see oslo.config 1.1.x, however some
packages might. This manifests itself as a user error trying to
start nova-api which uses DeprecatedOption, not in oslo.config 1.1.x
Because of the funny state pip is in, you can't uninstall oslo.config.
So in these situations, if we see old oslo.config in the filesystem,
pip install / uninstall it to ensure that everyone ends up using the
git version instead.
To reduce the amount of user confusion, do this on every
install_oslo for a while, which we can purge after Havana ships.
Change-Id: I7fa0b70497bf5622f4638da284afe5363a004d3c
Fixes: bug #1213089
Just search in the path where python searches for modules.
Let's use python for searching, it knows the exact rules.
Change-Id: I659f734c418ab5e56f4956f418af48dfbe054c8a
If the user had oslo.config installed prior to us setting up the
oslo.config out of git they can get themselves into this very funny
situation where pip doesn't see oslo.config 1.1.x, however some
packages might. This manifests itself as a user error trying to
start nova-api which uses DeprecatedOption, not in oslo.config 1.1.x
Because of the funny state pip is in, you can't uninstall oslo.config.
So in these situations, if we see old oslo.config in the filesystem,
pip install / uninstall it to ensure that everyone ends up using the
git version instead.
To reduce the amount of user confusion, do this on every
install_oslo for a while, which we can purge after Havana ships.
Change-Id: If92073be5a431840701c952a194e63a7c452c9ca
the libraries that have graduated from oslo incubation need to be
made available in devstack so that projects can develop against
upstream versions of these libraries, and that we can test their
compatibility in the gate.
This should also allow us to force global requirements on all the
projects during installation.
Change-Id: Idf527b16b50eb58564ec74428290cd31424f5de2