Comment 10 for bug 978127

I was suggesting the "api" call to maas. That makes sense to me, as the maas clock is actually the "right" clock (if maas server was out of date, syncing against anything else is just going to cause other confusion).

I dont' like putting the 'oauth_time_sync' in the config payload as that is stored locally in cloud-init as regular config. In the ephemeral image, every boot is "first boot" (as there is no way of storing a already-booted). Having a hard coded static time in a config file seems broken. I'd rather it point to a reference where a dynamic time can be obtained.

The api call in maas can be as simple as:
 print time.time()

If this is the right solution, then its the right path to SRU. Cobbling a solution that is different than what is done in trunk so it is more appropriate for SRU doesn't seem like a good idea. We should focus first on fixing trunk the right way.