Page MenuHomePhabricator

Requesting access to production for SWAT deploy for Urbanecm
Closed, DeclinedPublicRequest

Description

Username: Urbanecm@Wikitech, Martin Urbanec@SUL
Full name: Martin Urbanec
Preffered shell username: urbanecm
Project being worked on: I work on Wikimedia-Site-requests work. I'd like to have deploy access because it'll allow me to help site requests work even more. Namely, throttling rules and similar urgent things can be done without any deploy window if needed, but often it's problem to find a deployer. I'd be able to act on server-side upload requests as well and of course, help with SWAT as well. This will mean access to the deployment host (deploy1001 and naos for deploying, terbium for scripts/server-side uploads)

Experience for this shell access
As explained above, I write patches for site requests on regular basis and because of that I use SWAT windows quite often. I think I became quite familiar with deploy process, such as roughly what to do if I want to deploy a patch, how to purge a static file, how to run a script and why I should want this particular script to be run.

Outside site-requests work, I'm a sysadmin at Wikimedia Czech Republic and I take care about two MediaWiki instances and one self-developed expense-tracking Django app.

Of course, I'm going to learn new things and I'm aware of the importance to be careful and ask a second opinion.

Approvals

  • Approval for direct supervisor: I don't have currently one, I talked about requesting this rights with @zeljkofilipin.
  • Approval for project lead: this is to be asked to @greg

SSH key

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDVzRVo14P4G3NV5H9+C7LhDYlUCeAdFoZVa4HqHCBXp2cvHxQZf9kGVLHUgI1HdPlYyV8z2cgK7uCm4LHgbly0JtRPHhQPJZszR1DxJ+z34oSxu2N2tqn6aoWuEkM0D0vEEVx1aJ/rLRlq81C7zhwZzqFAzrQTohSIxP3fmPHQf+FZr7AHWM8GPdQnY4HTCJHm9g0W52hCy692ALroerx2gqgfTvN2+Mqs0nHx+B3EDCBcQDmfjxUxo+M8TdRm0Xccih7n+MWPzkCtA0rYXnZnkG3iWQdsnTlO44vY5LtONqCQbVSuPe2AKhe8ThqEK7NA26heiP7FnLNJHXNRJmybuFF//3Ah8/wj5J5Oc8l2qKMQL7svwWjGDcmfuxZOUAnfBS/SAv8edpKtoxCQIA3aY8FIWtL6GwEmRI1hGA1TCFBg5COUKjJhQ/T6Ab2mMeF3faAGWH9+koI7+K0Roug+GziOZ3XMtPTWM9/S5mJCEJ7JgA8k5IIdq+GCi5QaFt4N0Uv6bpeztW7K5WHgasj5WUJ9SK5GNmUHjrvLVioPDWjKoV4+ylQeL12jB6wo3PeICs9d+/Vgm/cR2hCZ9KJ7yxfjruO6svGCf4RqzyPQOgkPCSXK6IlYcJegpsZKpORXfAdKN9BYM0XznZeB8RrKaY+iBkezuIjXMN6FO7RAcQ== urbanecm-wikimedia-production

NDA
I did not signed Volunteer NDA yet.

SRE Clinic Duty Checklist for Access Requests

Most requirements are outlined on https://wikitech.wikimedia.org/wiki/Requesting_shell_access

This checklist should be used on all access requests to ensure that all steps are covered. This includes expansion to access. Please do not check off items on the list below unless you are in Ops and have confirmed the step.

  • - 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)
  • - sudo/deployment requests: all sudo requests require explicit approval during the weekly operations team meeting. No sudo requests will be approved outside of those meetings without the direct override of the Director of Operations.
  • - Patchset for access request

Event Timeline

Urbanecm created this task.Apr 23 2018, 6:34 PM
Restricted Application added projects: Operations, User-Urbanecm. · View Herald TranscriptApr 23 2018, 6:34 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Urbanecm updated the task description. (Show Details)Apr 23 2018, 6:38 PM
Urbanecm moved this task from Backlog to Later on the User-Urbanecm board.Apr 23 2018, 6:51 PM
Urbanecm moved this task from Later to Watching on the User-Urbanecm board.
hashar added a subscriber: hashar.Apr 24 2018, 1:36 PM
herron triaged this task as Normal priority.

@ Urbanecm - for the NDA, I'll need an email address and a physical address. You can email me the details: rstallman@wikimedia.org
Thanks!

@ Urbanecm - for the NDA, I'll need an email address and a physical address. You can email me the details: rstallman@wikimedia.org
Thanks!

Emailed.

RobH updated the task description. (Show Details)Apr 30 2018, 4:58 PM
RobH added a subscriber: RobH.Apr 30 2018, 6:06 PM

@Urbanecm: Please note we'll also need you to review and agree/sign the L3 document on phabricator for production shell access. I've added a checklist, but it should only be checked off by SRE team folks. (You'll need to meet all the checklist requirements though.)

We'll likely get an update on this task from @RStallman-legalteam when legal has reviewed the NDA, then we'll just need your sponsorship approval by @zeljkofilipin, and approval for swat deployment access by both @greg (release engineering) and then in an SRE team meeting (every Monday).

RobH updated the task description. (Show Details)Apr 30 2018, 6:07 PM

I signed L3. There are some upcoming issues with the NDA, I hope they'll be resolved soon.

RobH closed this task as Declined.May 2 2018, 3:53 PM

discussion with user off task.

Vvjjkkii renamed this task from Requesting access to production for SWAT deploy for Urbanecm to xeeaaaaaaa.Jul 1 2018, 1:14 AM
Vvjjkkii reopened this task as Open.
Vvjjkkii raised the priority of this task from Normal to High.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed subscribers: MarcoAurelio, Aklapper.
AfroThundr3007730 renamed this task from xeeaaaaaaa to Requesting access to production for SWAT deploy for Urbanecm.Jul 1 2018, 5:37 AM
AfroThundr3007730 closed this task as Declined.
AfroThundr3007730 lowered the priority of this task from High to Normal.
AfroThundr3007730 updated the task description. (Show Details)