Merge lp:~jameinel/juju-core/api-connect-upgrade-1199915 into lp:~go-bot/juju-core/trunk
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | John A Meinel | ||||
Approved revision: | no longer in the source branch. | ||||
Merged at revision: | 1435 | ||||
Proposed branch: | lp:~jameinel/juju-core/api-connect-upgrade-1199915 | ||||
Merge into: | lp:~go-bot/juju-core/trunk | ||||
Diff against target: |
191 lines (+166/-0) 4 files modified
cmd/jujud/machine.go (+4/-0) cmd/jujud/upgradevalidation.go (+73/-0) utils/apt.go (+45/-0) utils/apt_test.go (+44/-0) |
||||
To merge this branch: | bzr merge lp:~jameinel/juju-core/api-connect-upgrade-1199915 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email:
|
Commit message
cmd/jujud/
Related to bug #1199913. On startup we will 'apt-get install lxc' if we
need to. This uses the containers/lxc code to detect if we have lxc
available, and if it fails then we request to install it.
I've tested this live, and it does solve the immediate problem.
Also, the test suite still passes because all the things that call
MachineAgent.Run are already using the lxc.TestSuite and so the
containers code "provides" lxc via the MockFactory.
One test we could do is that we try to install lxc if we run
the machine agent (and inject a MockFactory that fails the List
request). But I felt live testing was appropriate for this.
Description of the change
cmd/jujud/
Related to bug #1199913. On startup we will 'apt-get install lxc' if we
need to. This uses the containers/lxc code to detect if we have lxc
available, and if it fails then we request to install it.
I've tested this live, and it does solve the immediate problem.
Also, the test suite still passes because all the things that call
MachineAgent.Run are already using the lxc.TestSuite and so the
containers code "provides" lxc via the MockFactory.
One test we could do is that we try to install lxc if we run
the machine agent (and inject a MockFactory that fails the List
request). But I felt live testing was appropriate for this.
Reviewers: mp+174207_ code.launchpad. net,
Message:
Please take a look.
Description: machineagent: install LXC on start
cmd/jujud/
Related to bug #1199913. On startup we will 'apt-get install lxc' if we
need to. This uses the containers/lxc code to detect if we have lxc
available, and if it fails then we request to install it.
I've tested this live, and it does solve the immediate problem.
Also, the test suite still passes because all the things that call
MachineAgent.Run are already using the lxc.TestSuite and so the
containers code "provides" lxc via the MockFactory.
One test we could do is that we try to install lxc if we run
the machine agent (and inject a MockFactory that fails the List
request). But I felt live testing was appropriate for this.
https:/ /code.launchpad .net/~jameinel/ juju-core/ api-connect- upgrade- 1199915/ +merge/ 174207
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/10986044/
Affected files: machine. go upgradevalidati on.go
A [revision details]
M cmd/jujud/
A cmd/jujud/
A utils/apt.go
A utils/apt_test.go