There were several things wrong with this doc since the migration
in-tree in pike, which are handled here:
- Updated options to use the current names.
- Any mention of the periodic_task_interval option is removed
since this doc is really about the FilterScheduler, and the
periodic task interval is only used by the CachingScheduler to
cache and refresh hosts, something the FilterScheduler doesn't do.
The note about service_down_time is already covered in the help
text for the periodic_task_interval option.
- Removed a broken (and oddly placed) link to the block storage
docs; it's unclear why the compute scheduler docs need to randomly
link to the block storage docs for schedluing (maybe that was
super legacy from the nova-volume days).
- Fixed a broken link to the 'evacuate instances' docs.
This change does not get into details for the individual filters
or weighers, only the overview and filter scheduler description.
Change-Id: Ie5bb9781e1997ad12521b5df5245a78b587a4a20
Closes-Bug: #1749235
The docs were using variable names from the filter code rather
than the actual config options.
Change-Id: I2694b32e9c90ad098101e41e4e3ae36ddafd8d0f
Related-Bug: #1746483
Nova has two pages in documentation listing things supported on several
architectures/hypervisors. This patch adds initial state of AArch64
into support matrix.
Document minimal qemu/libvirt for aarch64. Version 3.6.0 was first one
which worked for us with Nova without a need for extra patches.
Change-Id: I2ee7be9e88e20ed0f77be07fed4fdd800533b3c5
The 2.14 microversion makes the --on-shared-storage calculation
happen automatically in the compute service, so we should make a note
of that in the evacuate CLI docs.
Change-Id: I88806897a2412971b3c7488155f17156ae1c7bf9
In 'Writing to the API' section of nova doc index page(*),
there is the 'Compute API Guide::' item.
It should be 'Compute API Guide:'.
* https://docs.openstack.org/nova/latest/#writing-to-the-api
TrivialFix
Change-Id: I59455c9783baccbf6ca7c6cf9da7f040f235de14
This commit is to update support matrix and doc for VGPU feature
on XenAPI.
Implements: blueprint add-support-for-vgpu
Change-Id: I0c9797d1f274e37e3b084d94d0b85980260b2861
The affinity and anti-affinity server group policy is enforced by the
scheduler but two parallel scheduling could cause that such policy is
violated. During instance boot a late policy check was performed in
the compute manager to prevent this. This check was missing in case
of rebuild. Therefore two parallel evacuate command could cause that
the server group policy is violated. This patch introduces the late
policy check to rebuild to prevent such situation. When the violation
is detected during boot a re-scheduling happens. However the rebuild
action does not have the re-scheduling implementation so in this case
the rebuild will fail and the evacuation needs to be retried by the
user. Still this is better than allowing a parallel evacuation to
break the server group affinity policy.
To make the late policy check possible in the compute/manager the
rebuild_instance compute RPC call was extended with a request_spec
parameter.
Co-Authored-By: Richard Zsarnoczai <richard.zsarnoczai@ericsson.com>
Change-Id: I752617066bb2167b49239ab9d17b0c89754a3e12
Closes-Bug: #1735407
Now that Queens supports attaching virtual GPUs to an instance, we need to
properly document which hypervisors support that, how to use that feature and
what the existing caveats are.
Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com>
Change-Id: I871894c3584e92f80f6420dfc009e21b30450f8e
Implements: blueprint add-support-for-vgpu
This updates some busted links, adds ironic and powervm to the
table header, and copies a description from the admin guide.
Change-Id: If146a26a8d0c66a3ff218c62624e3a130744dde5
The instance list performance and reschedules issues have
been fixed in Queens so this updates the caveats section
of the cells v2 layout doc to point out those changes since
Pike.
Change-Id: I882f185554b6d2781534fa93e41e5010ea3a641d
Now that the instructions for booting from a volume
have been migrated to nova, the instructions for
booting from an encrypted volume can be added as
well.
This commit adds instructions for how to import an
image into an encrypted volume.
Closes-Bug: 1701614
Change-Id: Ida4cf70a7e53fd37ceeadb5629e3221072219689
This adds a mention of the nova-scheduler service requiring
placement 1.17 and also links to the placement upgrade notes
from the more general upgrade notes, since we are now firmly
in a place where placement needs to be upgraded before nova.
Since we consider placement global, this removes the 1.14
note about nova-compute since we assume that if you're going
to upgrade placement to get 1.17 for the scheduler, and control
services should be upgraded before computes, then the computes
are going to get a new enough placement service automatically.
Change-Id: I06937c7642dca4a1932cbbf46569acc9c58e44a6
This is a follow up to Ie039322660fd0e2e0403843448379b78114c425b.
A few things are changed here:
* The note about using file injection is removed. File injection
was deprecated in the API in Queens and not something that we
really want users using.
* Mention that creating a flavor is typically admin-only.
* Link to the BDM docs for more details about BDM parameter values.
* Update the manage-ip-address docs to make the examples rely on
using the networking resource CLIs rather than any proxy APIs
that were available in nova.
Change-Id: Ifa2e2bbb4c5f51f13d1a5832bd7dbf9f690fcad7
This imports the "launch instance" end user guide docs from
the openstack-manuals repo. As part of the docs migration
in Pike, these were forgotten. The copied contents come from
the stable/ocata branch of openstack-manuals, and therefore
likely need some updating, but that could be done in follow up
changes. This is an initial import to (1) publish the content
again somewhere and (2) fix broken links in the cinder docs
for booting from volume.
Change-Id: Ie039322660fd0e2e0403843448379b78114c425b
Partial-Bug: #1714017
Related-Bug: #1711267
This takes most of the release note and adds it to the user
flavor docs which is more discoverable for an end user.
Change-Id: Ia83af4dfcc0c040679b0d0cd5282830fca27bd63
The bug report says all:
"There is a mismatch configuration for placement.
In the controller configuration, the guide suggests endpoints creation
pointing to port 8778, however in the default file provided in SLES 12
SP3, the port used is 8780."
Fix documentation to match sample file.
Change-Id: Ib4c881058b9b90ba136ff223064c113e63f98379
Closes-Bug: #1741329