Page MenuHomePhabricator

Requesting access to 'deployment' for 'Joely Rooke WMDE'
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

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

  • Wikimedia developer account username: Joely Rooke WMDE
  • Email address: joely.rooke@wikimedia.de
  • SSH public key (must be a separate key from Wikimedia cloud SSH access):
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCxErsaAuRwbKQmj4VVY74fsg7WcPqRRrzupv4llbARaAP7IccoZQ2YY3AUASMhtP0idXa9euiErf6vDtVQBnz9eMDCJxwD8/T+08l6w2BNudeJzyMMDO5wOlSxOt5mudXJipxBXDaTXM/JX5XxpCL5kklRX9iu3tfKzb76hKIV3ffijk1qzvutWAYVdAqhgs0lfapRneCyw/DN9k/72OxXsacUcnGujkTkIROPuGhYaWDJP3zt1FoqgQzRDNZDr6S2SWo6psyWxMJnO+zFYYG83guXyPgam430XMIkb8NMHofiE5JBbVtS6YEvkzo4Liv00AinIF15Nopg9cCF2yxK1DaCNi5dLSn90f/yY0pQQcxIYAzGBmbCfcMKymOXr9BTS2A6E8Hab3jkJGydT6v1YsyEzIi1Wokl+HwTAMrSoJ+i2Jz6qHL8iIWa9mMaE+ssnCDy5YEiKxc69tR8HTHQMyLJp+LSQctjzR1hBXMO+XoQGMcixy53+0EU/nEouFlmqP2jlrxvtELty3LLDKFXDMaY2QA6MuH6HVmvtyL2uJpCONhQ/+QfpdsgDvoMT2IgM7SYZU/CTzBpgnZm6uQO0J6f1auD55XCqsuCsFc/2OQlUb9zm/TwM/9l7z/lsBH76zEr+L5CTyAQssa5Ewx59h85gpozva91uB8OSHHaPQ== cardno:20_560_921
  • Requested group membership: deployment
  • Reason for access: I will be working on adding Wikidata support to new wikis (See documentation 1, 2 and example ticket T376575 ). This seems to involve running maintenance scripts on production servers. I believe this requires deployment LDAP group membership. Please advise if another/ alternative group should be joined
  • Name of approving party (manager for WMF/WMDE staff): @WMDECyn (manager) is absent on AL. @WMDE-leszek is my interim manager.
  • 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 --> deployment group replaced with restricted.

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

Details

Event Timeline

I approve this request on WMDE end. thank you!

This request first requires signing an NDA with Legal - tagging @KFrancis as per the access request process. Thanks!

This request first requires signing an NDA with Legal - tagging @KFrancis as per the access request process. Thanks!

I have the information I need, so I'll send out the NDA today. Thx!

Hi all, I believe I have previously signed the NDA when I got basic LDAP access (https://phabricator.wikimedia.org/T366145) and confirmed when I got access to analytics-privatedata-users (https://phabricator.wikimedia.org/T371584). I'm happy to sign again though, or is it a different NDA?

Hi all, checking my records, @JoelyRooke-WMDE does have an NDA on file for access to the WMDE LDAP Group. If this is sufficient, please proceed.

thank you @KFrancis. I'll move forward with the request.

Just to note Joely has verified the SSH key in this ticket via slack

tappof changed the task status from Open to Stalled.Oct 29 2024, 11:05 AM
tappof added a subscriber: thcipriani.

@thcipriani your approval is needed for the deployment group.
Thanks.

@thcipriani your approval is needed for the deployment group.
Thanks.

Thanks!

Reason for access: I will be working on adding Wikidata support to new wikis (See documentation 1, 2 and example ticket T376575 ). This seems to involve running maintenance scripts on production servers. I believe this requires deployment LDAP group membership. Please advise if another/ alternative group should be joined

Reading the docs, I see mostly maintenance scripts that need to be run. There is one config change noted in the docs. The docs read, "Schedule a deployment of the config changes (or do it yourself if you have deployment permissions)."

So it sounds like it's not strictly needed.

Given that, @JoelyRooke-WMDE—I'd be fine approving you for the restricted group. That should give you the access you need to run maintenance scripts, but config deploys would use the backport process (or find someone who can deploy)—would that work?

Hi @thcipriani, I haven't yet received the training on this so I'm not sure exactly what I will need, but I trust your judgement! I will also confirm with @LucasWerkmeister when he is back from AL, but restricted group sounds sensible. I can always reopen this if it turns out deployment is strictly required.

Change #1084780 had a related patch set uploaded (by Tiziano Fogli; author: Tiziano Fogli):

[operations/puppet@production] add Joely Rooke WMDE to restricted group

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

Change #1084780 merged by Tiziano Fogli:

[operations/puppet@production] add Joely Rooke WMDE to restricted group

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

IMHO it’s a bit of an awkward time to add someone to restricted, given the status of T378429, but sure ^^ let’s see how far that gets us.