Underscores make for really ugly URLs and every other document here is
now using hyphens for this very reason. Let's try to keep that going.
Change-Id: I5c99ff6b04ee97bac210a0d6762015225775c5ee
This patch is follow-up for
I48d7c77a6e0eaaf0efe66f848f45ae99007577e1.
The hyperlink style is fixed.
Add a note that it need be updated for os-xenapi latest version.
Add a reference to nova policies.
TrivialFix
Change-Id: I274fb6b7ea0bb2ea81faaa68d783edbaa8ed06c3
There are currently two docs describing flavors in 'admin', which
contain a lot of overlapping information. Fix this by keeping the
configuration guide (how to create, delete, modify flavors) in
'admin', while moving the reference-style parts into 'user'. We
cross-reference the two internally.
Given that large chunks of this needed to be rewritten, we've taken the
opportunity to fix a poor description for the RXTX factor, closing a
longstanding bug in the process.
Change-Id: Ia57c93ef1e72ccf134ba6fc7fcb85ab228d68a47
Closes-Bug: #1688054
We haven't had a doc wide index or mod index in this
section on the main page for a long time, so it's a
weird title for just having a link to the search page.
This renames the section title, describes the link and
also links to the openstack-wide docs search page.
Change-Id: Idf63e6035841c8ff0ec1aa9bd2994fedf53555b1
This adds `nova-manage db ironic_flavor_migration` which allows
pushing the migrations ahead of time, and without ironic or nova
services running.
This is a similar operation to online_data_migrations, but there is
a need to pass data that would normally be retrieved from ironic.
However, we want this to work offline and thus that data must be
provided locally. When fast-forwarding through the pike release,
ironic and nova-compute will never be started and thus we can't rely
on the online nature of the migration integrated into the ironic
driver.
Change-Id: I459bce472227ee08230d3120d9e2eb1bde635218
VM diagnostics has been updated with v2.48 to include a standard formatting.
This change will update the admin documentation to mention the new standard
formatting.
Change-Id: I2498ae5400ad0903f6084bacaf96f0b76731b5a3
Closes-bug: 1696033
This fixes the two points in the note at the top of the
flavors page:
1. The policy rule in the first bullet was old so it's updated.
2. As of Ifa4e9cdfbbac1a1d4bf28679b24a17b13f637ddd in Pike,
Horizon no longer allows you to 'edit' a flavor by default.
Rather than try to explain historical bad behavior and the
new default behavior in the Dashboard, the second bullet is
simply removed.
Closes-Bug: #1715995
Change-Id: I372bf1e159d1db32461f843bd94c453d2e7df8d2
The idea is that each guide should be self contained, even though we can
link between them. Enforce this by duplicating a lot of the content from
the main index page to the user index page.
Change-Id: I160fed0f1b507eba7958666bf38f4138b0f62b3a
The attach volume section has LXC listed as 'missing' and you
need to be able to attach a volume when performing a swap
volume operation, so swap volume must also be marked as missing
for LXC.
Change-Id: I97b024d3ff817a7152906b0a88b1b64db93d7d7d
Update doc links according to OpenStack document migration,
Use https instead of http for docs links, and update.
Change-Id: Ia4c58ffd799444b939175603bdf511622def75cc
* "compute service set" command requires a host, not a zone
* the --disable-reason flag's argument has to be quoted
Change-Id: Iaf58d702b1619a66f97553cf2e47eb8c85166bf6
from commit
925eb734a9d3cb46bb89a89ec1a78281d2d7afe9
it says qpid is removed so nova should not guide user to use qpid.
Change-Id: Idf745ec5ccc08a3bab55c3e4394e4a4da900f56d
Notifications are essentially another API for end users, but
it can be hard to find the list of existing notifications or
their samples which are buried deep down via contributors >
technical reference deep dive > notitfications. If I'm an
end user, I'd like to just see them in the same set of links
on the main page as the API, under the "For End Users" section.
Change-Id: If3ca21b080d06a291ed27c9bcd84a566164c3b70
Now that we have a placement api-ref getting published, we
should link to it like we do for the compute api-ref. This
also links in the placement microversion history for consistency.
Change-Id: Id0c70486c5a72a4d6794d80d350a45a5f356ca37
Jenkins