ssh2: Honor admin.colors.enable

    Ssh2 admin interface did not honor admin.colors.enable, this patch resolve this problem.

    Ticket: http://rt.dcache.org/Ticket/Display.html?id=7820
    Acked-by: Gerd
    Target: master
    Require-book: no
    Require-notes: no

Squashed commit of the following:

commit 8e3db9a3f6cd0c9b8ce6f340f67eb3ecf3651163
Merge: 3887dc4 3e02f94
Author: Christian Bernardt <christian.bernardt@desy.de>
Date:   Mon Jul 15 18:33:45 2013 +0200

    Merge color fix branch with current master because not all changes got committed with the last push.

    Sorry.

    ssh2: Honor admin.colors.enable
    Ssh2 admin interface did not honor admin.colors.enable, this patch resolve this problem.

    Ticket: http://rt.dcache.org/Ticket/Display.html?id=7820
    Acked-by: Gerd
    Target: master
    Require-book: no
    Require-notes: no

commit 3887dc446e7d388659ffb651e5a0a9e1db67f868
Author: Christian Bernardt <christian.bernardt@desy.de>
Date:   Mon Jul 15 14:15:39 2013 +0200

    ssh2: Honor admin.colors.enable

    Ssh2 admin interface did not honor admin.colors.enable, this patch resolve this problem.

    Ticket: http://rt.dcache.org/Ticket/Display.html?id=7820
    Acked-by: Gerd
    Target: master
    Require-book: no
    Require-notes: no

commit 3e02f94eebb02bddf81441a9dd7ac41344577e74
Author: Christian Bernardt <christian.bernardt@desy.de>
Date:   Mon Jul 15 14:15:39 2013 +0200

    Change parameter to no type definition and switch line to above cell related properties

commit 89bd221adafba600ce35c5f103f65a6736c408e6
Author: Christian Bernardt <christian.bernardt@desy.de>
Date:   Mon Jul 15 12:22:09 2013 +0200

    Remove line that sets colors from environment param and not from within dCache

commit 0def3e296a3018c173062457b7256a4ac207ef30
Author: Christian Bernardt <christian.bernardt@desy.de>
Date:   Mon Jul 15 11:41:13 2013 +0200

    ssh2: Honor admin.colors.enable

    Ssh2 admin interface did not honor admin.colors.enable, this patch resolve this problem.

    Ticket: http://rt.dcache.org/Ticket/Display.html?id=7820
    Acked-by:
    Target: trunk
    Require-book: no
    Require-notes: no
Merge branch 'master' of github.com:dCache/dcache
Merge branch 'master' of github.com:dCache/dcache
Merge remote-tracking branch 'upstream/master'
admin: fail commands when user supplies an option that is unknown

The current behaviour for both annotated and ac_ commands is that
any options that are unknown to the command are simply ignored.

This behaviour can be dangerous; for example, the migration
module's move and copy commands accept a 'pnfsid' option to
limit the scope of the operation.  Multiple PNFS-IDs may be
specified as a comma-separated list; however, this leads to
the potential for invoking a move with the option:

     -pnfsids=<id1>,<id2>,...

The migration module will silently ignore the unknown 'pnfsids'
option and move or copy all files on the pool.

More generally, if there is an unknown option then the user is
intending some behaviour that the command will not honour:
irrespective of how dangerous this is, it can be frustrating
to diagnose why an apparently correct invocation isn't doing
what is intended.

This patch fixes this problem for annotated commands only.
This is sufficient to fix the specific issue mentioned in the
ticket.  Solving this for non-annotated commands might be
possible, but I believe only with considerable effort.  Such
effort would be better spent moving those commands to use the
new annotation-based command format.

Target: trunk
Request: 2.7
Request: 2.6
Ticket: http://rt.dcache.org/Ticket/Display.html?id=7991
Patch: http://rb.dcache.org/r/5957/
Acked-by: Albert Rossi
webadmin: wait untill billing cell is ready

StandardBillingService should wait untill billing cell is ready

Ticket: #7981
Acked-by: Albert Rossi
Acked-By: Paul Millar
Target: 2.6, 2.7, master

Require-book: no
Require-notes: no
Merge remote-tracking branch 'upstream/master'
Change ssh admin properties documentation, historyPath
srm: Fix regression in srmCopy

CopyRequest and CopyFileRequest are both processed by the
same SRM scheduler. Thus the scheduler must be configured
for a common base class of these two jobs.

Target: trunk
Request: 2.7
Require-notes: no
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Acked-by: Dmitry Litvintsev <litvinse@fnal.gov>
Patch: http://rb.dcache.org/r/5996/
srm: Do not use SQLException unless its about JDBC

SQLException is the main exception used by JDBC code. The SRM in many
places declares SQLException in code completely unrelated to JDBC, in
code that doesn't even throw SQLException, or uses it to propagate
non-JDBC errors.

This patch addresses this problem, mostly by removing the declaration
of SQLException in the throws clause of many methods. In some cases
SQLException is replaced by another exception, eg IOException or
SRMException.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Acked-by: Dmitry Litvintsev <litvinse@fnal.gov>
Patch: http://rb.dcache.org/r/5953/
srm: Use Spring JDBC support

Spring has extensive support for simplifying JDBC code. This patch updates
the srm to make use of Spring's JDBC support.

At the core of the patch is Spring's JdbcTemplate that provides methods
for common JDBC patterns. Given that the existing code was Connection
oriented, most uses of JdbcTemplate is for the ConnectionCallback pattern:
It encapsulates the acquisition, use and release of a Connection. There
are however plenty of other patterns, some of which are used in the patch.
A future patch may update more of the SRM code to make use of the higher
level patterns.

The patch also replaces most uses of SQLException. SQLExcepton is a catch
all JDBC exception. It has the problem that one has to inspect a vendor
specific error code to get more detailed information about the failure.
More over, a lot of SRM code is not JDBC specific, yet used the JDBC
exception. Eg JobStorage is not limited to JDBC, yet all methods threw
SQLException.

Spring provides the DataAccessException as a replacement for SQLException.
DataAccessException is a base class for an entire hierarchy of data
access related exceptions. Spring translates vendor specific SQL error
codes to an appropriate DataAccessException subclass. The translation
happens automatically when JdbcTemplate is used.

JdbcConnectionPool is now a factory of JdbcTemplate and TransactionTemplate.
It no longer provides methods for acquiring and releasing connections.

A consequence of the patch is that many errors that were previously caught
and ignored are now propagated.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Karsten Schwank <karsten.schwank@desy.de>
Patch: http://rb.dcache.org/r/5954/
namespace: remove dead FileAttribute to NFS atts method

Acked-by: Paul Millar
Target: master
Require-book: no
Require-notes: no
namespace: introduce CHANGE_TIME attrribute

Acked-by: Paul Millar
Target: master
Require-book: yes
Require-notes: yes
dcap: remove misterious sleep

Acked-by: Paul Millar
Target: trunk
Require-book: no
Require-notes: no
pool: fix startup for pools that saved configuration earlier than 2.2

A recent patch introduced strict checking of command options: if a
command supplies an option that is not recognised then the command will
fail.  This is limited to annotated commands.

Pools save their configuration in a 'setup' file as a series of
commands that are to be run on startup.  Unfortunately, this includes a
command with an option that isn't currently accepted. The result is
that pools with 'setup' files created earlier than 1.9.13 do not start.

This patch fixes the problem by updating the command to accept the
option but ignore it.  This is functionally the same as before
introducing the strict checking.

This patch also updates the pool defaults.  This is a set of commands
that are always executed before 'setup' to provide a base-line for
pools.  The current defaults includes the problematic command.

FOR RELEASE NOTES:

A change included in 2.6.8 prevented pools from starting up where the
pool has a 'setup' file created with a version of dCache before
v1.9.13.  This patch fixes this issue.

Target: master
Request: 2.7
Request: 2.6
Ticket: http://rt.dcache.org/Ticket/Display.html?id=8006
Requires-notes: yes
Requires-book: no