This change adds an experimental AWS driver. It lacks some of the deeper
features of the openstack driver, such as quota management and image
building, but is highly functional for running tests on a static AMI.
Note that the test base had to be refactored to allow fixtures to be
customized in a more flexible way.
Change-Id: I313f9da435dfeb35591e37ad0bec921c8b5bc2b5
Co-Authored-By: Tristan Cacqueray <tdecacqu@redhat.com>
Co-Authored-By: David Moreau-Simard <dmsimard@redhat.com>
Co-AUthored-By: Clint Byrum <clint@fewbar.com>
Move all doc related requirements to a separate requirements.txt so
that the tests do not install unneccessary dependencies.
Change-Id: I276775ee2d038209f82bfb42dca386a2f5bf02f0
stestr is maintained, while testrepository is not. OpenStack is
migrating to stestr, go ahead and follow suit.
The --no-subunit-trace flag is added to keep the quiet test run
behavior. If we remove it, stestr will by default print the name of each
test as it starts it.
This uses environment inclusions which need tox 2.8.1 due to a bug fix.
So increase the tox minversion.
Change-Id: I08cd4bee86b56d9a68644b049497c34e34e5f226
Do it a little bit differently than OpenStack and just put the
releasenotes into the documentation.
Add an initial release note with no contents so that the build flow and docs
integration can be verified. The note file can be removed later.
Change-Id: Iad16b575e2abbea997b64e3c0e5aa1497b4ff0d2
node_list takes an argument "detail" which adds a rather arbitrary
list of results to the output. This comes from the command-line,
where we're trying to keep width under a certain length; but doesn't
make as much sense here (especially for json).
For dashboard type applications, replace this with a simple "fields"
parameter which, if set, will only return those fields it sees in the
common text output function.
Note, this purposely doesn't apply to the JSON output, as it expected
client-side filtering is more appropriate there. We could also add
generic field support to the command-line tools, if considered
worthwhile.
Add some documentation on all the end-points, and add info about these
parameters.
Change-Id: Ifbf1019b77368124961e7aa28dae403cabe50de1
Providers no longer have "images" they have "diskimages". Update the
refs to reflect that. Also bump sphinx version and enforce warnings as
errors to catch these problems in the future.
Change-Id: I367e36243ff928e194986cb6dc3c68e0d48bbcd0
Story: 2000790
This is to fix a downstream issue between nodepool and
diskimage-builder pip dependencies. Since nodepool depends on
diskimage-builder, it would be nice to have common depends.
We also bump hacking to deal with pbr version issues.
Change-Id: I0efa395bc66c9e50bfe4a13e971232ad9184ad48
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
We are performing smoke tests for image update commands now. Lets
also assert their effects on the image-list command.
Change-Id: I322845e159e81315b1b5f75cbb998d4c795793c4
This was added to work around bug 1091333. A new sphinx has been
released and so this is no longer necessary.
Also update sphinx requirement with global requirements.
Change-Id: I9107884d964757a9154bdd1feb4ea6df4e9df43e
Finish the initial sections defined in the documentation index.
Add sphinxcontrib-programoutput to document command line utils.
Add py27 to the list of default tox targets.
Change-Id: I254534032e0706e410647b023249fe3af4f3a35f
And fix a bug in it that caused too-small allocations in some
circumstances.
The main demonstration of this failure was:
nodepool.tests.test_allocator.TwoLabels.test_allocator(two_nodes)
Which allocated 1,2 instead of 2,2. But the following tests also
failed:
nodepool.tests.test_allocator.TwoProvidersTwoLabels.test_allocator(four_nodes_over_quota)
nodepool.tests.test_allocator.TwoProvidersTwoLabels.test_allocator(four_nodes)
nodepool.tests.test_allocator.TwoProvidersTwoLabels.test_allocator(three_nodes)
nodepool.tests.test_allocator.TwoProvidersTwoLabels.test_allocator(four_nodes_at_quota)
nodepool.tests.test_allocator.TwoProvidersTwoLabels.test_allocator(one_node)
Change-Id: Idba0e52b2775132f52386785b3d5f0974c5e0f8e
flake8 does not pin its pep8 and pyflakes dependencies which makes it
possible for new sets of rules to suddenly apply whenever either of
those projects pushes a new release. Fix this by depending on hacking
instead of flake8, pep8, and pyflakes directly. This will keep nodepool
in sync with the rest of openstack even if it doesn't use the hacking
rules (H*).
Change-Id: Ice9198e9439ebcac15e76832835e78f72344425c
Tristan Cacqueray