mark billingDb to be forbidden

It seems billingDb was used at least until 1.9.12 instead of the current
billingLogsDir but never marked as forbidden.

* Mark billingDb to be forbidden and replaced by billingLogsDir.

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Merge branch 'master' into legacy-billing-options
mark more legacy options to be obsolete

It seems billingDbCommitRows and billingDbCommitIntervalInMilliseconds were used
at least until 1.9.12 and later replaced by similar options.
I use "obsolete" as both options seem to be not critical.

* Mark billingDbCommitRows to be obsolete and replaced by
  billingMaxInsertsBeforeCommit.
* Mark billingDbCommitIntervalInMilliseconds to be obsolete and replaced by
  billingMaxTimeBeforeCommitInSecs.

Require-notes: no
Require-book: no

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
drop gPlazma1 config file and options

gPlazma1 has been removed from master both as native code and as plug-in to
gPlazma2.

* Drop the gPlazma1 configuration file dcachesrm-gplazma.policy.
* Mark the options gplazmaPolicy and gplazma.legacy.config as being obsolete.

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
use a more secure default for webadminAdminGid

Haveing a default value of 1000 for webadminAdminGid seems a tiny bit insecure
to me. 1000 is in no way a special GID and might be already used for any group
even such that gPlazma may map to (actually we at LMU had a test user mapped
to 1000:1000 for a while).
0 (root) seems to be the only appropriate choice and aligns quite well to the
default of admin.ssh2.gid.
I'm not sure whether the choice of 1000 was made deliberately, but it seems
at least Gerd agrees that 0 would be better. So pick it if you like or not :).
The change should be noted in the release notes, as it may "break" the setup
of sites that actually used 1000.

* Changed the default value of webadminAdminGid to "0" (for the gid of root).

    Require-notes: yes
    Require-book: no

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Merge pull request #32 from calestyo/legacy-billing-options

Mark legacy billing options as forbidden or obsolete.

Acked-by: Gerd Behrmann <behrmann@nordu.net>
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Merge pull request #45 from calestyo/drop-gplazma1-stuff

gplazma: Drop gPlazma1 config file and options

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Acked-by: Gerd Behrmann <behrmann@nordu.net>
Merge pull request #46 from calestyo/more-secure-webdav-auth

httpd: Change webadminAdminGid default to 0

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Acked-by: Gerd Behrmann <behrmann@nordu.net>
skel: fix billing database properties to work with dcache database commands

module: skel, defaults

While conditional initialization of the billing database works when the cell is created (via Spring), the database commands currently do not handle correctly the case where there is no billing database and billingToDb=no.  In particular, database ls lists the billing database regardless, and database update fails because it tries to run the liquibase changelog on a non-existent database.

To fix this, we have added conditional immutable properties in the style of several other default properties files.

Target: master
Patch: http://rb.dcache.org/r/5563
Require-book: no
Require-notes: yes
Request: 2.6
Request: 2.2
Bug: http://rt.dcache.org/Ticket/Display.html?id=7809
Acked-by: Paul

RELEASE NOTES:  Fixes a bug in the dcache database commands where update could not run if the billing database does not exist.  dcache database ls now correctly lists or does not list the billing database, depending on the billingToDb property, and dcache database update will ignore billing if billingToDb=no.