Breakpad/Status Meetings/2017-02-22: Difference between revisions
< Breakpad | Status Meetings
Jump to navigation
Jump to search
(→Other Business: add note about schema file update problem) |
(→Splitting out collector (Antenna): antenna updates) |
||
| Line 31: | Line 31: | ||
=== Splitting out collector (Antenna) === | === Splitting out collector (Antenna) === | ||
* (miles, mbrandt, willkg, rpapa) Had a big meeting about load testing needs, plan and schedule. | |||
* (miles) Set up a -stage-like environment for load tests. Working on redoing deployment pipeline. | |||
* (mbrandt, rpapa) Working on load testing for the next week hopefully with results by Friday, February 24th. | |||
=== Deprecation rampage === | === Deprecation rampage === | ||
=== Processor rewrite === | === Processor rewrite === | ||
Revision as of 15:32, 22 February 2017
« previous meeting — index – next week » create?
Meeting Info
Breakpad status meetings occur on Wed at 10:00am Pacific Time.
Conference numbers:
Vidyo: Stability 650-903-0800 x92 conf 98200# 800-707-2533 (pin 369) conf 98200#
IRC backchannel: #breakpad
Mountain View: Dancing Baby (3rd floor)
Operations Updates
Project Updates
Deployment Triage
PR Triage
Major Projects
Splitting out collector (Antenna)
- (miles, mbrandt, willkg, rpapa) Had a big meeting about load testing needs, plan and schedule.
- (miles) Set up a -stage-like environment for load tests. Working on redoing deployment pipeline.
- (mbrandt, rpapa) Working on load testing for the next week hopefully with results by Friday, February 24th.
Deprecation rampage
Processor rewrite
Upgrading elasticsearch
Other Business
- Crash Reports schema file is not updated on S3: https://bugzilla.mozilla.org/show_bug.cgi?id=1340105
- that file is pushed to s3 via a crontabber job, however that job runs on a long-running admin node and the code doesn't automatically get updated on it
- is there a written process for updating that file?
- are there complexities in updating the code on the admin nodes? is that written down somewhere?
- how do we want to deal with code deploys and long-running nodes?