1002295 - Deploy tokenserver 1.2.5 to stage

Status: VERIFIED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Ryan Kelly [:rfkelly]]

This version of tokenserver completes the databases changes from Bug 988643.  It updates the app code to start using/populating the new "nodeid" column, and populates the column for existing rows.

    Bug 988643 - add index for looking up assignments by node node

The migration should be straightforward now that we've got alembic working properly and stage and prod dbs are in the same state:

  * Build the rpm and deploy to all webheads
  * From one of the webheads, run the migration tool as follows:

      ./bin/alembic upgrade head

After this we'll be able to use the nodeid index for much more efficient manipulations of node assignments, e.g. when nuking a node.

Comment 1

[Benson Wong [:mostlygeek]]

Deployed stack and ran database upgrade: 

[bwong@--- tokenserver]$ time ./bin/alembic upgrade head
INFO  [alembic.migration] Context impl MySQLImpl.
INFO  [alembic.migration] Will assume non-transactional DDL.
INFO  [alembic.migration] Running upgrade 846f28d1b6f -> 6569dd9a060, populate nodeid column and index

real    2m23.933s
user    0m0.785s
sys     0m0.304s

mysql> select count(1) from users;
+----------+
| count(1) |
+----------+
|  1138773 |
+----------+
1 row in set (0.26 sec)


The RDS is able create ~7800 index entries / second with the 500 write PIOPS. We can use this number to estimate the production performance impact window.

Comment 2

[Benson Wong [:mostlygeek]]

DNS updated to token.stage.mozaws.net points at the new stack.

Comment 3

[James Bonacci [:jbonacci]]

I will verify this later today...

Comment 4

[James Bonacci [:jbonacci]]

Stage looks good to me.
Let's roll this forward to Production (I can't seem to find the Prod deploy ticket, though)...