user clean-up for nmfs-openscapes hub

[eeholmes]

@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

[eeholmes]

@ateucher Ah, I did not use 2024-science-team for OceanHackWeek! I used 2024-CoastWatch. Whew, that makes things easier

[ateucher]

Thanks for writing this all out @eeholmes! I should be able to get the users/team list next week

[eeholmes]

Here is the users in nmfs-openscapes hub with last access and dir size

users_home_audit.csv

This can be cross walked against the table you produce with username and teams

[eeholmes]

@ateucher I have reviewed your file
nmfs-gh-team-members-access_2026-01-20.csv

And prepared this list of users whose home dirs can be removed and they can be removed from nmfs-openscapes JHub. Can I leave the user removal to you?
remove-home-dir.csv

• I put in a PR with 2i2c to change the teams
• I cleaned up the Teams a bit in github.com/nmfs-openscapes
• I did not remove ppl in 2024-science-teams who had not logged in before.

[eeholmes]

@ateucher Let's review our naming ideas once we get the 1st clean-up done.

This was in my notes, but now I am not sure.

• 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

[ateucher]

Thanks @eeholmes! 2i2c have added the archive bucket, and I have created an IAM user in AWS that I can use to archive home directories. I'll do that this afternoon.

For the users we are archiving, are we also removing them from teams (and from the entire org)? Are we remove those teams (2024-champions-cohort , 2024-coastwatch, others??) from the org?

[ateucher]

As for naming, I think longterm-access-2i2c is good, we should keep that. I think rather than having a team like shortterm-access-2i2c, we should use more tightly scoped teams where the name reflects the purpose - then we can manage access at the team level rather than trying to keep track of users within the team to remove access after a period of time.

[ateucher]

@eeholmes I have archived and deleted the home directories of those users. They are in an S3 bucket with policies that will auto-purge the archives six months from now.

One thing we haven't sorted out (as pointed out by @yuvipanda here is how to communicate with these users.

The users we removed are still part of the nmfs-openscapes org, and those that are members of 2024-nmfs-champions-cohort team still are. Since you removed the 2024-coastwatch team, those users are no long part of that team but are still org members.

[eeholmes]

• 2024-coastwatch Oh, and now I don't remember all their names....so I cannot remove from the org. Though I guess they are in your file.
• re users whose home dirs we deleted and those who have never logged in. I am not sure what to do. These should be (mostly be) NOAA ppl. I think your suggestion to have users associated with events helps.

[eeholmes]

How about we do another co-work in early February to clean up the members of the org. I think it would be easier to do as a joint effort while on video so we can bounce ideas off each other.

In anycase, we have made a lot of progress cleaning up old users and clearing out the oceanhackweek folks from the hub.

[eeholmes]

But I got rid of most of the OceanHackWeek folks by scanning member who were not on any teams.

[ateucher]

Thanks Eli, that sounds good to meet in February. I have added a couple of functions to kyber to help us process batches of users