libs: update to nfs4j-0.9.3

Changelog for nfs4j-0.9.2..nfs4j-0.9.3
    * [4d30382] nfsv4: release file state only after successful LayoutReturn
    * [1461589] nfsv4: disable grace period
    * [74feb02] pom: update to oncrpc4j-2.3.1

Acked-by: Gerd Behrmann
Target: master, 2.11
Require-book: no
Require-notes: no
nfs: stop embedded portmap on shutdown

Ticket: #8551
Acked-by: Gerd Behrmann
Target: master, 2.11, 2.10
Require-book: no
Require-notes: no
logback.xml: Replace layout by encoder

remove deprecated layout entries from logback files.

As described here these entries cause log messages as in the addressed tickets:
http://stackoverflow.com/questions/3257154/how-to-prevent-logback-from-outputting-its-own-status-at-the-start-of-every-log

Ticket: #8434
Acked-by: Paul
Target: master
Require-book: no
Require-notes: no
Patch: http://rb.dcache.org/r/7554/
pool: Refactor migration module task to decouple it further from the pool

Decouples the Task from JobDefinition and from CacheEntry. Removes coupling
between Task and the source state.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Patch: https://rb.dcache.org/r/7532/
pool: Expose error code to migration task callback

Not used by migration module, but other users may want to know the error
code.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Patch: https://rb.dcache.org/r/7534/
Ensure that LoginManager threads are terminated on shutdown

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Patch: https://rb.dcache.org/r/7542/
When introduced we had no other way to set custom log levels than
to have a logback.xml specific to system-test. Nowadays log levels
can be adjusted through properties in our regular configuration
files. Hence, there is no need for the custom logback configuration.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Karsten Schwank <karsten.schwank@desy.de>
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: https://rb.dcache.org/r/7552/
spacemanager: Get rid of access latency and retention policy defaults

I recently got contacted by KIT about the differences between the AL/RP
defaults in space manager and pnfs manager. It became clear that the
documentation in our property files wasn't clear enough about the difference.

While looking at this, it became clear that there was no need for defaults in
space manager. The defaults where used in two places: When creating
reservations through the command line interface and when creating reservations
through SRM. In the former case we can just as well make the al and rp options
required, forcing the admin to be explicit about the desired al and rp. In the
latter case, the SRM declares retention policy a required parameter (so we
don't need a default), but access latency is optional. However, rather than
limiting the access latency to a single site default, it makes much more sense
to let the retention policy steer the link group selection and then see which
options we have for access latency. Most likely the retention policy is enough
to limit the choice to a single link group and most likely only a single access
latency is possible for that case. This avoids the need for a default and
even makes the code more intelligent.

When reserving through the SRM withoug an explicit access latency, the code
prefer ONLINE for REPLICA reservations, and NEARLINE for CUSTODIAL reservations,
but falls back to whatever the link group allows.

For reservations through the command line (admin shell), the code has been
simplified: There is no point in a complicated query to the database when the
command invocation already specified the link group to use. All we need to do
is to verify the parameters. This also allows us to provide better error
messages. The patch makes one change to authorization for admin created
reservations: Previously the owner (the FQAN or user allowed to release the
reservation) had to be among the list of principals authorized to create
reservations in the link group. There is however no reason for this
restriction. Indeed, this limitation prevented useful scenarios, e.g. allowing
user made or implicit reservations in a link group, but block release of the
reservation by setting the owner to an admin.

The patch also gets rid of some dead code in the SpaceManagerService and
simplifies the logic for reserving space.

I request backport to 2.10 as the presence of the defaults in space manager has
caused confusion for those upgrading.

Target: trunk
Request: 2.11
Request: 2.10
Require-notes: yes
Require-book: yes
Acked-by: Dmitry Litvintsev <litvinse@fnal.gov>
Patch: https://rb.dcache.org/r/7538/