Description of problem: This RFE tracks the full support for the NVMe over TCP protocol in Cinder. The goal of this RFE is to make sure the protocol is properly implemented in the core components. RH will not ship any supported in-house driver. This RFE will allow partners to certify driver using NVMe over TCP. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The os-brick patches were ready and tested, but they need to be rebased and updated because the NVMe-oF Native multipathing will merge first ( https://review.opendev.org/c/openstack/os-brick/+/830800 ). This will make it harder to backport to 17, but it was already going to be a complicated backport and we want multipathing to be available before supporting it in OSP anyway. For testing the different os-brick code paths with the LVM driver I have a series of patches for Cinder as well: https://review.opendev.org/q/topic:lvm-nvmet-shared
Upstream patches: https://review.opendev.org/q/topic:nvme-4
The groundwork to support NVMe-oF is now available in os-brick. The combined patches to the LVM backend which allows it to support NVMe-oF were merged as well, and the usual tempest tests for volume do pass. openstack-cinder-18.2.2-1.20230411050850.109f91a.el9ost python-os-brick-4.3.4-1.20230128060810.cf69f92.el9ost openstack-tempest-33.0.0-1.20230406160852.1580f6f.el9ost python-cinder-tests-tempest-1.8.0-1.20230304051242.0e94611.el9ost
Updated the doc text to match the revised Top New Feature text.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577