DescriptionTahlia Richardson
2015-11-10 07:00:59 UTC
Feature:
Add API support for cluster fencing policy.
Reason:
In 3.5 we introduced fencing policy per cluster, but they were supported in the UI only. This feature adds API support as well.
Result:
Clusters retrieved from REST will have now the following section, which can be also set. For example:
<fencing_policy>
<enabled>true</enabled>
<skip_if_sd_active>
<enabled>false</enabled>
</skip_if_sd_active>
<skip_if_connectivity_broken>
<enabled>false</enabled>
<threshold>50</threshold>
</skip_if_connectivity_broken>
</fencing_policy>
+++ This bug was initially created as a clone of Bug #1176555 +++
+++ This bug was initially created as a clone of Bug #1127592 +++
In 3.5 we added fencing policy support to the engine, only with UI support. We need to add API support as well.