Page MenuHomePhabricator

Requesting access to analytics-privatedata-users for Steph Toyofuku
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

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

  • Wikimedia developer account username: SToyofuku-WMF
  • Email address: stoyofuku@wikimedia.org
  • SSH public key (must be a separate key from Wikimedia cloud SSH access): ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILPzNLzxzF0+Sjy80bIrbKyCyoDqcEB95X9z0fWh3F7x toyofuku@wmf3417
  • Requested group membership: analytics-privatedata-users
  • Reason for access: viewing superset queries as part of my job
  • Name of approving party (manager for WMF/WMDE staff): Nat Baca
  • Ensure you have signed the L3 Wikimedia Server Access Responsibilities document: I have
  • 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

@SToyofuku-WMF @NBaca-WMF Can you please clarify which specific type of access you want/need:

You mentioned access to analytics-privatedata-users and you provided an SSH key already. Do you also need Kerberos access? https://wikitech.wikimedia.org/wiki/Analytics/Data_access#Access_Levels lists the available options and what access is granted via them.

@odimitrijevic @WDoranWMF @Ahoelzl @Milimetric This needs your approval.

@MoritzMuehlenhoff apologies, I thought analytics-privatedata-users was the specific level, but I can see I was looking at the wrong table. I'm specifically looking for access to superset/hue, so I shouldn't need Kerberos access - I believe only the first two rows of the table you linked should be sufficient

@MoritzMuehlenhoff apologies, I thought analytics-privatedata-users was the specific level, but I can see I was looking at the wrong table. I'm specifically looking for access to superset/hue, so I shouldn't need Kerberos access - I believe only the first two rows of the table you linked should be sufficient

Ack, thanks. Once the service owner approval is in, we'll add your access.

MoritzMuehlenhoff triaged this task as Medium priority.

Change #1018634 had a related patch set uploaded (by Muehlenhoff; author: Muehlenhoff):

[operations/puppet@production] Add stoyofuku to analytics-privatedata-access

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

Change #1018634 merged by Muehlenhoff:

[operations/puppet@production] Add stoyofuku to analytics-privatedata-access

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

@SToyofuku-WMF : I've enabled your access. You should already be able to log into stat1010.eqiad.wmnet. The other servers will follow within the next 30 minutes after Puppet (our configuration managent tool) has deployed the change everywhere. Resolving. If you run into any issues, please reopen the task!