Page MenuHomePhabricator

Requesting access to analytics cluster for Ben Tullis
Closed, ResolvedPublicRequest

Description

Requestor provided information and prerequisites

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

  • Wikitech username: Btullis
  • Email address: btullis@wikimedia.org
  • SSH public key (must be a separate key from Wikimedia cloud SSH access):

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDLwVzH9rT959TVnPq/SBJIQU4T1eZXIBAdyEM5TchYg btullis@wikimedia.org

I confirm that this key is separate from my Wikimedia Cloud/Gerrit key.

  • Requested group membership: analytics-privatedata-users
  • Reason for access: Onboarding Ben Tullis in his role as an SRE in the analytics (data engineering) team
  • Name of approving party (manager for WMF/WMDE staff): Olja Dimitrijevic and/or Fransisco Dans
  • Ensure you have signed the L3 Wikimedia Server Access Responsibilities document:

I can confirm that I have signed this document today.

I believe that I also need the following:

  • Membership of the wmf group in LDAP
  • A Kerberos principal
  • 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
  • - prepare patchset for access

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

Event Timeline

BTullis updated the task description. (Show Details)
BTullis updated the task description. (Show Details)

Should I create a separate request for the LDAP group change?
I see from here that there is a special LDAP-Access-Requests tag that I should use.

Ottomata added subscribers: razzi, Ottomata.

Ben's first day was yesterday, so let's expedite this! @razzi will take care of this, and I will follow up with SRE on enabling root access after the initial access is granted.

Oh, I think analytics-admins is not needed since Ben will be an SRE and have root access, editing task description.

@razzi will take care of this, and I will follow up with SRE on enabling root access after the initial access is granted.

SGTM, I'll be on SRE clinic duty this week and will stay hands-off until hearing otherwise

On a related note -- is there another onboarding task to link as a parent?

Oh, and approved by me for analytics-privatedata-users.

@herron if you have time to do this now I'm sure @razzi would not mind, we just wanted to expedite :) Thank you!

Sure I'll go ahead and prep a patch. I may have missed it, but what realname should be used for btullis?

Would also be ideal to log a comment of approval from the approving party either here or via a parent onboarding task, etc. With that and a +1 review on the patch we should be good to go.

Oh, Ben Tullis.

Yes, we need approval from Ben's manager: @odimitrijevic Please approve!

Ottomata renamed this task from Requesting access to analytics cluster for btullis to Requesting access to analytics cluster for Ben Tullis.Jun 29 2021, 6:13 PM

Change 702197 had a related patch set uploaded (by Herron; author: Herron):

[operations/puppet@production] admin: create shell user btullis, add to analytics-privatedata-users

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

Change 702197 merged by Herron:

[operations/puppet@production] admin: create shell user btullis, add to analytics-privatedata-users

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

Shell account has been created, and ldap account has been added to group wmf

getting requests for ops-maintenance group access. These things have been checkboxes in the general onboarding tickets but there doesn't seem to be one here.

@Dzahn - Thanks, yes I requested it, because it was an entry on my onboarding checklist - I can confirm that I now have to the ops-maintenance group.

@BTullis Thanks, yes, I approved it. Welcome to WMF!

I also have an item on my checklist to say that I should be in the cn=ops LDAP group.

There are instructions on how I can add myself to that group, but only once I have sudo access.

Can anyone confirm this requirement? If so, can it be done on this ticket, or should I raise a new one?

I also have an item on my checklist to say that I should be in the cn=ops LDAP group.

There are instructions on how I can add myself to that group, but only once I have sudo access.

Can anyone confirm this requirement? If so, can it be done on this ticket, or should I raise a new one?

Hey @BTullis, Typically this is done with the onboarding buddy who has root already which is the case for @Ottomata and @razzi. So I'll defer to them on next steps for now. Fwiw it should work out to roughly two steps 1) being added to the ldap ops group, and 2) uploading, reviewing and merging/deploying a puppet patch adding your shell account to the unix ops group.

@herron, so we should do step 1 and then help Ben do step 2?

@herron, so we should do step 1 and then help Ben do step 2?

I think so, I'm basing that on is the "who starts it" column from https://office.wikimedia.org/wiki/Technology/Onboarding/Checklists/Ben_Tullis#Site_Reliability_Engineering. Of course happy to help with that as well if you'd prefer

Ok, done step 1. @BTullis you are in the ops LDAP group now.

I believe this means you can create a patch to add your user to the "ops" group in puppet in modules/admin/data/data.yaml. Add me and razzi as reviewer, and we'll +1, and then you can +2 and merge. We can do the puppet-merge stuff together! :)

Change 702424 had a related patch set uploaded (by Zabe; author: Btullis):

[operations/puppet@production] Add btullis to the ops security group

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

Change 702424 merged by Btullis:

[operations/puppet@production] Add btullis to the ops security group

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

Thanks. I can confirm that I've now been able to access puppetmasters and other servers requiring ops group membership.

One thing that doesn't seem to be working so far is Netbox. I can log in, but I get a permission denied message after that.
Do we need to do something in Django admin?

Also LibreNMS and Logstash authentication don't seem to let me in.
Neither is urgent, just thought I'd let you know in case there is anything else I should do.

Change 702739 had a related patch set uploaded (by Btullis; author: Btullis):

[operations/puppet@production] Grant icinga permissions to btullis

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

Change 702739 merged by Btullis:

[operations/puppet@production] Grant icinga permissions to btullis

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

Added myself to the root alias on puppetmaster1001

Added my GPG key to the pwstore repo.

MoritzMuehlenhoff subscribed.

Given that Ben is in root users and has cn=ops/cn=wmf LDAP membership this seems complete, closing the task so that it no longer shows up in the access request dashboard.

I have created myself a kerberos principal with the following command:

btullis@krb1001:~$ sudo manage_principals.py create btullis --email_address btullis@wikimedia.org
Principal successfully created. Make sure to update data.yaml in Puppet.
Successfully sent email to btullis@wikimedia.org

I'll follow up with a puppet change to admin/data.yaml

Change 704562 had a related patch set uploaded (by Btullis; author: Btullis):

[operations/puppet@production] Enable kerberos for btullis

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

Change 704562 merged by Btullis:

[operations/puppet@production] Enable kerberos for btullis

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

Change 711171 had a related patch set uploaded (by Btullis; author: Btullis):

[operations/puppet@production] Replace the username for btullis with Btullis

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

Change 711171 merged by Btullis:

[operations/puppet@production] Replace the username for btullis with Btullis

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

Change 731403 had a related patch set uploaded (by Btullis; author: Btullis):

[operations/puppet@production] Add initial personal dotfiles and one script

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

Change 731403 merged by Btullis:

[operations/puppet@production] Add initial personal dotfiles and one script

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

Change 742172 had a related patch set uploaded (by Jcrespo; author: Jcrespo):

[operations/puppet@production] admin: Fix path of btullis' dotfiles and one script

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

Change 742172 merged by Btullis:

[operations/puppet@production] admin: Fix path of btullis' dotfiles and one script

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