Firefox/Push/Progress Report/2017Q3

August 2, 2017

Q3 OKR Progress

Objective	Key Result	Confidence	Features	Notes
July 19	Aug 2	Aug 16	Aug 30	Sep 13	Sep 27	Score
1. Provide a more useful testing environment for WebPush.	1.1 Create an API Layer for Ardere.	50%	50%						API Layer for Ardere Issue 39: Create an API Layer for Ardere	Work has not begun yet but still sufficient time to complete by end of the quarter.
	1.2 Create a "smoke-test" for the service, a quick test that verifies it’s up and running.	50%	50%						Smoketest to verify Push is up and running Issue 40: New smoke-tester for autopush Issue 73: Rebuild testing python script for webpush	Work has begun. Created push-test, but will fork ap-loadtest to create far better version.
	1.3 Github/Jenkins API call integration with Ardere	50%	50%						Github/Jenkins API call integration with Ardere Issue 41: Jenkins API integration with Ardere	Dependent upon 1.1
2. Better understanding of production run environment	2.1 Detailed heap memory consumption report as the OS sees memory under load.	60%	65%						Detailed heap memory consumption report Issue 42: Detailed heap memory consumption Issue 76: Detail autopush heap's memory under load Issue 802: determine cause of memory leak on pypy (especially connection) nodes	Have done some planning.
	2.2 Code in PyPy that allows us to dump detailed object graphs of allocated Python objects. Note: Contractor is expected to help with this work. This involves a breakdown of what PyPy is doing.	50%	50%						Detailed object graphs of allocated Python objects 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.
	2.3 Create a graph showing the delta for memory consumption over time on a per-release basis.	80%	90%						Memory Consumption Per Release Graph Issue 44: Dashboard for memory use over time	Have a dashboard that provides this information. Need to makes some changes to display the graphs all in a row (to show memory consumption on a per release basis).
3. Reduce costs	3.1 Create and implement a Rust PoC plan.	80%	80%						Rust PoC Plan Issue 45: Create and implement a Rust PoC Issue 978 Create distilled threaded logic for websocket server for Rust PoC	Plan has been created and is in the process of being implemented.
	3.2 Spec a Rust <-> Python API of Rust PoC.	80%	100%						Rust <-> Python API of Rust PoC Issue 46: Spec a Rust <-> Python API of Rust PoC	API is spec’d out. Have started implementing it.
	3.3 Kill Simplepush.	60%	90%						Retirement of Simplepush Issue 47: Retire SimplePush Issue 799: End Server Support for Simplepush Issue 886: Obsolete UDP functions from autopush	Last rollout we introduced the flag to turn it off. At this point we can turn it off at any point.
	3.4 Relax VAPID checks for partner endpoints.	60%	100%						Relaxing of VAPID checks for partner endpoints. Issue 48: Relax VAPID checks for Partner Endpoints 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.