5 Commits

Author SHA1 Message Date
Adam Spiers
6a5aa7c6a2 Fix some Markdown formatting issues
Address miscellaneous issues with Markdown formatting in comments which
are consumed by shocco when generating the online documentation.

Change-Id: I953075cdbddbf1f119c6c7e35f039e2e54b79078
2013-10-24 17:38:19 +01:00
Alessio Ababilov
c2a4c9238d Fix 'olso' typo in lib/oslo
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
2013-08-16 21:57:20 +03:00
Attila Fazekas
025fc5e5f5 Faster old oslo.config detection
Just search in the path where python searches for modules.
Let's use python for searching, it knows the exact rules.

Change-Id: I659f734c418ab5e56f4956f418af48dfbe054c8a
2013-08-13 18:55:33 +02:00
Sean Dague
db5fadb5cb cleanup potentially installed older oslo.config
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
2013-08-09 14:05:36 -04:00
Sean Dague
1b6b5318a0 install oslo from upstream in devstack
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
2013-07-31 07:32:20 -04:00