CUIT account due to expire - will lose access to Pangeo JupyterHub if not renewed

[sgibson91]

Context

I received the below email claiming my Columbia CUIT account is due to expire. The only reason I have this account is to access the GCP project that the Pangeo JupyterHub is deployed to. We have also had many discussions throughout the team about how having separate university-based accounts for individual deployments is neither scalable nor sustainable.

Proposal

If the proposal in https://github.com/2i2c-org/meta/issues/279 is granted to deploy a Pangeo Binder to a GCP account that we own/manage and bill Columbia for, I would very strongly suggest that we also move the JupyterHub we are already running for the sake of ease.

Updates and actions

No response

Related issues

• Strategy for sharing access to clusters #353
• Research and discuss challenges around access/security policies of institutional clouds #184
• Pangeo Access for 2i2c Engineers #136
• https://github.com/2i2c-org/meta/issues/279
• ...

[yuvipanda]

Mine also expires:

[sgibson91]

Since the expiry date is very close, I forwarded the email I received to askcuit@columbia.edu cc'ing @rabernat with the following message:

Hello,

I am a contractor for 2i2c managing cloud infrastructure on a Columbia Google Cloud project, funded by a Pangeo grant led by Ryan Abernathy (cc'd). Please do not expire my account (UNI sg4058) as I need to retain access to the infrastructure that we have deployed and manage for research activities.

Many thanks,

[sgibson91]

Most unhelpful response 🙄

Greetings,

If you are a CU employee and you believe you are still eligible, please
contact your department administrator.

Regards,

CUIT Service Desk

[sgibson91]

Just want to thank @rabernat for all the emails he's sending right now to resolve this issue for all team members, not just myself 🙏🏻

[rabernat]

I would like to resolve this for all the team members, but right now I am just working on your UNI. Do we have a list of everyone who needs renewal?

[sgibson91]

So far, Yuvi is the only other person who reported the renewal email.

I believe @damianavila and @GeorgianaElena are the only others on the team with UNIs. Folks can you provide Ryan with your UNI IDs please?

[GeorgianaElena]

Mine is gd2616. Thanks!

[damianavila]

da3008 in my case.

[yuvipanda]

I'm yt2796

[sgibson91]

I was cc'd on an email from Ryan's colleague that mine and Yuvi's UNIs were extended 🎉

[damianavila]

Super!
It is intriguing to me that I have not received any notification (neither the first one nor the extension).
@GeorgianaElena is that the case for you as well?

[sgibson91]

@damianavila and @GeorgianaElena you won't have received an expiration notification from them, because you got your accounts after me and Yuvi, therefore your cycle is offset from ours :) It will probably be a year from when you got your accounts

Also, it wasn't really a "your account has been extended" notification type of email. Ryan just cc'd me into the email thread with an administrator at LDEO who extended the account and it was an email from them saying "I have completed this task".

Generally I'm a bit annoyed with this scenario. CUIT told me my email address was being expired because my "role at LDEO finished on the 17th". I had no idea I had a "role" at LDEO and I didn't receive any indication that that "role" was expiring either. It's university admin/politics that I don't really understand and is a big time sink (for a lot of people) to sort out.

[damianavila]

It's university admin/politics that I don't really understand and is a big time sink (for a lot of people) to sort out.

Yep, indeed. And Columbia is not alone. It is a spread "practice" among all the Universities I have interacted with...

[damianavila]

Closing this one since now @sgibson91 and @yuvipanda UNIs were extended.
We can reopen later down the road if this is eventually impacting others.

[sgibson91]

I just got pinged AGAIN - I thought the renewal was supposed to be good for a year?

[choldgraf]

huh, the date is even later than last time so something indeed got updated in their database, it's not just an accidental re-send of the same notice.

Another cross-ref to the incommon issue since I think that would resolve issues like these:

• https://github.com/2i2c-org/meta/issues/348

[damianavila]

I am reopening this one again until we know more about this one. @sgibson91 did you ping them again about this situation?

[sgibson91]

Yeah, it got renewed again so can be closed.

[sgibson91]

I'm really regretting not mentioning who the contact was in this issue as the email thread is gone and no one useful is showing up in my contacts

• https://github.com/2i2c-org/meta/issues/666