-
Notifications
You must be signed in to change notification settings - Fork 65
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
[New Hub] [Due by: 2024-12-06 ] [Spike: 30mins] Refine deployment phases - NASA-MAAP #5142
Comments
Note that there is two conflicting pieces of info here:
and
The VEDA hub is on the SMCE-VEDA account. None of us have access to the SMCE-MAAP account. So part of Phase 1 would be that one person gets access, and then creates accounts for every other engineer. |
Note we also have additional documentation for dealing with NASA SMCE aws accounts https://infrastructure.2i2c.org/hub-deployment-guide/new-cluster/smce/ |
@yuvipanda which 2i2c engineers already have SMCE "training" and access to the VEDA SMCE? we can request access to the MAAP SMCE for those same engineers, or new ones who do the "training" |
Given all of us have SMCE VEDA access, I think it means all of us already have the training. |
The following issues have been opened to track deployment of this new community, and prioritised accordingly in the Up Next column of the P&S board:
Please redirect any relevant conversation to the above issues |
A request (https://2i2c.freshdesk.com/a/tickets/2477) came in as part of NASA VEDA to deploy a new hub for MAAP:
Tasks
Tasks
Definition of Done
Each of the below phases for this new hub deployment should:
have an open issue,
have all the relevant information in the issue tables filled out and sections marked as READY,
have been placed in the Refined column of the Engineering board.
Phase 1
Phase 2
Phase 3
The text was updated successfully, but these errors were encountered: