And add some additional horizontal white space to make it easier to
understand different long bullets are different.
Part of bp: doc-migration
Change-Id: I36cd7513fa5d482b6cd85a062eace21704c49f85
List items need to be exactly 2 spaces off of the parent, and the top
level left justified, otherwise <blockquote> gets thrown into the
html.
Part of bp: doc-migration
Change-Id: I16634edbc562aff69744e5d7c7275689326ab8d0
What looked clear in the rst actually was far from clear when rendered
in HTML. The document was restructured a bit so all the options end up
in a single bullet list, and the combination description is a separate
section.
Part of bp: doc-migration
Change-Id: I2feee4018a332483658d24d299dbb04ec87f2df0
list bullets have to be exactly 2 spaces indented from the parent, and
the top level is left justified, otherwise we get lots of <blockquote>
html tags inserted.
Part of bp: doc-migration
Change-Id: Ie8b311ca286601a47475b33ef80da272efc9be31
Sub lists have to be indented exactly 2 additional spaces from their
parent, otherwise it is treated as a blockquote, which isn't what we
want.
Part of bp: doc-migration
Change-Id: Iab46b5e39e4bd0d154f33dc795f24362c77a88a5
The extra whitespace causes the content to be rendered in <blockquote>
which is not what we intended. It's far more noticable in the new
theme.
Part of bp: doc-migration
Change-Id: I18af115c17791cf2faf03311b857153f674c6367
A lot of our rst was actually misformatted with extra spaces indenting
the bullet lists. This wasn't very visually noticable in the
oslosphinx theme, but it's really bad in the new theme. There will
need to be lots of fixes here, but will do them one page at a time.
Part of bp: doc-migration
Change-Id: Ic1d1383148b005b884fdfa3e9a9658adcb13ee70
Test cases for resize to same host with confirm and revert scenarios
have been added.
The accounting of the current code is very incorrect at the moment, so this
asserts the existing (wrong) behavior, but marks the actual expected
values everywhere so that we can follow up with fixes to remove all of the
annotations.
Related-Bug: #1707252
Change-Id: Ica83ce5f43c0e7b84fd4117852e81e4d2979dea3
The license header isn't in a comment correctly, so it shows up
inline in the rpc page and looks pretty ugly. Add missing '.'
Change-Id: I7c05ee9c4074d1e29f77b4c1c292196bcf0b801d
Just to make it easier to see if items are in the list or not, we
should keep them sorted. No fancy hacking rules for this, just being
dilligent.
Change-Id: Icbfdcffbc15c5c32ca48ddd6fbac15d425ab8c44
From http://paste.openstack.org/show/617316/ this devref linked page
is our top 404 at the moment, add a redirect match for it.
Change-Id: Ie42935e5fa5d2199f9878edc2951ba0734e95a7c
The api-microversion-history doc has now moved under "reference/"
so we need a redirect.
This also removes the draft site redirect for cells since that
was only in here for CI testing to make sure the redirects work,
which we know they do now:
https://docs.openstack.org/nova/latest/cells.html
Change-Id: I21bcd71b21af3108e1b14229f90b5ec07cc8188b
Bug #1707669 highlighted a situation that arose when attempting to
remove part of an allocation for a source host during a resize
operation where the exiting allocation was not being properly deleted.
In this patch, we remove the part of the WHERE condition that limited
deleted allocation records to only those referring to a particular
resource provider. In doing so, we make the creation of an allocation
for a consumer a proper overwrite operation.
Change-Id: I0835e5b4f22277465012aab9a5bf474608cb533b
Fixes-bug: #1707669
Adds a number of assertions that usage and allocation records are what
we expect at the following times:
* After boot on the source host but before running periodics After
* resize operation but before confirming or reverting and before
running periodics
Change-Id: I23ed64d5c48f520f115d64a97c748e5b49bb5f20
Related-bug: #1707071
We broke the possibility in Ocata with Icdcf839b6d28893694bfa1355e9dbe8dbb5ea8c3
to use other scheduler drivers but the ones we provided in tree.
Unfortunately, that was an incidental change without any communication.
Removing the choices kwarg will allow operators to run their own scheduler driver.
Whether Nova would stop supporting custom drivers would require a totally separate
change which would clearly communicate thru a deprecation notice but that is not
the intent for that bugfix, which aims only to bring back the capability.
Change-Id: I346881bc3bc48794b139cc471be1de11c49b8ee3
Closes-Bug: #1704788
This adds a fresh cellsv2 overview document that talks about
deployment decisions for single and multiple cell environments
in an attempt to help address confusion about what the service
layouts look like in a multi-cell setup.
Change-Id: I1da7c375dbb98c125aebabec548280de8d8ed381
Test cases for resize with confirm and revert scenarios have been
added.
This test depends on the periodic update_available_resources call to heal
the resource allocations. The fake virt driver needed to be tweaked to
work when more than one compute service is created and periodic tasks
are enabled.
The accounting of the current code is very incorrect at the moment, so this
asserts the existing (wrong) behavior, but marks the actual expected
values everywhere so that we can follow up with fixes to remove all of the
annotations.
Change-Id: If7b02bcd8d77e94c7fb42b721792c1391bc0e3b7
blueprint: placement-claims
With multi-cell support in Pike, we should deprecate cells v1
so we can at least start the deprecation signaling in the
docs and release notes. We may not end up removing cells v1
code in Queens, but this at least gives us the option.
Note that we also want to do this because nova-network cannot
be removed until we remove cells v1.
Change-Id: I1a173f7ce0715e684850e030c358e8175fa8724c
Change If1e03c9343b8cc9c34bd51c2b4d25acdb21131ff made the
"PUT /os-services/*" APIs only work with nova-compute services
since they now rely on finding the compute service in a cell
via the host_mappings record in the API database, and host
mappings only exist for compute services.
No one should have relied on disabling a non-compute service since
that does nothing, at least with in-tree code.
This change just adds a release note for awareness.
Change-Id: Idb5bbc31a0aabc328f11e5a9979e5b80651a8f67
Closes-Bug: #1700359
In an environment where http_proxy env variable is needed to buil a
proper python virtualenv the functional test fails with:
RuntimeError: http_proxy or https_proxy set in environment, please unset
This patch removes passing proxy env varibles in tox.ini to avoid this
error.
Change-Id: Ia4d8fe952aecb5c3e688878ef0fdafd6fac4fc7a
Closes-Bug: #1706545
Jenkins