Page MenuHomePhabricator

[WIP] Requesting access to deployment group for TThoabala
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

This section is to be completed by the individual requesting access.

  • Wikitech username: TsepoThoabala
  • Email address: tthoabala@wikimedia.org
  • SSH public key (must be a separate key from Wikimedia cloud SSH access):ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILQH9jvacif4CGZ1Hby7HYwtR/EJSy0XDbRtWzHFb+3E tthoabala@wikimedia.org
  • Requested group membership: deployment
  • Reason for access: Help deploy config changes and backports for the Anti-Harassment team
  • Name of approving party (manager for WMF/WMDE staff): @JayCano
  • 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: 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.)
  • - 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

I just wanted to confirm that I approve of this request and I'm available for any questions. Thank you!

@TThoabala can you explain what access you require. i.e. which commands do yu expect to run and from where

@KFrancis could you please help confirm or arrange an NDA for @Tchanders

thanks

jbond triaged this task as Medium priority.Mar 21 2022, 5:50 PM

@jbond As TsepoThoabala is an employee of the WMF (tthoabala@wikimedia.org), no separate NDA is needed.

@jbond As TsepoThoabala is an employee of the WMF (tthoabala@wikimedia.org), no separate NDA is needed.

Doh! sorry i missed that

@Tchanders i have checked and you are in the deployment im guessing i should configure @TThoabala with the same access?

@jbond That would be great - thank you. @TThoabala is now on leave for a few months, so would it be more convenient to stall this until he returns?

@thcipriani are you able to approve @TThoabala membership of the deployment group

@Tchanders Sounds good to me, ill get all the approvals in [lace and create the change then its just a matter of merging when they get back

Change 772823 had a related patch set uploaded (by Jbond; author: John Bond):

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

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

jbond changed the task status from Open to Stalled.Mar 22 2022, 1:15 PM

Change to stalled until TsepoThoabala return

@thcipriani are you able to approve @TThoabala membership of the deployment group

Approved!

Change to stalled until TsepoThoabala return

When is TsepoThoabala expected to return?

Change to stalled until TsepoThoabala return

When is TsepoThoabala expected to return?

Not for a couple of months. @JayCano might be able to provide more information

Is it ok if we close this ticket and you just reopen it again once he is back?

Is it ok if we close this ticket and you just reopen it again once he is back?

Going ahead with this -- closing as "invalid" for lack of a better option since the request is not yet "resolved" and also not being "declined", only being deferred until later. Please re-open when ready to proceed thanks!

@herron / @Dzahn I am back from leave and I would like to carry on with this ticket. I generated a new key and updated it on the ticket.

Change 801400 had a related patch set uploaded (by Jbond; author: jbond):

[operations/puppet@production] admin: add tsepothoabala

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

Change 772823 abandoned by Jbond:

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

Reason:

https://gerrit.wikimedia.org/r/c/operations/puppet/+/801400

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

Change 801400 merged by Jbond:

[operations/puppet@production] admin: add tsepothoabala

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

Change 801401 had a related patch set uploaded (by Jbond; author: jbond):

[operations/puppet@production] admin: add correct key for tthoabala

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

Change 801401 merged by Jbond:

[operations/puppet@production] admin: add correct key for tthoabala

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

jbond claimed this task.

@TThoabala this has been merged, please re-open this task if you still have issues thanks