We're into the 2024.1 cycle now with a few 2023.2 specs remaining to be
reproposed. There were no specs approved for the 2023.1 release cycle,
this patch just makes an explicit note of that.
Change-Id: I49e80c36dc12157d7b074995571fcb718f109579
This is a reproposal of a previously merged spec in the Zed cycle[1].
We have had a long history of quotas going out of sync. This spec proposes
to fix the problem by introducing 2 new quota drivers:
1. Counting: Dynamically counting the resources
2. Counters: Store reserved and in-use quota values in DB and use it
[1] https://specs.openstack.org/openstack/cinder-specs/specs/zed/quota-system.html
Implements: blueprint count-resource-to-check-quota
Change-Id: Ic4c97e46553e94f57e3f8e22f7cd65d7464a34f8
The arguments that the Cinder CLI takes are reversed
from what this doc currently states.
$ cinder --os-volume-api-version 3.62 default-type-set
usage: cinder default-type-set <volume_type> <project_id>
error: the following arguments are required: <volume_type>, <project_id>
Change-Id: I72df8ed5b1d805e0596ba3d13ce28b29accedcae
This also involves splitting up of the backup status away from
the volume status. The change is intened to allow for less serialization
or blocking of volume actions such as attachments, resizing, ... by
backup tasks.
Co-Author: Niklas Schwarz <niklas.schwarz@inovex.de>
Change-Id: I43a9fb73150e3738554459a459d63b8891418ad0
This spec proposes a new volume action that can be used by Nova to
notify Cinder on success or failure when handling "volume-extended"
external server events.
The new volume action is used add support for extending attached volumes
to the NFS, NetApp NFS, Powerstore NFS, and Quobyte volume drivers.
Blueprint: extend-volume-completion-action
Change-Id: Iffe5e0e05287d57b27227d66864ee226424b5cd4
Cinder quotas have been a constant pain for operators and cloud users.
This spec proposes a new quota system to resolve inconsistencies in
tracking quota usage.
This spec proposes reduce the usage of the reservations to a minimum and
have 2 quota drivers, one that leverages the DB engine to dynamically
count resources and another that stores the in-use and reserved counters
in the DB similarly to what we do today.
Change-Id: I3773be238a9edfc971d2b81135b23abfd3c974d7
Implements: blueprint count-resource-to-check-quota
This spec outlines the addition of the get pools API response
to return the new calculated capacity factors.
Change-Id: I8308f5bfcd332a5fd981a16bd1e537040c5c4709
This spec was approved for Train first and its approved status has been
carried along through Yoga. We propose it for Zed again.
Change-Id: Ic038fd8b97e265285678c299ef25fd812e5709a0
For the reference style used in this spec, each reference needs
to separated by a blank line or they are all rendered together in
a single paragraph. (Alternatively, they could be included in an
ordered or unordered list, according to taste.)
Change-Id: I313a16f1615b6253432f3fdbdfa0b5d5eb56bf1f
With the release of Sphinx 4.4.0 this highlighed issues with duplicate
labels across multiple specs.
This patch fixes all the duplicate labels.
Change-Id: I9baf7c51e2fe9c397feae05a975ddecae7dceba8
The initial spec was a bit optimistic about how much would be
accomplished in Xena. Additionally, this initiative has been
formalized as a multi-cycle community goal and the direction of
the effort has been revised and expanded. So update the Xena
spec to reflect what was actually done in Xena, and add a new
spec for the continuation of this work in Yoga.
Change-Id: If6c289d6957bd739ed893f01519441e6039a7d00
This patch adds the spec for optimizing the path when we are
uploading a volume from RBD backend to glance RBD store.
Implements: blueprint optimize-upload-volume-to-rbd-store
Change-Id: I7bfc41b9594b8b7fbc6228973c3c276aa1cf5427
This patch adds the spec for reimage feature which enables the
functionality to rebuild a volume backed instance.
Implements: blueprint add-volume-re-image-api
Change-Id: I067d113cacaf9a4d9e6a7f4d7ed1e0dfcc3ae509
The team working on this effort has scaled it back to remove a
dependency that's been holding up development [0]. This change
has no impact on the current Cinder spec, which was approved
for Train, and whose approved status has been carried along through
Xena. It's now proposed for Yoga.
[0] https://review.opendev.org/c/openstack/glance-specs/+/792134
Change-Id: Ie483be9e82031d8c89dd49c8159373d769e5037d
Move unimplemented wallaby specs to xena and set up http redirects
so that the old URLs won't 404.
Change-Id: Ic7aa7e45ed9e6f09f72a87034cd0b88d1390117b
so that regular users can know the abstract back end
independent capabilities and features in volume types.
Implements: https://blueprints.launchpad.net/cinder/+spec/expose-user-visible-extra-specs
APIImpact
DocImpact
Co-Authored-By: Tom Barron <tpb@dyncloud.net>
Co-Authored-By: Alan Bishop <abishop@redhat.com>
Change-Id: Id236326dca9ee08aad8427ea6cb400e25e7ac09e
This spec proposes a way to easily track which volumes and snapshots are
temporary and should not be considered when updating the usage quota.
Change-Id: I0a3f5836641dec535c2d2bf49cbf3a435faa8224
Implements: blueprint temp-resources
Jon Bernard