This is an old spec but it provides useful context and was difficult to
find due to the naming. Resolve this.
Part of blueprint sriov-pf-passthrough-neutron-port
Change-Id: I864daa6eafd7eadb00076f51240a1726122463d6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Sphinx 1.6.x gained a cross-reference check warning that caused
the build to fail in "tox -e docs" environment. Removing underscores
from the citation reference identifier ensures that the cross references
are properly detected. Similarly missing references to footnotes are
now a warning (which is upgraded to an error in the docs tox
environment) so adjust references where it makes sense and is needed.
Closes-Bug: #1695127
Change-Id: I7e55dcf910e0ba6dd85b565db8cb1ecbdd39634a
TrivialFix:
"automaticly" should be "automatically"
"instnaces" should be "instances"
"verison" should be "version"
Change-Id: If470b65277718a4c6d1c56b4d215b565babe67d0
For some reason a number of specs (and docs) have zwsp characters
inserted in URLs. This causes crud in the reviews, and really
confusing errors around line lengths for people (we count them, but
they aren't seen in their editor).
This removes them and makes a test to make sure they never come back.
Change-Id: Ib6e94725e2716dbb2ff86f272fbe4a6987714444
Code was merged while in Mitaka, but there is some differents from this
spec, update it per code implemention.
Change-Id: Ia22636e0dc9ff9c22cad0cf30948c3c77915f8e7
Note that resource-classes was already moved but the redirects
file wasn't updated, that's fixed here.
There are some partial blueprints that were marked completed in
mitaka and are still being worked in newton, like the config
option work. I've moved those to implemented here also.
Change-Id: I16f279b4794127cb7abc40ffc22cc237702d14ed
A spec was renamed to better describe its purpose. Add a redirect entry
to ensure documentation links don't break.
Change-Id: Iae787491efb935201d206f30bce44becc7d78e64
The thread policy aspects of the virt-driver-cpu-pinning feature
are incorrect. There were not implemented for Kilo and shouldn't be
included in this doc. While there was a note stating as much, it makes
more sense to remove the documentation from the CPU pinning spec
and move it into the (renamed) CPU thread pinning spec.
Change-Id: I28980de107ae8e5b8b8c8394bf7b007ff028e855
https://blueprints.launchpad.net/nova/+spec/virt-driver-cpu-pinning
It was requested that an additional 'prefer' thread policy be added and
the 'avoid' and 'separate' policies be removed.
* The 'prefer' policy corresponds to the existing CPU thread policy.
Without this change, the policy can be implicitly selected by leaving
the 'hw:cpu_thread_policy' instance metadata and
'hw_cpu_thread_policy' image metadata fields blank. This change
allows the user to explicitly do this, while retaining the existing
implicit behavior. This is similar to how the 'shared' CPU policy
works.
* The 'avoid' thread policy provides another way to implement something
that can already be achieved using availability zones and the policy
is therefore be dropped.
* The 'separate' thread policy only helps to optimize performance (L2
cache usage) while the siblings are not occupied by other VMs. This
temporal optimization provides little value and is therefore dropped.
Some required clarifications on the remaining policies are also
included. Explicitly state whether hyperthreads are required or not
(this was implicit previously, which led to some misinterpretation).
There is a dependency on a bugfix which is required to enable usage of
the 'prefer' policy on hosts with sibling counts that are not dividends
of the overall instance core count. Document this.
Finally, "hyperthreading" is an implementation of SMT. Use the generic
term to illustrate the feature's applicability to other
SMT-implementations, i.e. on POWER.
Change-Id: I260d857921cc2191fbdcef6d8d6fb6af6e886af9
Makes a number of changes to the proposed resource-providers blueprint
database schema:
- Adds resource_providers.generation field along with lengthy
explanation as to the necessity of this field in compare-and-update
claim logic
- Adds resource_providers.name field to be used with
generic-resource-pools feature
- Adds can_host field to help in future scheduler work
Change-Id: Id875d46222d65f84df8b87a629005f326d15c26b
blueprint: resource-providers
We need a system that can properly account for resource capacity and
usage amounts, including when the deployment uses shared resource pools
like shared storage for ephemeral instance disks.
Change-Id: If6107a41152d8b085ba176d27f64763e4f77fcd6
Blueprint: resource-providers
Adds a blueprint specification for a new lookup table and Nova object
for the different classes of quantitative resources that may be used in
the system.
Change-Id: I89f718630d6fa6f9ad3fac884d90d3fe0c92ffbb
blueprint: resource-classes
This patches adds changes to the Nova REST API to allow users
to create a server with a description, rebuild a server with
description, update the description,
and get the description in the server details.
Note: Future commits will be done to support the server description
in python-novaclient and openstack-client.
APIImpact
Implements blueprint: user-settable-server-description
Change-Id: I262e1fd5cfcc6f78d7979c122f00434e95e3d709
During the implementation we made adjustments to the initial idea.
This update reflects that for documentation purposes.
bp/centralize-config-options
Change-Id: Icf14f349a158794147ced71133f7ea20f480911c
In the earlier phase the limitations were not listed in the
multi-attach spec. This patch adds the identified cases to the spec,
which need to be handled in the code to safely launch the feature.
Change-Id: I0df3d383409490f97ca51be1fa5e408181827330
Libvirt 1.2.9 version has included support to boot UEFI instances using OVMF,
therefore nova compute needs to be able to boot instances using UEFI images.
bp boot-from-uefi
Co-Authored-By: Ren Qiaowei <qiaowei.ren@intel.com>
Change-Id: I0f1d13ee9c1f81cfe688e174d9e8abce2f4051be
Same as the propose of blueprint abort-live-migration and blueprint
pause-vm-during-live-migration, the migration resource should be a
sub-resource of server '/servers/{id}/migrations'. The top-level
resource 'os-migrations' won't be extended anymore, and may totally
replaced by sub-resource migrations of server in the future.
This patch corrects the spec to add new fields into the
'/servers/{id}/migrations'. And clear the json-schema of new fields.
Also add new novaclient to the propose.
Also proposes adding the link to the old top-level resource
'/os-migrations', which also required add GET method for each migration
sub-resource of servers.
Partiail blueprint live-migration-progress-report
Change-Id: I6c2ed639cf8184466277c637d9e63982dde9ad84
https://blueprints.launchpad.net/nova/+spec/expose-host-capabilities
Ensuring proper scheduling can be difficult task, especially
when the instances require several host features or capabilities.
This would require the administrators to know what features are
available for a certain hypervisor version and / or creating
quite a few host aggregates, which can become tedious.
Implements: blueprint expose-host-capabilities
Change-Id: I7f31de7c5074561cbe2906c80d79ce8b825f1009
There was a valuable discussion in the review which I would like
to include in the approved spec for future reference.
Change-Id: Ifada0c71d9a77f0e34f371d6883e9f0f0b5f5866
Implements: blueprint libvirt-aio-mode
Zuul