How fast can device policy be "pushed" to a Chrome OS device?

[kr...@flintos.io]

Hi,

Could anyone shed some light on the question mentioned in the subject? During my testing it seems when a policy was changed in the admin console it was "pushed" to the Chromebook device instead of having to wait for hours until the fetch interval ran out. But what confused me is sometimes it took less than a minute while sometimes more than 10 mins. If the policies were pushed to devices I would expect the delay to be only a few seconds, like what push notification works on Android phones.

[Bartosz Fabianowski]

The push notification is pretty much instantaneous, but there is server-side processing of policy changes that needs to happen first.

In addition to these push notifications, the device will also fetch policies "just in case it missed an update" on certain events, e.g. login or once every 24 hours.

- Bartosz

On 08/02/18 09:49, kr...@flintos.io wrote:

Hi,

Could anyone shed some light on the question mentioned in the subject? During my testing it seems when a policy was changed in the admin console it was "pushed" to the Chromebook device instead of having to wait for hours until the fetch interval ran out. But what confused me is sometimes it took less than a minute while sometimes more than 10 mins. If the policies were pushed to devices I would expect the delay to be only a few seconds, like what push notification works on Android phones.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ee264e4-362f-4ae9-aa9d-ae4df6ab5569%40chromium.org.

[Kai Liu]

Hi Bartosz,

Thanks for your reply! Could you also share some technical detail on how pushing is implemented, such as the protocol used (HTTP or websocket or some thing else), does it make use of some Google's messaging infrastructure like FCM or just Chrome's own implementation? Or could you point me to the code in Chromium source that handles these?

On Thu, Feb 8, 2018 at 6:00 PM, Bartosz Fabianowski <bar...@chromium.org> wrote:

The push notification is pretty much instantaneous, but there is server-side processing of policy changes that needs to happen first.

In addition to these push notifications, the device will also fetch policies "just in case it missed an update" on certain events, e.g. login or once every 24 hours.

- Bartosz

On 08/02/18 09:49, kr...@flintos.io wrote:

Hi,

Could anyone shed some light on the question mentioned in the subject? During my testing it seems when a policy was changed in the admin console it was "pushed" to the Chromebook device instead of having to wait for hours until the fetch interval ran out. But what confused me is sometimes it took less than a minute while sometimes more than 10 mins. If the policies were pushed to devices I would expect the delay to be only a few seconds, like what push notification works on Android phones.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ee264e4-362f-4ae9-aa9d-ae4df6ab5569%40chromium.org.

--

Best Regards.

Kai Liu

Mobile / Wechat / Telegram: +86 186 6591 9086

[Bartosz Fabianowski]

For historical reasons, these notifications are called "invalidations"
(you can think of them telling the device that the policy it has is
stale and no longer valid). We use standard Google infrastructure to
deliver these. Back when I worked on this in 2013, it was one system, I
believe it was since swapped out for another... the code will always
have the ground truth. Your entry point into all this would be here:

https://cs.chromium.org/chromium/src/chrome/browser/policy/cloud/cloud_policy_invalidator.h

- Bartosz

On 08/02/18 11:33, Kai Liu wrote:
> Hi Bartosz,
>
> Thanks for your reply! Could you also share some technical detail on how
> pushing is implemented, such as the protocol used (HTTP or websocket or
> some thing else), does it make use of some Google's messaging
> infrastructure like FCM or just Chrome's own implementation? Or could
> you point me to the code in Chromium source that handles these?
>
>
> On Thu, Feb 8, 2018 at 6:00 PM, Bartosz Fabianowski
> <bar...@chromium.org <mailto:bar...@chromium.org>> wrote:
>
> The push notification is pretty much instantaneous, but there is
> server-side processing of policy changes that needs to happen first.
>
> In addition to these push notifications, the device will also fetch
> policies "just in case it missed an update" on certain events, e.g.
> login or once every 24 hours.
>
> - Bartosz
>

> On 08/02/18 09:49, kr...@flintos.io <mailto:kr...@flintos.io> wrote:
>> Hi,
>>
>> Could anyone shed some light on the question mentioned in the
>> subject? During my testing it seems when a policy was changed in
>> the admin console it was "pushed" to the Chromebook device instead
>> of having to wait for hours until the fetch interval ran out. But
>> what confused me is sometimes it took less than a minute while
>> sometimes more than 10 mins. If the policies were pushed to
>> devices I would expect the delay to be only a few seconds, like
>> what push notification works on Android phones.
>> --
>> --
>> Chromium Developers mailing list: chromi...@chromium.org

>> <mailto:chromi...@chromium.org>

>> View archives, change email options, or unsubscribe:
>> http://groups.google.com/a/chromium.org/group/chromium-dev
>> <http://groups.google.com/a/chromium.org/group/chromium-dev>
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "Chromium-dev" group.
>> To unsubscribe from this group and stop receiving emails from it,

>> send an email to chromium-dev...@chromium.org
>> <mailto:chromium-dev...@chromium.org>.

>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ee264e4-362f-4ae9-aa9d-ae4df6ab5569%40chromium.org

>> <https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ee264e4-362f-4ae9-aa9d-ae4df6ab5569%40chromium.org?utm_medium=email&utm_source=footer>.

[Kai Liu]

Very much appreciated. I searched for "push" previously in the code but didn't notice anything really seems related to push notification :D.

    <mailto:chromium-dev@chromium.org>

    View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev
    <http://groups.google.com/a/chromium.org/group/chromium-dev>
    ---
    You received this message because you are subscribed to the Google
    Groups "Chromium-dev" group.
    To unsubscribe from this group and stop receiving emails from it,

    send an email to chromium-dev+unsubscribe@chromium.org
    <mailto:chromium-dev+unsubscrib...@chromium.org>.

    To view this discussion on the web visit
    https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ee264e4-362f-4ae9-aa9d-ae4df6ab5569%40chromium.org
    <https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/5ee264e4-362f-4ae9-aa9d-ae4df6ab5569%40chromium.org?utm_medium=email&utm_source=footer>.

--



Best Regards.


Kai Liu
Mobile / Wechat / Telegram: +86 186 6591 9086