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

As we discussed in the pre-PTG ML thread and on the PTG[2] we don't see too
much value keeping the Feature Liaison mandatory in the spec but we keep
it as an optional way for new contributors to declare that they would like
to be mentored.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014917.html
[2] https://etherpad.opendev.org/p/nova-victoria-ptg
Change-Id: I3769eb16fe396404113eba75a64d86e6b3d86f81

This spec adds details on the changes needed to allow nova the ability
to download Glance images into the libvirt image cache via a direct RBD
download instead of over the Glance HTTP API.
Change-Id: Icfcdf203ccce16f417ae043d71381f344e0feaaa
Blueprint: nova-image-download-via-rbd

This patch updates the histroy and re-proposes
the spec for the victoria cycle.
Change-Id: I93d78fff517c49d76059b2dea6acac5e2a86f40c

The feature aims at providing a safer remote console with password
authentication. End users can set console password for their instances.
Any user trying to access the password-encrypted console of instance
will get a locked window from web console prompting for ``password``
input, and this provides almost the same experience as using VNC clients
(e.g vncviewer) to access vnc servers that require password
authentication.
Previously-Approved: Ussuri
Partially-Implements: blueprint nova-support-webvnc-with-password-anthentication
Change-Id: I09a2aeb1c1b0c26ea22bd668e582f53f22252325

This is a proposal to configure resource provider visibility, ownership,
inventory, trait, and aggregate settings using a standardized YAML file format.
This was previously approved in Train [1] and Ussuri[2] but did not make
it into the release.
[1] http://specs.openstack.org/openstack/nova-specs/specs/train/approved/provider-config-file.html
[2] https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/provider-config-file.html
Previously-approved: Train, Ussuri
Blueprint: provider-config-file
Change-Id: I24e67e3776d83ec1ac29f336b8392b1883d8934d

This patch moves all specs that were implmented
in the ussuri release and sets up the redirects accordingly.
Change-Id: I7eddfab1d3b6aa5a23f47b6d8966760ca5648faa

We'd like to propose a way to create instance to
take using of PCPU and VCPU resource in one instance.
Re-proposed in victoria.
Change-Id: Ic75c41fc1d19d5a8bd74d820624935e3ccff703f

As talked in [1], using PUT (update a volume attachmet API) instead of using
PATCH to update attached volume.
[1]https://review.opendev.org/#/c/693828/19/nova/api/openstack/wsgi.py@54
Blueprint: destroy-instance-with-datavolume
Change-Id: I319c2b7e90874820fb98736701398b9466d754c3

This patch moves all specs that were implmented in
the train release and set up the redirects accordingly.
Change-Id: Id4b17e07f2d37cdcd789f4407b7bddd1008a23c1

Co-Authored-By: Takashi Natsume <takanattie@gmail.com>
Change-Id: Ie6688d8947c2a25de2a919b28bd26b5aef187796

https://review.opendev.org/#/c/712697/ completed this NOTE,
so we should remove it from this spec.
Part of blueprint action-event-fault-details
Change-Id: Iff32702fb4b372fac2a37c19d685e89928d7cb4d

This blueprint proposes to allow changing the ``deleted_on_termination``
attribute of a volume after an instance is booted.
APIImpact
Blueprint: destroy-instance-with-datavolume
Change-Id: If06bd29a8fcad322aed337bb7fdb54aae304c8dc

To make our tooling happier, make the spec's file name match the
blueprint name. Include a redirect to not break links in the wild.
Change-Id: I707409ba1cc668bb7e67c16a1eb7e848a5033625
blueprint: support-live-migration-with-virtual-persistent-memory

Fixed minor suggestions given on [1].
[1] https://review.opendev.org/#/c/641210/
Blueprint: support-glance-multiple-backend
Change-Id: I5d689d3edaa118f1a0defd63ac375a83b9ee553a

Some follow-up patch given some comments in the last version.
Change-Id: I2ce6b82b464ac2b3a563f4a197164bbecc38b318

Spec for explaining the relationship between a root RP and
and one or more Non-Uniform Memory Access (NUMA) nodes (aka. cells)
Spec-for: blueprint numa-topology-with-rps
Change-Id: I0c804743db77da5717c9c37e3c5ba57a9a3950ad

The feature aims at providing a safer remote console with password
authentication. End users can set console password for their instances.
Any user trying to access the password-encrypted console of instance
will get a locked window from web console prompting for ``password``
input, and this provides almost the same experience as using VNC clients
(e.g vncviewer) to access vnc servers that require password
authentication.
Blueprint: nova-support-webvnc-with-password-anthentication
Related-bug: #1447679
Change-Id: I8416ceb88b9e9e6498a81c678944bc5d96700fc3

Use fast NVME SSD or persistent memory to cache for slow remote volumes
Depends-On: https://review.opendev.org/#/c/684556/
Change-Id: I5ed7626ad5c45514bcdedaf1625778e2380b3cac
Blueprint: support-volume-local-cache
Signed-off-by: Liang Fang <liang.a.fang@intel.com>

Add support for Keystone's Unified Limits in Nova.
blueprint unified-limits-nova
Change-Id: I33301cbb02941d8498c17fb19ea07f0c0cae0bfc

We'd like to propose a way to create instance to
take using of PCPU and VCPU resource in one instance.
Re-proposed in U release.
Change-Id: I0c4ffe349dc9381c83c836efb4af99d072169c88

Previously-approved: Train
Blueprint: allow-secure-boot-for-qemu-kvm-guests
Change-Id: I158080dab789de6acd06a8f73fd3bc6b72523a52
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>

Change-Id: I637665f0b05a863f31255274f6b96f3a58d5afa4

Some follow-ups.
Change-Id: I95b6a3470e78ceaa05d556a9909746fbe89f05f6
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

Previously known as the (rather lengthy)
'flavor-extra-spec-image-property-validation-extended' spec.
Part of bp flavor-extra-spec-validators
Change-Id: I1b3b74f1fd2af9419f7aa0c79b5dad5b26065b57
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

Many instances filter are restricted to admin-only users, while the
related attribute are readable when showing instance detail for non
admin users.
In order to stay coherent, all existing instance filters who are
related to a field readable by default to non admin users when showing
instance details, should be allowed by default without policy
modification.
APIImpact
Change-Id: I288e4a2bd12702a1e7f7ebed544c95eb4a40e641
Implements: blueprint non-admin-filter-instance-by-az