[RFE] Netapp make netapp_snapmirror_quiesce_timeout end user option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
kiran pawar |
Bug Description
Hi,
currently netapp_
There are situations where a high timeout may be good: safeguarding planned failovers to prevent data loss.
But there are also situations where no time should be waited at all: disaster stroke and I want to do an unplanned failover fast.
So there is no: one fits all. Let's move the decision up to the end user client whether the timeout should be at a certain higher value or zero.
I can imagine this being implemented as a force option to the replica promote API, since this is nothing that could be expressed via share type. One and the same share could get into both described example situations at different times, so it is not a describing attribute of the share itself, but rather a thing to provide at the time of calling promote (or some cleverness to determine, whether it is a disaster situation or not. but how to implement such goes beyond my imagination currently)
Thanks in advance for your thoughts about this,
Maurice
Changed in manila: | |
importance: | Undecided → Medium |
assignee: | nobody → kiran pawar (kpdev) |
Changed in manila: | |
milestone: | none → antelope-3 |
More thoughts after brainstorming with kpdev: instead of a force-option the option per call can also be giving the value of the quiesce wait time to be used for that particular promote operation.