Uses openstackdocstheme to match other content
Has a dependent change in project-config also so that
file will build to developer.openstack.org/compute
at https://review.openstack.org/#/c/231000/
Change-Id: Ic060a1e79e4b2f8695cb788ff4df018e0cfd3286
Clarify in the hypervisor support matrix docs that "Stop instance CPUs"
is the same as "pause", and that "Resume instance CPUs" is the same as
"unpause".
Change-Id: I26d6a065dd239f376b57ae44d34276a994b30b2e
Closes-Bug: #1511487
It's not currently possible to create snapshots if you
use libvirt driver with parallels virt_type. First of all
it's because snapshot_extract method is not implemented
in imagebackend.Ploop class. There are also issues in
utils.extract_snapshot, find_disk and get_disk_type.
This patch solves all those issues, so snapshots will
work with parallels virt_type.
DocImpact: parallels now supports snapshot
Closes-bug: 1484074
Implements: blueprint ploop-snapshot-support
Change-Id: Id3b5bfc946a858f7e6ed710f2b44c7ca63a10723
The `nova-manage db archive_deleted_rows` command doesn't print any
results, not even how many rows were deleted, which is something the
database API returns.
The number of rows deleted also changes depending on the max_rows input
and how many rows are deleted in each table, it's a cumulative effect.
We should keep track of which tables we've deleted rows from along with
how many rows, and print that all out to the CLI console if the user
passed a --verbose option.
Implements blueprint print-table-archived-rows
Change-Id: I5c47cd5633eca056f8ae508753a41e2c1ed9e523
The code-review guidelines document should be a somewhat agreed list
of what to consider when doing a review. This patch set adds the
items to check if the review contains changes which involves config
options.
Change-Id: I142ab25fa7fc1c4ece5a68f68c5d841c797af1be
This adds a document that aims to provide a checklist-like review
guideline for code reviewers. We can encode small decisions and tribal
knowledge in this document to help increase consistency.
Right now, this just adds upgrade-related review items as those are
some of the more complicated and least-documented at the moment.
Change-Id: I5bbb7e4e2192b853373fed38ca0ad873fc8b329e
Given that we have some confusion with a NoValidHost returned by a failing
RetryFilter, adding more explanations to the devref to help the operators.
Change-Id: I1f88379a5c1bf6f87ee99dbddd04714ba8def144
This moves material from 2.0_general_info into the index to make an
improved index page.
Some details from the general_info have been moved into the server
concepts, where that information is a better fit.
The general_info page has been expanded with TODOs so we are clear
about some the missing details.
Co-Authored-By: Ed Leafe <ed@leafe.com>
Change-Id: I2a878586d6a073026d1f997e6f0f7ee87a01f726
This removes the one seqdiag that is in our docs which drops the whole
chain of sphinxcontrib-seqdiag which requires Pillow, which requires
that you have a C compiler and jpeg-dev package on your environment to
build documenation for a python project.
Change-Id: Ie7615d48b5524b5e5e1159a25c357f5b3f0eee0e
404 error code is always one of the return code when url or
resource does not exist, so 404 is an available status code for all the
Nova API. Then no microversion bump required for fixing 500 to 404
.
Change-Id: I4b1703e82cd89192b2ba4ce2603741e33dd26586
This commit adds sample config file generation to the nova devref
using the oslo.config sphinxconfiggen module which was recently added.
This will generate a new sample config each time build sphinx is run.
This is then used on a new docs page where you can either view the file
in its entirety, or download the file. The sphinx module was added in
the oslo.config 2.3.0 release.
Change-Id: I6d9150d81c8204bee8f775021a854928671bdd02
The TrustedFilter is the only in-tree scheduler filter that calls an external
3rd-party service (OpenAttestation) for decision-making. Thus, the OAT service
is not listed as an official Nova dependency and consequently not even gated,
even by a 3rd-party CI.
Besides, some discussions have been captured in a ML thread that show that
running this filter is not the best way for enforcing trusted compute nodes [1]
but I leave that out of the review (just a FYI) because the main reason for
making experimental the filter is to send a signal to operators that they will
either have to find another solution or accept the current gaps.
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-June/067766.html
Related-Bug: #1456228
Change-Id: I6ab013faf22a0e88424207830ec399724f827622
Guru Meditation Reports (GMR) code in oslo.reports was recently updated
to expect SIGUSR2 as opposed to SIGUSR1, because it is reserved by
Apache 'mod_wsgi' for its own use.
So, update the Nova doc, gmr.rst, to reflect this new reality.
[1] https://review.openstack.org/#/c/223133/ -- guru_meditation_report:
Use SIGUSR2 instead of SIGUSR1
Change-Id: Iac2d606103189b965581e0c6c20b55360a04e3a6
Since the AZ knowledge is mostly tribal and can have some corner cases, we could
help the operators by giving more visibility on how it's made and what to prevent.
The related ticket mentioned below is one example of a common mistake that is
quite not easily fixable from the Nova standpoint since the design is mostly broken.
Change-Id: I092c8caa9e450a68a7a952940b0bb288b8fe6fb0
Related-Bug: #1444841
Updated to reflect Nova's current relationship with the database.
Also adding references to work on cells.
Change-Id: I7dcf9378fdd1c1f62a51944ea64ac20f8cdfe0d6
In addition to being a database proxy and object backporter the
conductor also manages rebuild, resize/migrate, and building instances.
This documents why that is done.
Change-Id: Ieb9134302d21a11fe9b9ee876bb7b0dd32b437e1
Nova v2.1 API validates a request with JSON-Schema, and there are
some specific usage on that. This patch adds it to the rst file
for the implementation hint.
Change-Id: I4edac8b6b53d198f2a237bb163b8975528319c9b
The commit Ic19f2d019c2c78f1de14a0eced85e84f2d2cec28 has changed
API directory structure, but we forgot to update the corresponding
doc. This patch updates it.
Change-Id: Ie287fc99a6b9b30befa09b7a30226ac6460ad612
Added a set of schema and data migration policy rules to the `upgrades`
devref document to facilitate live upgrades.
Change-Id: I4e38a228b38927115bb13652966d45f250cc2af6
As the API validation code always return 400 when request with
invalid json body, so 400 is an available status code for all the
Nova API. Then no microversion bump required for fixing 500 to 400.
Change-Id: I0454e95cd0655c910fad8b39ead2b5edab216b68
Related-Bug: 1471239
Change Ia782ab9d9a31d37854606f7be82582de6d7bc374 returns a 403 rather
than a 500 for OverQuota and adds that to the list of expected errors in
the v2.1 case.
There is no microversion change required since the 403 case is implied
given keystone authentication can fail with a 403 on any API.
This change updates the docs to mention the exceptional case for 403.
Related-Bug: #1444559
Change-Id: I7ea8c5c50d4eac53837f5f76e09277ac185288a9
We shouldn't require a microversion bump for translating a 500 error to
some 400-level error code since 500s should not be part of the API
contract and clients shouldn't expect them for cases that the client can
change, i.e. don't ask for things that don't exist, don't ask to do
things that raise quote and you're already maxed out, etc.
There was some confusion in the doc about the statement that a
microversion is needed when changing from a 501 to a 400, but that's a
different case (going from something not being implemented to it
suddenly being implemented - that's a case where the client should
opt-in and a microversion bump is required).
Not returning 500s is just fixing bugs and shouldn't require a
microversion, the docs even already say that in the first footnote -
this just adds notes to clarify.
Also fixes the links to the [1] footnote.
Change-Id: I4526a72458a23662bd8aaa7f89be32844a511929
The old peer code review wiki has been replaced by the infra dev manual
for peer review, so update the link in our docs.
Change-Id: Ib84e2e10e32a2328d9252c86b539b1b40830761d
Whenever someone asks about v2 vs v2.1 vs v3 API and I point
to the docs, I also point to the Liberty summit session which
is good for new people to watch before trying to sort through
the docs and code, so add a link to the high-level section
of the docs.
Change-Id: I34d734454afcfdae3f874160dfd11662e61c2faa
Jenkins