Skip to content

Commit 9aca9eb

Browse files
bari12agheata
andauthored
Rucio GSOD proposal 2020 (#760)
* Added Rucio GSOD proposal 2020 * Added mentors; Updated logo path * Sorted mentors Co-authored-by: Andrei Gheata <[email protected]>
1 parent f12c2e8 commit 9aca9eb

File tree

4 files changed

+58
-1
lines changed

4 files changed

+58
-1
lines changed
+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
project: Rucio
3+
layout: default
4+
logo: RUCIO-logo.jpg
5+
description: |
6+
[Rucio](https://rucio.cern.ch/) is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customisable policies. The data can be spread across globally distributed locations and across heterogeneous data centers, uniting different storage and network technologies as a single federated entity. Rucio offers advanced features such as distributed data recovery or adaptive replication, and is highly scalable, modular, and extensible. Rucio has been originally developed to meet the requirements of the high-energy physics experiment ATLAS, and is continuously extended to support LHC experiments and other diverse scientific communities.
7+
---
8+
9+
{% include gsdocs_project.ext %}
+47
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: Rucio - Exascale data management
3+
layout: gsdocs_proposal
4+
project: Rucio
5+
year: 2020
6+
organization:
7+
- CERN
8+
---
9+
10+
## Description of project idea
11+
12+
Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customisable policies. The data can be spread across globally distributed locations and across heterogeneous data centers, uniting different storage and network technologies as a single federated entity. Rucio offers advanced features such as distributed data recovery or adaptive replication, and is highly scalable, modular, and extensible. Rucio has been originally developed to meet the requirements of the high-energy physics experiment ATLAS, and is continuously extended to support LHC experiments and other diverse scientific communities. For example, the ATLAS experiment orchestrated an Exabyte of data transfer and processing and is growing rapidly.
13+
14+
The current documentation is available from multiple places and in different formats, including [scientific articles](https://arxiv.org/abs/1902.09857), [readthedocs.io](https://rucio.readthedocs.io/en/latest/) with source in the [code](https://github.com/rucio/rucio/tree/master/doc/source), [Google Drive](https://drive.google.com/drive/folders/1EEN8l1dFjDSgavPrAMMooDjEodHP7aU7?usp=sharing), [Github](https://github.com/rucio/rucio), [DockerHub](https://hub.docker.com/u/rucio), or [Wikis](https://twiki.cern.ch/twiki/bin/view/AtlasComputing/AtlasDistributedComputing). This dispersion and diversity makes it difficult to pinpoint information and to recognise which information is outdated or superseded, wrong, or simply lacking in detail. Especially in Wikis the information is usually directed towards a single experiment instance of Rucio, however the underlying concepts can be applicable to multiple different instances.
15+
16+
With this proposal we aim to achieve the following tasks:
17+
18+
* Due to this wide dispersion of different documentation pieces, we want to move our documentation to one central place. Possibly based on mkdocs, but we are open to other documentation technology.
19+
* Restructure the documentation into clear and distinct parts. (User Howtos, Setup and tutorials, Operators documentation, Developer documentation, etc.)
20+
* Consolidate the different sources and integrate them into this new structure.
21+
* Write new documentation, to connect the different pieces where applicable.
22+
23+
## Project duration
24+
25+
We are open to both 3 month and 6 month projects, depending on what you think is required to achieve these tasks.
26+
27+
## Related material
28+
29+
- [Rucio Website](https://rucio.cern.ch)
30+
- [Rucio Documentation](https://rucio.readthedocs.io/en/latest/)
31+
- [Rucio Documentation Source](https://github.com/rucio/rucio/tree/master/doc/source)
32+
- [Rucio Journal Article](https://arxiv.org/abs/1902.09857)
33+
- [Rucio Github](https://github.com/rucio/rucio)
34+
- [Rucio Docker](https://hub.docker.com/u/rucio/)
35+
- [Rucio Workshop 2018](https://indico.cern.ch/event/676472/)
36+
- [Rucio Workshop 2019](https://indico.cern.ch/event/773489/)
37+
- [Rucio Workshop 2020](https://indico.cern.ch/event/867913/)
38+
39+
## Expected results
40+
One central documentation page servicing the different types of users. The different existing documentation sources should all be consolidated in this documentation page and restructured. New documentation, especially to support the information flow, should be written.
41+
42+
## Experience required
43+
General knowledge of Python, Docker, GIT is required.
44+
45+
## Mentors
46+
* [Martin Barisits](mailto:[email protected]), CERN
47+
* [Mario Lassnig](mailto:[email protected]), CERN

gsdocs/2020/mentors.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,9 @@ layout: plain
55

66
## Full Mentor List (Name, Email, Org)
77

8+
* Martin Barisits [[email protected]](mailto:[email protected]) CERN
89
* Olivier Couet [[email protected]](mailto:[email protected]) CERN
10+
* Mario Lassnig [[email protected]](mailto:[email protected]) CERN
911
* Axel Naumann [[email protected]](mailto:[email protected]) CERN
1012
* Paul Schütze [[email protected]](mailto:[email protected]) DESY
1113
* Simon Spannagel [[email protected]](mailto:[email protected]) DESY
12-

images/RUCIO-logo.jpg

133 KB
Loading

0 commit comments

Comments
 (0)