Current Series Release Notes

15.0.0.0rc1-46

New Features

  • The LINSTOR Driver for Cinder now supports LINSTOR 0.9.12.

  • Fujitsu Driver: Added multiple pools support.

Upgrade Notes

  • The LINSTOR driver for Cinder supports LINSTOR 0.9.12. The driver supports LINSTOR backend using REST API.

    The new driver adds ‘linstor_autoplace_count’ configuration option that specifies the number of volume replicas.

  • SolidFire supports Synchronous, Asynchronous and SnapshotsOnly replication modes. This adds the config option solidfire:replication_mode to specify the mode to be used by Cinder. Its value can be Sync, Async or SnapshotsOnly.

  • The Virtuozzo driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it.

Deprecation Notes

  • The Virtuozzo driver has been marked as unsupported and is now deprecated. enable_unsupported_driver will need to be set to True in the driver’s section in cinder.conf to continue to use it. If its support status does not change, it will be removed in the ‘U’ development cycle.

Bug Fixes

  • An incorrect lock in the remotefs code, which is used for the NFS driver, and other similar drivers, resulted in concurrent clone volume operations failing. create_cloned_volume now locks on the source volume id, meaning multiple clone operations from the same source volume are serialized.

    A lock in the volume manager flow generally prevents this on normal clone volume operations, but this clone method in the driver is called for operations such as cloning from the cinder image-volume cache or cloning from a cinder backend used as a glance store.

  • The SolidFire replication was fixed. Several bugs were addressed (creating replicated volumes from snapshots, from volumes, retype a volume to a replicated type, managing a volume to a replicated type, correctly updating portal info on failover/failback and some minor other fixes). Closes bugs #1834013, #1751932.

  • This change fixes bug 1845483 - 3PAR: For Peer Persistence, add policy options in RCG. Following options are added after Remote Copy Group (RCG) is created: autoFailover, pathManagement, autoRecover