Upgrade Instructions
This page summarizes changes made to configuration files, database
schemas and deprecated features in dCache releases since 1.9.0-1. When
upgrading dCache we strongly encourage to read through all release
notes of intermediary releases, however this page gives a summary of
things that are crucial to check when upgrading.
Since we follow a two dimensional release structure, some changes
may be listed several times. This happens when a change was introduced
on several release series at the same time.
For each version we list crucial changes from the previous
release. Hence when upgrading from one version to another, you have to
read bottom to top, starting from the section for the version you
upgrade from, and ending with the section you upgrade to.
Rather than repeating all instructions in this document, we link to
the appropriate sections of the release notes.
Releases
1.9.13
- A new index was added to the space manager database schema.
- ACLs are no longer supported with the PNFS name space backend.
- SRM returns SRM_FILE_UNAVAILABLE for unavailable files.
- Plain FTP defaults to using gPlazma for authentication.
- The misspelled property
gPlazmaNumberOfSimutaneousRequests is deprecated.
- ACL command lines tools have been merged into the Chimera client
tools.
1.9.12
- The arguments and behaviour of /opt/d-cache/bin/dcache create
pool have changed.
- The output of the /opt/d-cache/bin/dcache create pool has
changed.
- The script /opt/d-cache/install/install.sh has been
removed.
- The SRM no longer submits PostgreSQL specific vacuum
commands to the database.
- The output format of the PNFS manager info command has
changed.
- The info provider configuration file
/opt/d-cache/etc/glue-1.3.xml was replaced by
/opt/d-cache/etc/info-provider.xml. The file formats of the
two files are different.
- The database schema of the pin manager has changed and will be
updated on first start.
- The command line interface of the pin manager has changed
slightly.
- Several DNS lookups and reverse lookups have been eliminated. This
may affect installations on multihomed hosts.
- The configuration parameters httpHost,
xsltProcessor, xylophoneConfigurationDir,
xylophoneConfigurationFile, xylophoneXSLTDir,
saxonDir, srmJdbcMonitoringLogEnabled,
srmNumberOfDaysInDatabaseHistory,
srmOldRequestRemovalPeriodSeconds,
srmJdbcSaveCompletedRequestsOnly, srmJdbcEnabled,
and srmCleanPendingRequestsOnRestart are deprecated.
- The configuartion parameters srmVacuum,
srmVacuumPeriod, webdav.images.logo,
webdav.images.directory, webdav.images.file,
webdav.style.css, webdavLogoPath,
webdavDirIconPath, webdavFileIconPath,
webdavCssPath, dirIconPath, fileIconPath,
and cssPath are obsolete.
- The values of the configuration property broker.scheme
have changed: jms and hybrid have been replaced by
amq and cells+amq-embedded, respectively.
- SSH keys used by the admin door have moved from
/opt/d-cache/config/ to /opt/d-cache/etc/.
- Static content used for the httpd service has moved from
/opt/d-cache/docs/ to
/opt/d-cache/share/httpd/static/. Deployments that replace
any of these files have to be updated.
- The new pin manager requires at least PostgreSQL 8.3. The upgrade
will fail with older versions.
1.9.11
- Names of pool mover states have changed. Third party scripts may
need to be adapted.
- File size verification on SRM upload may now fail transfers that
would succeed with previous versions of dCache.
- Escape sequences in SURLs are now decoded correctly. Clients that
do not decode escape sequences and may have worked with previous
version of dCache may now fail. This only affects transfers of files
with SURLs containing escape sequences.
- Chimera settings have moved to the dCache configuration file. The
configuration likely needs to be adjusted during upgrade.
- The default database user name for Chimera has changed. The
configuration likely needs to be adjusted during upgrade.
- The Chimera client utilities have been moved to a different
directory.
- Upon upgrade the database schema of PinManager, SRM and transfer
managers will be updated.
- Some little used features of the pool group view have been
removed.
- Support for billing plots has been removed.
- Configuration parameters are no longer loaded into the context
environment of dCache domains. Third party scripts may be affected by
this change.
- The Berkeley DB version used on pools has been upgraded and the
new version uses an updated on disk format. The database is
automatically converted upon upgrade, but once converted it is no
longer possible to downgrade the pool. This only affects pools that
use the Berkeley DB meta data backend.
- The parameters of the command line dcache pool create
command have changed and third party scripts and documentation may
need to be updated.
1.9.10
- log4j was replaced by logback. As a consequence, logging
configuration files and admin commands have changed.
- The old HTTP door was removed.
1.9.9
- File system permission checks are now performed in PnfsManager: If
ACLs are enabled they now need to be configured in PnfsManager rather
than doors.
- The definition of mover queues on pools has changed. Pools that
define custom mover queues need to be reconfigured when upgrading.
- The pool commands p2p remove and p2p kill are
obsolete.
- The default value for the pool parameter
allowCleaningPreciousFiles has changed.
- Authorization of anonymous FTP clients has changed.
- Authorization of FTP clients with multiple FQANs has changed.
- dCache no longer supports Tomcat for hosting the SRM.
- The link group selection algorithm in the SpaceManager has
changed.
- The gPlazma module has been replaced by an embedded gPlazma cell
in each door domain.
- File ownership of new name space entries is now defined by the
subject creating the entry rather than inherited from the parent
directory.
1.9.8
- The default value of webdavAnonymousAccess has changed.
- The interpretation of xrootdAllowedPaths has changed.
- The authorization performed by the xrootd door has changed. You
may need to change the permissions of files exposed through the xrootd
door.
- The parameter gsiftpAllowPassivePool has been replaced by
ftp.proxy.on-active and ftp.proxy.on-passive.
- The default behaviour of FTP proxy mode has changed.
- The cleaner parameter useFilesystem has been removed.
- A default version of the file config/PoolManager.conf is
no longer included in the dCache package.
- Cell names of NFS doors have changed.
- Authorization of implicit space reservation has changed.
1.9.7
- Configuration files have changed: etc/node_config,
config/dCacheSetup, config/*.domains/ and
config/*.poollist are no longer used.
- All batch files have moved. Sites that deployed custom batch files
will have to refactor those to fit with the new configuration
files.
- Tomcat was replaced by Jetty as the SRM container.
- Pools using the Berkeley DB meta data store will be converted to a
new revision of the database library. The new version is backwards
compatible, however old versions are not forward compatible. Once
converted, one cannot downgrade the pool to earlier versions without
special steps.
- The logic for determining the IP and host name of multi-homed
machines has changed. There is a small risk that setups that worked by
accident in 1.9.6 will not work out of the box with 1.9.7.
- The definition of a volatile pool has changed slightly.
- The Chimera NFS 3 name space export daemon has been embedded into
dCache as a regular cell. The old init script is no longer
available.
- The old non-XSLT info provider has been removed. Use the new info
provider instead.
1.9.6
- Persistent command history in the admin door now needs to enabled.
- The output format of the ls command in the SRM cell has changed.
1.9.5
- If ACLs are used, they now also have to be configured in
PnfsDomain or ChimeraDomain, see Permission
Checking and ACLs.
- The configuration parameter PermissionHandlerDataSource
was removed, see Permission Checking and
ACLs.
- chimeraDomain no longer contains the directoryLookupPool
cell. Instead dirDomain has to be started.
- FTP doors no longer accept the -encp-put option.
- PnfsManager no longer accepts the -storageinfo-provider
option.
- The SpaceManagerDefaultAccessLatency parameter was
renamed to DefaultAccessLatencyForSpaceReservation.
1.9.4-2
- Chimera compatibility with PostgreSQL 8.1 has been restored.
1.9.4-1
- Chimera database schema changed. An SQL script must
be applied during upgrade.
- The new Chimera schema requires at least PostgreSQL 8.3. This is
fixed in 1.9.4-2.
- The xrootd door has been replaced with a new
implementation. dCacheSetup needs to be updated
to reference the new authorization plugin.
- As of version 1.9.4-1, dCache requires Java 6.
1.9.3-3
No changes to configuration files or database schemas.
1.9.3-2
No changes to configuration files or database schemas.
1.9.3-1
- We now verify that GSI Certificate Revocation Lists are up to date
and signing policies are enforced. You will see authentication
failures if the certificate revocation lists are not up to date.
- The legacy init scripts dcache-core and
dcache-pool have been removed.
- PID files have moved to /var/run/. Make sure dCache has
permission to write into this directory.
1.9.2-9
No changes to configuration files or database schemas.
1.9.2-8
No changes to configuration files or database schemas.
1.9.2-7
No changes to configuration files or database schemas.
1.9.2-6
No changes to configuration files or database schemas.
1.9.2-5
No changes to configuration files or database schemas.
1.9.2-4
No changes to configuration files or database schemas.
1.9.2-3
- The system wide default access latency and retention policy is now
defined by the PnfsManager. This requires changes
to dCacheSetup if PnfsManager and SRM run on different nodes.
- The format of the LinkGroup authorization file of the SRM space
manager has changed. If you use the SRM space manager, you will likely
have to update the authorization file. Check the release
notes for instructions.
- The /etc/grid-security/grid-vorolemap format has
changed. If you use VOMS based authorization, then the configuration
file will likely need to be updated. Check the release
notes for instructions.
- Chimera database schema changed. An SQL script must
be applied during upgrade.
- This version introduced a performance regression. The regression
was fixed in 1.9.2-6.
1.9.1-10
No changes to configuration files or database schemas.
1.9.1-9
No changes to configuration files or database schemas.
1.9.1-8
No changes to configuration files or database schemas.
1.9.1-7
No changes to configuration files or database schemas.
1.9.1-6
No changes to configuration files or database schemas.
1.9.1-5
1.9.1-4
- When upgrading from 1.9.1-1, 1.9.1-2 or 1.9.1-3, space reservation
accounting needs to be cleaned up. See the release
notes for details.
1.9.1-4
- When upgrading from 1.9.1-1, 1.9.1-2 or 1.9.1-3, space reservation
accounting needs to be cleaned up. See the release
notes for details.
-
1.9.1-3
No changes to configuration files or database schemas.
1.9.1-2
No changes to configuration files or database schemas.
1.9.1-1
- All logging is now done through log4j. Make sure you use
config/log4j.properties that is distributed with dCache. Make
sure that config/dCacheSetup in the java_options
variable contains the setting
-Dlog4j.configuration=file:${ourHomeDir}/config/log4j.properties. If
not, logging will be broken. See the release
notes for further details.
- The pool code was replaced. Several ancient features have been
removed. The output of the info command was changed, which
may break third party scripts.
- The new pool didn't work with the space manager. This was fixed in
1.9.1-4.
1.9.0-11
No changes to configuration files or database schemas.
1.9.0-10
- Chimera database schema changed. An SQL script must
be applied during upgrade.
- This version introduces a performance regression. The regression
was fixed in 1.9.0-11.
No changes to configuration files or database schemas.
1.9.0-9
No changes to configuration files or database schemas.
1.9.0-8
No changes to configuration files or database schemas.
1.9.0-7
No changes to configuration files or database schemas.
1.9.0-6
No changes to configuration files or database schemas.
1.9.0-5
No changes to configuration files or database schemas.
1.9.0-4
No changes to configuration files or database schemas.
1.9.0-3
No changes to configuration files or database schemas.
1.9.0-2
1.9.0-1
No mandatory changes to configuration files or database schemas.
- In etc/node_config, ADMIN_NODE was renamed to
NAMESPACE_NODE. ADMIN_NODE is deprecated and will be
removed at some point.