DCache.org

Become a dCache Administrator at PIC

• HowTo: dCache Management - GIT + Puppet

Management tools

• HowTo: Accessing to the dCache Admin Console
• HowTo: Installing & Configuring PCells to Administrate dCache (obsolete)

Instances

Test instance

• Version: this can be higher than the production instance.
• Needed for: test newer dCache releases.
• When to upgrade:

1. Whenever you want, whenever you need.
2. Recommended to test with Enstore before upgrading the Development instance
3. Recommended to backup DBs for rolling back upgrades.

• Upgrade requirements:

1. No requirements.

Development instance

• Version: should be always the same as the production instance
• Needed for: this instance is used in order to test Enstore with the dCache version running in production.
• When to upgrade:

1. Always upgrade before upgrading the dCache production instance.
2. Upgrade only as the last validation for the dCache upgrade procedure, just before upgrading the production instance.
3. Only upgrade when no Enstore interventions / changes are expected until the production instance is upgraded.

• Upgrade requirements:

1. Always ask to the Enstore admin if upgrades can be performed in the the Development instance.
2. Ensure that there are always DB backups before upgrading the instance.

Production instance

• Version: Any Golden or Production release.
• Needed for: production services.
• When to upgrade:

1. Always upgrade after upgrading and validating the upgrade for the dCache development instance.
2. Upgrade always ensuring that Enstore client and service was already tested in the test and development instances.

• Upgrade requirements:

1. Always ask to the Enstore admin if upgrade can be performed in the the Production instance.
2. Ensure that there are always DB backups before upgrading the instance.

CMS MWR (MiddleWare Readiness) instance

• Version: Latest dCache version.
• Needed for: CMS MRW tests (Debug)
• When to upgrade:

1. Whenever a new release is available is recommended to upgrade. However, there is no a strict requirement and you can wait few days / weeks before upgrading.

• Upgrade requirements:

1. For major release upgrades, always inform the CMS Contact and CMS MWR team.
2. Ensure that there are always DB backups before upgrading the instance.

Service Administration

gPlazma

• HowTo: Configuring gPlazma (obsolete)

Pools Management

• Data Migration:

• HowTo: Migrate dCache Pool
• HowTo: Permanent Migration to dCache Read Only Pools

• HowTo: srm22 - Generating poolmanager.conf & LinkGroupAuthorization.conf

• HowTo: Adding/Removing pools to a VO

dCacheAdmin

• HowTo: Configure SSH2 access to the Admin Console

SRM

• HowTo: Managing Space Reservation (Tokens)

Billing

• HowTo: Reset Billing PostgreSQL
• HowTo: Clean old Billing PostgreSQL records

Info Provider

• HowTo: Publishing dCache Information

dCache + Enstore Administration

• HowTo: Managing Tape File Families in dCache

Doors

NFSv3/NFSv41 Service in dCache

HowTo: Exporting a new dCache NFS directory (obsolete)

WebDAV

• HowTo: WebDAV properties:

• File Checksum check via WebDAV

CMS XRootD

• HowTo: CMS XRootD configuration (obsolete)

dCache Advanced Administration

• dCache Metadata Commands
• dCache Administration Console Commands
• Monitoring dCache with ELK (obsolete)

Alarms

• DCACHE_CHECK_POOL_BTREE_MEMORY
• DCACHE_CHECK_POOL_METADATA

Others

• dCache OpenID Connect