[GCE] Cache configured VM count in the datastore

Like the connected and created counts, the configured count needs to be
reported globally. Precompute it similarly. Also fix created count to
sum values across Swarming servers, since created count doesn't have a
field for the server.

Bug: 897355
Change-Id: I243e13f634e040f72d000e3ae864938b9043c1d3
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1558868
Commit-Queue: smut <smut@google.com>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
3 files changed
tree: ecb2c4e68172240e492a6b47d3d845ce535b6286
  1. appengine/
  2. auth/
  3. buildbucket/
  4. cipd/
  5. client/
  6. common/
  7. config/
  8. cq/
  9. dm/
  10. examples/
  11. gce/
  12. grpc/
  13. hardcoded/
  14. logdog/
  15. luci_notify/
  16. lucicfg/
  17. lucictx/
  18. machine-db/
  19. milo/
  20. mmutex/
  21. mp/
  22. scheduler/
  23. scripts/
  24. server/
  25. starlark/
  26. swarming/
  27. tokenserver/
  28. tools/
  29. tumble/
  30. vpython/
  31. web/
  32. .gitattributes
  33. .travis.yml
  34. AUTHORS
  35. codereview.settings
  36. CONTRIBUTING.md
  37. CONTRIBUTORS
  38. LICENSE
  39. OWNERS
  40. pre-commit-go.yml
  41. PRESUBMIT.py
  42. README.md
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

Contributing

Contributing uses the same flow as Chromium contributions.