CrashKill/StabilityWeek2013/Actions
Jump to navigation
Jump to search
| Session | Person | Item | Bug | Status |
|---|---|---|---|---|
| Rethinking Socorro Storage | laura | Push on the ops/training/support troubles. Try and get some dedicated attention (a person, for instance) allocated to us. | ? | |
| Rethinking Socorro Storage | lonnen | Backups: costed on Amazon Glacier | ? | |
| Rethinking Socorro Storage | laura | Backups: waiting on bmoss to approve the expense | ? | |
| Rethinking Socorro Storage | erik, rhelmer | Write a failing test against some kind of playground environment to expose Thrift failures. Once that's failing, we can do experiments to figure out what's wrong. | ? | |
| Rethinking Socorro Storage | selena | Research alternative connection methods to Thrift | ? | |
| Rethinking Socorro Storage | rhelmer | Rhelmer will look at CM4 and see what we can get out of that for monitoring, etc | ? | |
| Rethinking Socorro Storage | selena | Go shopping for query tools - Cascading, Hive, Impala, etc - must be open source | ? | |
| Rethinking Socorro Storage | selena | Research alternatives to HBase | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | mbrandt | Get Selenium suite polling for new Socorro commits so the tests get run more promptly and we have less trouble tracking down regressions. | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | selena | How about some tests for our stored procs? Write some. They'll call the procs through the middleware layer. | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | mbrandt | Stop running tests against dev. | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | selena, rhelmer, lonnen | Audit stage's config; make sure it's the same as prod. | ? | |
| Stats | lonnen | File a bug and do something about it. | bug 908334 | FIXED |