| OLD | NEW |
| 1 Cluster Telemetry | 1 Cluster Telemetry |
| 2 ================= | 2 ================= |
| 3 | 3 |
| 4 ### Contents ### | 4 ### Contents ### |
| 5 | 5 |
| 6 * [Overview](#overview) | 6 * [Overview](#overview) |
| 7 * [Framework Usage](#framework_usage) | 7 * [Framework Usage](#framework_usage) |
| 8 * [System Architecture](#system_architecture) | 8 * [System Architecture](#system_architecture) |
| 9 + [System Diagram](#system_diagram) | 9 + [System Diagram](#system_diagram) |
| 10 + [Detailed explanation of steps](#detailed_explanation) | 10 + [Detailed explanation of steps](#detailed_explanation) |
| (...skipping 63 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 74 | 74 |
| 75 <a name="detailed_explanation"></a> | 75 <a name="detailed_explanation"></a> |
| 76 ### Detailed explanation of steps | 76 ### Detailed explanation of steps |
| 77 | 77 |
| 78 1. User submits a Lua script task, a Performance task, or an Admin task (rebuild
chrome, recreate pagesets, recreate webpage archives, capture SKPs) using the G
CE web application [here](http://ct.skia.org). | 78 1. User submits a Lua script task, a Performance task, or an Admin task (rebuild
chrome, recreate pagesets, recreate webpage archives, capture SKPs) using the G
CE web application [here](http://ct.skia.org). |
| 79 | 79 |
| 80 2. Each task is exposed by the web application in JSON. The CT master polls the
web application and picks up new tasks. | 80 2. Each task is exposed by the web application in JSON. The CT master polls the
web application and picks up new tasks. |
| 81 | 81 |
| 82 3. The master pushes new tasks to all the workers using the master scripts [here
](https://skia.googlesource.com/buildbot/+/master/ct/go/master_scripts/). The ma
ster scripts then check to see when the workers are done with the requested task
. | 82 3. The master pushes new tasks to all the workers using the master scripts [here
](https://skia.googlesource.com/buildbot/+/master/ct/go/master_scripts/). The ma
ster scripts then check to see when the workers are done with the requested task
. |
| 83 | 83 |
| 84 4. The workers execute the task using the worker scripts [here](https://skia.goo
glesource.com/buildbot/+/master/ct/go/worker_scripts/). All generated artifacts
(CSV files, logs, SKP files, archives, etc) are then stored locally and copied t
o Google Storage. | 84 4. The workers execute the task using the worker scripts [here](https://skia.goo
glesource.com/buildbot/+/master/ct/go/worker_scripts/). All generated artifacts
(CSV files, logs, SKP files, archives, etc) are then stored locally and copied t
o Google Storage. Worker logs are available [here](https://uberchromegw.corp.goo
gle.com/i/skia-ct-master/all_logs). |
| 85 | 85 |
| 86 5. The master scripts periodically check the workers to see when they are done w
ith the requested task. Once the workers are done the generated artifacts are th
en read from Google Storage and consolidated (if required). | 86 5. The master scripts periodically check the workers to see when they are done w
ith the requested task. Once the workers are done the generated artifacts are th
en read from Google Storage and consolidated (if required). |
| 87 | 87 |
| 88 6. The master scripts then email results of the task to the user who requested i
t. The master scripts also update the status of the task to completed on App Eng
ine. | 88 6. The master scripts then email results of the task to the user who requested i
t. The master scripts also update the status of the task to completed on App Eng
ine. |
| 89 | 89 |
| 90 | 90 |
| 91 <a name="code"></a> | 91 <a name="code"></a> |
| 92 Code | 92 Code |
| 93 ---- | 93 ---- |
| 94 | 94 |
| 95 Cluster Telemetry is primarily written in Go with a few python scripts. The fram
ework lives in [master/ct](https://skia.googlesource.com/buildbot/+/master/ct). | 95 Cluster Telemetry is primarily written in Go with a few python scripts. The fram
ework lives in [master/ct](https://skia.googlesource.com/buildbot/+/master/ct). |
| 96 | 96 |
| 97 <a name="contact_us"></a> | 97 <a name="contact_us"></a> |
| 98 Contact Us | 98 Contact Us |
| 99 ---------- | 99 ---------- |
| 100 | 100 |
| 101 If you have questions, please email <cluster-telemetry@chromium.org> or contact
rmistry@ directly. | 101 If you have questions, please email <cluster-telemetry@chromium.org> or contact
rmistry@ directly. |
| OLD | NEW |