Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
cta
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dCache
cta
Commits
cc37be35
Commit
cc37be35
authored
6 years ago
by
Eric Cano
Browse files
Options
Downloads
Patches
Plain Diff
Added detailed migration from CASTOR side.
parent
cccbc256
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/migration/migrationFromCASTOR.md
+24
-0
24 additions, 0 deletions
doc/migration/migrationFromCASTOR.md
with
24 additions
and
0 deletions
doc/migration/migrationFromCASTOR.md
+
24
−
0
View file @
cc37be35
...
...
@@ -71,6 +71,30 @@ Any?
2.
Migrate new CTA data and CTA-repacked CASTOR data to CASTOR
2.
Remove immmutable flag from CTA files.
## CASTOR side scenarios
1.
Stager shutdown means no read, no write, but move and delete are still possible (nameserver operations).
Other scenario:
1.
Remove write rights for CASTOR
1.
B/W lists in stager
2.
archive route removal
3.
Tapes marked readonly (FULL|RDONLY) (option new state/column in the DB)
4.
Expriment commit to not change the files (we rely on this)
2.
ND import for CASTOR to CTA
1.
import to EOS NS in parallel to next
2.
import to CTA catalogue
3.
Tapes in CTA are disabled
4.
Tapes in CASTOR are readonly
3.
Switch ownership of tapes
1.
Marked are exported in CASTOR
2.
Mark tapes as readonly on CTA
3.
Mark all files in CASTOR "EXPORTED" as in CTA
4.
Look in CASTOR NS logs for renames/delete (and apply to CTA?)
5.
Scan CASTOR NS for differences
## Other requirements
Monitoring of files on tape should be created in continuity with CASTOR's.
## Redirector and experiment workflow effects
## Rollback
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment