Page MenuHomePhabricator

Requesting access to deployment for Kosta Harlan
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

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

  • Wikitech username: Kosta Harlan
  • Preferred shell username: kharlan
  • Email address: kharlan@wikimedia.org
  • Ssh public key (must be dedicated key for wmf production): ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHZqJOizHso9YldV5FMsnoJnWfLIno11qlXjVGfSBWb5 kharlan@kharlans-MacBook-Pro.local
  • Requested group membership: deployment
  • Reason for access: See T265893#6669424, I would like to be able run helmfile -e for deploying updates to the new link recommendation service. (I also plan to do backport/config training at some point in the next quarter or two.)
  • Name of approving party (hiring manager for WMF staff): @marcella
  • Requestor -- Please Acknowledge that you have read and signed the L3 Wikimedia Server Access Responsibilities document: Yes
  • Requestor -- 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. (This can be checked by Operations via the NDA tracking sheet & is included in all WMF Staff/Contractor hiring.)
  • - User has provided the following: wikitech username, preferred shell 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 share 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 (sponser for volunteers, manager for wmf staff)
  • - Patchset for access request

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

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
kostajh renamed this task from Requesting access to RESOURCE for USER[S] to Requesting access to deployment for Kosta Harlan.Dec 9 2020, 10:03 AM
kostajh added a subscriber: akosiaris.

Requestor -- Please coordinate obtaining a comment of approval on this task from the approving party.

cc @akosiaris @marcella Please let me know if you have any questions, thank you.

Requestor -- Please coordinate obtaining a comment of approval on this task from the approving party.

cc @akosiaris @marcella Please let me know if you have any questions, thank you.

None from my side, this can proceed as a normal deployment rights request as far as I am concerned.

@kaldari you are listed as kostajh manager as such can you approve this access request
@thcipriani are you able to approve adding kostajh to the deployment: group

@jbond I am Kosta's manager and I approve this request. Thank you!

I approve as well in case it matters ;)

@thcipriani are you able to approve adding kostajh to the deployment: group

Approved!

@jbond I am Kosta's manager and I approve this request. Thank you!

! In T269731#6680958, @kaldari wrote:

I approve as well in case it matters ;)

Thanks both the data source i was using is obviously out of date/incorrect . Will proceed now

Change 647651 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] admin: add kharlan to deployment group

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

Change 647651 merged by Jbond:
[operations/puppet@production] admin: add kharlan to deployment group

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

I have now added you to the deployment group. however there is currently on going work which means it may take a few hours for this change to propogate. if you are still unable to access the correct systems within a day please reopen this task for me to investigate further (or feel free to ping me directly on irc jbond42)

jbond triaged this task as Medium priority.