orchestra team mailing list archive

[Scott Moser <smoser@xxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of
orchestra, which is the registrant for Orchestra.
https://bugs.launchpad.net/bugs/850260

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

Status in juju:
  Confirmed
Status in Ubuntu Orchestra:
  Confirmed
Status in “orchestra” package in Ubuntu:
  Confirmed

Bug description:
  Currently, ensemble/JuJu Orchestra Provider, provides both the user-
  data and meta-data. This means that both, the meta-data and user-data
  are generated on the ensemble/JuJu side of things. However, on ec2,
  ensemble/JuJu only generates the user-data and not the meta-data as
  this is obtained from the provider.

  For this reason, we should made cobbler/orchestra directly provide the
  meta-data to the deployed systems, rather than having ensemble/juju
  provide it to cobbler and then to the systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/850260/+subscriptions