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

Bug #850260 reported by Andres Rodriguez on 2011-09-14
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Orchestra
High
Andres Rodriguez
pyjuju
High
Andres Rodriguez
orchestra (Ubuntu)
Critical
Andres Rodriguez

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.

NOTE: Changes have been merged into juju. For this reason, this needs to be released in Ubuntu, otherwise we will have a broken interaction between Orchestra and JuJu.

Related branches

Changed in juju:
status: New → Confirmed
Changed in orchestra (Ubuntu):
status: New → Confirmed
Changed in orchestra:
status: New → Confirmed
assignee: nobody → Andres Rodriguez (andreserl)
Changed in juju:
assignee: nobody → Andres Rodriguez (andreserl)
Changed in orchestra (Ubuntu):
assignee: nobody → Andres Rodriguez (andreserl)

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.

description: updated
description: updated
Scott Moser (smoser) wrote :

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.

Changed in juju:
status: Confirmed → Triaged
status: Triaged → In Progress
Changed in orchestra:
status: Confirmed → In Progress
Changed in orchestra (Ubuntu):
importance: Undecided → High
Changed in juju:
importance: Undecided → High
Changed in orchestra:
importance: Undecided → High
William Reade (fwereade) on 2011-09-15
Changed in juju:
milestone: none → eureka
Changed in orchestra:
status: In Progress → Fix Committed
Changed in juju:
status: In Progress → Fix Committed
Changed in orchestra (Ubuntu):
importance: High → Critical
description: updated
Launchpad Janitor (janitor) wrote :

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

Changed in orchestra (Ubuntu):
status: Confirmed → Fix Released
Changed in juju:
status: Fix Committed → Fix Released
Changed in orchestra:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers