help in reporting, fixing and cleaning up errors

Could you be a bit more specific, maybe? This feels a bit like "I want to help anywhere and everywhere" ticket (which is very kind) but this can also make it quite hard to get an idea which access levels might be appropriate/needed depending on what exactly you plan to do... :)

In T231684#5456991, @Aklapper wrote:

help in reporting, fixing and cleaning up errors

Could you be a bit more specific, maybe? This feels a bit like "I want to help anywhere and everywhere" ticket (which is very kind)

I understand @Aklapper and you have a point there. The issue is though I may have access to beta-cluster LS etc, I'll not be helping everywhere or anywhere as I'm not that capable to understand all logs I see.

The issue is, I'll be making contributions from my end by tackling what I'm capable (for example on mediawiki/*, I merge only what I fully understand and have tested). It's something like that but let me try to be specific a bit.

1. Access to beta-cluster Logstash - for viewing staged error logs and fix issues I find (within my reach) and fix them before they hit production.
2. Maybe SSH access beta-cluster - in order for me to test fixes both locally and on BC to make sure it's fixed before it hits production.

Not sure if both make sense but that's how specific I can go. Thanks!

In T231684#5457017, @D3r1ck01 wrote:

In T231684#5456991, @Aklapper wrote:

help in reporting, fixing and cleaning up errors

Could you be a bit more specific, maybe? This feels a bit like "I want to help anywhere and everywhere" ticket (which is very kind)

I understand @Aklapper and you have a point there. The issue is though I may have access to beta-cluster LS etc, I'll not be helping everywhere or anywhere as I'm not that capable to understand all logs I see.

The issue is, I'll be making contributions from my end by tackling what I'm capable (for example on mediawiki/*, I merge only what I fully understand and have tested). It's something like that but let me try to be specific a bit.

1. Access to beta-cluster Logstash - for viewing staged error logs and fix issues I find (within my reach) and fix them before they hit production.

I guess that's possible without doing anything specific - just create an account or share the shared account PWD with you. @Krenair, what do you think?

2. Maybe SSH access beta-cluster - in order for me to test fixes both locally and on BC to make sure it's fixed before it hits production.

Manually editing files on beta is going to blow the (beta)world :-). Jenkins overrides them all the time.

Not sure if both make sense but that's how specific I can go. Thanks!

In T231684#5504698, @Urbanecm wrote:

In T231684#5457017, @D3r1ck01 wrote:

In T231684#5456991, @Aklapper wrote:

help in reporting, fixing and cleaning up errors

Could you be a bit more specific, maybe? This feels a bit like "I want to help anywhere and everywhere" ticket (which is very kind)

I understand @Aklapper and you have a point there. The issue is though I may have access to beta-cluster LS etc, I'll not be helping everywhere or anywhere as I'm not that capable to understand all logs I see.

The issue is, I'll be making contributions from my end by tackling what I'm capable (for example on mediawiki/*, I merge only what I fully understand and have tested). It's something like that but let me try to be specific a bit.

1. Access to beta-cluster Logstash - for viewing staged error logs and fix issues I find (within my reach) and fix them before they hit production.

I guess that's possible without doing anything specific - just create an account or share the shared account PWD with you. @Krenair, what do you think?

We could do either. It looks like we have two users - the shared one with credentials on deployment-deploy01, and an individual one for cwhite. Could just make a new user for Derick, or share the password with him, or give him SSH access. I don't mind which as long as someone (or some group of supporting existing users) signs off on whichever option we're going to do.

In T231684#5504698, @Urbanecm wrote:

2. Maybe SSH access beta-cluster - in order for me to test fixes both locally and on BC to make sure it's fixed before it hits production.

Manually editing files on beta is going to blow the (beta)world :-). Jenkins overrides them all the time.

Eh, I've been known to sneakily test stuff on beta while Jenkins is not looking from time to time.

The reason beta-cluster Logstash no longer uses regular LDAP I believe has to do with privacy and sensitive nature of the data there. It is currently limited to Beta Cluster roots, and presumably requires an NDA on-file.

In T231684#5504758, @Krinkle wrote:

The reason beta-cluster Logstash no longer uses regular LDAP I believe has to do with privacy and sensitive nature of the data there. It is currently limited to Beta Cluster roots, and presumably requires an NDA on-file.

AFAIK deployment-prep has no NDA requirement (there was some talk about adding one back in dark, dark times before Let's Encrypt, when people were discussing the foundation procuring TLS certificates for beta and putting them on some beta instances - AFAIK it never happened). Password authentication against Wikimedia LDAP is against the Cloud Services ToU.

Hi @xSavitar, is this still wanted?

@xSavitar: Could you please answer the last comment? Thanks in advance!

Thanks for pinging @Aklapper, much appreciated. I had already forgotten about this and I had to read the logs before I remembered.

@Majavah, I think this is no longer needed as I've already had logstash access and deployment access. So it's good. I'll go ahead and close it.

See: T268150: LDAP access to the "nda" group for Alangi Derick and T281564: Requesting access to Deployment shell for derick

Thank you @Majavah 🙏🏽