Lines Matching +full:build +full:- +full:docker +full:- +full:cpu
3 … of Bigtrace services NOT Bigtrace users. This is also designed for non-Googlers - Googlers should…
11 
14 There are three clients to interact with Bigtrace: a Python API, clickhouse-client and Apache Super…
15 - The Python API exists in the Perfetto python library and can be used similar to the TraceProcesso…
16 - Clickhouse is a data warehousing solution which gives a SQL based interface for the user to write…
17 - Superset is a GUI for Clickhouse which offers an SQLLab to run queries offering support for moder…
37 - A GCP Project
38 - GCS
39 - GKE
40 - gcloud (https://cloud.google.com/sdk/gcloud)
41 - A clone of the Perfetto directory
45 - Storage Object User - to allow for the Worker to retrieve GCS authentication tokens
49 ---
57 3. In Cluster basics, select a location type - Use zonal for best load balancing performance
59 4. In Node pools > default-pool > Nodes, select a VM type - Preferably standard - e.g. e2-standard-…
71 gcloud container clusters get-credentials [CLUSTER_NAME] --zone [ZONE]--project [PROJECT_NAME]
75 ---
81 To build the image and push to Artifact Registry, first navigate to the perfetto directory and then…
84 docker build -t bigtrace_orchestrator src/bigtrace/orchestrator
86 docker tag bigtrace_orchestrator [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/bigtrace_orchestr…
88 docker push [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/bigtrace_orchestrator
92 To use the images from the registry which were built in the previous step, the orchestrator-deploym…
95 image: [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/bigtrace_orchestrator
98 The CPU resources should also be set depending on the vCPUs per pod as chosen before.
103 cpu: [VCPUS_PER_MACHINE]
105 cpu: [VCPUS_PER_MACHINE]
108 …o deploy the Orchestrator you apply both the orchestrator-deployment.yaml and the orchestrator-ilb…
111 kubectl apply -f orchestrator-deployment.yaml
112 kubectl apply -f orchestrator-ilb.yaml
118 Similar to the Orchestrator first build and push the images to Artifact Registry.
121 docker build -t bigtrace_worker src/bigtrace/worker
123 docker tag bigtrace_worker [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/bigtrace_worker
125 docker push [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/bigtrace_worker
131 image: [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/bigtrace_worker
140 cpu: [VCPUS_PER_MACHINE]
146 kubectl apply -f worker-deployment.yaml
147 kubectl apply -f worker-service.yaml
152 #### Build and upload the Clickhouse deployment image
156 docker build -t clickhouse src/bigtrace_clickhouse
158 docker tag clickhouse [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/clickhouse
160 docker push [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/clickhouse
166 kubectl apply -f src/bigtrace_clickhouse/config.yaml
168 kubectl apply -f src/bigtrace_clickhouse/pvc.yaml
170 kubectl apply -f src/bigtrace_clickhouse/pv.yaml
172 kubectl apply -f src/bigtrace_clickhouse/clickhouse-deployment.yaml
174 kubectl apply -f src/bigtrace_clickhouse/clickhouse-ilb.yaml
176 With the clickhouse-deployment.yaml you must replace the image variable with the URI to the image b…
182 - name: clickhouse
183 image: # [ZONE]-docker.pkg.dev/[PROJECT_NAME]/[REPO_NAME]/clickhouse
185 - name: BIGTRACE_ORCHESTRATOR_ADDRESS
204 …ser's requirements. (https://clickhouse.com/docs/en/operations/server-configuration-parameters/set…
206 ### Accessing Clickhouse through clickhouse-client (CLI)
211 ./clickhouse client --host [ADDRESS] --port [PORT] --receive-timeout=1000000 --send-timeout=100000…
215 There are two methods of deploying Superset - one for development and one for production.
223 Superset can then be connected to Clickhouse via clickhouse-connect by following the instructions a…