OLD | NEW |
1 # Clovis in the Cloud: Developer Guide | 1 # Clovis in the Cloud: Developer Guide |
2 | 2 |
3 This document describes how to collect Chromium traces using Google Compute | 3 This document describes how to collect Chromium traces using Google Compute |
4 Engine. | 4 Engine. |
5 | 5 |
6 [TOC] | 6 [TOC] |
7 | 7 |
8 ## Initial setup | 8 ## Initial setup |
9 | 9 |
10 Install the [gcloud command line tool][1]. | 10 Install the [gcloud command line tool][1]. |
(...skipping 77 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
88 ``` | 88 ``` |
89 | 89 |
90 The first time, you may need to get more access tokens: | 90 The first time, you may need to get more access tokens: |
91 | 91 |
92 ```shell | 92 ```shell |
93 gcloud beta auth application-default login --scopes \ | 93 gcloud beta auth application-default login --scopes \ |
94 https://www.googleapis.com/auth/cloud-taskqueue \ | 94 https://www.googleapis.com/auth/cloud-taskqueue \ |
95 https://www.googleapis.com/auth/cloud-platform | 95 https://www.googleapis.com/auth/cloud-platform |
96 ``` | 96 ``` |
97 | 97 |
98 Create a JSON file describing the deployment configuration: | 98 Create a JSON dictionary file describing the deployment configuration, with the |
| 99 keys: |
99 | 100 |
| 101 - `project_name` (string): Name of the Google Cloud project |
| 102 - `cloud_storage_path` (string): Path in Google Storage where generated traces |
| 103 will be stored. |
| 104 - `chrome_path` (string): Path to the Chrome executable. |
| 105 - `src_path` (string): Path to the Chromium source directory. |
| 106 - `taskqueue_tag` (string): |
| 107 - `trace_database_filename` (string, optional): Filename for the trace |
| 108 database in Cloud Storage. Must be unique per worker to avoid concurrent |
| 109 access. Defaults to `trace_database.json`. |
| 110 |
| 111 Example: |
100 ```shell | 112 ```shell |
101 # CONFIG_FILE is the output json file. | |
102 # PROJECT_NAME is the Google Cloud project. | |
103 # CLOUD_STORAGE_PATH is the path in Google Storage where generated traces will | |
104 # be stored. | |
105 # CHROME_PATH is the path to the Chrome executable on the host. | |
106 # CHROMIUM_SRC is the Chromium src directory. | |
107 cat >$CONFIG_FILE << EOF | 113 cat >$CONFIG_FILE << EOF |
108 { | 114 { |
109 "project_name" : "$PROJECT_NAME", | 115 "project_name" : "$PROJECT_NAME", |
110 "cloud_storage_path" : "$CLOUD_STORAGE_PATH", | 116 "cloud_storage_path" : "$CLOUD_STORAGE_PATH", |
111 "chrome_path" : "$CHROME_PATH", | 117 "chrome_path" : "$CHROME_PATH", |
112 "src_path" : "$CHROMIUM_SRC", | 118 "src_path" : "$CHROMIUM_SRC", |
113 "taskqueue_tag" : "some_tag" | 119 "taskqueue_tag" : "some_tag" |
114 } | 120 } |
115 EOF | 121 EOF |
116 ``` | 122 ``` |
117 | 123 |
118 Launch the app, passing the path to the deployment configuration file: | 124 Launch the app, passing the path to the deployment configuration file: |
119 | 125 |
120 ```shell | 126 ```shell |
121 python $CHROMIUM_SRC/tools/android/loading/cloud/backend/worker.py \ | 127 python $CHROMIUM_SRC/tools/android/loading/cloud/backend/worker.py \ |
122 --config $CONFIG_FILE | 128 --config $CONFIG_FILE |
123 ``` | 129 ``` |
124 | 130 |
125 You can now [use the app][2]. | 131 You can now [use the app][2]. |
126 | 132 |
127 Tear down the local environment: | 133 Tear down the local environment: |
128 | 134 |
129 ```shell | 135 ```shell |
130 deactivate | 136 deactivate |
131 ``` | 137 ``` |
132 | 138 |
133 [1]: https://cloud.google.com/sdk | 139 [1]: https://cloud.google.com/sdk |
134 [2]: #Use-the-app | 140 [2]: #Use-the-app |
135 [3]: ../frontend/README.md | 141 [3]: ../frontend/README.md |
OLD | NEW |