Merge lp:~dimitern/juju-core/290-lp-1240667-cloud-tools-priority into lp:~go-bot/juju-core/trunk
Status: | Merged |
---|---|
Approved by: | Dimiter Naydenov |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2312 |
Proposed branch: | lp:~dimitern/juju-core/290-lp-1240667-cloud-tools-priority |
Merge into: | lp:~go-bot/juju-core/trunk |
Diff against target: |
344 lines (+149/-22) 7 files modified
cloudinit/cloudinit.go (+37/-3) cloudinit/cloudinit_test.go (+41/-2) cloudinit/options.go (+19/-2) cloudinit/sshinit/configure.go (+12/-1) cloudinit/sshinit/configure_test.go (+12/-2) environs/cloudinit/cloudinit.go (+21/-9) environs/cloudinit/cloudinit_test.go (+7/-3) |
To merge this branch: | bzr merge lp:~dimitern/juju-core/290-lp-1240667-cloud-tools-priority |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+205816@code.launchpad.net |
Commit message
Fixed bug #1240667: pin priority for cloud-tools
This introduces several new calls in cloudinit,
which deal with apt sources, their preferences
(/etc/apt/
install from there.
Basically, when deploying a precise machine that
needs to install mongodb-server package, we add
the cloud-tools pocket, but by default this will
add it as an apt source with a higher priority
than the main archive. As a consequence, charms
that try to install packages from main, which
are also in the cloud-tools pocket get the latter,
rather than the former (i.e. the described problem
with python-django's version 1.5 in cloud-tools vs.
1.14 in main, which breaks openstack-dashboard charm).
Now, when adding the cloud-tools archive we also
change its apt preferences, so that its priority
as an apt source is lower than main, which means
when installing mongodb-server during cloudinit
we need to explicitly specity --target-release
'precise-
from cloud-tools.
Live tested on EC2 and works as expected.
https:/
R=gz, rogpeppe
Description of the change
Fixed bug #1240667: pin priority for cloud-tools
This introduces several new calls in cloudinit,
which deal with apt sources, their preferences
(/etc/apt/
install from there.
Basically, when deploying a precise machine that
needs to install mongodb-server package, we add
the cloud-tools pocket, but by default this will
add it as an apt source with a higher priority
than the main archive. As a consequence, charms
that try to install packages from main, which
are also in the cloud-tools pocket get the latter,
rather than the former (i.e. the described problem
with python-django's version 1.5 in cloud-tools vs.
1.14 in main, which breaks openstack-dashboard charm).
Now, when adding the cloud-tools archive we also
change its apt preferences, so that its priority
as an apt source is lower than main, which means
when installing mongodb-server during cloudinit
we need to explicitly specity --target-release
'precise-
from cloud-tools.
Live tested on EC2 and works as expected.
Reviewers: mp+205816_ code.launchpad. net,
Message:
Please take a look.
Description:
Fixed bug #1240667: pin priority for cloud-tools
This introduces several new calls in cloudinit, preferences. d/) and packages that we
which deal with apt sources, their preferences
(/etc/apt/
install from there.
Basically, when deploying a precise machine that
needs to install mongodb-server package, we add
the cloud-tools pocket, but by default this will
add it as an apt source with a higher priority
than the main archive. As a consequence, charms
that try to install packages from main, which
are also in the cloud-tools pocket get the latter,
rather than the former (i.e. the described problem
with python-django's version 1.5 in cloud-tools vs.
1.14 in main, which breaks openstack-dashboard charm).
Now, when adding the cloud-tools archive we also updates/ cloud-tools' to pick the version
change its apt preferences, so that its priority
as an apt source is lower than main, which means
when installing mongodb-server during cloudinit
we need to explicitly specity --target-release
'precise-
from cloud-tools.
Live tested on EC2 and works as expected.
https:/ /code.launchpad .net/~dimitern/ juju-core/ 290-lp- 1240667- cloud-tools- priority/ +merge/ 205816
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/61410051/
Affected files (+151, -22 lines): cloudinit. go cloudinit_ test.go options. go sshinit/ configure. go sshinit/ configure_ test.go cloudinit/ cloudinit. go cloudinit/ cloudinit_ test.go
A [revision details]
M cloudinit/
M cloudinit/
M cloudinit/
M cloudinit/
M cloudinit/
M environs/
M environs/