diff options
| author | jaysri@chromium.org <jaysri@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-02 21:45:35 +0000 |
|---|---|---|
| committer | jaysri@chromium.org <jaysri@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-05-02 21:45:35 +0000 |
| commit | 8cb8e1e07a0aa1cacc4be4f98af436d4c88291ac (patch) | |
| tree | 7f3617e53dcf0ed3d2a62a42173696d8e57dc931 | |
| parent | ec6ad4e70a21029627db0eb87aa30bd0802cf39d (diff) | |
| download | chromium_src-8cb8e1e07a0aa1cacc4be4f98af436d4c88291ac.zip chromium_src-8cb8e1e07a0aa1cacc4be4f98af436d4c88291ac.tar.gz chromium_src-8cb8e1e07a0aa1cacc4be4f98af436d4c88291ac.tar.bz2 | |
Add enterprise policy support to scatter downloading of ChromeOS updates
Enterprise admins need some form of control to reduce the spikes in bandwidth consumption when a new Chrome Device update is made available. This CL introduces a new policy to randomly distribute those downloads over a configured amount of time to reduce the spikes.
BUG=chromeos-29615: Implement scattering of downloads in UpdateEngine
TEST=update_engine works fine with new policy code.
Review URL: http://codereview.chromium.org/10281005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@134996 0039d316-1c4b-4281-b951-d872f2087c98
| -rw-r--r-- | chrome/browser/policy/proto/chrome_device_policy.proto | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/chrome/browser/policy/proto/chrome_device_policy.proto b/chrome/browser/policy/proto/chrome_device_policy.proto index 697fbde..b899812 100644 --- a/chrome/browser/policy/proto/chrome_device_policy.proto +++ b/chrome/browser/policy/proto/chrome_device_policy.proto @@ -158,6 +158,22 @@ message AutoUpdateSettingsProto { // 1412.24.34: update to this specific version only // --------------------------------------------------------------------- optional string target_version_prefix = 2; + + // The Chrome browser version (e.g. "17.*") corresponding to the + // target_version_prefix above. The target_version_prefix is the internal OS + // version that external users normally are not aware of. This display_name + // can be used by the devices to display a message to end-users about the auto + // update setting. + optional string target_version_display_name = 3; + + // Specifies the number of seconds up to which a device may randomly + // delay its download of an update from the time the update was first pushed + // out to the server. The device may wait a portion of this time in terms + // of wall-clock-time and the remaining portion in terms of the number of + // update checks. In any case, the scatter is upper bounded to a constant + // amount of time so that a device does not ever get stuck waiting to download + // an update forever. + optional int64 scatter_factor_in_seconds = 4; } message StartUpUrlsProto { |