Excerpts from Nick Coghlan's message of 2013-02-21 12:25:06 +1000:
> A nicer idea might be to have the harness "check in"
at the start of
> the
> recipe, report its name and version (and its configuration, and other
> useful info too?) -- Marian Csontos has suggested something similar in
> the past, and you can already get most of the way there by just having
> the harness upload a recipe log under a certain well-known name
> ("debug/harness-checkin.txt" or whatever).
A check-in API sounds good to me.
Perhaps it could be considered as a possible replacement for our current
install-done callback, that we hit from the kickstart file with wget or
curl?
It wouldn't be a replacement for the install_done checkin, because that
happens at a different time (at the end of the installation before
reboot, rather than after reboot when the harness starts up). And there
is a lot that can go wrong in that one reboot :-)
Also, the harness check-in is only relevant for recipes (as opposed to
manual provisioning where there is no harness).
I don't see it as crucial in the first draft, mainly because the harness
can still always do a poor man's check-in by uploading a log. So I will
add this to the "deferred features" section.
--
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Infrastructure Engineering and Development
Red Hat, Inc.