** Description changed: + [Impact] + * The Infinidat Cinder driver currently creates a volume from another + volume or a snapshot by mapping both objects and copying the data with + dd. Large clones take longer and consume host I/O and bandwidth even + when the storage system supports snapshot promotion. + * This feature backport uses snapshot promotion on InfuzeOS 8.1 or later + with InfiniSDK 250.0.0 or later to create independent volumes without + copying their contents. Older SDKs or storage systems retain the + existing generic data-copy path. + + [Test Plan] + * Use a Cinder deployment with an Infinidat backend, an InfuzeOS 8.1+ + array, InfiniSDK 250.0.0+, and a volume type mapped to that backend. + Record the installed Cinder and InfiniSDK versions. Create a 10 GiB + source volume of that type, attach it, write a recognizable data pattern, + verify it can be read, and detach it before taking a snapshot. + * Before installing the proposed package, create (a) a volume from the + source volume and (b) a volume from its snapshot, each of size 20 GiB. + Confirm that both contain the pattern and use the driver's generic + data-copy path (backend operation traces or Cinder logs). Record the + operation times as a baseline; timing alone is not proof of promotion. + * Install the proposed package and restart cinder-volume. Repeat both + create operations with new names. Confirm in the array's operation + history that each creates and promotes a writable child snapshot + rather than mapping devices and copying data. Both resulting volumes + must be independent, available, 20 GiB on the backend, and contain the + original pattern; deleting the source or its snapshot must not make + the cloned volumes unusable. Check that the source snapshot is intact. + + [Where problems could occur] + * This changes both create-from-snapshot and clone-from-volume paths for + Infinidat backends. Incorrect promotion or a premature cleanup could + leave a clone incomplete, corrupt its data, or affect the source + snapshot. Inherited size must be extended when the requested size is + larger than the source. + * Promoted objects inherit settings from their source; applying the wrong + provisioning, compression, QoS, metadata, or consistency-group setting + could change how clones behave or leave orphaned backend objects after + failure. The normal create-volume path also changes the provisioning + argument passed to InfiniSDK and needs regression coverage. + * Capability detection at driver startup could prevent existing backends + from initializing with older InfiniSDK versions, or mistakenly use + promotion on unsupported storage. If the fallback is broken, cloning on + those installations could fail rather than continuing to copy data. + + [Other Info] + * Upstream feature: https://review.opendev.org/c/openstack/cinder/+/940236 + * The upstream feature change alone requires InfiniSDK >= 250.0.0 even + for systems using generic data copy. Include the separate compatibility + fix https://review.opendev.org/c/openstack/cinder/+/1011532 + (LP: #2171540) in the proposed backport before upload; it restores + support for older SDKs. Give that fix its own bug reference in the + package changelog and verify both together. + * Because this introduces a new feature to a stable release, request the + applicable feature-SRU exception and identify the target Ubuntu/UCA + series before upload. This draft does not assert that the exception, + backports, or hardware validation have already been approved or done. + + + --- + + Improve Infinidat driver by: * Adding support for snapshot promote feature * Expanding unit-test coverage
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2174690 Title: Infinidat: add support for snapshot promote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/2174690/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
