Requesting access to analytics-privatedata-users for JTanner
Closed, ResolvedPublicRequest
Actions

Assigned To

Authored By

	JTannerWMF
	Feb 7 2024, 9:09 PM

Description

Requestor provided information and prerequisites

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

Wikimedia developer account username: JTanner
Email address: jtanner@wikimedia.org
SSH public key (must be a separate key from Wikimedia cloud SSH access): not neeeded
Requested group membership: analytics-privatedata-users
Reason for access: Superset
Name of approving party (manager for WMF/WMDE staff): @MMiller_WMF
Ensure you have signed the L3 Wikimedia Server Access Responsibilities document: Done
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

Details

	Subject	Repo	Branch	Lines +/-
	admin: add jaz to analytics-privatedata-users	operations/puppet	production	+8 -5

Customize query in gerrit

Related Objects

Mentioned In: T359440: [REQUEST] Product Analytics data instrumentation: CTR, Cirrus Search data and Superset dashboarding thereof
Mentioned Here: T344199: Grant Access to analytics-privatedata-users for ATsay-WMF

Event Timeline

JTannerWMF created this task.Feb 7 2024, 9:09 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 7 2024, 9:09 PM

I am @JTannerWMF's manager and I approve.

Jelto triaged this task as Medium priority.Feb 8 2024, 9:38 AM

Jelto updated the task description. (Show Details)

@JTannerWMF you have to sign the L3 Wikimedia Server Access Responsibilities Document.

Also we need a SSH public key (must be a separate key from Wikimedia cloud SSH access).

Also we need the approval for analytics-privatedata-users from one of the owners (@odimitrijevic , @WDoranWMF, @Ahoelzl)

Jelto updated the task description. (Show Details)Feb 8 2024, 9:44 AM

Dzahn changed the task status from Open to In Progress.Feb 8 2024, 4:11 PM

Dzahn moved this task from Untriaged to Awaiting User Input on the SRE-Access-Requests board.

@mpopov mentioned I wouldn't need the SSH key. I've signed the agreement.

@Jelto: This is to access dashboards in Superset that do access private data, no need for Hadoop/analytics client servers access. So no SSH public key needed. See https://wikitech.wikimedia.org/wiki/Analytics/Data_access

This is same type of request as T344199: Grant Access to analytics-privatedata-users for ATsay-WMF

Jelto updated the task description. (Show Details)Feb 9 2024, 9:30 AM

Great, thanks for signing the L3. And you are right, no SSH key is needed.

Let's wait for a approval from a analytics-privatedata-users owner (@odimitrijevic , @WDoranWMF, @Ahoelzl @Milimetric) and then we can proceed here.