Ensemble branch option needs to allow for distro pkg, ppa, and source branch install
Bug #828147 reported by
Kapil Thangavelu
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloudfoundry |
New
|
Undecided
|
Unassigned | ||
pyjuju |
Fix Released
|
Critical
|
Jim Baker | ||
juju (Ubuntu) |
Fix Released
|
Critical
|
Clint Byrum |
Bug Description
Ensemble currently defines an ensemble-branch environment option which allows specification of where to get ensemble code for machine deployments (limited to bzr published branches). At the moment we default to ppa package installation if this option is not specified.
Its critical for the oneiric rellease that we have a mechanism that defaults to using the distro package, but allows specifying the ppa, or a branch. This should also rename the 'ensemble-branch' option to 'ensemble-origin'.
Related branches
lp://staging/~jimbaker/pyjuju/env-origin
- Gustavo Niemeyer: Approve
- William Reade (community): Approve
-
Diff: 608 lines (+337/-27)19 files modifieddocs/source/provider-configuration-ec2.rst (+9/-3)
juju/providers/common/cloudinit.py (+78/-2)
juju/providers/common/launch.py (+9/-2)
juju/providers/common/tests/data/cloud_init_bootstrap (+0/-2)
juju/providers/common/tests/data/cloud_init_bootstrap_zookeepers (+0/-2)
juju/providers/common/tests/data/cloud_init_branch_trunk (+17/-0)
juju/providers/common/tests/data/cloud_init_normal (+0/-2)
juju/providers/common/tests/data/cloud_init_ppa (+15/-0)
juju/providers/common/tests/test_cloudinit.py (+109/-3)
juju/providers/ec2/tests/common.py (+1/-0)
juju/providers/ec2/tests/data/bootstrap_cloud_init (+0/-2)
juju/providers/ec2/tests/data/launch_cloud_init (+0/-2)
juju/providers/ec2/tests/data/launch_cloud_init_branch (+20/-0)
juju/providers/ec2/tests/data/launch_cloud_init_ppa (+15/-0)
juju/providers/ec2/tests/test_bootstrap.py (+1/-0)
juju/providers/ec2/tests/test_launch.py (+60/-2)
juju/providers/orchestra/tests/common.py (+3/-1)
juju/providers/orchestra/tests/data/bootstrap_user_data (+0/-2)
juju/providers/orchestra/tests/data/launch_user_data (+0/-2)
Changed in ensemble: | |
milestone: | none → eureka |
importance: | Undecided → Critical |
Changed in ensemble: | |
assignee: | nobody → Jim Baker (jimbaker) |
Changed in ensemble: | |
status: | New → In Progress |
Changed in juju (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → ubuntu-11.10 |
Changed in juju: | |
status: | In Progress → Fix Released |
Changed in juju (Ubuntu): | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Excerpts from Kapil Thangavelu's message of Wed Aug 17 16:17:46 UTC 2011:
> Public bug reported:
>
> Ensemble currently defines an ensemble-branch environment option which
> allows specification of where to get ensemble code for machine
> deployments (limited to bzr published branches). At the moment we
> default to ppa package installation if this option is not specified.
>
> Its critical for the oneiric rellease that we have a mechanism that
> defaults to using the distro package, but allows specifying the ppa, or
> a branch. This should also rename the 'ensemble-branch' option to
> 'ensemble-origin'.
Can solve this and allow for private hosting by making ensemble-origin
flexible as either a branch (lp:xxx), a ppa:xxx, or an apt sources line:
ensemble-origin: "deb http:// mymirror. internal/ ubuntu oneiric main"
ensemble-version: 0.5+306-0ubuntu1
ensemble-origin: lp:ensemble
ensemble-version: 306
ensemble-origin: ppa:ensemble/ppa
Unspecified version should always mean the "latest available".
On a "higher order" note, I wonder if, for repeatability, we shouldn't
process all of this on the client side, and just build a deb or tarball
that is pushed into file storage.