Firefox/Push/Progress Report/2017Q3: Difference between revisions

Jump to navigation Jump to search

Firefox/Push/Progress Report/2017Q3 (view source)

Revision as of 00:35, 5 August 2017

69 bytes removed ,  5 August 2017
Updated August 2nd confidence levels.
(Updated August 2nd confidence levels.)
Line 24: Line 24:
| align="left"|1.1 Create an API Layer for Ardere.
| align="left"|1.1 Create an API Layer for Ardere.
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 34: Line 34:
* Issue TBD
* Issue TBD
|
|
*Currently used through AWS interface. Want more of a command line interface (CLI). 1.1 is a prereq. for 1.3
*Work has not begun yet but still sufficient time to complete by end of the quarter.  
|-
|-
|align="left"| 1.2 Create a "smoke-test" for the service, a quick test that verifies it’s up and running.
|align="left"| 1.2 Create a "smoke-test" for the service, a quick test that verifies it’s up and running.
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 48: Line 48:
* Issue # [https://github.com/mozilla-services/push-service/issues/73 push-service#73]
* Issue # [https://github.com/mozilla-services/push-service/issues/73 push-service#73]
|
|
*Need to circle back on assessing confidence level for this one when JR is available, as he is the owner/champion.
*Work has begun.
 
* Created [https://github.com/mozilla-services/push-test push-test], but will fork ap-loadtest to create far better version.
* Created [https://github.com/mozilla-services/push-test push-test], but will fork ap-loadtest to create far better version.
|-
|-
|align="left"| 1.3 Github/Jenkins API call integration with Ardere
|align="left"| 1.3 Github/Jenkins API call integration with Ardere
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 65: Line 63:
*Issue # TBD
*Issue # TBD
|
|
*
*Dependent upon 1.1
|-
|-
|rowspan=3| 2. Better understanding of production run environment
|rowspan=3| 2. Better understanding of production run environment
| align="left"|2.1 Detailed heap memory consumption report as the OS sees memory under load.
| align="left"|2.1 Detailed heap memory consumption report as the OS sees memory under load.
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|65%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 80: Line 78:
*Issue # TBD
*Issue # TBD
|
|
*Already began this work
*Have done some planning.
|-
|-
| align="left"|2.2 Code in PyPy that allows us to dump detailed object graphs of allocated Python objects.
| align="left"|2.2 Code in PyPy that allows us to dump detailed object graphs of allocated Python objects.
Line 87: Line 85:
This involves a breakdown of what PyPy is doing.
This involves a breakdown of what PyPy is doing.
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 97: Line 95:
* Issue # TBD
* Issue # TBD
|
|
*External dependency on the contractor is a risk. Contractor has been identified and a request submitted via CASA.
*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.
|-
|-
| align="left"|2.3 Create a graph showing the delta for memory consumption over time on a per-release basis.
| align="left"|2.3 Create a graph showing the delta for memory consumption over time on a per-release basis.
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 111: Line 109:
* Issue # TBD
* Issue # TBD
|
|
*A lot of this work is already done.
*Have a dashboard that provides this information.
*First prototype  latest release
*Need to makes some changes to display the graphs all in a row (to show memory consumption on a per release basis).
*Next step is to create a dashboard will be datadog or quicksite. Need to run code to extract data metrics.
|-
|-
|rowspan=4|3. Reduce costs
|rowspan=4|3. Reduce costs
| align="left"|3.1 Create and implement a Rust PoC plan.  
| align="left"|3.1 Create and implement a Rust PoC plan.  
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 128: Line 125:
* Issue # TBD
* Issue # TBD
|
|
*Needs full spec from 3.2 so it can do the final binding.
*Plan has been created and is in the process of being implemented.
*Should map out what steps are necessary to bring it up to a production level deploy.
|-
|-
| align="left"|3.2 Spec a Rust <-> Python API of Rust PoC.
| align="left"|3.2 Spec a Rust <-> Python API of Rust PoC.
|align="center"|80%
|align="center"|80%
|align="center"|
|align="center"|100%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 143: Line 139:
*Issue # TBD
*Issue # TBD
|
|
*Not spec’d out yet. Documenting how the web socket client interacts with the service.
*API is spec’d out. Have started implementing it.
*Need for it to undergo Adere load testing.  
|-
|-
| align="left"|3.3 Kill Simplepush.
| align="left"|3.3 Kill Simplepush.
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 159: Line 154:
*[https://github.com/mozilla-services/autopush/issues/799 Issue 799: End Server Support for Simplepush]
*[https://github.com/mozilla-services/autopush/issues/799 Issue 799: End Server Support for Simplepush]
|
|
* Will need to remove the code needed to connect to simplepush.
*Last rollout we introduced the flag to turn it off.
*At this point we can turn it off at any point.
|-
|-
| align="left"|3.4 Relax VAPID checks for partner endpoints.
| align="left"|3.4 Relax VAPID checks for partner endpoints.
|align="center"|60%
|align="center"|60%
|align="center"|
|align="center"|100%
|align="center"|
|align="center"|
|align="center"|
|align="center"|
Line 173: Line 169:
*Issue # [https://github.com/mozilla-services/autopush/issues/938 938]
*Issue # [https://github.com/mozilla-services/autopush/issues/938 938]
|
|
* A lot of this work might already be done. Need to check with jr.
* Rolled out on stage for testing purposes but haven’t done it for any partners yet.
|-
|-
|}
|}
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1177415"

Navigation menu