This patch adds a snapshot clean operation in the
cleanup_incomplete_backup_operations process of c-bak.
Co-Authored-by: Christian Rohmann <christian.rohmann@inovex.de>
Closes-Bug: #1938488
Change-Id: Ifa3d572139fc37c94e3b50a02e61c9818a1b6501
This change is to update the live migration ability in environments
using PowerMax. In previous 2023.1 version, the live migration fails
without a pool name.
The update adds the ability of live migration without a pool name.
Change-Id: Iad767cd516c8527136508470629236f68e0c7cc2
Closes-Bug: #2034937
Dell PowerMax SnapVx unlink fails as the linked device
is not yet fully defined.
This patch fixed the issue by checking the new configuration
'snapvx_unlink_symforce' and the linked device 'defined' status
to determine the value of 'symforce' in the payload of
SnapVx unlink restcall.
Closes-Bug: #2045230
Change-Id: I614f6aef2d4da76c417b4a143ab80e4a5f716dcd
Two possibilities of clone volume:
1] same size, online copy
Existing behaviour: start clone & return from function.
Error occur because clone is not yet complete and
code tries to create vol on secondary array.
2] size is different, offline copy
Existing behaviour: (i) create new replicated vol.
(ii) during clone operation below error occur:
Volume is involved in remote copy
(iii) Since clone operation fails, delete new replicated vol (as cleanup).
To overcome both possibilities, code changes are done.
For clone of replicated vol, create offline copy only.
Steps:
(i) Create new vol without replication.
(ii) Perform clone operation; wait till completion (offline copy).
(iii) Create vol on secondary array.
Closes-Bug: #2021941
Change-Id: I1f025542a2509e36919ece01b29064377dbbe189
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I4311c34b40838da8ecc48802091908f08bf6f48f
The stable/victoria and stable/wallaby branches have been deleted,
so reno can't find their release notes. Use the victoria-eom and
wallaby-eom tags to indicate the end of the
Cinder project's maintenance of these series.
Also fix our override for the reno closed_branch_tag_re to include
the -eom tags. Add the changed reno.yaml file to all relevant
irrelevant-files lists.
This strategy is what we used for the yoga transition, and was
discussed at a cinder weekly meeting:
https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2024-02-07.log.html#t2024-02-07T14:06:09
Change-Id: I505b7cc12888d2373a0550b40bb945d75bb11067
The following three volume drivers are no longer supported, because
the storage products are now EOL[1].
- Dell SC Series Storage Driver (iSCSI, FC)
- Dell VNX Storage Driver (FC, iSCSI)
- Dell XtremeIO Storage Driver (iSCSI, FC)
This change marks these drivers unsupported, so that we can remove
these drivers after 2024.1 release.
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/7D7GUOI66BOD7Z3ZQWPWYYHH6VHAY4JJ/
Change-Id: I763278ec72adaf6f2ddd21edbfc687ca2f17f09a
Space allocation is an important NetApp driver specific feature.
This needs to be set when the cinder volume is created.
This is not related to thin/thick provisioning feature of cinder
volumes.It is independent of that. It enables ONTAP to reclaim
space automatically when host deletes data.This helps ONTAP
and host to see the actual space correctly when the host
deletes data.
It also helps to keep a LUN (cinder volume) online when the
LUN (cinder volume) in ontap runs out of space and containing
volume (in ONTAP) cannot automatically grow more space.
User can configure it by using volume type extra spec.
By default Space allocation value is disabled for ONTAP LUN
netapp:space_allocation: "<is> True" # to enable space allocation
netapp:space_allocation: "<is> False" # to disable space allocation
Blueprint: netapp-space-allocation-support
Change-Id: Ib7072f3093067ecd8ad84e396aaecec8f15c49ba
Add volume type extra spec boolean property
'powermax:disable_protected_snap'. Enabled when set to: `'<is> True'`,
`'True'`, `'true'`, or True, otherwise the property is disabled by
default.
When set to True, snapshot won't be replicated and won't
match the source volume type, it will be a regular device
no matter what.
If the property is not enabled in the volume type extra_specs, then
there is no change from the current behavior.
Implements blueprint powermax-protected-snap-config
Change-Id: Iafa44dcf0e8f46749b5ef37f0b8d341e8253a3bd
An apostrophe was in place of a backtick, and as a result the
hyperlink to the LP bug didn't display as a hyperlink.
Change-Id: I42867de19c35255f275f47eb78062130f5756cab
Added connect and read timeout into rest API call
of PowerFlex to avoid cinder hang issue.
Deafult value of connect and read timeout
is 30 seconds.
Closes-Bug: #2052995
Change-Id: I032d76627466f74121e3dc4fb2c8e175d830fa14
Added connect and read timeout into rest API call
of PowerMax to avoid cinder hang issue.
Deafult value of connect and read timeout
is 30 seconds.
Closes-Bug: #2051830
Change-Id: I2d419b4257bae75c69577a34758910c4889e2507
Split off the finalization part of the volume manager's
extend_volume method and make it externally callable as the new
os-extend_volume_completion admin volume action.
This is the first part of a feature that will allow volume drivers
to rely on feedback from Nova when extending attached volumes,
allowing e.g. NFS-based drivers to support online extend.
See the linked blueprint for details.
Implements: bp extend-volume-completion-action
Change-Id: I4aaa5da1ad67a948102c498483de318bd245d86b
Provide major rework of Open-E JovianDSS driver that involves:
- improve performance of volume and snapshot creation and deletion
- remove revert to snapshot support
- improve storage net interface picking algorithm
Change-Id: Ifc2aa5d3622315ae5c70b2d8e809e1b1553684ea
Implements: blueprint open-e-joviandss-iscsi-rework
The stable/yoga branch has been deleted, so reno can't find its
release notes. Use the yoga-eom tag to indicate the end of the
Cinder project's maintenance of the Yoga series.
Change-Id: Ic7b9cdac4dd52a9be0f3e9f35ae5087bcc83e323
Fixes an issue introduced by change Ie9561eeb30a54539cbd, which added
support for PowerMax Unisphere 10.
Closes-bug: #2051828
Change-Id: Ib66688f319d6aed5d7339f4eabdd7ca9ce7e0f6c
Logs show deprecation warning in the logs when creating backups.
Warnings are related to the "backups" and "backup_gigabytes" quota
resources:
Deprecated: Default quota for resource: backups is set by the default
quota flag: quota_backups, it is now deprecated. Please use the
default quota class for default quota.
Deprecated: Default quota for resource: backup_gigabytes is set by the
default quota flag: quota_backup_gigabytes, it is now deprecated.
Please use the default quota class for default quota.
This warning is shown because the ``quota_classes`` table doesn't have
entries for these 2 resources for the "default" quota class.
This patch adds a database migration to create the ``backups`` and
``backup_gigabytes`` entries in the ``quota_classes`` table like we have
for the other standard resources, such as ``volumes``, ``gigabytes``,
etc.
Closes-Bug: #1952420
Change-Id: I2a83e9b23f40a8ef4a734b456e4b7afb1ad65f94
Zuul
OpenStack Release Bot