Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documenting comprehensive and complete story #33

Closed
MattSlm opened this issue Mar 24, 2022 · 1 comment
Closed

Documenting comprehensive and complete story #33

MattSlm opened this issue Mar 24, 2022 · 1 comment
Assignees

Comments

@MattSlm
Copy link
Collaborator

MattSlm commented Mar 24, 2022

Quoting Jordi:
"Thanks @MattSlm. Is this the umbrella ticket we discussed to write a user friendly document explaining the complete story? If so, at a high level the idea here will be:

The story starts from the very beginning (LHC experiment collides atoms generating gigantic datasets, see for instance https://cds.cern.ch/record/2276551)
The datasets are kept in storage.
The Rucio server replicates the datasets to various nodes
Scientists download datasets by choosing from the various available replicas.
Scientists can use ALTO to optimize the download decision
At each step, please specify the protocols that are being used (e.g., xrootd, Rucio, ALTO).

Suggest that URLS to the various protocol documents be included (xrootd, Rucio, RFCs, etc.) so a reader can dig more into them if he/she wants to learn about the details.

Please also use our hackathon example network to illustrate at each step how things get done (file upload, download, etc.):

              Rucio
      1Mbps    |     5Mbps
      25ms     |     25ms
  s1 --------- s3 ----------- s4 -- XRD3
  |            |              |
  |            | 25ms         | 50ms
  |            | 1Mbps        | 2Mbps
  |            |              |
 XRD1          s2 -- XRD2     s5 -- XRD4

Can I suggest that in the above diagram we separate the Rucio server from the Rucio client (where the scientist is located)? I think it will make it more realistic and functionally easier to understand. (Note: I have created a ticket to modify the network configuration to accommodate for this change: #31)

The document should be written so that both a non-technical person can understand the story flow and a also for a technical person to understand how the various protocols are used end-to end. So good artistic writing skills are needed there :)

The story should also be written in a compelling manner, motivating the use case and the benefits of using ALTO. Thks."

@MattSlm MattSlm self-assigned this Mar 24, 2022
@MattSlm MattSlm moved this from Todo to In Progress in IETF Hackathons: OpenALTO Mar 29, 2022
@MattSlm MattSlm moved this from In Progress to In Code Review in IETF Hackathons: OpenALTO May 26, 2022
@MattSlm MattSlm moved this from In Code Review to In Progress in IETF Hackathons: OpenALTO May 26, 2022
@fno2010 fno2010 moved this from In Progress to Done in IETF Hackathons: OpenALTO Jul 11, 2022
@fno2010
Copy link
Member

fno2010 commented Jul 11, 2022

Closed by PR #44

@fno2010 fno2010 closed this as completed Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants