This is mentioned on the page but it’s easy to miss.
For the current status of tape storage at CERN see: https://indico.cern.ch/event/1471803/contributions/6967379/a...
For reference, most disk storage for physics data uses an in-house solution called EOS: https://eos-web.web.cern.ch/eos-web/
"As of June 29th 2020, CTA, the CERN Tape Archive, started to be operated as the successor of CASTOR and gradually replaced it."
(looks like this submission uses https://castor.web.cern.ch/content/home.html instead of https://castor.web.cern.ch/castor/ the second link does not have the broken image)
With another 4PB available which can be processed on request to extract samples of interest: https://opendata.cern.ch/docs/lhcb-releases-service-to-acces...
https://gitlab.cern.ch/cta/CTA
Its memory is still alive in CTA, however:
https://gitlab.cern.ch/cta/CTA/-/blob/main/catalogue/TapeSea...
Tape is boring but when an intern / AI / tectonic plate accidently destroys your database setup it is a huge lifesaver
Anybody know what these fancy Oracle tapes are? Is it just their implementation of a regular standard?
There isn’t a recording but slides at linked from that page.
Wouldn't have been my choice for a software project :-)
And to keep this thread, I think our three languages should count as one, because at least 20 years ago, it was quite common to have Portuguese, Italian and Spanish mingle in several activities.
Source, ATLAS TDAQ/HLT Alumni.
- CASTOR at CERN had also its disk centric derivative named DPM (Disk pool manager) that helped to power the LHC computing grid for multiple decades (WLCG) before getting deprecated.
- Interestingly DPM had an architecture quite aligned with the original Google File system even if developed completely separately: (One metadata node, multiple disk node. Design to do Write-once-read-many with very partial POSIX semantics).
- The LHC computing Grid is an association of research centers with their own infrastructure. As such, they had (historically) many diffent storage systems with diffent protocols and interface.
- To unify this madness, an attempt to do a "standard" protocol was made in the 2000s: the SRM protocol (storage resources manager). In a pure XKCD fashion, it went as bad as you can imagine. It tried to rely on the tech of the time (XML, SOAP, WSDL) and is a school case of terrible protocol design (bloated, slow, weak consistency, massive server overhead, stupidly complex to implement and quite insecure). The spec are worth a read if you want a good laugh [1].
- After 20y of struggle, SRM was eventually dropped for a more pragmatic and ad hoc solution based on HTTP + xrootd [2]. EOS itself uses xrootd quite extensively. (if this did not change)
- The history of computing at CERN is globally interesting because it is a pretty good image of the evolution of computing and of the "tech fashions" associated with it.
[1]: https://sdm.lbl.gov/srm-wg/doc/SRM.spec.v2.1.1.html
[2]: https://xrootd.org/