Merge lp:~thumper/juju-core/autostart-containers-after-creation into lp:~go-bot/juju-core/trunk
Status: | Merged |
---|---|
Approved by: | Tim Penhey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2405 |
Proposed branch: | lp:~thumper/juju-core/autostart-containers-after-creation |
Merge into: | lp:~go-bot/juju-core/trunk |
Prerequisite: | lp:~thumper/juju-core/fast-lxc |
Diff against target: |
245 lines (+87/-45) 5 files modified
container/lxc/export_test.go (+4/-3) container/lxc/lxc.go (+57/-30) container/lxc/lxc_test.go (+8/-6) container/lxc/mock/mock-lxc.go (+17/-5) container/lxc/testing/test.go (+1/-1) |
To merge this branch: | bzr merge lp:~thumper/juju-core/autostart-containers-after-creation |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Juju Engineering | Pending | ||
Review via email: mp+210099@code.launchpad.net |
Commit message
Set lxc autostart after creation.
Currently for a recent LXC version, the autostart is controlled
by a setting in the lxc config. We were setting this in the
config file that we use for creation. However this is not clone
friendly, as we do not specify a config file for clone.
However it is perfectly valid to modify the config for the container
once it has been created. This then becomes common for both
normally created containers and those that have been cloned.
A key here is that our template container that we want to use
as a base to clone off we do not want auto-starting, however
the containers that we clone off that may well want to auto-start
(in fact all will until we add the autostart policy for local).
Description of the change
Set lxc autostart after creation.
Currently for a recent LXC version, the autostart is controlled
by a setting in the lxc config. We were setting this in the
config file that we use for creation. However this is not clone
friendly, as we do not specify a config file for clone.
However it is perfectly valid to modify the config for the container
once it has been created. This then becomes common for both
normally created containers and those that have been cloned.
A key here is that our template container that we want to use
as a base to clone off we do not want auto-starting, however
the containers that we clone off that may well want to auto-start
(in fact all will until we add the autostart policy for local).
Reviewers: mp+210099_ code.launchpad. net,
Message:
Please take a look.
Description:
Set lxc autostart after creation.
Currently for a recent LXC version, the autostart is controlled
by a setting in the lxc config. We were setting this in the
config file that we use for creation. However this is not clone
friendly, as we do not specify a config file for clone.
However it is perfectly valid to modify the config for the container
once it has been created. This then becomes common for both
normally created containers and those that have been cloned.
A key here is that our template container that we want to use
as a base to clone off we do not want auto-starting, however
the containers that we clone off that may well want to auto-start
(in fact all will until we add the autostart policy for local).
https:/ /code.launchpad .net/~thumper/ juju-core/ autostart- containers- after-creation/ +merge/ 210099
Requires: /code.launchpad .net/~thumper/ juju-core/ fast-lxc/ +merge/ 209801
https:/
(do not edit description out of merge proposal)
Please review this at https:/ /codereview. appspot. com/73300043/
Affected files (+71, -35 lines): lxc/export_ test.go lxc/lxc. go lxc/lxc_ test.go lxc/mock/ mock-lxc. go lxc/testing/ test.go
A [revision details]
M container/
M container/
M container/
M container/
M container/