Page MenuHomePhabricator

Requesting access to stat1004, stat1007, stat1006, notebook1003, notebook1004 for Kate Zimmerman
Closed, ResolvedPublicRequest


  • Wikitech username: Kate Zimmerman
  • Preferred shell username: kzeta
  • Email address:
  • Ssh public key (must be dedicated key for wmf production):
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPMWu5DNleqah845EhqYF3yYqVBhHCFseT1lEq5dzym1
  • Requested group membership: analytics-privatedata-users, researchers
  • Reason for access: Need access to run Jupyter notebooks and query data
  • Name of approving party (hiring manager, for WMF staff): Jon Katz

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
jcrespo added subscribers: Nuria, jcrespo.

As per procedure, this will require also approval of project lead of access requested, in this case @Nuria.

I was going to comment the need to sign L3, but I see it was already done: Sat, Dec 14, 00:20

jcrespo triaged this task as High priority.Dec 16 2019, 2:08 PM
jcrespo moved this task from Backlog to Acknowledged on the SRE board.

This should be now only pending on 3-business day wait, although I will ask some analytics sres a doubt I have, meanwhile.

@kzimmerman One small correction, to make sure the request is correct, you asked for analytics-wmde, we can grant analytics-wmde-users sudo rules, which will allow to schedule crons and troubleshoot as analytics-wmde unix user. I am guessing you are working together with wmde analytics... (no problem on granting that, just confirming that is correct, as most people on that group are from WMDE).

@jcrespo I'm going to remove analytics-wmde-users (and yes, it should not have been analytics-wmde) from my request, thank you for checking! I'll circle back if I do end up needing access.

Just to be clear- there is no problem requesting it, it just seemed odd for WMF work, and that is why I asked. If later you need it, there is not a reason to not provide if needed.

We will now wait the 2 business day left and change will be provided as requested for analytics-privatedata-users and researchers on Wednesday.

Change 558316 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/puppet@production] admin: Provide access to kzimmerman (kzeta) to production analytics

Thank you for the updates, Jaime!

Change 558316 merged by Jcrespo:
[operations/puppet@production] admin: Provide access to kzimmerman (kzeta) to production analytics

@kzimmerman Access has been deployed, please wait at least 30 minutes after this comment so the change applies to all servers and then follow the guide at to test your access and permissions, then resolve the ticket or ping back so I can debug any problem.

Please do not hesitate to contact back for help connecting (I needed a little guidance when I first got access), production has some particularities due to its strict configuration, like not being to work with certain outdated ssh clients.

Because no feedback has been given for a while, this is considered as resolved. Please reopen if you see any issues.

@jcrespo Thank you! I missed your ping earlier; I'll reopen if I end up running into issues.