Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1279729

Summary: [Docs] [REST] [RFE] add API for Cluster Fencing Policy
Product: Red Hat Enterprise Virtualization Manager Reporter: Tahlia Richardson <trichard>
Component: ovirt-engineAssignee: Ori Liel <oliel>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: adahms, apinnick, bugs, cminkema, emesika, juan.hernandez, lsurette, mperina, pstehlik, ratamir, rhev-docs, Rhev-m-bugs, s.kieske, srevivo
Target Milestone: ovirt-4.3.0Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1176555 Environment:
Last Closed: 2019-01-10 15:01:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1127592    
Bug Blocks: 1148393    

Description Tahlia 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.
Comment 1 Yaniv Lavi 2016-05-09 11:00:29 UTC 
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
Comment 3 Juan Hernández 2016-11-08 13:53:31 UTC 
As far as I know this hasn't been addressed in the specification of the API for 4.0.5, so I am re-targeting to 4.0.6.
Comment 4 Sandro Bonazzola 2017-12-20 13:56:39 UTC 
oVirt 4.2.0 has been released on Dec 20th 2017. Please consider re-targeting this bug to next milestone
Comment 5 Martin Perina 2019-01-10 14:30:12 UTC 
Merged long time ago in https://gerrit.ovirt.org/67489. Cheryl, is it something else needed from us?
Comment 6 Cheryl Minkema 2019-01-10 15:01:52 UTC 
Martin, nothing further is needed. Ondra has seen it, so that's good enough for us.