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

[Request deployment] New Hub: EarthScope #3394

Closed
2 of 7 tasks
colliand opened this issue Nov 9, 2023 · 12 comments · Fixed by #3530
Closed
2 of 7 tasks

[Request deployment] New Hub: EarthScope #3394

colliand opened this issue Nov 9, 2023 · 12 comments · Fixed by #3530
Assignees
Labels
new hub For issues that request a new hub deployment

Comments

@colliand
Copy link
Contributor

colliand commented Nov 9, 2023

The GitHub handle of the community representative

@timdittmann

Hub important dates

  • Target Start Date: 2023-12-07
  • Required Start Date: 2023-12-15

Hub Authentication Type

Other (may not be possible, please specify in comments)

First Hub Administrators

[GitHub Auth only] How would you like to manage your users?

None

[GitHub Teams Auth only] Profile restriction based on team membership

No response

Hub logo image URL

pending

Hub logo website URL

https://www.earthscope.org/

Hub user image GitHub repository

pending

Hub user image tag and name

pending

Extra features you would like to enable

  • Dedicated Kubernetes cluster
  • Scalable Dask Cluster

(Optional) Preferred cloud provider

AWS

(Optional) Preferred cloud region

pending

(Optional) Billing and Cloud account

I need help figuring out the billing and cloud accounts

Other relevant information to the features above

This hub will be deployed with special access methods based on Auth0. In January 2024, this hub will be enriched with token passing from Auth0 to allow users to access restricted EarthScope resources. These aspects have been discussed with @yuvipanda and members of the EarthScope team.

EarthScope will provide 2i2c's engineering team with access to the cloud infrastructure and Auth0 accounts required to set up this customized research hub.

Tasks to deploy the hub

  • 1. Deploy information filled in above
  • 2. Engineer who will deploy the hub is assigned
  • 3. If using GitHub Orgs/Teams Auth, Engineer is given Owner rights to the org to set this up.
  • 4. Initial Hub deployment PR
  • 5. Administrators able to log on -> Hub now in steady-state
@colliand colliand added the new hub For issues that request a new hub deployment label Nov 9, 2023
Copy link

github-actions bot commented Nov 9, 2023

Hey @timdittmann and @colliand! 👋
I noticed there is still pending information about the new hub deployment.
Can you please help us fill it in?

The information pieces still missing, are:
- hub logo image url
- hub user image github repository
- hub user image tag and name

Details about each of them can be found in the top comment. But if you have questions about any of them, please ping the 2i2c/engineering team and they will help you.

After the form in the top comment is filled in, an engineer will be assigned and will start deploying the new hub 🚀. Thank you!

@damianavila
Copy link
Contributor

This is assigned to be worked on by @AIDEA775 with support from @yuvipanda (who already have more context from previous discussions).

AFAIK, the scope of this new hub request is to deploy a daskhub in a new dedicated AWS cluster.
Ale will be doing this deployment for the first time and Yuvi is going to help him in any blockage he may have.

EarthScope will provide 2i2c's engineering team with access to the cloud infrastructure and Auth0 accounts required to set up this customized research hub.

@colliand, can you please make sure the community representatives provide the needed AWS account details and credentials so we can start with this deployment ASAP? Thanks!

@damianavila damianavila assigned AIDEA775 and colliand and unassigned damianavila Nov 28, 2023
@yuvipanda
Copy link
Member

I just pinged them on email as well to get the AWS account setup.

@damianavila
Copy link
Contributor

@AIDEA775, any updates on this one? I think the AWS credentials were provided, am I right?

@chad-earthscope
Copy link

chad-earthscope commented Dec 8, 2023

Not part of the requested information, but we want our hub parked at geolab.earthscope.cloud. I'm not sure when that becomes important but putting it here early just in case. We own that domain and can configure DNS when needed.

@yuvipanda
Copy link
Member

Thanks @chad-earthscope. Once we have it setup, we'll provide you with some targets (CNAMEs) you can point that domain to.

@timdittmann
Copy link
Contributor

Regarding this comment:

The information pieces still missing, are:

  • hub logo image url
    High res, low res options. (Does this file get stored in the repo or do we need to host this somewhere more permanent?)
  • hub user image github repository
    Can we use standard 2i2c base image for initial deployment, while we experiment with custom images on our end?

@AIDEA775
Copy link
Contributor

@timdittmann We are deploying the cluster in the us-east-2 zone on AWS. Is that ok?

@timdittmann
Copy link
Contributor

@timdittmann We are deploying the cluster in the us-east-2 zone on AWS. Is that ok?

Yes, thank you @AIDEA775

@AIDEA775
Copy link
Contributor

@timdittmann, the hub was deployed, and you can access it at https://staging.earthscope.2i2c.cloud/ (staging) and https://earthscope.2i2c.cloud/ (production). Can you try it?

@timdittmann
Copy link
Contributor

@timdittmann, the hub was deployed, and you can access it at https://staging.earthscope.2i2c.cloud/ (staging) and https://earthscope.2i2c.cloud/ (production). Can you try it?

@AIDEA775 Yes, I am able to access prod with CILogin.
I see that @yuvipanda has initiated the auth0 integration. This is great news.

@colliand
Copy link
Contributor Author

Auth0 integration request was completed as of 2024-01-29.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new hub For issues that request a new hub deployment
Projects
No open projects
Status: Done 🎉
Development

Successfully merging a pull request may close this issue.

6 participants