Google Git
Sign in
cos / cos / policymanager / refs/heads/release-R101
commit25eb11e9dac3bab34657bcf7fadf2f4ddf9e1c2b[log] [tgz]
authorKe Wu <mikewu@google.com>Fri Jul 22 17:06:33 2022 -0700
committerKe Wu <mikewu@google.com>Mon Jul 25 10:53:12 2022 -0700
treecd6e17028378736a1f7d02ace8fad0bc3bfb73d3
parent7a99a03ca9d2172297f9ed2293322fa433f26ed3 [diff]
Set loggingService to logging-agent.target

It allows policymanager to manage stackdriver logging agents together.

BUG=b/192104059
TEST=stackdriver e2e test; presubmit
RELEASE_NOTE=None

Change-Id: I583547ff4cf996e957a3dba5f958f1ad45d92acc
1 file changed
tree: cd6e17028378736a1f7d02ace8fad0bc3bfb73d3
  1. cmd/
  2. pkg/
  3. protos/
  4. third_party/
  5. .gitignore
  6. CONTRIBUTING.md
  7. gen_proto.sh
  8. go.mod
  9. go.sum
  10. LICENSE
  11. main.go
  12. OWNERS
  13. PRESUBMIT.cfg
  14. README.md
README.md

Policy Manager for COS(Container-Optimized OS) Image

Overview

Policy Manager is the client for the COS control plane. It is responsible for reporting current instance status and fetching device update config.

It is designed to be a system daemon that's started immediately after boot. It sends status update to an update manager, which will respond with the appropriate update config.

Using the update config, it will generate the appropriate update policy blobs to enforce the update strategy set by the user.

How to run

  • Policy Manager must be run with root privileges in order to access update_engine status and control device policy.
  • It continuously reports status and fetches update policy from metadata server under monitor mode.

What's up with update [policy, strategy, config]?

Part of Policy Manager's features is to allow users to control the OS update behavior of their COS instances.

Instances will only receive updates within their major release version. For example, if both 12.1.0 and 13.0.0 are available, an instance running 12.0.0 will only get updated to 12.1.0 if it has this strategy.

The actual enforcement of the strategies are done by the update policy, which is a Chrome OS feature. An update policy is a protobuf blob that contains the parameters that will be used to fetch updates from Omaha. Policy Manager is responsible for deciding when to enable or disable the update engine.

Building

  • To build and test Policy Manager, please run FEATURES=test emerge-lakitu policymanager

Protobufs

  • To compile protobuf definitions, run ./gen_proto.sh.
  • Do NOT submit the generated protobufs into the repo.