openstack/nova-specs - nova-specs - OpenDev: Free Software Needs Free Tools

There are a few clarifications added based on the stein
spec review feedback: https://review.openstack.org/#/c/616037/
A known issue is added for personality files not being retained
in the config drive during a cross-cell resize.
A link to the code series is added in the References section
and the History section is updated for Train.
Details about the need to hard-delete the instance and its
related records is also added since the Stein spec.
Previously-approved: Stein
Spec for blueprint cross-cell-resize
Change-Id: I68498afd481f7291a6102928d7999b4be49ded7a

Updated footer to track reproposal, no other changes.
Blueprint: add-emulated-virtual-tpm
Previously-approved: Stein
Change-Id: I780f93fd0ca4740b8199c96315bbb5d9d3501b4b

This is useful for recording data during the cycle to use to create
a burndown chart for blueprints. The script counts: Targeted,
Approved, and Implemented blueprints. It also checks if there are any
approved specs whose corresponding blueprints need approval and emits
warnings for each one found.
Since this shares some code with the existing move_implemented_specs
script, the common code is factored out into an importable lib.py
module.
This also adds a tox target for running the script and makes it share
the same envdir as the move-implemented-specs target since both need
the same dependency of launchpadlib.
Change-Id: I9a9d3f7f2883a6eb151230da651d9a4c4fda77b4

There are multiple steps necessary here:
- Switch to openstackdocstheme which, unlike the EOL'd oslosphinx theme,
 supports Sphinx 2.0. This is mostly trivial, though we do need to set
 the 'release' and 'version' options to the empty string since specs,
 like release notes and API docs, are unversioned.
- Require yasfb 0.8.0, which adds support for Sphinx 2.0
- Remove configuration for configuration for the 'autodoc' extension,
 any builder that isn't HTML or LaTeX, or stuff that duplicates
 defaults. All of these were noise that was simply confusing matters.
Change-Id: I111f5e2b0314b35bdde3e00f7615a380734bc2aa

Blueprint: request-filter-image-types
Change-Id: I5a25a48d110034aa25c07c0fa0f35b4768c934ab

updated footer to track reporposal no other changes
Blueprint: libvirt-neutron-sriov-livemigration
Previously-approved: Stein
Change-Id: I4c58ee6553c173cde567e6cc9551eb0c0c42930f

This change simply forward ports the spec to train
and updates the spec history footer to reflect this.
Blueprint: numa-aware-live-migration
Previously-approved: Stein
Change-Id: I5b876fcdc7cf616594ef46d703d2fd6c02765797

* Fix warnings when executing 'tox -e docs'.
* Fix consistency for expressions of REST APIs.
* Remove 'json' in some code-blocks
 because the contents include comments
 so they are not in accordance with JSON format.
* Add the '-W' option in the sphinx-build command
 for the docs target.
Change-Id: Iaaa4e2444030622539a61055e114a649466be497

This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
 http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ia9081a1f0249a7a8b863093faa0f0b05f27cbb85

This moves the completed Stein specs to the implemented directory and
adds the redirects. This was done using:
 $ tox -e move-implemented-specs stein
This also removes the stein-template symlink from the docs.
And renames the handling-down-cell_new.rst spec to handling-down-cell.rst
to match the blueprint.
Change-Id: Id92bec8c5a2436a4053765f735d252c7c165f019

Previously-approved: Stein
Change-Id: I7d7a88201451a2525eed85531b59436f2e8f0889

The spec is updated based on what was implemented during the Stein
cycle.
Change-Id: I52424adf73756823aee81a1a32329f6c8f131c22
blueprint: bandwidth-resource-provider

"Filter Allocation Candidates by Provider Tree" spec has been approved
proposing the new "in_tree" queryparm, but it didn't address how it
works with the granular requests using "in_tree<N>" syntax.
This patch updates the spec to clear it out.
Change-Id: I2726b1b1a632ef3627af872c150ed6564e65b108
Blueprint: alloc-candidates-in-tree

This is a followup that addresses comments from change
Ib86a7994d7a577b8e6a2dd32f4fcf12b7f788af8 and fixes the code block
formatting for a pseudocode section.
Related to blueprint count-quota-usage-from-placement
Change-Id: I7c9e490a2f614c5ea6f85d2ed70fa35dd0c81417

As discussed in Berlin Summit, there are some
considerations should be added to the design:
1. Expose ``boot_index`` in this feature could
make it easier for users to detach and attach
volumes[1].
2. As discussed in Maillist[2], we are not going
to allow detach/attach volumes for instance in
states other than STOPPED,SHELVED/SHELVE_OFFLOADED
so we make it clear in the spec.
[1] https://etherpad.openstack.org/p/BER-bfv-improvements
[2] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001344.html
Change-Id: I0a03d4840e83cd01f3d546ed0517105dcb6e5328

Change-Id: I4225e37b889bf1a26d6d3ba197e524d3863c472e

- This change introduces a spec to describe
 extension of the nova libvirt driver to
 support live migration of guests with
 SR-IOV interfaces.
blueprint libvirt-neutron-sriov-livemigration
Change-Id: Ic2650ec51f9f97f3db3dbda049863ce2c538af34

This spec present server group info to user in server show API.
APIImpact
Change-Id: I9dceba013f643925aac8e09d95b1306bcb3c4434
bp: show-server-group

This spec present numa information in server diagnostic API.
APIImpact
Change-Id: I36872473a569f3c8bb0f835d0e2c725c7764d69c
bp: show-server-numa-topology

blueprint: flavor-extra-spec-image-property-validation
Change-Id: I25992fd699bfecb867ae412006be94ef658e115a
Signed-off-by: Jack Ding <jack.ding@windriver.com>

SmartNICs allow complex packet processing on the NIC. In order to
support hardware acceleration for them, Nova core needs modifications
to support the combination of VIF and vRouter plugging they support.
This spec proposes a hybrid SR-IOV and vRouter model to enable
acceleration.
Change-Id: If4c2795d33dbd701582bfb8ea5aa4b14f4e69341
Signed-off-by: Jan Gutter <jan.gutter@netronome.com>
blueprint: vrouter-hw-offloads

Add support for providing unique per-instance serial numbers to servers.
Spec for blueprint per-instance-libvirt-sysinfo-serial
Change-Id: I819b888e5c6cae8fc8898489815dbe2254d33fe7

In Pike, we re-architected the quota system to count actual resource
usage instead of using reservations and tracking quota usages in a
separate database table. We're counting resources like instances, CPU,
and RAM by querying each cell database and aggregating the results per
project and per user. This approach is susceptible to undesirable
behavior if a cell becomes unavailable. If a cell becomes unavailable,
resources in its database cannot be counted and will not be included in
resource usage until the cell returns. Cells could become unavailable
if an operator is performing maintenance on a cell or if a cell
database is experiencing problems and we cannot connect to it.
We can make resource usage counting for quotas resilient to temporary
cell outages by querying placement and the API database for resource
usage instead of reading separate cell databases.
Spec for blueprint count-quota-usage-from-placement
Change-Id: Ib86a7994d7a577b8e6a2dd32f4fcf12b7f788af8

Expand resize (cold migration) support across multiple cells.
Spec for blueprint cross-cell-resize
Change-Id: I3f89324f1876e3313e8dce73057f7aed0396e432

The AMD SEV spec was just merged, but there were a few minor nits
outstanding, so address them here.
blueprint: amd-sev-libvirt-support
Change-Id: I93840aa852b837c03ede9e21e720c1e1c1c773f2

Currently we uses cpu_model in nova.conf (when cpu_mode is set to
‘custom’) to specify the CPU model the instance should use on this host.
This could have implications on availability of compute nodes for live
migration if you ended up with an "advanced" CPU model when all you
really cared about was an older feature flag.
To mitigate the problem , we use cpu_models to replace cpu_model, where
cpu_models is an ordered list of CPU models the host supports. The list
is ordered so that the more common and less advanced CPU models are
listed earlier. End users specify CPU features they required through
traits, libvirt driver then select the first one in the list that can
provide the required feature traits. This would make it more likely that
the instance could be live-migrated later on.
blueprint: cpu-model-selection
Change-Id: I546230ac115eb3de14eac25b9dd0c74aafdaccd5
Signed-off-by: Jack Ding <jack.ding@windriver.com>