[Reserve Workshop] OceanHackWeek 2025

[eeholmes]

Use this issue to reserve access to the NMFS Workshop Hub URL: https://workshop.nmfs-openscapes.2i2c.cloud.

Describe the event
OceanHackWeek 2025 https://oceanhackweek.org/
5-day in person hackweek on ocean data science

Event Start Date/Time and Event End Date/Time
Pre-HackWeek prep (organizers and project leads): Aug 11-15.
HackWeek Aug 18, 9am to Aug 22 5pm Pacific

Reset Date
Aug 25, 2025

Number of Participants
40 max

Resources that Participant Need

1. What RAM will participants typically need? 2Gb (default) is fine for most tasks. Some may need up to 7Gb.

2. Are there any special storage needs? Like will participants need access to large shared files?

Yes some projects will need to put shared dataset into the Shared-Public directory for access to all participants.

Do you anticipate that participants might download lots (10s of Gb or more) of data?

Some participants will download lots of data, but most will not and we will discourage that workflow.

Event organizers (ppl who will be responsible for the infrastructure/images) with GitHub handle

• Alex Kearney @abkfenris
• Eli Holmes @eeholmes

Once we confirm

You will see your event in the workshop spreadsheet.
Your event password will be live on the "Password Change Date" in column 1 in the spreadsheet.

Checkboxes for event organizer (person submitting the issue) and hub POC (Eli or Andy)

• Hub POC: Sent confirmation to organizer (a comment in this issue thread is fine)
• Hub POC: Submitted a ticket by email to 2i2c for the workshop as per instructions, cc'ing hub POC.
• Hub POC: Confirm [Event] issue opened by 2i2c in response to ticket (example)
• Organizer: Two weeks before event. I have tested the default hub images on the nmfs-openscapes.2i2c.cloud hub or conferred with hub POC on plan for workshop specific hub.
• Organizer: In the week before the event (or when POC indicates password should be live). I tested that the workshop password works and images work.
• Hub POC: After event, put in a 2i2c ticket to remove the participants directories, cleared shared-public, and reset password.

[eeholmes]

@abkfenris Alex, check if above looks right.

[abkfenris]

@eeholmes Yup, I think that looks right other than a Fort in Nebraska rather than my last name.

[eeholmes]

@ateucher did you email 2i2c about this? I think we need to figure out better who does what on alerting 2i2c. I keep assuming it is something you do.

[ateucher]

Hi Eli, sorry I did not email 2i2c about this. We usually leave it to the workshop organizer to send the email to 2i2c. What can I do to help now?

[eeholmes]

@ateucher We ended up not using the workshop hub for OceanHackWeek due to a series of problems.

• We ran into 'no memory' errors even though users had nothing on disk. They tried to clone 100Mb repos and would run into no memory after 20 or so Mb. 2i2c removed all memory limits and that seemed to fix.
• Users could not use gh-scoped-creds. This was a set-up error and hopefully fixed.
• Users kept getting 'user not recognized' errors. This has been reported by another workshop trying to use the workshop hub.

[ateucher]

Hi @eeholmes sorry it didn't work well for you. From your comments, it looks like 2i2c has been informed of these issues? Is there anything else I can help follow up on? The 'use not recognized' errors is definitely something I've seen before...