Bug 1127592

Summary: [RFE] add API for Cluster Fencing Policy
Product: [oVirt] ovirt-engine Reporter: Oved Ourfali <oourfali>
Component: RestAPIAssignee: Eli Mesika <emesika>
Status: CLOSED CURRENTRELEASE QA Contact: movciari
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, emesika, gklein, iheim, juan.hernandez, mperina, pzhukov, rbalakri, yeylon, ykaul, ylavi
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature
Target Release: 3.6.0Flags: rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764 Doc Type: Enhancement
Doc Text:
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>
Story Points: ---
Clone Of:
: 1176555 (view as bug list) Environment:
Last Closed: 2016-02-10 12:54:27 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:    
Bug Blocks: 1176555, 1279729    

Description Oved Ourfali 2014-08-07 08:24:04 UTC
In 3.5 we added fencing policy support to the engine, only with UI support. We need to add API support as well.