Cloud computing offers unparalleled flexibility, a constantly increasing set of “Infrastructure As A Service’’ capabilities, resource elasticity and security isolation. One of the most significant barriers in astronomy to wholesale adoption of cloud infrastructures is the cost for hot storage of large datasets - particularly for Rubin, a Big Data project sized at 0.5 Exabytes (500 Petabytes) over the duration of its 10-year mission. We are planning to reconcile this with a “hybrid” model where user-facing services are deployed on Google Cloud with the majority of data holdings residing in our on-premises Data Facility at SLAC. We discuss the opportunities, risks, and technical challenges of this approach.
- Live drafts: https://dmtn-287.lsst.io
- GitHub: https://github.com/lsst-dm/dmtn-287
This repository includes lsst-texmf as a Git submodule. Clone this repository:
git clone --recurse-submodules https://github.com/lsst-dm/dmtn-287Compile the PDF:
makeClean built files:
make cleanA table of the technote's acronyms and their definitions are maintained in the acronyms.tex file, which is committed as part of this repository. To update the acronyms table in acronyms.tex:
make acronyms.texNote: this command requires that this repository was cloned as a submodule.
The acronyms discovery code scans the LaTeX source for probable acronyms. You can ensure that certain strings aren't treated as acronyms by adding them to the skipacronyms.txt file.
The lsst-texmf repository centrally maintains definitions for LSST acronyms. You can also add new acronym definitions, or override the definitions of acronyms, by editing the myacronyms.txt file.
lsst-texmf includes BibTeX files, the lsstdoc class file, and acronym definitions, among other essential tooling for LSST's LaTeX documentation projects. To update to a newer version of lsst-texmf, you can update the submodule in this repository:
git submodule update --init --recursiveCommit, then push, the updated submodule.