I assume this is why I can't log into grafana - ran into it a few months
ago but couldn't figure out why I didn't have access and never followed up.
If I could be added that'd be great.

Change 475995 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/puppet@production] admin: Add Mvolz to ldap-only users

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

Change 475995 merged by Jcrespo:
[operations/puppet@production] admin: Add Mvolz to ldap-only users

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

@Mvolz you have been added to the wmf group, please verify you can now log in into Grafana: https://grafana.wikimedia.org/login?redirect=%2F

In T209901#4777257, @jcrespo wrote:

@Mvolz you have been added to the wmf group, please verify you can now log in into Grafana: https://grafana.wikimedia.org/login?redirect=%2F

Thanks, I confirmed that I can log in now.

@Jdforrester-WMF since this task is visible on the ops clinic board, is it ok if we mark this as "Resolved" and let whoever needs access to create a new task as @jcrespo suggested?

In T209901#4793822, @jijiki wrote:

@Jdforrester-WMF since this task is visible on the ops clinic board, is it ok if we mark this as "Resolved" and let whoever needs access to create a new task as @jcrespo suggested?

Not really. Access to these services is part of the day job of the individuals I mentioned. Making people jump through hoops is decidedly not helpful.

In T209901#4795036, @Jdforrester-WMF wrote:

In T209901#4793822, @jijiki wrote:

@Jdforrester-WMF since this task is visible on the ops clinic board, is it ok if we mark this as "Resolved" and let whoever needs access to create a new task as @jcrespo suggested?

Not really. Access to these services is part of the day job of the individuals I mentioned. Making people jump through hoops is decidedly not helpful.

We're not doing this to make people jump through hoops, we're just following our standard workflow, as listed https://wikitech.wikimedia.org/wiki/LDAP/Groups and https://phabricator.wikimedia.org/project/profile/1564/:

• one access request task per person (to make them quickly actionable and not tie multiple processes together) as those are reviewed on an ongoing basis by the "SRE clinic duty"
• to get confirmation that it works for the users and to comfirm the correct UID/username (in particular for users who also have shell access)

Going forward a similar task should be opened for new hires as well.

I don't think it's unreasonable to ask for a quick "i need this for ..". Access requests should be based on a real need. It's not just an oversight in an onboarding process. They require real code changes too. We are more than happy to add people based on individual need, also with high priority. But in this form as a blanket addition based on job role i'm afraid we have to decline it.

In T209901#4805591, @MoritzMuehlenhoff wrote:

we're just following our standard workflow, as listed https://wikitech.wikimedia.org/wiki/LDAP/Groups and https://phabricator.wikimedia.org/project/profile/1564/:

• one access request task per person (to make them quickly actionable and not tie multiple processes together) as those are reviewed on an ongoing basis by the "SRE clinic duty"

Aha, sorry, didn't know that. Will open follow-up tasks.