Comment 11 for bug 596993

cloud-init does a lot of things. I guess what I'm looking for is whether cloud-init could be made to emit events as it works such that other upstart jobs can listen for those events and then use them to trigger their startup as opposed to waiting for the entire cloud-init process to complete.

eg:
cloud-init: initctl emit hostname

myjob: start on hostname