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: I669e77c1cc1d626552939b8f65e093e7901ad754
There are scenarios where it is useful to create a ConfigOpts
and register_opts on it before ever calling the PlacementFixture.
If that is done we don't want to re-register the opts within
the fixture as this can lead to errors (especially when CLI
opts are involved).
The scenario that discovered this problem is in nova in a regression
test [1] where a ConfigOpts is created and registered, the placement
DatabaseFixture is started and then that same config is used in
multiple instances of the PlacementFixture, each of which again
register_opts(). Until commit b647919666a451092189f963786e367d0baa82be
this wasn't a problem because the default opts in placement did
not include any CLI options. Adding logging opts brought some in.
This change adds a flag to the constructor for PlacementFixture,
register_opts, defaulting to True, which lets the caller say
no, I don't want do register.
It also reverts the revert of b647919666a451092189f963786e367d0baa82be
to perform oslo_log.log.register_opts() from a central location.
[1] test_bug_1679750.TestLocalDeleteAllocations.test_local_delete_removes_allocations_after_compute_restart
Change-Id: I360a306b5d05ada75274733038b73ec2f2bdc4d4
Needed-By: I042e41ac8c41c0e5f0389904eb548e0e97d54c60
Related-Bug: #1821092
This reverts commit b647919666a451092189f963786e367d0baa82be.
It appears that this causes issues with cross project testing.
Related-Bug: #1821092
Change-Id: Ic612aed0651c083ee5f0396cba07a179324d158b
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: Iff38b88808fa21afeb00b22bd31a614a2f559a8f
Sem-Ver: feature
We have the 'versionadded' directives, but the table of contents is
still a mess. This makes things a little more grokable, IMO.
Change-Id: I6a40e1aa38bc129361fc3db1c6404ce5e8aab625
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
This adds content to the verify doc, part of which is
the placement-status upgrade check command usage from
the from-pypi doc.
Change-Id: I06e731314e8aad8e314e2ba2c3765c19a6c32bf5
Story: 2005190
Task: 29944
In the review of the initial create of the `to-stein` document [1]
some shortcomings were identified that this patch tried to address:
* making it clear that upgrading to extracted placement doesn't have to
be the same time as upgrading to stein
* stop using contractions
* clarify several points. In some cases this means being more
general, in others more specific
* Add some thoughts on verification
* Change the verb "copy" to "move" in a few places. This was done
to help make sure that nova will not remain configured to use
its own placement, which would be very messy.
[1] I32b22d75400c7f7b428ed3d48ac928584071ed29
Change-Id: I722275eba2d17e0751a9a4ccfc58a8e7ede864da
The deployment section provides an overview of install steps.
Make it a bit more useful by linking to examples of creating
service user and service catalog entries.
Change-Id: I3661cdea9e182a87821ac3d18ca0e2fe045947f1
Story: 2005190
Task: 29938
This is intentionally short and sweet. There's very little user
facing, except for the upgrade from nova, so that is highlighted.
Change-Id: Iffb98d22b4f202dfdacc310300cf67ee0a73a52d
This is an attempt at documentation for upgrading to extracted placement
from nova. It is effectively a translation, with links, of the script
used in grenade. It tries to provide details where it matters, but be
vague where independent initiative is warranted.
Story: 2005190
Task: 29940
Change-Id: I32b22d75400c7f7b428ed3d48ac928584071ed29
Provide step by step instructions for installing from pypi.
Note that this is a greenfield installation, not an upgrade.
Only one of many possible web servers is described as there
are too many choices to describe them all.
The depends-on adds oslo.log to config doc generation,
allowing a link to the debug option. This is done as a
depends-on to avoid a rebase.
Depends-On: https://review.openstack.org/644589
Change-Id: I580fa4394cb93b8e8141ee2d546543c174356a47
Story: 2005190
Task: 29943
The concept/name of controller was copied over from nova when the
docs were imported. That concept doesn't really fit in with
placement and also does not describe what the docs are actually
doing. We're not installing a controller, we're installing
placement.
Thus filenames and titles are updated and intro paragraphs
clarified.
Also, the endpoints.rst file is moved into a shared directory as it
is not a standalone install doc.
Note that the big warning remains on the top of the install docs
because it is still true. These instructions and the packages they
mention have not been verified.
Story: 2005190
Change-Id: I5fcbc90eda3ef74dba2336ea3e5c9f53938c6378
Move the registration of oslo.log config options into conf/__init__.py
with the rest.
Change-Id: I4cd3d637878eb5bb798b78fd73f5be99e141da9d
Story: 2005264
Task: 30078
Adds the oslo.log entry point to config-generator.conf so our docs get
the logging config options emitted.
Change-Id: I1d84754cf46852dbd15eeec4a7a244632fd78484
Story: 2005264
Task: 30077
There wasn't really a good overview on how to use placement,
so I've tried to start something by expanding on how nova uses
placement in very broad strokes. The intent here is not to
instruct people on the details of how to manage resources with
placement, rather that they _can_ manage resources with
placement and here's the major steps involved.
Change-Id: I11cd622162efce2e87a21fa5ae5d297f4b248541
When the install docs were ported from nova, cleaning up "databases" ->
"database" was inconsistent. This patch gets the lingering errors.
Change-Id: Id051d8656c58dfc0a351a6de540bb12ef69c1bc6
This patch refactors _get_all_by_filters_from_db() function used in
`GET /resource_providers` to use more common function,
get_providers_with_resource().
SQL queries will increase slightly by this patch, but it is done
for the readability and the debuggability.
Change-Id: Iff0cec9445e6ddafa37c852438ce0c54fef77082
Continuing lines with backslashes is considered icky in python. However,
sqla's function chaining lends itself to doing that, so we had some
backslash continuations in placement. This commit removes them and
reformats the code accordingly.
Change-Id: I703d3ec3ae88c93b9ad2cf48a59642353f8628ce
This patch is a follow up of If815d98a92e411b8006f147cd5ccf419e90f06fc
changing _get_trees_matching_all() to return an empty RPCandidateList
object rather than an empty list to avoid causing bugs later.
Change-Id: Ibfd1fe8dc9b6a0225cfb5aa24b562207acec04aa
We got rid of OVO and otherwise refactored the object layer,
so make that (more) clear in the contributor docs.
Change-Id: I9995a81e47daa4d151d3ff1f027e8caf474a69ed
Story: 2005190
Task: 29945
AllocationCandidatesTestCase includes tests using get_by_requests().
However, it also includes two tests for specific functions,
test_get_trees_matching_all() and test_get_trees_with_traits().
This patch separates the two tests creating a new test class,
ProviderTreeDBHelperTestCase.
Change-Id: I83fc00a96353b985aa2aa60fb146329dd2f4e767
In [1], TestAllocation should have been moved but was missed. Done here.
[1] Ic673dfa95f6c8e42692c6287fb8d7cc27ee6cbf6
Change-Id: Ie948a7bded8dab17d4a85c6ebaf519e01466bc80