We're currently considering a feature[1] request that would expose the
hypervisor's
host name to it's guest recipe via environment variables.
We currently expose many guest recipe details via the to_xml() (which is what produces
the output of the /recipes/<recipe_id> harness API call). To include the host's
FQDN
in this details would seem to be consistent with existing behaviour and would take
minimal code changes (as opposed to creating a new harness API call, controller, and model
methods).
1
https://bugzilla.redhat.com/show_bug.cgi?id=887760