Skip to content
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

Closed
2 tasks done
jmunroe opened this issue Nov 19, 2024 · 6 comments
Closed
2 tasks done
Assignees

Comments

@jmunroe
Copy link
Contributor

jmunroe commented Nov 19, 2024

A request (https://2i2c.freshdesk.com/a/tickets/2477) came in as part of NASA VEDA to deploy a new hub for MAAP:

We would like to stand up a new JupyterHub to support the Multi-Mission Algorithm and Analysis Platform (MAAP) project. Below is relevant information I found referencing an earlier ticket

Community representative
@wildintellect
@freitagb

Hub important dates
Target Start Date: 2024-12-06
Required Start Date: 2025-01-06

Hub Authentication Type
GitHub

First Hub Administrators
Alex Mandel (@wildintellect)
Brian Freitag (@freitagb)

Hub logo image URL

https://maap-project.org/wp-content/uploads/2021/10/nasamaaplogo3.png

Hub logo website URL

https://maap-project.org/

Extra features to enable

Please replicate the current VEDAHub infrastructure

Cloud Provider
AWS

Cloud Region
us-west-2

Billing and cloud account
SMCE-MAAP account

Other relevant information
This hub deployment request is part of 2i2c's ongoing NASA VEDA project. The ESDIS hub will be launched with configuration and image based on the VEDAHub. The hub should be deployed in the NASA SMD cluster where 2i2c is currently operating the NASA VEDA hub.

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

@yuvipanda
Copy link
Member

Note that there is two conflicting pieces of info here:

The hub should be deployed in the NASA SMD cluster where 2i2c is currently operating the NASA VEDA hub.

and

Billing and cloud account
SMCE-MAAP account

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.

@yuvipanda
Copy link
Member

Note we also have additional documentation for dealing with NASA SMCE aws accounts https://infrastructure.2i2c.org/hub-deployment-guide/new-cluster/smce/

@wildintellect
Copy link
Contributor

wildintellect commented Nov 19, 2024

@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"

@yuvipanda
Copy link
Member

Given all of us have SMCE VEDA access, I think it means all of us already have the training.

@sgibson91 sgibson91 self-assigned this Nov 22, 2024
@wildintellect
Copy link
Contributor

@freitagb I think you need to email SMCE for this request (cc: @jjfrench)

@sgibson91
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants