Breakpad/Status Meetings/2017-01-04
From MozillaWiki
< Breakpad | Status Meetings
« previous meeting — index – next week » create?
Contents
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
- what's the status of infrastructure?
- not much has changed, monitoring is working
- wakes miles up!
- not much has changed, monitoring is working
- 5 minute blip downtime, 2 weeks ago
- seemed to be a failure of the healthcheck
- miles to follow up
- priorities:
- antenna deploy
- rebuilding the elastic search cluster
- includes an upgrade?
- needs a plan, adrian has concerns about upgrade path
- mid-term planning, devs please dockerize all the things:
- there is no overlap between dev and ops working hours
- we will switch to stage auto-deploy (CI/CD)
- prod will have a window for deploys Wednesday morning at 9AM PST until 10AM PST
- we will assume we need to deploy unless there is mail saying otherwise
Project Updates
- where do we want to be end-of-January? (goals, not deadlines)
- elasticsearch cluster in better shape
- migrated to antenna
- e2etests in better shape
Deployment Triage
PR Triage
Major Projects
Splitting out collector (Antenna)
- Antenna -dev is running, albeit with out pigeon
- Need to finish up load test system, get system test running in -dev, get -stage working and updated and figure out migration plan for getting to -prod
Deprecation rampage
- nothing new (but going to proceed soon)
e2e tests
- Will taking over from Peter to drive e2e changes
- API tests are written; needs to be reviewed
- phantomjs support was implemented; needs to be reviewed
- [mbrandt] Beginning work on cleanup of the tests into smarter components so we can track our coverage in TestRail
- [mbrandt] tox?
Processor rewrite
- https://github.com/lonnen/processor/
- lots of new commits
- adrian has some feedback about interface design
- we are going to try and reconcile crashmill and processor by the end of the week
Signature generation hacking
- working on a plan
- step 1. make it easy to test just signature generation rules
- isolate them
- write a script that takes a list of crash ids, run the rules on their data, and shows the differences
- step 2. integrate changes in the new processor
- step 3. find more brilliant ideas
- step 1. make it easy to test just signature generation rules