Proposed EOS/CTA production setup: Hardware, capacity, configuration

• Julien Leduc (CERN)

Room: 31/S-027

Migration of CASTOR metadata

• Michael Davis (CERN)

Room: 31/S-027 - Analysis of CASTOR/CMS namespace (directories, files, users, groups, etc) - handling special cases (symlinks, POSIX permissions/ACL's, zero-length files, empty directories) - Read-only pre-import onto EOSCTA for validation - Migration milestones

Current CASTOR use cases and their translation into CTA Room: 31/S-027 Which ones will be taken over by Rucio and which ones will require direct EOS/CTA access? :- - pit->T0 transfers - QA checks - local users with CASTOR home directories

Others (time permitting) Room: 31/S-027 CASTOR vs EOS/CTA configuration: - CMS service classes, file classes, tape pools in CASTOR; their equivalents in CTA and how to select/set them - CMS CASTOR migration and recall policies and their equivalents in CTA FTS specifics for CTA: - disk buffer eviction, request canceling, handling GC, checking for tape residency