Public bug reported:
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_TIMEOUT, n being the number of containers
running.
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.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Branch linked: lp:~kampka/ubuntu/quantal/lxc/upstart-instance
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1049908
Title:
Upstart control of lxc container instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1049908/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
