跳转到主内容

OpenStack Cinder NVMe/TCP 多路径:仅有一个控制器路径在 NetApp ONTAP 中可见

Views:
37
Visibility:
Public
Votes:
0
Category:
openstack
Specialty:
virt
Last Updated:

适用于

  • NetApp ONTAP(例如,9.17.1P6,AFF-C250)
  • OpenStack Cinder 使用 NetApp ONTAP NVMe/TCP 统一驱动程序
  • 启用了本机 NVMe 多路径的 Linux 主机
  • 使用 os-brick 进行 NVMe/TCP 的 OpenStack 部署(例如,Platform9)
  • 具有多个 NVMe/TCP LIF 的多控制器 NetApp 集群

问题

当使用 OpenStack Cinder 将 NetApp ONTAP NVMe/TCP 卷挂载到虚拟机时,计算节点上只会自动建立一个 NVMe/TCP 路径/控制器。因此,默认情况下不支持多路径和冗余。需要手动发现并连接到第二个 LIF,以建立额外的路径。

日志输出示例(来自 cinder-volume 和 os-brick):

DEBUG cinder.volume.drivers.netapp.dataontap.nvme_library Initialize connection info: { 'driver_volume_type': 'nvmeof', 'data': { 'target_nqn': 'nqn.1992-08.com.netapp:...', 'host_nqn': 'nqn.2014-08.org.nvmexpress:uuid:...', 'portals': [('<nvme data lif ip1>', 4420, 'tcp')], 'vol_uuid': '...' } } DEBUG cinder.volume.manager Connection info returned from driver { 'target_nqn': 'nqn.1992-08.com.netapp:...', 'host_nqn': 'nqn.2014-08.org.nvmexpress:uuid:...', 'portals': [('<nvme data lif ip2>', 4420, 'tcp')], ... } DEBUG os_brick.initiator.connectors.nvmeof Found a valid portal at ('<nvme data lif ip1>', '4420', 'tcp', ...) DEBUG os_brick.initiator.connectors.nvmeof Skipping ('<nvme data lif ip2>', '4420', 'tcp', ...), not part of portals [...]

预期: 应在 portals 列表中返回两个 LIF。

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.