Confirmed users
513
edits
Auto-tools/Projects/Charts: Difference between revisions
formatting
Klahnakoski (talk | contribs) (reword) |
Klahnakoski (talk | contribs) (formatting) |
||
| Line 1: | Line 1: | ||
= charts.mozilla.org | = Overview of charts.mozilla.org = | ||
This project is responsible for presenting the dashboards and details required by management to track progress on the B2G releases and highlight possible bottlenecks in development. | This project is responsible for presenting the dashboards and details required by management to track progress on the B2G releases and highlight possible bottlenecks in development. | ||
This project is highly visible to the FirefoxOS team, and Mozilla in general. | This project is highly visible to the FirefoxOS team, and Mozilla in general. | ||
= Hacking/Contributers = | |||
This project can benefit from your help. | This project can benefit from your help. | ||
| Line 15: | Line 13: | ||
* Setting up a development environment is very simple because of this simple static nature | * Setting up a development environment is very simple because of this simple static nature | ||
==Good First Bugs== | |||
<div> | <div> | ||
| Line 32: | Line 30: | ||
</div> | </div> | ||
==All Open Issues== | |||
<div> | <div> | ||
<bugzilla> | <bugzilla> | ||
| Line 46: | Line 44: | ||
==Contact== | |||
You can contact me, Kyle Lahnakoski | You can contact me, Kyle Lahnakoski | ||
| Line 54: | Line 52: | ||
I am available to get you started and discuss bus that you may find interesting. | I am available to get you started and discuss bus that you may find interesting. | ||
= Architecture = | |||
The '''charts.mozilla.org''' application is a pure Javascript client running on the browser. It accesses the [https://wiki.mozilla.org/BMO/ElasticSearch BMO/ES] cluster for data. | The '''charts.mozilla.org''' application is a pure Javascript client running on the browser. It accesses the [https://wiki.mozilla.org/BMO/ElasticSearch BMO/ES] cluster for data. | ||
== Web Server == | |||
[[image:Auto_tools_Projects_Charts_Architecture.png|right|thumb|200px]] | [[image:Auto_tools_Projects_Charts_Architecture.png|right|thumb|200px]] | ||
The application itself is served as a set of static html and javascript files from the Mozilla PAAS Stackato servers. There are two versions, Production and Staging; the latter will usually have more features, while being slightly more buggy. Please us the staging server as much as possible: like Firefox Nightly, using staging will help find bugs sooner. | The application itself is served as a set of static html and javascript files from the Mozilla PAAS Stackato servers. There are two versions, Production and Staging; the latter will usually have more features, while being slightly more buggy. Please us the staging server as much as possible: like Firefox Nightly, using staging will help find bugs sooner. | ||
| Line 73: | Line 71: | ||
Since the app is entirely client-side, it does not matter where the application is served from (I have various development versions on my people page). If both these servers are down, a simple <code>git clone</code> can allow you to "serve" the app directly from your local filesystem. | Since the app is entirely client-side, it does not matter where the application is served from (I have various development versions on my people page). If both these servers are down, a simple <code>git clone</code> can allow you to "serve" the app directly from your local filesystem. | ||
== esFrontline == | |||
esFrontline is a simple Python-based proxy to limit ES requests to search requests and limit the indexes exposed. Other than these restrictions, ''this proxy is invisible to client application''. See https://wiki.mozilla.org/BMO/ElasticSearch for more details. | esFrontline is a simple Python-based proxy to limit ES requests to search requests and limit the indexes exposed. Other than these restrictions, ''this proxy is invisible to client application''. See https://wiki.mozilla.org/BMO/ElasticSearch for more details. | ||
== ElasticSearch Clusters == | |||
Once the application is downloaded it will attempt to contact both the private and public clusters simultaneously; whichever responds will be chosen for all future connections, with preference given to the private cluster. The queries for the dashboard are then sent to the cluster as the dashboard app requires. | Once the application is downloaded it will attempt to contact both the private and public clusters simultaneously; whichever responds will be chosen for all future connections, with preference given to the private cluster. The queries for the dashboard are then sent to the cluster as the dashboard app requires. | ||
The clusters are configured to accept requests from any client. Hopefully this will promote development of alternative dashboards and charts. | The clusters are configured to accept requests from any client. Hopefully this will promote development of alternative dashboards and charts. | ||
== Development == | |||
The Development server is responsible for secondary indexes built from the main <code>bug_version</code>. Currently it maintains the hierarchy index for determining recursive dependencies on bugs. | The Development server is responsible for secondary indexes built from the main <code>bug_version</code>. Currently it maintains the hierarchy index for determining recursive dependencies on bugs. | ||
== Slowness == | |||
There are some sources of slowness: | There are some sources of slowness: | ||
| Line 108: | Line 106: | ||
* For problems with the database, e.g. basic framework loads but no data appears, see jakem, cyliang, or fubar in #it on irc. | * For problems with the database, e.g. basic framework loads but no data appears, see jakem, cyliang, or fubar in #it on irc. | ||
== Instructions == | |||
* [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30081453#MozillaPaaS%28Stackato%29-ObtainingandInstallingtheClient Stackato Instructions on Mana] | * [https://mana.mozilla.org/wiki/pages/viewpage.action?pageId=30081453#MozillaPaaS%28Stackato%29-ObtainingandInstallingtheClient Stackato Instructions on Mana] | ||
* [https://api.paas.allizom.org/console/overview/ Stackato web console ] | * [https://api.paas.allizom.org/console/overview/ Stackato web console ] | ||
= Past Problems = | |||
== CORS == | |||
The charts application makes cross-platform requests: The app is served from charts.mozilla.org and data requested from esfrontline.bugzilla.mozilla.org. This requires the various proxy servers (not shown in architecture) ensure the <code>Access-Control-Allow-Origin</code> HTTP response header be set appropriately. In the past it has been shown this header is stripped from the esFrontline response and set according to Operations' guidelines. | The charts application makes cross-platform requests: The app is served from charts.mozilla.org and data requested from esfrontline.bugzilla.mozilla.org. This requires the various proxy servers (not shown in architecture) ensure the <code>Access-Control-Allow-Origin</code> HTTP response header be set appropriately. In the past it has been shown this header is stripped from the esFrontline response and set according to Operations' guidelines. | ||
== Clusters Down or Not Responding == | |||
ElasticSearch is still prone to OutOfMemoryExceptions. Occasionally, this will bring down nodes in the cluster. '''The best solution has always been to reboot the problem nodes''' (or all of them). | ElasticSearch is still prone to OutOfMemoryExceptions. Occasionally, this will bring down nodes in the cluster. '''The best solution has always been to reboot the problem nodes''' (or all of them). | ||
The chance of data loss is very low: First, the data is replicated 2 times (for a total of three copies). Second, the ETL daemon (responsible for filling the cluster) performs some simple data checks, and writes full history of all changed bugs: Effectively overwriting corruption on any bugs that does occur. Corruption on inactive bugs can linger; assuming corruption exists, and assuming a change happened when the cluster was misbehaving, and assuming the ETL did not detect the misbehavior. Third, there are consistency checks built into MoDevMetrics that monitors or consistency between bug versions, corruption is sometimes detected, and inevitably fixed by the next ETL run. | The chance of data loss is very low: First, the data is replicated 2 times (for a total of three copies). Second, the ETL daemon (responsible for filling the cluster) performs some simple data checks, and writes full history of all changed bugs: Effectively overwriting corruption on any bugs that does occur. Corruption on inactive bugs can linger; assuming corruption exists, and assuming a change happened when the cluster was misbehaving, and assuming the ETL did not detect the misbehavior. Third, there are consistency checks built into MoDevMetrics that monitors or consistency between bug versions, corruption is sometimes detected, and inevitably fixed by the next ETL run. | ||