Confirmed users
537
edits
(→Deprecation rampage: add update for adrian) |
(→Operations Updates: ops updates) |
||
Line 18: | Line 18: | ||
== Operations Updates == | == Operations Updates == | ||
* Miles wrote up a new migration document with different details than in past versions. https://docs.google.com/document/d/18xKCDeXQDpoPtVpxJ9BeisAMrxLXyKhFUIfJNWklaYM/edit | |||
** we're going to "tee" off the infrastructure at Antenna and then build two parallel Socorro universes which should let us figure out all the stuff and then cut over smoothly | |||
* We saw a weird uptick in processor/elasticsearch save_raw_and_processed times and the symbols api hits. | |||
** RabbitMQ queues were backing up, so Miles threw more processors at the queue. | |||
** It's weird because it doesn't look like we're processing more crashes. | |||
** Adrian fixed some issues in the processor and maybe that'll make things better. We'll find out after -prod deploy and investigate further if need be. | |||
* System test for Tecken is working again. | |||
** There are some issues with https urls, but Peter and Miles will take that offline. | |||
* We have a crontabber thing that runs in SCL3 that needs to send data to postgres for ADI. | |||
** How to do this in the new upcoming infrastructure? | |||
** Switch it to push via HTTP to the webapp rather than send stuff to Postgres. | |||
** Also, that box is "interesting", so it's probably hard to update/deploy/etc. | |||
** We might be able to get rid of this altogether. | |||
** Peter will file a bug about this server. | |||
* Miles asked whether we can ditch crontabber on admin nodes. Probably not, yet. | |||
* Official ES migration plan involves snapshots and that's the way it's going to go. | |||
== Security Updates == | == Security Updates == |