Monitoring proxy for time series data

appengine/chrome_infra_mon_proxy/vm2.yaml

Index: appengine/chrome_infra_mon_proxy/vm2.yaml
diff --git a/appengine/chrome_infra_mon_proxy/vm2.yaml b/appengine/chrome_infra_mon_proxy/vm2.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..12a0c01d2fdd9f14c494b82db34da965e9ee78e8
--- /dev/null
+++ b/appengine/chrome_infra_mon_proxy/vm2.yaml
@@ -0,0 +1,32 @@
+application: chrome-infra-mon-proxy

[agable, 2015/04/14 21:46:25]

Unfortunate that we have 3 files for the 3 vms. Prevents us from landing a
1-line change to scale up from 3 to 5, or something similar. Is there any way to
abstract across a single template yaml file? If not, no problem, but maybe worth
investigating.

[Sergey Berezin (google), 2015/04/16 04:39:08]

Note, that it's not 3 VMs, but 3 modules, one per NAT box. Each module can scale
the number of instances (VMs) independently.

Making the design generic in the number of NAT boxes gets ugly very fast, and
IMHO is not worth the trouble. Three NAT boxes can handle likely >1000 qps, so I
don't expect needing more. More NAT boxes also means more static IPs to
whitelist, so it's already a hassle.

+# version: 2 # Must specify version explicitly.
+runtime: python27
+vm: true
+module: vm2
+api_version: 1
+threadsafe: true
+
+automatic_scaling:
+  min_num_instances: 1
+  max_num_instances: 6
+  cool_down_period_sec: 60
+  cpu_utilization:
+    target_utilization: 0.6
+  max_concurrent_requests: 25
+
+resources:
+  cpu: 4
+  memory_gb: 2
+  disk_size_gb: 10
+
+network:
+  instance_tag: managed-gae-vm2
+
+handlers:
+- url: /.*
+  script: vm_module.app
+
+health_check:
+  enable_health_check: True
+  check_interval_sec: 10
+  restart_threshold: 20