Storage section

[s-sajid-ali]

make HPC storage section in https://nyu-its.github.io/rts-docs-dev/docs/hpc/storage/intro/

• Storage intro
• fix storage intro 2 column layout
• Hardware Specs (Available Storage Systems now)
• Best Practices
• Storage Status
• Data Management
• Data Transfers
• Sharing Data on HPC
• Research Project Space (RPS)
• fix RPS Google sheet placeholder
• Datasets
• Globus
• Large number of small files
• Transferring Cloud Storage Data with rclone
• move 3/11 to 4/1 (datasets is currently under storage)

Also:

• Tools and Software - Software on Greene
• Tools and Software - Singularity: Run Custom Applications with Containers

[RobJY]

Hi @s-sajid-ali, I've got a couple questions about the Research Project Space page I'm working on.

1. It has an embedded Google spreadsheet,
   but when I go to 'Publish to Web' it says This document is not published to the web. so I wanted to make sure it's ok to publish it, even though it looks like it's already published. Apologies for checking, but I'd rather err on the side of caution.

2. Here's a google slide that says it's not shared, but looks like it is: https://sites.google.com/nyu.edu/nyu-hpc/training-support/tutorials/containers-on-the-hpc. Please confirm that it's ok to share this. Thanks!

3. One of the questions in the FAQ section is:
   How can I find out how much of the storage and inodes have I used in my lab RPS volume with the answer TBD. Any idea if there's a way to do this or who I could contact to check?

Thanks!

[RobJY]

The storage into page has a 2 column layout that I'm having trouble duplicating in Docusaurus. Is the current single column solution ok? I can keep working on getting the 2 column version working, but didn't want to spend too much time on it if it's not something we want to continue using.

I guess I could put the 2 columns into a table, but that seems a little clunky.

[RobJY]

The Data Management page has an embedded iframe that contain a Google sheet with details about mount points and their purpose, quota, etc. Does this change often or is it needed in lots of other places? If not, maybe a native table with this information would be better?

[s-sajid-ali]

It has an embedded Google spreadsheet,
but when I go to 'Publish to Web' it says This document is not published to the web. so I wanted to make sure it's ok to publish it, even though it looks like it's already published. Apologies for checking, but I'd rather err on the side of caution.

I agree that it's better to leave it as a link that can require logging into Google with a valid nyu.edu email address rather than having it display the information publicly.

Here's a google slide that says it's not shared, but looks like it is: https://sites.google.com/nyu.edu/nyu-hpc/training-support/tutorials/containers-on-the-hpc. Please confirm that it's ok to share this. Thanks!

This is fine to share publicly. It would be good to have this as a tutorial section as well.

How can I find out how much of the storage and inodes have I used in my lab RPS volume

They ask us for now.

The storage into page has a 2 column layout that I'm having trouble duplicating in Docusaurus. Is the current single column solution ok? I can keep working on getting the 2 column version working, but didn't want to spend too much time on it if it's not something we want to continue using.

Sure, we can edit it later.

The Data Management page has an embedded iframe that contain a Google sheet with details about mount points and their purpose, quota, etc. Does this change often or is it needed in lots of other places? If not, maybe a native table with this information would be better?

Embedding the iframe is fine for now. @kapuic can migrate that to a native table later.

[RobJY]

Sounds good. Thanks for your help with this @s-sajid-ali !

Please take a look to make sure I've handled those embedded iframes correctly and that the link for the Current HPC RPS Stakeholders is correct when you've got time. I'll go ahead and make a draft PR for this to check the linting and hopefully this will be ready to merge soon.

[RobJY]

related PR (#65) was merged, so I'm closing .