Instead of referring to a specific network, refer to the appropriate
place in the OpenStack Contributor Guide where this info can be
found.
Change-Id: I4331dab740b241c7f6f69489892e753cb8c36f34
- add a link to make the release note info easier to find in the
contributor guide to increase the likelihood that people will
actually follow the standard format
- add some guidance about using past tense to describe fixes
- update the sample notes to reflect the above
Change-Id: Iddf0b3de4ba44f9b14d2e144097b51fd7a4ccf61
We have many issues with quota:
- Wrong values caused by race conditions
- Duplicated quota usage entries caused by race conditions
- Code that doesn't clean quota usage
Our current code has mechanisms to automatically refresh these values,
but there could be admins that don't want to enable it all the time, and
others that will be affected by bug #1697906 and cannot enable it.
There are a couple of scripts available online, but they all have their
issues: Not taking into account config option no_snapshot_gb_quota, not
fixing backups and groups, being racy, etc. Moreover, they are external
tools to the OpenStack community.
We will eventually fix quotas, but in the meantime we should provide a
tool to help administrators manage the situation.
This patch adds a new 'quota' category to cinder-manage and two actions
'check' and 'sync' to allow administrators to check and fix on demand
the status of quotas (for a single or all projects).
Related-Bug: #1869749
Related-Bug: #1847791
Related-Bug: #1733179
Related-Bug: #1877164
Related-Bug: #1484343
Change-Id: Ic9323f8cfd75c0fbc425ddc9c9b35959fbe7d482
Update min brick version to the wallaby brick release, and adjust
requirements files and lower constraints to accommodate the versions
of dependencies requested by os-brick 4.3.0.
Change-Id: I74b897a6ec27ca2ef00811fbbc2e6c43d31e307f
We've recently formalized some of the extra meetings we've been
having (for example, I325a998983dc and I16aceb82ba4f), so add them
to the new contributor doc.
Change-Id: Ic9befbd5e5f1740ce9725bbedd8695324d4c0b6f
Added support of authenticity verification through
self-signed certificates for JovianDSS data storage.
Added support of revert to snapshot functionality.
Expanded unit-test coverage for JovianDSS driver.
Change-Id: If0444fe479750dd79f3d3c3eb83b9d5c3e14053c
Implements: bp jdss-add-cert-and-snapshot-revert
This patch changes following items of the Zadara driver:
- Changing the code layout of the Zadara driver.
- Using json format
This patch adds some missing features to the Zadara driver:
- Volume manage and unmanage
- Snapshot manage and unmanage
- List manageable volumes and snapshots
- Multiattach
- IPv6
Change-Id: I787e9e40c882e6ab252e10c239778019acb2e6c6
Nova defaults to using the QEMU decryption layer
instead of cryptsetup now, and cryptsetup was never
needed on the compute for RBD encrypted volumes, so
this is not very useful advice.
Ref: https://review.opendev.org/c/openstack/nova/+/523958
Change-Id: Ib158ffa9543fcbf5bf1cc8bfbd42e1ca766bfa30
We keep seeing people concerned about data leakage and thorough deletion
of data from volumes on volume deletion [1][2], and Cinder currently
only worries about the data leakage, not the stealing of the physical
disks.
In order to clarify this for administrators and to reduce the number of
specs proposed to address this issue we are adding additional
documentation on security aspects as well as data leakage.
This patch was decided as an action from the discussion during the
Wallaby PTG [3].
[1]: https://review.opendev.org/#/c/758375/
[2]: https://review.opendev.org/#/c/759553/
[3]: https://wiki.openstack.org/wiki/CinderWallabyPTGSummary#Two_proposed_specs_on_the_same_topic_.28mutually_assured_destruction.29
Change-Id: I9f8d413cf8337e75241ad24c85692135b34a17fc
Implements: blueprint specify-data-secure-deletion
In python 3, all strings are considered as unicode string.
This patch drops the explicit unicode literal (u'...')
or (u"..") appearances from the unicode strings.
Change-Id: I5c4b0eb24ecade37c22e7777640466116a893a89
Cinder driver for PowerStore supports volumes/snapshots with
replication enabled according to OpenStack volume replication specification.
Implements: blueprint powerstore-replication-support
Change-Id: I94d089374dee76d401dc6cf83a9c594779e7eb3e
Add back-end QoS support for Pure Storage.
Two parameters are supported:
maxIOPS - maximum IOPS per volume - range 100 -100M
maxBWS - maximum I/O bandwidth in MB/s - range 1 - 524288
DocImpact
Implements: blueprint pure-backend-qos
Change-Id: I7f548b1aa1285499b5835fc2ebba3b6e55d8fb15
Updating the specs repo for the next release cycle isn't currently
listed in the release cycle tasks, so add it.
Change-Id: I8c9077d0ca1ebee047db4f7506ebdf2e3d1f1fc8
openstack-cinder in RDO victoria depends on python-cinder
which depends on:
python3-keystoneauth1 >= 3.14.0
python3-keystoneclient >= 1:3.15.0
python3-keystonemiddleware >= 4.21.0
closes-bug: #1916258
Change-Id: If772b29d7b59ca99c1f2796ff75ef846b3904875
Due to Fusionstorage rename to OceanStor 100D, there is a necessary
to support OceanStor 100D with Fusionstorage Cinder Driver.(dsware)
Change-Id: I10afd1fb781f8f3c933a2783723215654da31e00
Report SAN driver options:
Added configuration options(san_ip, san_ssh_port, san_login) to report on their specific "get_driver_options" method.
Abandon the target parameter:
The target parameter should not be required or used. Automatic adaptation when mapping.
This patch resolves the remaining issues with the target parameter and get_driver_options method in review [1].
[1]: https://review.opendev.org/c/openstack/cinder/+/767290
Change-Id: If127b75aac1ea6b25ec6473913410b1a7ec217d4
If there are some iSCSI or FC targets (ESXi for example) that
are not connected to the OpenStack host,
attach volume operation waits until timeout.
The XtremIO Cinder driver needs a new option to support ports
filtering.
Change-Id: I2a521118598de336148a56c1d5352107ece80721
Closes-Bug: #1915800
Last year, code changes were done to add Peer Persistence
support for the HPE 3PAR backend.
Change details: I2d0342adace69314bd159d3d6415a87ff29db562
The same code changes work for the newer HPE Primera backend.
This patch updates the documentation.
Change-Id: I0df55ee5548caa6f37522253ffa6f081000c78bb
