[lago-devel] time keeping

David Caro dcaro at redhat.com
Mon Mar 14 10:01:28 UTC 2016


On 03/14 11:46, Yaniv Kaul wrote:
> I'm concerned with two (different) time keeping issues:
> 1. Timezone - we need to ensure all VMs have the same timezone (At least by
> default).
> Best option would be to edit the deploy scripts and set the timezone to the
> host timezone?
> should be fairly easy to add @TIMEZONE@ variable to the deploy script in a
> similar manner to what we do today in the domain XML.
> It'll be in a command like 'ln -s /usr/share/zoneinfo/@TIMEZONE@
> /etc/localtime

For this there's already an issue:

   https://github.com/lago-project/lago/issues/2

> 
> 2. Time drifting - I have a feeling there's a time drift when we do all the
> freeze-thaw and snap/revert... Perhaps we should run 'ntpdate' after such
> actions?


  Yes, that might be happening, not sure though if we should get bound to
  ntpdate in specific or we should try to do something more generic (have to
  investigate if there's anything generic :/)


> _______________________________________________
> lago-devel mailing list
> lago-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/lago-devel


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro at redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/lago-devel/attachments/20160314/497c9380/attachment-0001.sig>


More information about the lago-devel mailing list