Main on dCache.org

Posts

Wed, 10 Jun 2020 00:00:00 +0000

News about dCache development, storage technology and life around it.

Downloads

Mon, 01 Jan 0001 00:00:00 +0000

Binary packages

v11.2.x Latest Golden Release
v11.1.x Feature Release
v11.0.x Feature Release
v10.2.x Golden Release
v10.1.x Feature Release
v10.0.x Feature Release
v9.2.x Golden Release

Unsupported releases

v9.1.x Feature Release
v9.0.x Feature Release
v8.2.x Golden Release
v8.1.x Feature Release
v8.0.x Feature Release
v7.2.x Golden Release
v7.1.x Feature Release
v7.0.x Feature Release
v6.2.x Golden Release
v6.1.x Feature Release
v6.0.x Feature Release
v5.2.x Golden Release
v5.1.x Feature Release
v5.0.x Feature Release
v4.2.x Golden Release

Plugins

CMS-TFC Plugin

v4.0.x for dCache 6.2+

dCache.org Official Signing Key

Download Key

pub rsa2048/0x3B97732D3321DE4C 2020-03-11 dCache (dCache.org Official Signing Key) <securityԹdcache.org>
Key Fingerprint =  5244 E542 ACB0 1347 D8E0 3DA1 3B97 732D 3321 DE4C

Source code

GitHub

Releases

Mon, 01 Jan 0001 00:00:00 +0000

Release policy

dCache follows a time-boxed two dimensional release policy. Every four months we produce a feature release. Feature releases have version numbers like 8.x.0, where x is a positive integer. A new feature release marks the start of a branch; for example, the release of dCache 8.1.0 marked the start of the 8.1-branch.

A feature release is followed up by a number of maintenance releases containing bug fixes or high priority feature tweaks. Maintenance releases for release 8.x.0 have version numbers 8.x.y, with y being some number larger than 0; for example, 8.1.0 is a feature release, 8.1.1 is the first maintenance release for the 8.1-branch and 8.1.2 is the second maintenance release.

Support period

Typically once a year, we designate one branch to a long-term supported release: a golden release. The only difference between long-term releases and other branches is the support period. A golden release is supported until the second subsequent long-term release, which is typically two years. Other branches are supported until the end of the previous golden release support period.

Choosing between golden releases and other branches is a matter of site policy and a matter of taste. Newer branches contain newer features, but they also have shorter support periods and often fewer dCache instances using them. However, upgrading from a golden release to a non-golden branch does not affect the end-of-support date.

Some sites use dCache that is repackaged by another distribution. Such a distribution may recommend a specific version. Sites should follow their distribution’s recommended version.

Upgrading

It is not just possible to upgrade from one feature release to the next one, but also from one golden release to the next. In oder to understand the implications and changes, one needs to read all release notes from the intermediate feature releases. We also usually provide an upgrade guide from one golden release to the next that highlights important and breaking changes.

Documentation

Mon, 01 Jan 0001 00:00:00 +0000

General

Installation and Getting started Tutorial for dCache
The Book - A general guide for administrators
UserGuide - A guide for getting the most out of dCache.

Publications

Manuals

The Ultimate Golden Release Upgrade Guide X - How to get from 10.2 to 11.2. And crucial changes from 9.2. This is a community supported document; our thanks to those who have contributed.
The Ultimate Golden Release Upgrade Guide IX - How to get from 8.2 to 9.2. This is a community supported document; our thanks to those who have contributed.
The Ultimate Golden Release Upgrade Guide VIII - How to get from 6.2 to 7.2. This is a community supported document; our thanks to those who have contributed.
The Ultimate Golden Release Upgrade Guide VII - How to get from 5.2 to 6.2. This is a community supported document; our thanks to those who have contributed.
The Ultimate Golden Release Upgrade Guide VI - How to get from 2.13 to 2.16. This is a community supported document; our thanks to those who have contributed.
The Ultimate Golden Release Upgrade Guide V - How to get from 2.10 to 2.13.
The Ultimate Golden Release Upgrade Guide IV - How to get from 2.6 to 2.10.
The Ultimate Golden Release Upgrade Guide III - How to get from 2.2 to 2.6.
The Ultimate Golden Release Upgrade Guide II - How to get from 1.9.12 to 2.2.
The Ultimate Golden Release Upgrade Guide I - How to get from 1.9.5 to 1.9.12.
dcap lib client API
dccp (dCache copy program)

Support

Mon, 01 Jan 0001 00:00:00 +0000

dCache.org issue tracking system

For all kinds of support requests, please send an e-mail to our ticket system support(at)dcache.org.

When sending bug reports please provide sufficient information for us to reproduce the problem. This should include:

The dCache version number.
The dcache.conf and layout files.
Log files, if they include unexpected entries, especially Java stack traces.
A brief description on how your setup looks like (doors, pools, services).

and of course a detailed description of your problem.

Please allow for two working days for the initial reply.

Security issues

The security related issues must be sent to security(at)dcache.org.

Mailing lists

For more general questions please subscribe to the dCache user forum by following the instructions below to ask questions to other dCache users. The developers also read and answer this list.

To subscribe/unsubscribe to one of the mailing lists above, send an e-mail by clicking below.

Subscribing to the user forum

To subscribe, send an email with the subject subscribe user-forum to user-forum-subscribe(at)dcache.org.

Unsubscribing from the user forum

To unsubscribe, send an email with the subject signoff user-forum to user-forum-unsubscribe(at)dcache.org.

About us

Mon, 01 Jan 0001 00:00:00 +0000

The goal of this project is to provide a system for storing and retrieving huge amounts of data, distributed among a large number of heterogenous server nodes, under a single virtual filesystem tree with a variety of standard access methods. Depending on the persistency model, dCache provides methods for exchanging data with backend (tertiary) storage systems as well as space management, pool attraction, dataset replication, hot spot determination and recovery from disk or node failures. Connected to a tertiary storage system, the cache simulates unlimited direct access storage space. Data exchanges to and from the underlying HSM are performed automatically and invisibly to the user. Beside HEP specific protocols, data in dCache can be accessed via NFSv4.1 (pNFS) as well as through WebDav. Read more »

Project partners and funding

dCache is a joint venture between the Deutsches Elektronen-Synchrotron, DESY, the Fermi National Accelerator Laboratory, FNAL and the Nordic e-Infrastructure collaboration, NeIC.

Contributing

As an open source project, dCache welcomes community contributions. It uses the linux kernel model where git is not only source repository, but also the way to track contributions and copyrights. A good place to start is our GitHub or the Developer’s Corner.

Where we are

Map of dCache installations around the world

Project status

Since the end of 2001 our full production release is in use at an increasing number of sites world-wide and is delivering petabytes of data from over hundreds of distributed server nodes.

Contact

support(at)dcache.org
security(at)dcache.org

Developer's Corner

Mon, 01 Jan 0001 00:00:00 +0000

dCache is an open source project that may be found on GitHub, which not only hosts the repository but is used to track contributions, copyright and issues. This page intends to summarize the basic information of interest for development, especially collect helpful links to repositories and tools. External contributions to the dCache project are welcome!

Getting started

Details on how to contribute a patch and our specific workflows can be found here.

Another document describes how to build dCache, which not only includes how to build various packages, but also how to create the system-test deployment, which provides a quick and easy way to create a small, ready-to-start test instance.

Workflows and best practices

Following the dCache release policy, several production branches are maintained at any point in time, including the lastest feature releases up to the newest golden release. Changes are first added to the master branch, bug fixes are then backported to supported branches and published as maintenance releases once a week.

In order to add a patch to the dCache codebase, external contributors must submit a pull request. Core team members use the Review Board software to inspect and discuss changes before allowing submission into the master branch.

Testing is an important aspect of software quality. We use JUnit for functional testing, SpotBugs for static code analysis and the Robot framework for black-box integration testing. When committing a patch to the GitHub repository, a continuous integration process is triggered that automatically builds dCache and runs this test suite to catch regression errors, giving feedback on the commit. This workflow is increasingly mirrored at and moved to our GitLab instance at DESY, where we are testing and deploying in kubernetes.

What to work on

There are three main areas that are addressed on on a regular basis. The first one is bug fixing – users open tickets or we discover issues ourselves that need to be corrected and backported. These issues are usually reported either via opening a GitHub issue, creating a ticket via our support(at)dcache.org mailing list or writing directly to our dev(at)dcache.org mailing list.

The second area is continual software maintenance, which includes keeping the used libraries and general code base up to date, but also experimenting with more modern approaches and frameworks for existing functionalities.

Lastly, dCache is enriched with new capabilities. These may be based on feature requests, for example via GitHub or discussions with users, but are also often motivated by the general roadmap of the dCache project. These goals that we set ourselves include extending functionality that certain components already have to other ones, anticipating upcoming developments of relevance for dCache and in general striving to make the lives of admins easier.

dCache core team meeting notes

The core development team meets weekly to discuss current issues and tickets, ongoing developments and future plans. The meeting notes are tracked in a GitHub repository that is accessible to core team members.

Release-notes

Mon, 01 Jan 0001 00:00:00 +0000

RSS Feeds

Mon, 01 Jan 0001 00:00:00 +0000

All The whole site as a feed
Posts Only news and technical posts
Releases Only releases