[rfe] validation to check for overcloud node clock sync relative to Undercloud

[Dan Trainor]

Overcloud deployments are comprised of a carefully orchestrated collection of individual steps preformed on a number of different nodes. These steps are both synchronous and asynchronous, and many of them rely on an accurate clock relative to each other and the Undercloud node.

A validation should exist that warns if an Overcloud node clock skew is outside of a given delta, e.g. skewed 3 minutes from the Undercloud. This date should be relative to the Undercloud's clock.

A local system clock time relative to when an overcloud node was introspected does not appear to be part of any node's ironic data, but this should be easy enough to stuff in to the node report.

With a clock that is skewed (greater than a few minutes), the timeouts are often not respected, either leaving a process running too long, or not long enough, relative to what the timeout parameter is. An example of this would be a Galera database sync.

[Marios Andreou (marios-b)]

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo