Per change I613b48a9e89270b2f0266bffc5aeeefad37ce8fb encryption
is not supported with multiattach-capable volumes.
Change-Id: Ife204c380a9d3d12938a907dee6d93d01aaec0ce
Related-Bug: #1770689
There was a mistake in an earlier patch where
'snapshot' was used instead of 'volume'. This
follow-up patch corrects the wording.
Change-Id: Ib1a03521c277c12d1b7f1c91eb1f2df1972e883f
The new Lenovo storage systems should be branded as
DS-Series systems. This patch corrects the documentation
accordingly.
Change-Id: I2ff8d321c97b70744037f60fee632e9d9b9dc383
The option 'allow_inuse_volume_type_modification' is
introduced as a bridge to not break upgrades without
notice. It is introduced in Ocata release [1], so it
is time to remove this option.
[1] https://review.openstack.org/#/c/440680/
Change-Id: I8c61b11994c1f8f571e65cefe4965f7d69b13100
Change If1e34ea112b0cff328a58ec2fc9c3f5a5005f1c6 renamed the Google
backup driver, but the configuration docs for the driver were not
updated. This results in the incorrect driver name being provided
for backup driver configuration and local document builds failing
due to no configuration options being found when looking for them
in the old location.
Change-Id: I40fa544892ed9ea9fb5975baeafb7c9a7e2f12a3
Add user messages for these cases below when performing
extend volume operation.
1. When no valid host is found.
2. When nova failed to perform extend volume event.
3. When backend failed to extend block device.
Change-Id: I7d2061ac13b2c74745da56feecfe6ed53b284fc4
Closes-Bug: #1773833
The DataCore drivers have not run 3rd Party CI
in more than 60 days. This patch marks them
unsupported and they will be removed in Stein
if the 3rd Party CI Issues are not resolved.
Change-Id: Id0f7ff5c1e8d0973941c9635558a6bd9d2204aea
This patch adds jsonschema validation for below volume type
encryption API's:
* POST /v3/{project_id}/types/{volume_type_id}/encryption
* PUT /v3/{project_id}/types/{volume_type_id}/encryption/{encryption_id}
Partial-Implements: bp json-schema-validation
Change-Id: I6488cc89e60a31605ddf80c7aa56ddf4871d3c1a
If a volume snapshot failed during create, it may exist in the database
but not on the ZFSSA. This change allows deletion of such a snapshot.
It also cleans up some redundant code for getting snapshot details.
Change-Id: I522fb0841dfaeb31da3999d3f73a2c9398c5b9c8
Closes-Bug: 1774066
We have released new S-Series storage models since we
originally created the documentation. This patch updates
the documentation accordingly.
Change-Id: Ida18d451b2e15f1d57fe4e1ffef393de20cc8828
The Cinder code that processes Glance image metadata
is a bit confused about whether this particular field
is a Glance property or metadata.
Since it isn't a defined a Glance property and is stored
in image metadata, ensure that Cinder also tracks it
metadata and not as a property.
This mismatch prior to this fix causes Cinder to create
volumes with the wrong encryption key when creating a
volume from an encrypted image, which results in an
unreadable volume.
Closes-Bug: #1764125
Change-Id: Ie5af3703eaa82d23b50127f611235d86e4104369
TrivialFix:
_static folder and the inside files are auto generated
when running docs, _ga is unused, so remove these.
Change-Id: I43b8cff826a98329607eed65a75eaf1ebaf54646
"backup_gigabytes" and "per_volume_gigabytes" parameters
are supported in api v2, they aren't mentioned in api v2
document[1]. On the other hand both of them are mentioned
in api v3 document[2].
[1] https://developer.openstack.org/api-ref/block-storage/
v2/index.html#update-quotas
[2] https://developer.openstack.org/api-ref/block-storage/
v3/index.html?highlight=backup_gigabytes#update-quotas
-for-a-project
Change-Id: I135efd5c2b4735f5821922643926390976453bf5
Closes-bug: #1727631
This patch adds jsonschema validation for below admin_actions API's
* POST /v3/{project_id}/volumes/{volume_id}/action
* POST /v3/{project_id}/snapshots/{snapshot_id}/action
* POST /v3/{project_id}/backups/{backup_id}/action
Partial-Implements: bp json-schema-validation
Change-Id: Ib9057fe57c1b9cdcd0d924b029f03da3589507a2
Show v3 API version details should not return informations about v2,
meanwhile location is not in Response Parameters.
Change-Id: Ida12222b3bdac10d030d56b9724f09ee097c0b3c
In current implementation, Unity driver doesn't return the targets which
connect to the logged-out initiators, which causes the zone manager
fails to clean up the FC zone.
The fix returns all the targets of specified initiators no matter they
are logged in or not.
Change-Id: I1438d0bd4a43e1813dfb0a6e9b3c4a177c2fee8f
Closes-bug: #1773305
With newer versions of sqlite tests are failing
on sqlite3.OperationalError : Cannot add a column with
non-constant default. In SQL queries is boolean without
apostrophes which causes sqlite3 error. This fix is
solving this issue by replacing text('false') to
expression.false() from sqlalchemy.sql which is
working correct.
Change-Id: Ia96255a2a61994a18b21acc235931ad03a8501ea
Closes-Bug: #1773123
This commit updates the author in the latex build metadata in the sphinx
conf.py. This was set to Anso Labs, LLC from the initial fork out of
Nova in 2012. It's highly unlikely that an LLC acquired by Rackspace in
2011 is actually the author of the latex version of the docs so this
commit changes it to be "Cinder Contributors" to be accurate.
Change-Id: I5f1f7ea2f389783fe8b936d67d0ab99d759c4124
There are two changes here:
1. Fix the formatting on the note for configuring
nova-compute to comment out the fixed_key (note
that I'm not sure why this is even in here)
2. Add a note that the --device specified to attach
the volume to the server might not reflect where
it actually shows up in the guest, especially since
the libvirt driver completely ignores what the user
specified.
Change-Id: I5f9870d46b7f49cc45d46f5794d8ee0c1bc4a1e2
With the addition of the hostname validation check for Rocky release,
the regex used does not allow for '+' to be used in a hostname. This
breaks the Dell EMC VMAX driver as + symbols are used in constructing
host/pool names. To resolve this issue, add '+' to the regex string.
Change-Id: Ib58741bcf5b1abe7196e9b2ad37d849776b17fbe
Closes-Bug: #1772659