Comment 20 for bug 1295732

Ghe - ok so

[2014-03-26 16:07:15] undercloud : 673 s
[2014-03-26 16:07:15] overcloud : 900 s
vs

[2014-03-27 08:03:22] undercloud : 251 s
[2014-03-27 08:03:22] overcloud : 586 s

both virto-io, both cached.

Since the undercloud is faster to bring up, how about we focus there and see where the time is going. Lets get instrumentation to identify:
 - time to load the image into glance
 - time till the VM is booted (e.g. pingable vs scripts completed)
 - time till in-instance scripts have completed (heat signals CREATE_COMPLETE)
 - time to fully configure via APIs

and surface that at the end of the devtest_undercloud script or something. I can then run the same thing and we can divide and conquer.