Page MenuHomePhabricator

Requesting access to L3 data access for kimpham (developer name Kim.pham)
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

Complete ALL items below as the individual person who is requesting access:

  • Wikimedia developer account username: Kim.pham
  • Email address: kim.pham@wikimedia.de
  • SSH public key (must be a separate key from Wikimedia cloud SSH access): ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBI32mUvVy41VnzSfZq3z/dLmGXN7saWm2LNWD5MRqnS prod-superset
  • Requested group membership: level 3
  • Reason for access: I would like to be in the analytics_privatedata_users level 3 group, to access data e.g. Superset and Hadoop, including querying it with Spark/Hive.
  • Name of approving party (manager for WMF/WMDE staff): @WMDE-leszek
  • Ensure you have signed the L3 Wikimedia Server Access Responsibilities document: yes
  • Please coordinate obtaining a comment of approval on this task from the approving party.

SRE Clinic Duty Confirmation Checklist for Access Requests

This checklist should be used on all access requests to ensure that all steps are covered, including expansion to existing access. Please double check the step has been completed before checking it off.

This section is to be confirmed and completed by a member of the SRE team.

  • - User has signed the L3 Acknowledgement of Wikimedia Server Access Responsibilities Document.
  • - User has a valid NDA on file with WMF legal. (All WMF Staff/Contractor hiring are covered by NDA. Other users can be validated via the NDA tracking sheet)
  • - User has provided the following: developer account username, email address, and full reasoning for access (including what commands and/or tasks they expect to perform)
  • - User has provided a public SSH key. This ssh key pair should only be used for WMF cluster access, and not shared with any other service (this includes not sharing with WMCS access, no shared keys.)
  • - The provided SSH key has been confirmed out of band and is verified not being used in WMCS.
  • - access request (or expansion) has sign off of WMF sponsor/manager (sponsor for volunteers, manager for wmf staff)
  • - access request (or expansion) has sign off of group approver indicated by the approval field in data.yaml

For additional details regarding access request requirements, please see https://wikitech.wikimedia.org/wiki/Requesting_shell_access

Event Timeline

I approve this request on WMDE's end. Thank you

FCeratto-WMF changed the task status from Open to In Progress.Jan 19 2026, 10:40 AM

Hello @Milimetric @Ahoelzl @Ottomata - can you please review this access request for analytics-privatedata-users? Thanks

Change #1228481 had a related patch set uploaded (by Federico Ceratto; author: Federico Ceratto):

[operations/puppet@production] admin: add pham to analytics-privatedata-users

https://gerrit.wikimedia.org/r/1228481

Change #1228481 merged by Federico Ceratto:

[operations/puppet@production] admin: add pham to analytics-privatedata-users

https://gerrit.wikimedia.org/r/1228481

FCeratto-WMF claimed this task.

Change deployed, closing task.

I don't see krb: present in the patch, so looks like this was done as level 2 instead of the requested level 3. Is this correct?

Change #1236249 had a related patch set uploaded (by Elukey; author: Elukey):

[operations/puppet@production] admin: add the krb flag to the pham user

https://gerrit.wikimedia.org/r/1236249

I don't see krb: present in the patch, so looks like this was done as level 2 instead of the requested level 3. Is this correct?

Yep! I am going to add the krb credentials :)

Change #1236249 merged by Elukey:

[operations/puppet@production] admin: add the krb flag to the pham user

https://gerrit.wikimedia.org/r/1236249

elukey@krb1002:~$ sudo manage_principals.py create pham --email_address=kim.pham@wikimedia.de
Principal successfully created. Make sure to update data.yaml in Puppet.
Successfully sent email to kim.pham@wikimedia.de

@kimpham Hi! You should have received an email with a temporary kerberos password. You can ssh to any statXXX host and run kinit to change it to a new one. You'll be required to kinit with the new password anytime you'll use the hadoop cluster (launching jobs via spark, using hive, etc..). Lemme know if you have questions!