netapp dr replica export location missing

Bug #1925153 reported by Maurice Escher
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)

Bug Description


I use share replication with the NetApp driver.

My customers want to see the export locations of the to-be-promoted non-active replicas so they can prepare for planned (and also for unplanned) failovers upfront.

Though those export locations cannot already be used for mounting at that point in time, it is already determined how they will look like: the share server with IPs is already there, as well as the replication target volume names and therefore the names of the resulting junction paths.

Definitely this requires some documentation, maybe even a new flag on the export location metadata?
What do you think, can this be added to manila?
I'm not sure about the other drivers, though.

Best regards,

description: updated
tags: added: netapp
Vida Haririan (vhariria)
tags: added: replication
Vida Haririan (vhariria)
Changed in manila:
importance: Undecided → Medium
status: New → Confirmed
milestone: none → xena-2
Vida Haririan (vhariria)
Changed in manila:
status: Confirmed → New
importance: Medium → Undecided
milestone: xena-2 → none
Revision history for this message
Vida Haririan (vhariria) wrote :
Revision history for this message
Maurice Escher (maurice-escher) wrote :

tl;dr: this is a feature request, discussion about this topic should go to a spec

Vida Haririan (vhariria)
Changed in manila:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.