Thanks Gorka for the detailed description. The LVM+nvmet changes certainly are a good candidate for FFE and adds value to our testing framework. Hence, I would like to grant FFE for the LVM+nvmet patches. On Mon, Feb 20, 2023 at 3:38 PM Gorka Eguileor <geguileo@redhat.com> wrote:
On 20/02, Rajat Dhasmana wrote:
Hello Argonauts,
We are past the feature freeze deadline i.e. 17 Feb, 2023[1]. If you have a feature which you would like to get it into the 2023.1 (Antelope) release, please request a feature freeze exception on the OpenStack discuss mailing list with the following subject: *[cinder] Request for Feature Freeze Exception* Include the patch details, reason for missing the feature freeze deadline and current status in the email.
The feature freeze exception will be granted for 1 week i.e. till 24th Feb, 2023 and no features will be accepted after that.
Following are the targeted features and their current status:
*Hitachi: support data deduplication and compression* Patch: https://review.opendev.org/c/openstack/cinder/+/850831 Status: Fix merge conflict and add unit test
*Add iSCSI export support to the StorPool driver* Patch: https://review.opendev.org/c/openstack/cinder/+/847536 Status: Has multiple negative votes with feedback that needs to be addressed
*[SVf] Adding support of clone operation for volumegroup* Patch: https://review.opendev.org/c/openstack/cinder/+/871257 Status: Has negative votes with feedback that needs to be addressed
*LVM NVMe Target* Topic: https://review.opendev.org/q/topic:lvm-nvmet-shared Status: Need confirmation that the patches are in a reviewable state
Hi Rajat,
Thanks for bringing this up.
I would like to request a FFE for the LVM+nvmet patches.
They had a small bug that was detected by the WIP tempest CI job which got fixed a while back, but I've been fighting the normal CI job with spurious errors since then.
Now they all have +1 from CI and are ready to merge.
These patches add new features to the LVM driver over NVMe-oF, like native multipathing and sharing targets. Thanks to those any developer will be able to work on the NVMe-oF os-brick code without needing a high end storage array, and we'll be able to have CI jobs that can exercise those code paths as well.
Cheers, Gorka.
[1] https://releases.openstack.org/antelope/schedule.html#a-ff
Thanks Rajat Dhasmana