Page MenuHomePhabricator

Requesting access to deployment for OSleger_WMF
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

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

  • Wikimedia developer account username: osleger
  • Email address: osleger@wikimedia.org
  • SSH public key (must be a separate key from Wikimedia cloud SSH access): ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHSfjkdaISfy9jfx5/Zfl+yDeyZGkp1o07773K50XmLT osleger@wmf3705
  • Requested group membership: deployment
  • Reason for access: I need access to deployment server to be able to do backports when needed.
  • Name of approving party (manager for WMF/WMDE staff): @SLopes-WMF
  • 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

Details

Event Timeline

As Otto's manager, I approve this request.

@thcipriani Here is a request for "deployment" group.

Approved. @OSleger-WMF for backports, you'll also want these bits:

  • Our web deploy tool SpiderPig also requires you request membership in the spiderpig-access group in Bitu/IDM
    • Once requested, I can approve there and then you should be able to login to the web interface.
    • For clarity, both deployment group membership and spiderpig-access are needed to access the web interface.
  • Ensure you've joined the ops-l mailing list – announcements impacting deployers are often sent there.

Thanks!

Thanks all. Almost all boxes are already checked now. Just need to verify the SSH key outside of the ticket.

@Aklapper Want to verify if Phab user is linked properly?

@OSleger-WMF Could you maybe send a direct email between our official wikimedia inboxes to confirm this is you and the correct key? I am dzahn@ . Cheers

As Otto points out they have an existing key and membership in parsoid-admins.

Verified!

Change #1298830 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] admin: add osleger to deployment group

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

Dzahn changed the task status from Open to In Progress.Jun 8 2026, 4:12 PM

Change #1298830 merged by RLazarus:

[operations/puppet@production] admin: add osleger to deployment group

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

RLazarus assigned this task to Dzahn.
RLazarus subscribed.

All done! This will take up to 30 minutes to roll out everywhere, then make sure to follow the instructions in T428262#11990183.

Marking this resolved, but feel free to reopen if you have any trouble using your new access.