Orchestra (Cobbler) Should generate cloud-init's meta-data for ensemble/JuJu

could elaborate a bit more on what this means? the description is unclear

Excerpts from Andres Rodriguez's message of Wed Sep 14 18:44:55 UTC 2011:
> Public bug reported:
>
> Currently, ensemble/JuJu provides the user-data and meta-data. However,
> the meta-data should be provided only by the provider rather than by
> ensemble/JuJu.

Currently juju drives cloud-init by providing a kickstart variable that is run in the installer via late_command.

Through that kickstart variable, juju writes /var/lib/cloud/seed/nocloud-net/{meta-data,user-data}.

Essentially, that means that the juju orchestra provider is providing both the user-data for cloud-init *and* the meta-data.

This is less than ideal, and different from other providers where the provider would provide cloud-init with meta-data and ensemble only provide user-data.

The solution that Andreas and I have decided fits well is to make Cobbler able to write meta-data for cloud-init (via the seed and late-command) and require JuJu only to provide the user-data, and in the form of a kickstart variable.

This will model much better other clouds, and reduce some of the JuJu' knowledge of cloud-init.

This bug was fixed in the package orchestra - 2.13-0ubuntu1

---------------
orchestra (2.13-0ubuntu1) oneiric; urgency=low

  * Handle generation of cloud-init's meta-data and late_command for
    user-data and meta-data from the orchestra side. So that this is not
    done from the juju/ensemble. (LP: #850260)
  * Change any reference for 'ensemble' to 'juju' (LP: #851967).
  * Move etc/orchestra/ubuntu-orchestra-client.seed to examples.
 -- Andres Rodriguez <email address hidden> Fri, 16 Sep 2011 11:07:24 -0400