Bug 1129871

Summary: Document: 'pcs cluster cib': implement --scope as cibadmin does
Product: Red Hat Enterprise Linux 7 Reporter: Steven J. Levine <slevine>
Component: doc-High_Availability_Add-On_ReferenceAssignee: Steven J. Levine <slevine>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: cfeist, cluster-maint, cluster-qe, mnovacek, slevine, tojeline
Target Milestone: rcKeywords: Documentation, FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1115537 Environment:
Last Closed: 2014-11-07 21:45:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1115537, 1190168    
Bug Blocks:    

Comment 1 Steven J. Levine 2014-11-07 21:45:57 UTC 
As a general rule, we do not want to expose the cib to the user. There's some pretty explicit discussion of this in BZ#1085100.

We do, however, document the pcs cluster cib command to show how to make changes to a file locally and then push them to the whole cluster.

But the reason for this feature is not along those lines -- it's about removing resources and then adding them again. The use case of wanting to work locally on only a particular scope of cib and then pushing only that scope of changes back seems very narrow -- and can be addressed in the documentation on the help screen alone. 

So after discussion with Chris Feist, I am closing this as not a bug. As noted, the feature remains documented on the help screen (which is pretty much all that would be in the manual anyway).