Enable custom scale-down of runner instances (#11688)

Currently, instances only delete themselves when they finish their job.
This doesn't help if the group has scaled up too much and then a bunch
of instances sit idle. This introduces a periodic check if the runner
is idle and the autoscaler thinks the group should scale down and stops
the runner if so.

There's a few refactors in here. Commits should mostly be reviewable
individually (I think some earlier commits may have some syntax errors,
so perhaps overlook those till the end). Of note, this adds cloud
logging for systemd services from these VMs, which is helpful when
debugging.

Tested:
Deployed to test environment, including a test instance-deleter
service. Deliberately over-scaled instance group and confirmed that it
scaled back down within ~30 minutes


![image](https://user-images.githubusercontent.com/5732088/210158149-b546c2df-02ae-4c5f-8d91-0d3a29d4e790.png)

Ran jobs against test environment and confirmed no issues:
https://github.com/iree-org/iree/actions/runs/3810920085/jobs/6488260971
and that group scaled up and then back down again:


![image](https://user-images.githubusercontent.com/5732088/210158162-87fc59f0-46de-4f73-b278-ba26244a8666.png)

Note that when the presubmit run had finished, the group was still at
seven instances, so it was this new functionality that caused the scale
down.
28 files changed
tree: ffb0091ec1c407ca775480bee8fd4be0452d2a35
  1. .github/
  2. benchmarks/
  3. build_tools/
  4. compiler/
  5. docs/
  6. experimental/
  7. integrations/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazelignore
  15. .bazelrc
  16. .bazelversion
  17. .clang-format
  18. .dockerignore
  19. .gitignore
  20. .gitmodules
  21. .pylintrc
  22. .style.yapf
  23. .yamllint.yml
  24. AUTHORS
  25. BUILD.bazel
  26. CITATION.cff
  27. CMakeLists.txt
  28. configure_bazel.py
  29. CONTRIBUTING.md
  30. LICENSE
  31. README.md
  32. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.

See our website for project details, user guides, and instructions on building from source.

CI Status

Project Status

IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.