Firefox/Push/Progress Report/2017Q3

From MozillaWiki
< Firefox‎ | Push/Progress Report
Revision as of 00:28, 29 July 2017 by Juliemccracken (talk | contribs) (removed extra percentage sign)
Jump to navigation Jump to search

July 25, 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%

API Layer for Ardere

  • Issue TBD
  • Currently used through AWS interface. Want more of a command line interface (CLI). 1.1 is a prereq. for 1.3
1.2 Create a "smoke-test" for the service, a quick test that verifies it’s up and running.

Smoketest to verify Push is up and running

  • Issue # TBD
  • Need to circle back on assessing confidence level for this one when JR is available, as he is the owner/champion.
1.3 Github/Jenkins API call integration with Ardere 50%

Github/Jenkins API call integration with Ardere

  • Issue # TBD
2. Better understanding of production run environment 2.1 Detailed heap memory consumption report as the OS sees memory under load. 60%

Detailed heap memory consumption report

  • Issue # TBD
  • Already began this work
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%

Detailed object graphs of allocated Python objects

  • Issue # TBD
  • External dependency on the contractor is a risk. Contractor has been identified and a request submitted via CASA.
2.3 Create a graph showing the delta for memory consumption over time on a per-release basis. 80%

Memory Consumption Per Release Graph

  • Issue # TBD
  • A lot of this work is already done.
  • First prototype latest release
  • Next step is to create a dashboard will be datadog or quicksite. Need to run code to extract data metrics.
3. Reduce costs 3.1 Create and implement a Rust PoC plan. 80%

Rust PoC Plan

  • Issue # TBD
  • Needs full spec from 3.2 so it can do the final binding.
  • Should map out what steps are necessary to bring it up to a production level deploy.
3.2 Spec a Rust <-> Python API of Rust PoC. 80%

Rust <-> Python API of Rust PoC

  • Issue # TBD
  • Not spec’d out yet. Documenting how the web socket client interacts with the service.
  • Need for it to undergo Adere load testing.
3.3 Kill Simplepush. 60%

Retirement of Simplepush

  • Will need to remove the code needed to connect to simplepush.
3.4 Relax VAPID checks for partner endpoints. 60%

Relaxing of VAPID checks for partner endpoints.

  • Issue # TBD
  • A lot of this work might already be done. Need to check with jr.