751736 - create databases and user permissions for treestatus.mozilla.org

Status: RESOLVED FIXED

(Data & BI Services Team :: DB: MySQL, task)

Description

[Chris Turra [:cturra]]

there currently is a treestatus_dev database/user setup and we now need stage and prod databases/users for the treestatus project. looks like we only need a read-write account, no read-only required.

Comment 1

[Sheeri Cabral [:sheeri]]

Any preferences on where the database lives for production? e.g. "on the same db server as graphs" or "tinderbox" or whatever?

Comment 2

[Chris Turra [:cturra]]

:sheeri dev currently sits on dev2.db.phx1.mozilla.com (zev-zeus-rw.db.phx1.mozilla.com) so you can use that for stage. for production, please use generic1.db.phx1.mozilla.com.

Comment 3

[Sheeri Cabral [:sheeri]]

passwords and such are in /home/cturra/treestatus_mysql_auth.txt on generic1.

Comment 4

[Chris Turra [:cturra]]

:sheeri while setting up the stage environment i found that the database name is: treestats_allizom_org rather than treestatus_allizom_org. can i please have this renamed?

Comment 5

[Sheeri Cabral [:sheeri]]

oof, typos! Sure.

mysql> show tables;
+---------------------------------+
| Tables_in_treestats_allizom_org |
+---------------------------------+
| log                             |
| status_stack_trees              |
| status_stacks                   |
| tokens                          |
| trees                           |
| users                           |
+---------------------------------+
6 rows in set (0.00 sec)

mysql> create database treestatus_allizom_org;
Query OK, 1 row affected (0.03 sec)

mysql> alter table log rename treestatus_allizom_org.log; alter table status_stack_trees rename treestatus_allizom_org.status_stack_trees; alter table status_stacks rename treestatus_allizom_org.status_stacks; alter table tokens rename treestatus_allizom_org.tokens; alter table trees rename treestatus_allizom_org.trees; alter table users rename treestatus_allizom_org.users;
Query OK, 0 rows affected (0.01 sec)

Query OK, 0 rows affected (0.01 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.01 sec)

Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.01 sec)

mysql> show tables;
Empty set (0.00 sec)

mysql> drop database treestats_allizom_org;
Query OK, 0 rows affected (0.09 sec)

Comment 6

[Sheeri Cabral [:sheeri]]

also updated the privileges:


mysql> drop user treestatus_stage@'10.8.70.20_';
Query OK, 0 rows affected (0.10 sec)

mysql>  GRANT ALL PRIVILEGES ON `treestatus_allizom_org`.* to treestatus_stage@'10.8.70.20_' IDENTIFIED BY PASSWORD 'HASH ELIDED' ;