Difference between revisions of "DCache.org"
Jump to navigation
Jump to search
| Line 87: | Line 87: | ||
* [[HowTo: CMS XRootD configuration]] '''(obsolete)''' | * [[HowTo: CMS XRootD configuration]] '''(obsolete)''' | ||
| − | == dCache Advanced Administration == | + | == dCache Advanced Administration == |
* [[dCache Metadata Commands]] | * [[dCache Metadata Commands]] | ||
* [[dCache Administration Console Commands]] | * [[dCache Administration Console Commands]] | ||
| − | * [[Monitoring dCache with ELK]] | + | * [[Monitoring dCache with ELK]] '''(obsolete)''' |
== Alarms == | == Alarms == | ||
Latest revision as of 15:16, 13 June 2022
Become a dCache Administrator at PIC
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:
- Whenever you want, whenever you need.
- Recommended to test with Enstore before upgrading the Development instance
- Recommended to backup DBs for rolling back upgrades.
- Upgrade requirements:
- 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:
- Always upgrade before upgrading the dCache production instance.
- Upgrade only as the last validation for the dCache upgrade procedure, just before upgrading the production instance.
- Only upgrade when no Enstore interventions / changes are expected until the production instance is upgraded.
- Upgrade requirements:
- Always ask to the Enstore admin if upgrades can be performed in the the Development instance.
- 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:
- Always upgrade after upgrading and validating the upgrade for the dCache development instance.
- Upgrade always ensuring that Enstore client and service was already tested in the test and development instances.
- Upgrade requirements:
- Always ask to the Enstore admin if upgrade can be performed in the the Production instance.
- 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:
- 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:
- For major release upgrades, always inform the CMS Contact and CMS MWR team.
- Ensure that there are always DB backups before upgrading the instance.
Service Administration
gPlazma
- HowTo: Configuring gPlazma (obsolete)
Pools Management
- Data Migration:
dCacheAdmin
SRM
Billing
Info Provider
Alarms
dCache + Enstore Administration
Doors
NFSv3/NFSv41 Service in dCache
HowTo: Exporting a new dCache NFS directory (obsolete)
WebDAV
CMS XRootD
- HowTo: CMS XRootD configuration (obsolete)
dCache Advanced Administration
- dCache Metadata Commands
- dCache Administration Console Commands
- Monitoring dCache with ELK (obsolete)