CSH - Deeper dive on CryoCloud NSF ACCESS

[aprilmj]

Context

In https://2i2c.freshdesk.com/a/tickets/5762 Tasha asked for input on her NSF ACCESS request. Let's make sure CryoCloud is prepared for any transition issues they may run into as they move to a CloudBank allocation.

What we need to do

We expect cost data (both group and user level) to operate differently on CloudBank; I believe their approach to dashboards adds a layer over top of AWS' data.

That could have significant implications for CryoCloud and for other communities who aim to transition to NSF ACCESS allocations.

Definition of Done

• We understand the cost dashboard implications of transitioning from AWS commercial to AWS paid by NSF ACCESS allocation
• We and CryoCloud have a plan
• If we need to do development work, that work is described in our roadmap so it can be funded
• Lessons learned have been documented and sharable with other communities

[2i2c-Bot]

🔗 Asana task created for Community Success Hours

This issue has been synced to Asana: https://app.asana.com/0/1213265455732675/1215515717277881

Automated by csh-sync

[yuvipanda]

Needs 2i2c-org/initiatives#35 for cost monitoring to work there. I believe we have done this work before for victor, and records there may have more information.