Support multiple shares on the same NFS back-end with different IPv4 addresses

Bug #1664218 reported by Felipe Alfaro Solana on 2017-02-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel Plugin Cinder Netapp
Undecided
Felipe Alfaro Solana

Bug Description

Cinder/NetApp plug-in for Fuel 9.x supports multiple NFS shares per backend. However, all shares use a common IPv4 address. For example, a typical /etc/cinder/shares_1.conf file looks like this when generated by plug-in version 6.x:

10.0.0.1:/a_simple_netapp_share1
10.0.0.1:/a_simple_netapp_share2

In our production clusters, a single NetApp back-end has several IPv4 addresses. We export one share on each IPv4 address for resiliency, so our /etc/cinder/shares_1.conf file looks like this instead:

10.0.0.1:/a_simple_netapp_share1
10.0.0.2:/a_simple_netapp_share2

For this to work, a small change is required to the Cinder/NetApp fuel plug-in to embed the IPv4 address into the NFS share path.

Changed in fuel-plugin-cinder-netapp:
assignee: nobody → Felipe Alfaro Solana (felipe-alfaro-gmail)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-plugin-cinder-netapp (master)

Fix proposed to branch: master
Review: https://review.openstack.org/433066

Changed in fuel-plugin-cinder-netapp:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-plugin-cinder-netapp (master)

Change abandoned by Clark Boylan (<email address hidden>) on branch: master
Review: https://review.opendev.org/433066
Reason: Fuel projects have been retired.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers