Page MenuHomePhabricator

Create a parallel OTRS database with a frozen snapshot of the production one
Closed, ResolvedPublic

Description

A new database will be setup, separate for the production otrs database (scheduled to be hosted on test db host db1077) from a consistent copy/backup of the original one.

This will be used to test the upgrade process before production "for real" upgrade.

Event Timeline

jcrespo triaged this task as Medium priority.Jul 14 2020, 2:13 PM
jcrespo moved this task from Triage to In progress on the DBA board.

I was planning on doing this slowly with @akosiaris so at the same time he learned about streamlined db provisioning system, but I think serviceops may be quite busy at the time, so I will resolve this quickly on my own.

Reedy renamed this task from Create a parallel OTRS database with a freezed snapshot of the production one to Create a parallel OTRS database with a frozen snapshot of the production one.Jul 14 2020, 2:16 PM

Mentioned in SAL (#wikimedia-operations) [2020-07-14T14:42:26Z] <jynus> stopping db1117:3322 (m2) replication temp. for otrs db cloning T257928

jcrespo moved this task from In progress to Blocked external/Not db team on the DBA board.

A clone of the otrs database has been setup on db1077. The question now, @akosiaris, is what needs access to it in order to add the required grants/accounts and firewall holes, if necessary.

A clone of the otrs database has been setup on db1077. The question now, @akosiaris, is what needs access to it in order to add the required grants/accounts and firewall holes, if necessary.

You are awesome! Thanks!

Access wise, otrs1001.eqiad.wmnet (10.64.16.39) should suffice.

Np. More questions: do we setup it with a separate user/password (to avoid mistakes with the production db) or the same (for convenience).

Np. More questions: do we setup it with a separate user/password (to avoid mistakes with the production db) or the same (for convenience).

I 'd say the former (separate user/password). Just to be on the safe side.

Credentials have been setup and shared on client root dir, feel free to productionize as you see adequate:

root@otrs1001:/root$ cat otrs_test_credentials
[client]
host = db1077.eqiad.wmnet
...

Port should be open. However, while everything should work, I wasn't unable to test directly as mysql client is not installed on client host.

Change 616012 had a related patch set uploaded (by Jcrespo; owner: Jcrespo):
[operations/puppet@production] mariadb: Set db1077 in read-write

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

Change 616012 merged by Jcrespo:
[operations/puppet@production] mariadb: Set db1077 in read-write

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