|author||Rayan Dasoriya <email@example.com>||Thu Mar 03 22:15:16 2022 +0000|
|committer||Rayan Dasoriya <firstname.lastname@example.org>||Tue Mar 08 17:13:12 2022 +0000|
Added get_status api in policy manager BUG=b/222726350 TEST=presubmit RELEASE_NOTE=Added get_status api in device_policy_manager Change-Id: I5b4b3f4e27adce4b663bbe0fa74b6a07351a1a01
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.
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.
FEATURES=test emerge-lakitu policymanager