On Tue, 28 Apr 2015 11:30:33 +0100 Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote: > On Tue, Apr 28, 2015 at 9:07 AM, Neil Williams <codehelp@debian.org> > wrote: > > > Chroot tests suffer from limitations with daemons (changed port > > numbers if the same daemon is running outside etc.) and are subject > > to whatever the running kernel can offer. > > has anyone considered modifying any automated chroot-based systems to > use lxc? There hasn't been any work on lxc in LAVA at least. It's been mentioned and some work has been planned but it's not scoped yet and there is insufficient reason / insufficient resources to push for it. > three years ago at phil hand's recommendation i converted a > XEN server with five guests over to lxc and it has worked out > extremely well. > > with a bit of arseing about i was even able to add the LVM partitions > formerly used by the XEN guests over to lxc, meaning that i didn't > have to mess with the filesystems (copy them out or anything). > > using lxc would solve the limitation that you describe, neil, about > daemons having to change port numbers. the only thing you can't do is > test kernel-related stuff (udev-related) with lxc. Kernel testing is the main objective of LAVA testing currently, so when chroot isn't enough, a complete test as a virtual machine or a new deployment is the main go-to. There's no overriding reason to have something in-between. Eventually, when other priorities are met - maybe. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgp61Rv3ODD4u.pgp
Description: OpenPGP digital signature