Regular maintenance releases 2.16.18 et al.

dCache · Nov 22, 2016 · 66e57cf · 66e57cf
1 parent 0af9b73
commit 66e57cf
Show file tree

Hide file tree

Showing 7 changed files with 2,256 additions and 5 deletions.
diff --git a/release-notes-2.10 b/release-notes-2.10
@@ -102,6 +102,26 @@ Paul Millar  &lt;[email protected]&gt;
   xrootd is now consistent with information recorded for other
   protocol transfers.
 
+## Release 2.10.62
+
+### poolmanager
+
+PoolManager was updated to properly handle the `dcache.authz.staging.pep` and `dcache.authz.staging` parameters. This allows to enable stage protection properly.
+
+
+### Changelog 2.10.61..2.10.62
+
+<!-- git log 2.10.61..2.10.62 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n:   %s%n' -->
+
+[29cbe36](https://github.com/dcache/dcache/commit/29cbe36c4093e59f26b2e010ce0270a0c4fe6b18)
+:   [maven-release-plugin] prepare release 2.10.62
+
+[4247d9a](https://github.com/dcache/dcache/commit/4247d9a749149a4b4d0a9f5c0abd738d6300aa9b)
+:   PoolManager : stage protection, fix error in stage.fragment
+
+[332e0ff](https://github.com/dcache/dcache/commit/332e0ff275fe3a32f4cf41beb62370ee9211613f)
+:   [maven-release-plugin] prepare for next development iteration
+
 ## Release 2.10.61
 
 ### pnfsmanager

diff --git a/release-notes-2.13 b/release-notes-2.13
@@ -137,6 +137,33 @@ Highlights from this release:
   required upon upgrading, but downgrading is not possible without
   explicitly converting the format.
 
+## Release 2.13.49
+
+### dcap
+
+Connections of non-DCAP clients to a dCache no longer result in stack-traces in the logs.
+
+### poolmanager
+
+PoolManager was updated to properly handle the `dcache.authz.staging.pep` and `dcache.authz.staging` parameters. This allows to enable stage protection properly.
+
+
+### Changelog 2.13.48..2.13.49
+
+<!-- git log 2.13.48..2.13.49 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n:   %s%n' -->
+
+[8777492](https://github.com/dcache/dcache/commit/8777492ee3a3e09c99854ac6bc913bce26445db3)
+:   [maven-release-plugin] prepare release 2.13.49
+
+[704121e](https://github.com/dcache/dcache/commit/704121e61ccdfcedca3578e7e6da48f6d2e758c0)
+:   dcap: don't create stack-trace if tunnel fails due to bad client
+
+[6ffa136](https://github.com/dcache/dcache/commit/6ffa136a1b93d467f4cd6c173d2f1520694fae0f)
+:   PoolManager : stage protection, fix error in stage.fragment
+
+[f26ad6b](https://github.com/dcache/dcache/commit/f26ad6b3b8cec0631b4568d370e2234acf6c86d4)
+:   [maven-release-plugin] prepare for next development iteration
+
 ## Release 2.13.48
 
 ### Changes affecting multiple services

diff --git a/release-notes-2.14 b/release-notes-2.14
@@ -149,6 +149,33 @@ Highlights from this release:
   SRM requests will be lost from the database. Third party scripts
   that access the SRM database directly may have to be updated.
 
+## Release 2.14.38
+
+### dcap
+
+Connections of non-DCAP clients to a dCache no longer result in stack-traces in the logs.
+
+### poolmanager
+
+PoolManager was updated to properly handle the `dcache.authz.staging.pep` and `dcache.authz.staging` parameters. This allows to enable stage protection properly.
+
+
+### Changelog 2.14.37..2.14.38
+
+<!-- git log 2.14.37..2.14.38 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n:   %s%n' -->
+
+[d1c87a9](https://github.com/dcache/dcache/commit/d1c87a91e2a61b26b5c3ef6bb084e63c6d81981d)
+:   [maven-release-plugin] prepare release 2.14.38
+
+[3aeb652](https://github.com/dcache/dcache/commit/3aeb652f4911e18a124878ba62cb33cb826630fd)
+:   dcap: don't create stack-trace if tunnel fails due to bad client
+
+[051f57f](https://github.com/dcache/dcache/commit/051f57f0a1e4d18863c2e9d3705fd4bce2086e7d)
+:   PoolManager : stage protection, fix error in stage.fragment
+
+[fa39df6](https://github.com/dcache/dcache/commit/fa39df64a73d6c575d89cc9365de9e2adf9ec4e0)
+:   [maven-release-plugin] prepare for next development iteration
+
 ## Release 2.14.37
 
 ### Changes affecting multiple services

diff --git a/release-notes-2.15 b/release-notes-2.15
@@ -94,6 +94,33 @@ Highlights from this release:
   enforced. Clients that relied on these not being enforced will
   fail after upgrade.
 
+## Release 2.15.25
+
+### dcap
+
+Connections of non-DCAP clients to a dCache no longer result in stack-traces in the logs.
+
+### poolmanager
+
+PoolManager was updated to properly handle the `dcache.authz.staging.pep` and `dcache.authz.staging` parameters. This allows to enable stage protection properly.
+
+
+### Changelog 2.15.24..2.15.25
+
+<!-- git log 2.15.24..2.15.25 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n:   %s%n' -->
+
+[073a1d5](https://github.com/dcache/dcache/commit/073a1d5a771a2fb4dbea9e35139e5159aa4b68a5)
+:   [maven-release-plugin] prepare release 2.15.25
+
+[477c6c0](https://github.com/dcache/dcache/commit/477c6c06584634cc49ad4d14596ac7a13ff24920)
+:   dcap: don't create stack-trace if tunnel fails due to bad client
+
+[07b4153](https://github.com/dcache/dcache/commit/07b415323213412b1f68dd4d063c22fca6045cc6)
+:   PoolManager : stage protection, fix error in stage.fragment
+
+[194d914](https://github.com/dcache/dcache/commit/194d91431bd51b167ce0adc8731b6ed4892b131b)
+:   [maven-release-plugin] prepare for next development iteration
+
 ## Release 2.15.24
 
 ### Changes affecting multiple services

diff --git a/release-notes-2.16 b/release-notes-2.16
@@ -111,6 +111,82 @@ HTML header: <title>dCache 2.16 Release Notes</title>
 * Sites with a custom `httpd.conf` configuration will have to adjust
   this upon upgrade to inject the cell address of the `info` service.
 
+## Release 2.16.19
+
+### dcap
+
+Connections of non-DCAP clients to a dCache no longer result in stack-traces in the logs.
+
+### pool
+
+A lock contention scenario in the migration module was removed, increasing performance and throughput.
+
+### poolmanager
+
+PoolManager was updated to properly handle the `dcache.authz.staging.pep` and `dcache.authz.staging` parameters. This allows to enable stage protection properly.
+
+### resilience
+
+When building the central pool information data structure for resilience
+(PoolInfoMap), it was (erroneously) assumed that pool group names would 
+never conflict with storage unit names, since the latter would always contain an '@'.
+
+Obviously, there is no restriction on the naming of pool groups, so
+it is possible (though perhaps unlikely) that the name of a group
+could be identical to that of a storage unit.   In this case,
+when the PoolInfoMap is updated, the storage group will overwrite
+the values for the pool group.  This will eventually lead to the
+failure of all files belonging to that pool group to be replicated.
+
+This potential problem was mitigated by this patch.
+
+Resilience Manager was updated to support globbed expressions for PoolSelectionUnits.
+
+A Python script, `share/migration/migrate_from_repman_to_resilience.py`, is provided for migrating from replica manager to the new resilience service. 
+
+### srmclient
+
+SrmShell has been modified to actively probe for connection information that the
+user has not specified. This reduces unnecessary reconnection attempts.
+
+If an SRM request originating from a BeStMan system has to be rejected, the client now properly
+reports the situation. 
+
+
+### Changelog 2.16.18..2.16.19
+
+<!-- git log 2.16.18..2.16.19 -no-merges -format='[%h](https://github.com/dcache/dcache/commit/%H)%n:   %s%n' -->
+
+[a4d5824](https://github.com/dcache/dcache/commit/a4d5824a071a58bc7eee37ea77fcb1bab0219668)
+:   [maven-release-plugin] prepare release 2.16.19
+
+[53e953a](https://github.com/dcache/dcache/commit/53e953a02010cfaebcf46565f9ce5ff4a6b75c3f)
+:   resilience: python script for making database changes necessary for migration from old replica manager setup
+
+[1c9704b](https://github.com/dcache/dcache/commit/1c9704ba2c5acdf815d37a05b2283b103c031475)
+:   pool: Reduce lock contention in migration module
+
+[5e8e9c7](https://github.com/dcache/dcache/commit/5e8e9c76e13ad581995df31aa18424aec025c6cd)
+:   srmclient: fix compatibility with Bestman
+
+[d2e7b95](https://github.com/dcache/dcache/commit/d2e7b95c3d3a8e845e51bfd958854c6feb0b14f5)
+:   srmclient: probe for SRM endpoint parameters that the user doesn't specify
+
+[6752620](https://github.com/dcache/dcache/commit/6752620c62d68bb70e2ae2261579ed89b139725d)
+:   Resilience: separate out the data structures for handling storage units from those for pool groups
+
+[98ec759](https://github.com/dcache/dcache/commit/98ec7594c03c998e3c3df29bfabaaeccd23cd225)
+:   Resilience: Support matching the universal and class default storage unit expressions
+
+[d430a02](https://github.com/dcache/dcache/commit/d430a02f2c1e3e9b23e026122af9fccedaa159d0)
+:   dcap: don't create stack-trace if tunnel fails due to bad client
+
+[de42e02](https://github.com/dcache/dcache/commit/de42e02b49f8a230b8c4db3248043ec3874b0934)
+:   PoolManager : stage protection, fix error in stage.fragment
+
+[5bd8b17](https://github.com/dcache/dcache/commit/5bd8b1705f7670e443e5fb68f46dce0033a65bcd)
+:   [maven-release-plugin] prepare for next development iteration
+
 ## Release 2.16.18
 
 ### Changes affecting multiple services