When we switched to free, the task timing isn't accurate because it
records time between two tasks. With free, the tasks may be on different
hosts and not even the same task so the timing was the time between some
tasks. This rewrite adjusts where we start and stop the task timing and
includes a hostname in the calculation. The inclusion of the hostname
allows us to pinpoint if tasks take longer on specific hosts as task ids
are generally (but not always) the same between hosts.
Change-Id: If0194091eb03186203e7724d506fdd36fd82baeb
The profile_tasks callback has been moved out of the base ansible code
base as part of 2.10. We already override most of the logic so let's
drop this inclusion to make tripleo_profile_tasks compatible with
ansible >2.9.
Change-Id: Iae3cb2b763eac435a2b8546182d1c65e917516e6
If a trace occurs, a final line break is visually useful to know when
the task profiling ends. The trace will be show *after* the callback so
we reduce confusion where the problem is.
Change-Id: Ibe21bdf046f71ce45f0fd36068635c4d954da5f2
It's useful to know when a command last ran as well as being able to
cross coordinate when something was running between the ansible output
and other logs. We can use the output timestamp do this.
Change-Id: I3f55f0a7f966f025a9938576ccf735f50f4c8589
If we switch to tripleo_dense, the upstream profile_tasks breaks the
formatting. So we can extend the profile_tasks and override the
functions that print out the other formatting.
Change-Id: I19f2aace53b0806496477966680925bf298b677f
Alex Schultz