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
The display heads was designed as consumable resource; but actually
it's not. We will change to make it as vGPU's trait. This commit
is to reflect this change and also refine some sections to make the
document be rendered better.
Change-Id: I805e7e071384eddbd88e69fe90ab65024b5c0796
blueprint: vgpu-rocky
Upon implementation, the per-device configuration was deemed preferable
to adding yet more image metadata and flavor extra spec keys. Update the
spec to reflect this change.
Part of bp share-pci-between-numa-nodes
Change-Id: I503e0cd00325daa2f3286aad1e6a2beba7fc6cf9
* The minimum required Cinder API microversion that Nova
checks for is 3.44.
* The first TODO about disallowing a volume to be attached to
the same instance multiple times has been resolved by
change I049f00f993e45eeb090a1e1a5e5696cf2f103187.
* The second TODO about adding a new microversion is removed;
we added microversion 2.60 for multiattach volume support in nova.
Change-Id: I12efa58b95ba1a2f8615256924f4a7a44c354ced
During the review of I7e01f95d7173d9217f76e838b3ea71555151ef56
we made the decision to also add the migration uuid to the server
migrations GET responses to be consistent with the os-migrations
change to add the uuid to the response. This change simply amends
the spec to mention that change as well.
Part of blueprint add-pagination-and-change-since-for-migration-list
Change-Id: Icdd598d34748240a3ed9dade561f8f34857adbc3
Edit the Queens specification for bp nested-resource-providers to
reflect what actually got accomplished in Queens. See background
discussion in IRC [1]. Highlights of the delta:
- Remove/soften assertions about how NUMA and SR-IOV will be
implemented. None of this was done in Queens, and the vision of how
it will eventually be handled has evolved (particularly due to the
introduction of update_provider_tree [2]).
- Update the ?root={uuid} filter to its glorious new name,
?in_tree={uuid}, and more clearly document its behavior.
- Mention the future work needed in GET /allocation_candidates (series
starting at [3], Rocky spec to be proposed) and update_provider_tree
[2] to make this usable.
[1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2018-02-12.log.html#t2018-02-12T20:14:58
[2] https://review.openstack.org/#/c/540111
[3] https://review.openstack.org/#/c/531899
blueprint: nested-resource-providers
Change-Id: I3d8194e5cf6d3b39878edad99fe0b17092129271
This moves the completed queens specs to the implemented
directory, adds the redirects and also removes the queens-template
symlink from the approved directory and docs.
This was done using:
$ tox -e move-implemented-specs -- queens
Change-Id: I9e4d9aec4a1ced181ef7850627b9c67de376beae
The py27 job was not executed
when Id7ed89a24ff6e2fd7ab4eee5b117cb6b6c763c44 was merged.
So fix the maximum length of the line.
Change-Id: I9953a8576942d394b91152a5fe221683d1057fb9
Closes-Bug: #1732581
The request and response bodies diverged when GET was implemented, this
spec provides a plan for fixing it and updating each of the following
accordingly
* PUT /allocation/{consumer_uuid} request body
* GET /allocation/{consumer_uuid} response body
* GET /allocation_candidates response body
Change-Id: Id7ed89a24ff6e2fd7ab4eee5b117cb6b6c763c44
Related-Bug: #1708204
Blueprint: symmetric-allocations
During implementation it was realized the spec never
considered the GET /flavors API. After talking with some
stakeholders it was agreed to add the description field
to the GET flavors response, since that's a more limited
list response that a user can then use to get more details
from the GET /flavor/{flavor_id} API.
Related to blueprint flavor-description
Change-Id: I730a2759dae68ad37abb336ca544511c4f84da96
- This spec addresses the consumption of neutron's
new port binding api in nova.
https://specs.openstack.org/openstack/neutron-specs/specs/pike/portbinding_information_for_nova.html
- This proposed change will modify nova to use multiple port binding
when performing actions that will move a VM between hosts.
e.g. live migration
Co-Authored-By: Sean Mooney <sean.k.mooney@intel.com>
blueprint neutron-new-port-binding-api
Change-Id: Ie776601d5966d14fea55d958c7407dd6b710df38
Currently, os-instance-actions API does not support pagination.
As in production deployment the number of instance action records
can be also very large query them all can lead to performance
bottleneck, it will be very useful to support pagination.
Also, os-instance-actions API does not support filter the instance
action record by last updated time. As for production deployment, an
instance can be up for a very long time, and the number of instance
action records will also be very big. It will be very useful to support
filter by last update time.
APIImpact
Previously-approved: newton
Co-Authored-By: Zhenyu Zheng <zhengzhengyu@huawei.com>
Change-Id: I3b7cd44fdad9a49022e086d6c4f54c7812f2027c
Implements: blueprint pagination-add-changes-since-for-instance-action-list
This spec describes changes that would allow Nova to perform
certificate validation when verifying Glance image signatures.
While image signing ensures that image data is obtained
unmodified from Glance, it does not prevent an attacker from
uploading and signing a malicious image. The addition of Nova
API changes allows Nova users to control the certificates
which are allowed to sign images.
This spec describes work related to image verification. For
more information, see: https://review.openstack.org/#/c/343654
APIImpact
Previously-approved: Pike
Change-Id: I121b2e7641c77a4872a1e801eb039050e6a996ea
The spec is describing the Nova side of the 'multiattach' feature.
The functionality targets to add support for attaching a Cinder
volume to multiple VM instances.
Change-Id: Ib0415add7cc92e94303f6494f1f0287848f27c98
Previously-approved: newton
Implements: blueprint multi-attach-volume
Currently, os-migrations API does not support pagination
and timestamp filtering. As for large scale production
deployment, the number of migration records can be very
big, it will be very useful to add pagination and time
stamp filtering support for os-migrations API.
APIImpact
Previously-approved: newton
Co-Authored-By: Zhenyu Zheng <zhengzhengyu@huawei.com>
Change-Id: If50f8de61dc9401f76ab442c96810f4245b571ac
Implements: blueprint add-pagination-and-change-since-for-migration-list
The performance of filtering instance by IP is poor, this is due to that
IP address is one part of the instance.network_info JSON, we have to
iterate one by one to find the instance that matches the request.
This spec propose to get filtered ports according to the provided IP
addresses from Neutron and retrieve the instance uuid from the
port.device_id first and then merge to the other filters as discussed
in the Queens PTG [1].
[1]http://lists.openstack.org/pipermail/openstack-dev/2017-September/122258.html
blueprint improve-filter-instances-by-ip-performance
Change-Id: I0d2f3c1bc16274da0cf013e862e4878e2fa8c1cc
As generic and nested resource providers begin to crystallize and be
exercised, it becomes necessary to be able to express:
- Requesting an allocation of a particular resource class with a
particular set of traits, and requesting a *different* allocation of
the *same* resource class with a *different* set of traits.
- Ensuring that requests of certain resources are allocated from the
same resource provider.
- The ability to spread allocations of effectively-identical resources
across multiple resource providers in situations of high saturation.
This specification attempts to address these requirements by way of a
numbered syntax on resource and trait keys in flavor extra_specs and the
GET /allocation_candidates Placement API.
APIImpact
blueprint: granular-resource-requests
Change-Id: I49fb16c0e080361e6754edc64754abde3a975e14