Open elopatin-uc3 opened 4 years ago
From Scott: " these are the non-Dryad collections we have configured in our application from the old Dash."
dataone.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/dataone_dash" lbnl.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/lbnl_dash" ucb.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucb_dash" ucd.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucd_lib_dash" uci.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/uci_dash" ucla.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucla_dash" ucm.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucm_dash" ucop.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucop_dash" (not enabled) ucpress.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucpress_dash" ucr.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucr_lib_dash" ucsb.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucsb_dash" ucsc.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucsc_dash" ucsf.yml: endpoint: "http://mrtsword.cdlib.org:39001/mrtsword/collection/ucsf_lib_datashare"
@dloy I've updated this ticket with ARK information for all DASH collections. Once a procedure is documented, these are the collections to start replication to Dryad first, followed by flipping the primary node.
@dloy Scott confirmed with Daniella that the UCOP and UC Press Dash collections should be treated the same as all of the others; no differences in terms of replication or migration.
Related to #482
Moving this off the project board and back to the Merritt Futures board, for when we begin dealing with the other collections that have their primary object copies in S3.
Summary
A series of 44 collections that are owned by CDL and campuses continue to use S3 as their primary storage node. The total storage capacity used by these collections as of March 2020 is 5.6TB. For the purpose of cost savings and simplification, the majority of these collections should be reconfigured to use Minio as a primary storage node, with Glacier and Wasabi as secondary nodes. In some cases, ownership changes will also be needed in the Inventory database (e.g. Dash > Dryad).
High-priority Collections
The first collections to migrate will be the existing Dash collections. They also require an ownership change. All Dash collections should migrate from primary node 5001, to primary node 3041.
Tasks