Adding a new volume type extra-spec option 'vmware:adapter_type'
to override the default adapter type of volumes.
DocImpact
The VMDK driver now supports a new extra-spec option
'vmware:adapter_type' to override the default adapter
type specified by config option 'vmware_adapter_type'.
Change-Id: Ifc641d82e6eecbe12aa0e77242ce8555b7e57b76
Closes-bug: #1691285
Currently vmdk volumes are created with lsiLogic adapter.
The volume may not be recognized if the guest OS does not
support lsiLogic. Adding config option 'vmware_adapter_type'
to specify the default adapter type for new volumes.
DocImpact
Added new driver config option 'vmware_adapter_type' to
specify the default adapter type for new volumes created
by the VMware VMDK driver.
Partial-bug: #1691285
Change-Id: I2b923af59d51a8b0c94ef4e111d20958d44182b0
In attachment-delete we attempt a little short cut
in cases where the volume is reserved but not actually
attached to an instance. In this case we don't have a
connector and we never actually sent anything to the
driver, so we take a short cut in cinder.volume.api
and we just call an object.destroy().
The problem with this is that the object doesn't do
the proper/needed context settings and checks and just
fails due to policy. We should clean this up and add
the extra db update steps and also include the
notification messages.
Change-Id: Ib448f0548739cd42edf03eab07f305b3ac184d8f
Closes-Bug: #1702512
Commit 8f5e10d7ed8eead221cccb6a0ccf1afea310b0a9 wrongly assumed that
the "ignoreskipactivation" flag is not needed when using thin LVM
provisioning. This is wrong.
Using thin LVM leads now to an error when the content will be copied:
ERROR cinder.volume.manager Command: sudo cinder-rootwrap /etc/cinder/
rootwrap.conf dd if=/dev/mapper/cinder--volumes-_snapshot--UUID
of=/dev/mapper/cinder--volumes-volume--UUID
count=1073741824 bs=1M iflag=count_bytes conv=sparse
The reason is that the the snapshot is not activated and due to that,
no device node is available under /dev/mapper .
This reverts commit 8f5e10d7ed8eead221cccb6a0ccf1afea310b0a9 and makes
thin provisioning for LVM working again.
Change-Id: I788b297af92e11063b18c05a415b6f4d4d4bcd2c
Closes-Bug: #1702322
Related-Bug: #1701545
Once we'll get generic-backup-implementation blueprint done it will be
confusion to have 'delete' method in volume drivers. After this change
we'll have two methods: 'delete_volume' and 'delete_backup' which should
be clear for maintainers.
This patch doesn't change any public API so it should be clear for
operators and users.
Change-Id: I7f975066c1c848fec7e930a9d71b7225f3250acc
Related-blueprint: generic-backup-implementation
We don't use any advanced features of 'versionobjects.fields.Enum'
in message fields. We can directly use 'object' there.
Change-Id: I3e2a7f52c8348ff6b1fb82d849a26c650236e78c
Our cinder.conf.sample lists all of the options that are defined by
drivers in the [DEFAULT] section. Since removal of single-backend config
(without enabled_backends) this is misleading as those options are
functional only when defined in [<backend_name>] section. This commit
aims to move all of the driver options to [backend_defaults] section.
Assumption is that this will affect only sample config generation and
should not break anything else.
Change-Id: Ia4766eb313e15adc92a92875519b22db64e95d65
The SnapshotStatus and SnapshotStatusField have been defined already, This
change just replace the omissive snapshot status string with snapshot enum
field.
Follow up https://review.openstack.org/#/c/284825/
Change-Id: I175398bcad863eaead8b35095d7ff84f9f63aadb
Partial-Implements: bp cinder-object-fields
Logging in scheduler's filters have improved greatly over the years, but
there are still two code paths that exclude backends but don't log the
reason.
This patch adds debug log levels to those 2 paths so all exclusion code
paths will be covered.
TrivialFix
Change-Id: I57c773849200439713b18b61874dc33d8ee34390
when creating a volume with group_id, the driver need to look in the
group specs to see if the group is a cg or a regular generic group
Change-Id: I4e606d4b25251f7fdb56a1e2f76093a93f81a3b3
Closes-Bug: 1701231
Huawei Dorado array only supports 'Thin' lun type, this patch adds
the verification for user's configuration, and if user doesn't
specify this parameter, default use 'Thin' type.
Change-Id: Ie94e5e1106b1e5ea9063effcecddc2e30e8b4f92
Remove the codes in `create/remove_export_snapshot`. The code there
is designed for mounting snapshots for remotefs filesystems. It is
unnecessary in Unity.
Change-Id: Ib2dcba29ca4d97f77501fd0068499aad09984ad6
Closes-bug: 1701311
The GroupStatus and GroupStatusField have been defined already, This
change just replace the omissive group status string with group enum
field.
Change-Id: Ic9c43a3fa95901de7d68b0e23358e2a742a9901a
Partial-Implements: bp cinder-object-fields
Force detach sends None as connector which meens detach the volume from
all IG's. using volumes property "lun-mapping list" to get all IG
indexes.
Change-Id: I40cb1acaa4426d5f5bdf322cf665b4273e2fea7c
Closes-bug: #1700467
The Dot Hill driver is no longer supported by an independent CI, so
the driver was marked unsupported in the Ocata release, and is being
disabled in Pike. The driver code remains in place since it's
subclassed by other drivers (lenovo, hpmsa), but attempting to load
the dothill driver will throw an exception.
DocImpact: Remove description of Dot Hill AssuredSAN driver
UpgradeImpact: Dot Hill storage requires configuration of a new driver.
Change-Id: Ic2cec24ac33813cbce4c3166cc04f32ad3df6396
Updating the Datera Cinder driver to version 2.4.0 and implemented
the following features:
- Scalability bugfixes
- Volume Placement, ACL multi-attach bugfix
- Fast retype support
Change-Id: I7a742a8d7590f6a29e4cb24c57615ea94c79ee83
We were missing the context parameter... and apparently
never tested with cache limits enabled. This fixes
it and updates the unit tests to check for it too.
I'll follow up with a devstack patch to set some
limits by default too so we cover more of this
code and have it behave like a production deployment
in gate jobs.
Change-Id: Ia6d43b35843682bd201e57bb2941ca0243606412
Closes-Bug: #1701696
SVC Global Mirror with Change Volumes(gmcv) provides asynchronous
replication based on point-in-time copies of data. Two
properties: replication_type="<in> gmcv" and
drivers:cycle_period_seconds=500 in volume type to support replication
volume with gmcv. Here is an example to define a gmcv replication
type: openstack volume type set
--property replication_type="<in> gmcv"
--property replication_enabled='<is> True'
--property drivers:cycle_period_seconds=500
--property volume_backend_name=svc75 SVCGMCVReplicationType
DocImpact
Change-Id: I525f82dccf88bc085825523d7e899143e2190a96
Implements: blueprint gmcv-support-in-svc-driver
