-
Notifications
You must be signed in to change notification settings - Fork 11
Create production_liasion_guidelines.md #57
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
base: master
Are you sure you want to change the base?
Conversation
|
||
### Send Information | ||
|
||
Run the following command and email the output to `[email protected]`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we get a workflow for this that doesn't depend on a single person but is routed through service now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
create a incident at Jlab service now.
(this requires Jlab account)
|
||
Then you can transfer the files from the source location to desired directory structure on JLAB RSE following the [input pre-processing guidelines](https://eic.github.io/epic-prod/documentation/input_preprocessing.html). Make sure that the dataset can be traced to a version controlled github repo before this transfer happens because you will need the version tag for the directory structure and nomenclature. An example of the transfer is shown here: | ||
``` | ||
python /opt/campaigns/hepmc3/scripts/register_to_rucio.py \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use an example that will always work because people will run this. Need access to file to upload. Need to avoid did clashes. Prefer to just upload a small file to a date-stamped temporary did 'directory'.
Briefly, what does this PR introduce?
Create guidelines for production liasions
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
Does this PR change default behavior?