Start uploading production data to tape storage at NESE

[landreev]

We have the first batch of data to upload there: https://fly.cs.umb.edu/omama/
We will use it to resolve and iron out any technical kinks in the workflow, and to develop service policies for future use and for offering it to clients.

[cmbz]

2024/03/21

• Related: Project: Pilot Large Data Support Service dataverse-pm#178
• Prioritized as part of pilot, moved to Needs Sizing

[landreev]

I put a size 10 on it for now. I am actively working/focusing on this, so probably needs to be in progress.

[landreev]

Got the new (prod.) NESE end point set up and the new service account and the app client given the right permissions on their end. Everything is seemingly configured identically to how the DEMO tape was set up. Tried the first upload in prod. - it bombed. Trying to figure out what's going on and what is different from that demo configuration that is known to work.
Reached out to Jim and Victoria, in case they can help me diagnosing it. But at least I have something to work with now. Will try to resolve it asap.

[landreev]

Got the globus app to work.
Can now upload data to the production tape. Everything is working like a charm when I'm doing it from my own Dataverse instance. With our actual prod. instance, something is failing in the very last step, when Dataverse just needs to register the file in its own database.
Working on figuring this part out. We are very close. 🥲

[landreev]

OK, we are in business of uploading serious prod. data.
These are the first bundles of 2D images from the Omama collection:

[landreev]

One remaining task (other than uploading the second OMAMA dataset-worth of data which is pending on local delivery) is to get the globus app to work properly in prod. for redirecting _down_load requests for NESE-stored objects.

[landreev]

The OMAMA dataset mentioned above: https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/KXJCIU&version=DRAFT
Thinking of closing the issue since the tasks outlined above have been completed. Will be opening new issues for next steps and phases of the effort. The most important one being developing a doc. guide for future customers of this big data-to-tape storage service.