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
This just adds some more detailed docs for upgrading
to Ocata and notable things for the Placement service
and related components as part of that upgrade.
The Ocata release notes will have some of this
information too, but I think it's good to also have
a single place for some of this, like an install/upgrade
guide for Placement.
Change-Id: Id33b9c852bb36ae80a6f29ae33d963a78cbff193
Depends-On: Ie12acb76ec5affba536c3c45fbb6de35d64aea1b
The docs for this command were woefully out of date. This
change clarifies the wording since we're really upgrading
the schema in the database, not "synchronizing" it even
though that's the name of the command - the migration scripts
run the 'upgrade' method only. Also, it was saying this was
how you created the main database, which is totally wrong
since this command doesn't create the database. The deployer
creates the database, this command migrates the schema on that
database.
Then I also added the arguments along with a description of each
and noted that this will by default upgrade the cell0 schema.
Change-Id: I3d40cb32c325bc3f665e727b921082efba043192
This is just a simple change that provides a references section
for setting up cells v2 and points to the nova-manage cell_v2
man pages.
Change-Id: I94d3de97f4ff2120e250ac40ac82c31372d90a2b
There are two changes here:
1. Removes the mention of the message queue since the cell0
mapping has a transport_url but it's effectively none meaning
we don't use RPC for accessing cell0 objects.
2. Adds boilerplate wording on the config option used to determine
the database connection if the --database_connection argument
is not specified. This was particularly confusing at one point
because it originally started out as the CONF.api_database.connection
but we changed that mid-cycle in Ocata since the schema for cell0
is the cell (nova) DB, not the nova_api DB.
Change-Id: Ie869f8565460600da767d99e9e397abc5e8bf0e0
Document the `nova-manage cell_v2 delete_cell` command.
This is part of a series to document the nova-manage cells
commands.
Change-Id: I280b87ad38feeaa68728f51c78b1c6a0dc895ca7
Document the `nova-manage cell_v2 list_cells` command.
This is part of a series to document the nova-manage cells
commands.
Change-Id: I0cd0c3d8c6cd0229a62b3eaf18679d4931c6e4eb
Document the `nova-manage cell_v2 discover_hosts` command.
This is part of a series to document the nova-manage cells
commands.
Change-Id: I7ce9a93384741e42f409324cf0ee3cb1fc4c6a67
Document the `nova-manage cell_v2 create_cell` command.
This is part of a series to document the nova-manage cells
commands.
Change-Id: Ic9ddef319aaf8a377d733633cc279a0fc1558cb2
Document the `nova-manage cell_v2 verify_instance` command.
This is part of a series to document the nova-manage cells
commands.
Change-Id: Id243299bdf0f115e86200cee38634791ea359b2a
Document the `nova-manage cell_v2 map_cell_and_hosts` command.
This is part of a series to document the nova-manage cells
commands.
Change-Id: I4ed1e77f100e9d90d6a1ebd5e20bdd1f1ff5ce6e
This patch adds a new method "trigger_crash_dump" to Ironic virt
driver. Ironic supports this feature since Ironic API version 1.29.
It also requires python-ironicclient >= 1.11.0.
Change-Id: I33812abbff919e5e477334c3bc46309491d14b6a
Implements: blueprint inject-nmi-ironic
Co-Authored-By: Tang Chen <chen.tang@easystack.cn>
Co-Authored-By: xiexs <xiexs@cn.fujitsu.com>
Depends-On: Iac112b82bab9cdf8a383879f9424cb368df741d6
Jenkins