Page MenuHomePhabricator

Requesting access to analytics-privatedata-users for vpoundstone - WMF
Closed, ResolvedPublic

Description

Requestor provided information and prerequisites

Wikitech username: https://wikitech.wikimedia.org/wiki/User:vpoundstone-WMF
Email address: vpoundstone@wikimedia.org
SSH public key (must be a separate key from Wikimedia cloud SSH access): ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDI0AAFEUTKt6+sqZnG5ykhisGQkqD8lSGk42hqz4QIk vpoundstone@wikimedia.org
Requested group membership: analytics-privatedata-users
Reason for access: PM on the Product Platform team need read access to generated datasets for analysis. I will be using superset UI mainly to view data. I don't need shell access at this point.
Name of approving party (manager for WMF/WMDE staff): Desiree Abad
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: wikitech 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.) [No shell access necessary]
  • - 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

Hello @Ottomata or @odimitrijevic this is asking for your group approval. Thanks

Note that the Phabricator account @VirginiaPoundstone is linked to a self-created, non-WMF SUL wiki account. This can make verification of other access requests way more complicated, plus it hinders realizing someone's affiliation in Phab. Is there a particular reason why the WMF-ITS provided SUL wiki account was not used?

Note that the Phabricator account @VirginiaPoundstone is linked to a self-created, non-WMF SUL wiki account. This can make verification of other access requests way more complicated, plus it hinders realizing someone's affiliation in Phab. Is there a particular reason why the WMF-ITS provided SUL wiki account was not used?

Thanks for catching this @Aklapper. Beginner's error. Please use vpoundstone-WMF. I updated this in the description as well.

Is it possible to delete the self-created account (VirginiaPoundstone) to remove future confusion? I do not see the option to delete the account myself.

VirginiaPoundstone renamed this task from Requesting access to analytics-privatedata-users for virginiapoundstone to Requesting access to analytics-privatedata-users for vpoundstone - WMF.Tue, Aug 9, 7:11 PM
BCornwall triaged this task as Medium priority.

Change 822123 had a related patch set uploaded (by BCornwall; author: BCornwall):

[operations/puppet@production] admin: add Virginia Poundstone (vpoundstone)

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

Change 822123 merged by BCornwall:

[operations/puppet@production] admin: add Virginia Poundstone (vpoundstone)

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

The changes have been accepted. Virginia, your new access should be applied shortly. Please feel free to reopen if there are still unresolved issues!