We have to continue scrubbing our documentation for anything
that generically refers to 'cells' since older documentation is
referring to cells v1, and we don't want people to confuse that
with cells v2. This simply provides a warning that cells v1 is
not recommended for new deployments and if you were looking for
help with cells v2 commands, we need to redirect you.
Change-Id: I3bd0332607bff169b5f496d17e4fc7d372ea991b
As of change If1e03c9343b8cc9c34bd51c2b4d25acdb21131ff, using
"nova hypervisor-list" before compute hosts are mapped to a cell
will result in an empty list.
Our cells v2 install steps mention using 'nova hypervisor-list' after
creating a cell and starting compute services to tell when to run
the discover_hosts command, but now hypervisor-list won't work until
you've run discover_hosts, so it's a catch-22.
This change adds a release note to let people writing deployment tools
to know about the change in behavior and also updates the install steps
to use service-list instead of hypervisor-list, since service-list does
not require the compute host to be mapped to the cell first.
We are going to need to make a similar change in the OpenStack install
guide since that also mentions using 'nova hypervisor-list' before
discover_hosts.
Change-Id: If2baab40c2e2a3de20e561bba50688d615b002ef
Closes-Bug: #1682060
This copies a line from the ComputeCapabilitiesFilter description
which points out that if the flavor does not have any extra specs
then it passes the filter. I had to figure this out via code inspection
so it would be good to document it.
Change-Id: Id7b3ec5dd2847c9ea615981031d7e0f2b1beb3e2
This was previously hidden within the code review guide making it almost
impossible to find from the initial index page.
Change-Id: I47e771c641d72a837345b1b9a07e86ca4313b518
The note about rolling upgrades not being supported for cells
was referring to cells v1, so let's make that clear.
We will support rolling upgrades for cells v2 deployments, we
just haven't documented it yet (or done it in a grenade job).
Change-Id: I6a8b3d3aaa49859e8b769a296684ac96883719f8
fixed some typos and reword the statement for better
readability in stable_api.rst file.
also, do some enhancement on /extensions API about it
is already deprecated and no more add to it.
Change-Id: I9946d8b095b1418aedb2210ab3a22589625fd2fb
After I817ce4bae0dd37e0d06bd44f21ba81b3cb800548 it is possible to
configure the topics where the versioned notifications are emitted.
Let's update the notificaton devref with this information.
Change-Id: I45b007cfb98330a5b885ef6870e9fcce7108403a
Currently only HTTP 404 can be raised. This enables other HTTP status
to be raised if microversion does not match with the minimum required.
This is useful for new methods created to raise other http status code
for older placement microversions, like 405 HTTPMethodNotAllowed.
Change-Id: I2b684fcfd93fc70fe385a93346ee255279909489
There are always some questions about how quotas work
in Nova, particularly how they are checked against
the configuration vs the 'default' quota class in the
database, and global vs project-specific quotas.
This change starts a document on quotas a high-level.
It does not get into the lower-level details of how
quotas work or are designed in Nova, or the issues
that can arise with the existing quota system or future
plans.
Change-Id: Iabe3d40f44c59f14fa89ceddc556497d2885845c
Since Ia1a0066dc30025c02553584a077365b28d8ff80e FilterScheduler will
no longer fall back to not using placement API. We need to require
version 1.4 to prevent NoValidHost errors.
Closes-Bug: #1669433
Change-Id: I6666cb2f558ed1f4e83f21e0317a206b07c25134
Extension is stablized now and no further development for it
so we can remove those todos in API concept doc.
Change-Id: I087caf4dec2d8dd281c2cf0a17aab4f43b081434
Turns out you can't embed a comment inside a toctree, resulting in the
following error:
WARNING: toctree contains reference to nonexisting document u'.. NOTE:
keep this list sorted by title'
Change-Id: Ifc3fbcde8371b8002f3b17364e6f252e36113702
Fix the following warnings.
- A warning in config sample generation
- Warnings about nova-status.rst
Change-Id: Ifcc3b4a89eeea9d0dd62e2a8b560c5e6a9ff3d1a
Closes-Bug: #1659485
In Ocata, the filter scheduler would not consult placement until all of
the computes had been upgraded. That check no longer makes sense in Pike
and isn't multi-cell-aware anyway. This removes that check.
Change-Id: Ia1a0066dc30025c02553584a077365b28d8ff80e
webob.dec.wsgify was replaced with wsgi_wrapper.PlacementWsgify in
change I3b81c5bd00a013f1659b9e6e80c71b373d965862 .
Here the placement_dev is updated to reflect that the new decorator
should be used.
Change-Id: I049c0d50b3af0d829cb7a041668d8ec4d6e0c590
Initialize optional parameters for update_cell() to None and
enable getting the transport_url and db_connection from
nova.conf if not specified as arguments.
Change-Id: Ib20cfeb7b17dba06f9f2db5eca1fa194d2795767
Closes-Bug: 1665145
Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests. This is exactly what is
currently done by OpenStack CI in project-config.
This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.
See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html
Update devref for this.
Needed-By: Iea42a0525b2c5a5cdbf8604eb23a6e7b029f6b48
Change-Id: Ie9bae659077dbe299eea131572117036065bdccf
In case a cell record was incorrectly created, or needs to be updated
to point to a new database or mq endpoint, we need a way for users to
be able to update a CellMapping record. Since deleting and re-creating
is definitely not an option, this patch adds an update_cell which
allows updating the mutable fields if necessary.
Change-Id: I75ddfa458a6fb650f1098505193398984f2be596
This removes some references to "online schema migrations", as well
as some references to in-progress things that have been (long since)
completed. It also clarifies some of the upgrade steps, and unifies
the notion of "offline" and "live" upgrades, calling out only a couple
places where the process differs.
This came from me explaining the document to someone and calling out
things that were no longer accurate.
Change-Id: Iec1d73c3fd0038d9bca7e7fa746caad06c329ed3
Jenkins