Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: I5637374ac8b957e948c2345a883636198cf15e9b
Move the requirements definitions and documentation files to the
standard places used by other OpenStack projects so our doc publishing
jobs will work.
Change-Id: Iea630d827976fe517afacf4e373b3a125efff9c9
We use pbr to install stevedore, and because of the way setuptools deals
with install-time requirements we also need to include it as a runtime
dependency to ensure it is installed by pip and not easy_install.
Change-Id: I0a39bb50218a1a7cdb2d42fb474a9b8f6d6ac32a
Closes-Bug: #1384919
This patch moves all unit tests to use
testr as the test runner. This means all
tests need to be subclassed from unittest
to be discovered by testr
Change-Id: I9b0e782be87ea2b5db72b56ddad1d239a83e9ee3
Closes-Bug: #1330204
After the move from stackforge the git repository location
in the documentation was no longer up to date.
Change-Id: I7ccb0abe188f4cdebd36b727f6a681aba370af0f
Move all test dependencies to test-requirements.txt and update
tox.ini to use that and the main requirements file to build the
virtualenv for testing. Remove redundant references to the different
requirements lists in other tox environment stanzas.
Change-Id: I1ff094778369ebfed567ebbb433ef487066f042a
When using the DriverManager class, if the driver fails to load, it's
actually better by default to re-raise the exception. It's not something
possible when loading multiple extension, but it's safe to do so with
drivers. This just changes the default behaviour, and it can still be
overridden.
The upside of that change is that when you try to load a driver that
cannot be loaded because of missing dependency, you actually get the
ImportError backtrace on your screen rather than the useless:
RuntimeError: No 'foo' driver found, looking for 'bar'
which doesn't help at all. And the default mechanism that logs via
LOG.error() doesn't print anything at the screen if the application
didn't configure the logging subsystem.
Change-Id: I67d9e13a07c822c54dd16ac9ae7716747a24dd73
Only log an error from loading a plugin if no load
failure handler callback is provided. Otherwise,
assume the handler will do any logging it wants.
Change-Id: Iac83f3c140067bc3d1996c40c0184e4a0d0b564a
Commit 3c2b1df85a88162e086d4f62bf99079432851ba8 hard-coded requirements
checking when a plugin is loaded to be turned off (the previous default
was turned on). This commit adds a parameter so the caller can decide.
Change-Id: I639c1fed7231b8adeab1e3ef9c863763a60bfd0d
A previous change added an argument to several methods without
updating their docstrings to describe it.
Change-Id: I10c753a2d935c0a4ae87ff9258c91f1530d398db
When entrypoints are loaded it is sometimes useful
to be able to do more than LOG the failure that could
be emitted from the plugin failing to be constructed,
allowing the manager classes to be provided a callback
that can be called when such extension fails to load
is useful to track these types of failures.
Change-Id: Idc7e55ade6b3f80c348123fbceea64425d7d3508
Update URLs in the documentation for the source and
bug tracker.
Add a .gitreview file to make reviews work.
Change the "style" tox env to "pep8" to be consistent with
the check job expectations.
Change-Id: I5dd1e157e11ef597dd22ab2e3f5d1219f0489a7e
