Upstart control of lxc container instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Medium
|
Serge Hallyn | ||
Quantal |
Won't Fix
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Serge Hallyn |
Bug Description
This change proposes that upstart takes care of running and managing lxc container instances instead of having them run as daemons.
This has some advantages:
- lxc containers can benefit from upstart supervision, eg. respawn can be easily enabled, and parallel job execution
At the moment with serial execution, stopping the lxc service can (worst case)
take up to n times $LXC_SHUTDOWN_
Having upstart manage instance shutdown avoids this problem.
- Administrators can write upstart jobs that run on lxc container startup/shutdown of a specific container.
Consider for example a job that enables transparent port 80 routing once a container names "squid" comes up.
I have not found any possibility to assign the instance kill timeout dynamically so for now it's fixed at two minutes.
Related branches
- Serge Hallyn: Approve
- Ubuntu branches: Pending requested
-
Diff: 98 lines (+32/-17) (has conflicts)4 files modifieddebian/changelog (+6/-0)
debian/lxc.lxc-instance.upstart (+23/-0)
debian/lxc.upstart (+2/-17)
debian/rules (+1/-0)
summary: |
- Upstart control of lxc container instances + [FFE] Upstart control of lxc container instances |
Status changed to 'Confirmed' because the bug affects multiple users.