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.

Sign up for GitHub

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

Jump to bottom

Automatically pull ghg-docs repo on server start on GHG hub (same as VEDA hub) #3565

Closed
yuvipanda opened this issue Jan 3, 2024 · 2 comments
Closed

Automatically pull ghg-docs repo on server start on GHG hub (same as VEDA hub) #3565

yuvipanda opened this issue Jan 3, 2024 · 2 comments

Comments

@yuvipanda
Copy link
Member

Via #3124 and follow-up PRs, the NASA VEDA hub automatically clones the GHG Docs repo each time a user server starts. Per https://2i2c.freshdesk.com/a/tickets/1209, this behavior is desired for the GHG center hub as well.
@github-project-automation github-project-automation bot moved this to Needs Shaping / Refinement in DEPRECATED Engineering and Product Backlog Jan 3, 2024
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jan 3, 2024
@yuvipanda
Use generated resource allocation options for veda hub
0763ee8 
While starting to work on 2i2c-org#3565,
I realized that VEDA was still using the older style 'node share'
rather than the generated 'resource allocation' options. I've swapped
over the options to now be based on images for users to choose and
resource allocation options generated by our resource allocation script.
This matches openscapes, and there has generally been pretty big positive
feedback on this mode.

I've kept the initial cloning to only happen on the pangeo image as
it currently exists, without making any changes. That should be cleaned
up as part of 2i2c-org#3565
@yuvipanda yuvipanda mentioned this issue Jan 3, 2024
Merged
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jan 4, 2024
@yuvipanda
Use generated resource allocation options for veda hub
f7c9e5f 
While starting to work on 2i2c-org#3565,
I realized that VEDA was still using the older style 'node share'
rather than the generated 'resource allocation' options. I've swapped
over the options to now be based on images for users to choose and
resource allocation options generated by our resource allocation script.
This matches openscapes, and there has generally been pretty big positive
feedback on this mode.

I've kept the initial cloning to only happen on the pangeo image as
it currently exists, without making any changes. That should be cleaned
up as part of 2i2c-org#3565
yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Jan 11, 2024
@yuvipanda
Make GHG profileList match VEDA's
d8a4e8b 
Brings in 2i2c-org#3566
(and follow-ups) to the GHG hub

Ref 2i2c-org#3565
@yuvipanda yuvipanda mentioned this issue Jan 11, 2024
Merged
@yuvipanda yuvipanda mentioned this issue Mar 7, 2024
Open
@batpad batpad mentioned this issue Mar 18, 2024
Closed
@batpad
Copy link
Contributor

batpad commented Mar 18, 2024

Copied this issue over to the veda-jupyterhub repo: NASA-IMPACT/veda-jupyterhub#7 .

@yuvipanda I think you can close here if that looks good / seems like the more appropriate place to track this.

@yuvipanda
Copy link
Member Author

\o/ Great!

@github-project-automation github-project-automation bot moved this from Needs Shaping / Refinement to Complete in DEPRECATED Engineering and Product Backlog Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
No open projects
DEPRECATED Engineering and Product Backlog
Status: Complete
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yuvipanda @batpad