Openscapes / Openscapes/openscapes.cloud
user clean-up for nmfs-openscapes hub
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
@ateucher Follow-up notes per nmfs-openscapes hub
- andy will create table of users in hub teams: user, teams, last hub access, size of home dir
- eli to contact Sunny re CoastWatch team
- eli to contact OHW users and let them know access is going away
once we have a spreadsheet, eli and andy will review and flag users for deletion. then we will
- flag users for removal @eeholmes
- id any 2024-champions-cohort users. move them to 2026-JupyterHub @eeholmes
- archive home directories of flagged users @ateucher
- remove users from hub @ateucher
- remove users from gh teams @eeholmes
- move remaining users to correct teams @eeholmes
then
- eli will create updated team names (see notes below) @eeholmes
- eli will put in a pr to 2i2c to update the prod.yaml for nmfs-openscapes hub
* remove 2024-champions-cohort from the prod.yaml
* remove 2024-coastwatch (which was for OHW25)
* change team names to new names
team naming notes
- fish-pace hackweek will be in fish-pace org and only for hackweek use
- users that need longer access for projects will request via form
- longterm-access-2i2c is for users who need longer term more persistent access
- shortterm-access-2i2c is for users who are ephemeral. accounts deleted after non-use or some period of time. anyhow, no assumption of permanence for them
code to get username, last mod file date and dir size
echo "date,time,size_gb,username" > users_home_audit.csv
find /home/jovyan/allusers -mindepth 1 -maxdepth 1 -type d \
-printf '%T@,%TY-%Tm-%Td,%TH:%TM,%p\n' \
| sort -nr \
| while IFS=',' read -r epoch date time dir; do
size_gb=$(du -s "$dir" 2>/dev/null | awk '{printf "%.2f", $1/1024/1024}')
user=$(basename "$dir")
printf "%s,%s,%s,%s\n" "$date" "$time" "$size_gb" "$user"
done >> users_home_audit.csv
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the completed checklist and the nmfs-openscapes hub's prod.yaml changes described in the issue. Run the provided home-directory audit command if verification is needed, then confirm the user, hub-team, archive, and team-naming work is complete; the issue does not identify repository file paths or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100