670
edits
Firefox/Push/Progress Report/2017Q3: Difference between revisions
Firefox/Push/Progress Report/2017Q3 (view source)
Revision as of 01:22, 5 August 2017
, 5 August 2017Added additional Issues
(Corrected some of the issues.) |
(Added additional Issues) |
||
| Line 32: | Line 32: | ||
|align="left"| | |align="left"| | ||
API Layer for Ardere | API Layer for Ardere | ||
*[https://github.com/mozilla-services/push-okr/issues/39 Issue 39: Create an API Layer for Ardere] | |||
| | | | ||
*Work has not begun yet but still sufficient time to complete by end of the quarter. | *Work has not begun yet but still sufficient time to complete by end of the quarter. | ||
| Line 45: | Line 46: | ||
| | | | ||
Smoketest to verify Push is up and running | Smoketest to verify Push is up and running | ||
*[https://github.com/mozilla-services/push-okr/issues/40 Issue 40: New smoke-tester for autopush] | |||
*[https://github.com/mozilla-services/push-service/issues/73 Issue 73: Rebuild testing python script for webpush] | *[https://github.com/mozilla-services/push-service/issues/73 Issue 73: Rebuild testing python script for webpush] | ||
| | | | ||
| Line 60: | Line 62: | ||
|align="left"| | |align="left"| | ||
Github/Jenkins API call integration with Ardere | Github/Jenkins API call integration with Ardere | ||
*[https://github.com/mozilla-services/push-okr/issues/41 Issue 41: Jenkins API integration with Ardere] | |||
| | | | ||
*Dependent upon 1.1 | *Dependent upon 1.1 | ||
| Line 74: | Line 77: | ||
|align="left"| | |align="left"| | ||
Detailed heap memory consumption report | Detailed heap memory consumption report | ||
*[https://github.com/mozilla-services/push-okr/issues/42 Issue 42: Detailed heap memory consumption] | |||
*[https://github.com/mozilla-services/push-service/issues/76 Issue 76: Detail autopush heap's memory under load] | |||
*[https://github.com/mozilla-services/autopush/issues/802 Issue 802: determine cause of memory leak on pypy (especially connection) nodes] | *[https://github.com/mozilla-services/autopush/issues/802 Issue 802: determine cause of memory leak on pypy (especially connection) nodes] | ||
| | | | ||
| Line 91: | Line 96: | ||
|align="left"| | |align="left"| | ||
Detailed object graphs of allocated Python objects | Detailed object graphs of allocated Python objects | ||
*[https://github.com/mozilla-services/push-okr/issues/43 Issue 43: PyPy object graph memory dumps] | |||
| | | | ||
*Still working on getting an SOW in place with the contractor. Movement through the CASA process has been slow. There is an open question re. how many hours this contractor will deliver in the calendar year for Mozilla as a whole. | *Still working on getting an SOW in place with the contractor. Movement through the CASA process has been slow. There is an open question re. how many hours this contractor will deliver in the calendar year for Mozilla as a whole. | ||
| Line 104: | Line 110: | ||
|align="left"| | |align="left"| | ||
Memory Consumption Per Release Graph | Memory Consumption Per Release Graph | ||
*[https://github.com/mozilla-services/push-okr/issues/44 Issue 44: Dashboard for memory use over time] | |||
| | | | ||
*Have a dashboard that provides this information. | *Have a dashboard that provides this information. | ||
| Line 119: | Line 126: | ||
|align="left"| | |align="left"| | ||
Rust PoC Plan | Rust PoC Plan | ||
*[https://github.com/mozilla-services/push-okr/issues/45 Issue 45: Create and implement a Rust PoC] | |||
*[https://github.com/mozilla-services/autopush/issues/978 Issue 978 Create distilled threaded logic for websocket server for Rust PoC] | *[https://github.com/mozilla-services/autopush/issues/978 Issue 978 Create distilled threaded logic for websocket server for Rust PoC] | ||
| | | | ||
| Line 133: | Line 141: | ||
|align="left"| | |align="left"| | ||
Rust <-> Python API of Rust PoC | Rust <-> Python API of Rust PoC | ||
*[https://github.com/mozilla-services/push-okr/issues/46 Issue 46: Spec a Rust <-> Python API of Rust PoC] | |||
| | | | ||
*API is spec’d out. Have started implementing it. | *API is spec’d out. Have started implementing it. | ||
| Line 163: | Line 172: | ||
|align="left"| | |align="left"| | ||
Relaxing of VAPID checks for partner endpoints. | Relaxing of VAPID checks for partner endpoints. | ||
*Issue | *[https://github.com/mozilla-services/push-okr/issues/48 Issue 48: Relax VAPID checks for Partner Endpoints] | ||
*[https://github.com/mozilla-services/autopush/issues/938 Issue 938: Don't check Vapid sig value for partner endpoint users] | |||
| | | | ||
* Rolled out on stage for testing purposes but haven’t done it for any partners yet. | * Rolled out on stage for testing purposes but haven’t done it for any partners yet. | ||