I am looking at XECS-1415 [1], to unify sipXsupervisor configuration. 

"Currently, sipXsupervisor (nee watchdog) takes configuration data from
3 different configuration files. This is a legacy of the fact that the
functionality used to be in different components. Much of what's in the
files is no longer needed - the rest should be combined into a single
file (preferably the sipxsupervisor-config file)."


>From my limited understanding on sipXsupervisor, here is what I see:

- ProcessDefinitions.xml: does not seem to be needed anymore. 
  
  Proposed changes: completely remove ProcessDefinitions.xml and
relevant code.

- WatchDog.xml: after Carolyn's changes for XECS-1500 [2], it is no
longer needed, except the logging level setting for sipxsupervisor.log. 

  Proposed changes: remove WatchDog.xml and relevant code, and move
logging level setting to sipxsupervisor-config.

- resourcemap.xml: Not needed anymore. 

  Proposed changes: completely remove resourcemap.xml and relevant code.


>From my investigation, the only configuration needed to be reserved from
the above configuration files that to be eliminated is the logging level
setting, and as the logging level is not exposed to the web UI,
therefore it can be hard-coded in the sipxsupervisor-config. 

- I removed the references to resourcemap.xml already, but for now,
since supervisor still uses watchdog to start/stop process, so we can
not obsolete ProcessDefinitions.xml and WatchDog.xml yet until XECS-1500
is complete. Given the changes to eliminate those configuration files
have dependence on the on-going restructure of the supervisor,  I would
suggest to park XECS-1415 for now and wait till the required dependency
is complete.


Thanks,
Huijun




[1] http://track.sipfoundry.org/browse/XECS-1415
[2] http://track.sipfoundry.org/browse/XECS-1500
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to