| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
Breaking Change: NetApp NVMe Subsystem Architecture Redesign |
| 5 |
|
| 6 |
Implemented a significant architectural change to NVMe volume attachment |
| 7 |
handling to address critical limitations with multi-attach workflows and |
| 8 |
QoS management. The previous implementation used a one-to-one mapping |
| 9 |
between hosts and subsystems, where each host would have its own |
| 10 |
dedicated subsystem, and multiple subsystems would map to a single |
| 11 |
namespace. This approach created two major issues: |
| 12 |
|
| 13 |
* QoS Limitations: Since QoS policies are applied at the subsystem |
| 14 |
level rather than the namespace level, having multiple subsystems |
| 15 |
per namespace made it impossible to enforce consistent QoS across |
| 16 |
all host connections to the same volume. |
| 17 |
|
| 18 |
* Multi-Attach Incompatibility: Different subsystems cannot enable |
| 19 |
true multi-attach functionality, which is essential for live migration |
| 20 |
and other advanced features where the same volume needs to be |
| 21 |
simultaneously accessible from multiple hosts. |
| 22 |
|
| 23 |
New Architecture: The implementation now uses a many-to-one mapping |
| 24 |
where multiple hosts share a single subsystem, ensuring a single |
| 25 |
subsystem-to-namespace relationship. This resolves both QoS consistency |
| 26 |
and multi-attach limitations. |
| 27 |
|
| 28 |
Compatibility Impact: This change is not backward compatible due to |
| 29 |
fundamental differences in how NVMe subsystem-to-namespace mappings are |
| 30 |
handled. Live migration of existing mappings is not technically feasible. |
| 31 |
|
| 32 |
Required Upgrade Path: |
| 33 |
|
| 34 |
* Take backup of all volumes using the old NVMe architecture |
| 35 |
* Upgrade OpenStack to the version with the new architecture |
| 36 |
* Restore volumes using the new many-to-one subsystem mapping model |
| 37 |
* For assistance with migration planning and any questions about this |
| 38 |
process, contact NetApp support who can provide guidance specific to |
| 39 |
your environment and help minimize disruption during the transition. |
| 40 |
|
| 41 |
This approach ensures data integrity while enabling the improved |
| 42 |
multi-attach and QoS capabilities of the new architecture. |
| 43 |
|
| 44 |
fixes: |
| 45 |
- | |
| 46 |
NetApp Driver `Bug #2078968 |
| 47 |
<https://bugs.launchpad.net/cinder/+bug/2078968>`_: Fixed NVMe namespace |
| 48 |
mapping fails during VM migration with "Namespace is already mapped |
| 49 |
to subsystem". Implemented architecture changes to support multiple |
| 50 |
hosts attaching to single namespace through shared subsystem model. |