If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Give Francois access to the Treeherder RO replica DB

RESOLVED FIXED

Status

Tree Management
Treeherder: Infrastructure
P1
normal
RESOLVED FIXED
4 months ago
4 months ago

People

(Reporter: emorley, Assigned: emorley)

Tracking

Details

(Assignee)

Description

4 months ago
<jgraham> emorley, camd: francois_ is going to be working on autoclassification over the summer (between now and the start of August)
<jgraham> emorley: At some point in the next couple of days I suggest we set him up with access to the RO replica of the treeherder db
<jgraham> emorley: But no rush; once he's set up he will spend some time sheriffing -prototype to get an idea of how that works (I assume that's a better idea than starting off on production)
(Assignee)

Updated

4 months ago
Group: mozilla-employee-confidential
(Assignee)

Comment 1

4 months ago
Done (using steps at: https://treeherder.readthedocs.io/admin.html#direct-database-access).

I'll contact you out of bug with the RO replica connection specifics.

Please remember to enable SSL (and as "required") when connecting and if using the command line mysql client to use 5.7.x+ (not 5.5/5.6 since they are vulnerable to MITM). I would recommend using MySQLWorkbench:
https://www.mysql.com/products/workbench/

If using the CLI, make sure to also follow the Amazon docs on SSL connection options here:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MySQL.html#MySQL.Concepts.SSLSupport

Rather than have to download the Amazon CA cert separately you can instead point MySQLWorkbench or the CLI at the cert in the Treeherder repo:
https://github.com/mozilla/treeherder/tree/master/deployment/aws
Status: ASSIGNED → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.