Bug 707222

Summary: [RFE] wallaby - Collector in SharedPort feature
Product: Red Hat Enterprise MRG Reporter: Lubos Trilety <ltrilety>
Component: condor-wallaby-base-dbAssignee: grid-maint-list <grid-maint-list>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: DevelopmentCC: iboverma, matt, tstclair
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:04:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lubos Trilety 2011-05-24 12:59:56 UTC 
Description of problem:
SharedPort feature should also set Collector daemon to use shared port, for that following parameters have to be set properly:
COLLECTOR_HOST
COLLECTOR_ARGS
(SHARED_PORT_ARGS)

where 
 - COLLECTOR_HOST could be set to '$(CONDOR_HOST):<port>?sock=collector'
 - COLLECTOR_ARGS is needed only on machine with running Collector, but can be set
also on other machines, they simply ignore it. It could be set to '-sock
collector'
 - probably also SHARED_PORT_ARGS has to be set to assure that shared port use particular port, which is needed in COLLECTOR_HOST setting. It could be set for example to '-p 4080'

Version-Release number of selected component (if applicable):
condor-wallaby-base-db-1.12-1
Comment 3 Timothy St. Clair 2011-12-05 20:16:48 UTC 
The following is an example

All nodes will need:
USE_SHARED_PORT=True
SHARED_PORT_ARGS = "-p 9620"
DAEMON_LIST = $(DAEMON_LIST),SHARED_PORT
SHARED_PORT_DEBUG = D_FULLDEBUG
DAEMON_SOCKET_DIR = /tmp/$(USERNAME)-condor-test-sock
COLLECTOR_HOST = $(CONDOR_HOST):9620?sock=collector

Collector will need ^above^ +:
COLLECTOR_ARGS = -sock collector
Comment 4 Anne-Louise Tangring 2016-05-26 20:04:09 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.