loginbroker: Comply with new configuration policy

Drops the service srm-loginbroker. All doors now register with
a single login broker called LoginBroker and SRM and all
monitoring services query this one LoginBroker to locate doors.
SRM is updated to exclude srm as a transfer protocol, thus
making it safe to register all doors in the same login broker.

The dcache.service.loginbroker property is updated to take
a comma separated list of loginbrokers to register with or
to query. httpd now uses this property to configure which
loginbrokers to query.

New properties

loginbroker.cell.name
srm.protocols.disallowed.get
srm.protocols.disallowed.put
srm.protocols.preferred

Target: trunk
Require-notes: yes
Require-book: yes
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5742/
cleaner: Clean up cleaner.properties

Besides cleaning up the comments, this patch turns the previously
obsoleted property cleaner.hsm into a deprecated property.

Target: trunk
Require-notes: yes
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5744/
spacemanager: Allow previously obsoleted values for deprecated srmSpaceManagerEnabled

This patch adds legacy values for srmSpaceManaerEnabled. Thus one can
once again use true, on, yes, enabled, false, off, no, disabled, but
only when using the legacy property.

Also fixed a bug in srm.batch introduced when previously deprecating
srmSpaceManagerEnabled.

Require-book: no
Require-notes: yes
Target: trunk
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5748/
replica: Restored legacy values of deprecated replicaManager property

When renaming the configuration properties of replica manager, the
replicaManager was marked deprecated and the allowed values changed
to true and false rather than yes and no. This patch restored the
legacy values such that yes and no can be used. The new
dcache.enable.replica property still requires the values true and
false.

The default value of the property has been changed from yes/true to
no/false, as this better reflect most dCache instances.

Target: trunk
Require-notes: yes
Require-book: yes
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5749/
alarms: Comply with new configuration policy

RELEASE NOTES:
BOOK:

Deprecated:

alarms.server.config
alarms.store.db.type
alarms.store.path
alarms.store.db.rdbms
alarms.store.db.driver
alarms.store.db.host
alarms.store.db.user
alarms.store.db.pass
alarms.store.db.properties
alarms.store.db.url

New:

alarms.cell.name=alarms
alarms.log.config.path=${alarms.server.config}
(one-of?off|error|warn|info|debug|${alarms.server.log.level})alarms.log.root-level=${alarms.server.log.level}
(one-of?off|xml|rdbms|${alarms.store.db.type})alarms.db.type=off
alarms.db.xml.path=${alarms.store.path}
alarms.db.rdbms.type=${alarms.store.db.rdbms}
alarms.db.driver=${alarms.store.db.driver}
alarms.db.host=${$alarms.store.db.host}
alarms.db.user=${$alarms.store.db.user}
alarms.db.password=${alarms.store.db.pass}
alarms.db.name=alarms
alarms.db.config.path=${alarms.store.db.properties}
alarms.db.url=${alarms.store.db.url}
alarms.db.schema.auto
alarms.db.schema.changelog

Obsolete:
alarms.store.db.changelog

Target: master
Require-notes: yes
Require-book: yes
Patch: http://rb.dcache.org/r/5743
Acked-by: Gerd
Fix CellStub timeout handling

A recent change to CellStub introduced a time unit property. Thus
the interpretation of getTimeout() changed, as the value was no
longer guaranteed to be in milliseconds. This patch updates the
code that uses getTimeout() and either lets it use getTimeoutInMillis()
instead, or updates it to be time unit aware. The patch also fixes
several calls to setTimeout().

Thanks to Dmitry for finding this.

Target: trunk
Require-book: no
Require-notes: no
Acked-by: Albert Rossi <arossi@fnal.gov>
Patch: http://rb.dcache.org/dashboard/
Merge branch 'master' of github.com:dCache/dcache