Bug 865507

Summary: RFE: RHHAv2 add option --riccihostname to wallaby cluster-* commands
Product: Red Hat Enterprise MRG Reporter: Tomas Rusnak <trusnak>
Component: condor-cluster-resource-agentAssignee: grid-maint-list <grid-maint-list>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.2CC: matt, rrati
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-26 20:03:52 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:

Description Tomas Rusnak 2012-10-11 15:44:50 UTC
Implement option --riccihostname for all wallaby cluster-* commands to provide a way how to say ccs to configure cluster over remote running ricci daemon. 

It's require changes in cmd_cluster.rb in calls of ccs -h localhost to provided hostname.

Following commands must to be changed:

cluster-add-jobserver:  Add a JobServer to an existing HA Schedd cluster configuration
cluster-add-node:  Add a node to an existing HA Schedd cluster configuration
cluster-add-queryserver:  Add a QueryServer to an existing HA Schedd cluster configuration
cluster-create:  Create an HA Schedd cluster configuration
cluster-delete:  Delete an HA Schedd cluster configuration
cluster-remove-jobserver:  Remove a JobServer from an existing HA Schedd cluster configuration
cluster-remove-node:  Remove a node from an existing HA Schedd cluster configuration
cluster-remove-queryserver:  Remove a QueryServer from an existing HA Schedd cluster configuration
cluster-sync-to-store:  Replaces HA configuration(s) in the store with the cluster configuration

Comment 1 Anne-Louise Tangring 2016-05-26 20:03:52 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.