Comment 5 for bug 107371

I discussed this with Robert Collins. He suggests using chroots to run multiple instances of the test suite on the one machine. This is kind of a cheat, but it's the kind of cheating that I like.

Each chroot can use a different loopback interface, and we can customize the hosts file of the chroot when we create it. We need to be sure that the Launchpad in each chroot is running on a different loopback interface.

<lifeless> jml: chroots
<lifeless> jml: + subunit
<jml> lifeless, chroots don't work around the port problem, I think.
<lifeless> jml: they can have their loopback interace e 127.0.0.2 etc
<lifeless> jml: so with a little alias love, and perhaps the odd patch - yes
<jml> I wonder how much alias love and how odd the patches would need to be.
<lifeless> s/127.0.0.1/localhost/ inside the code base
<lifeless> the alias stuff is triival - ip addr add in a schroot exec script
* lifeless handwaves furiously
<jml> lifeless, the codebase doesn't use 'localhost', it uses things like 'bazaar.launchpad.dev'
<jml> but that's a detail.
<lifeless> those are even easier ;)
<lifeless> thats just hosts in the chroot
<jml> right.
<lifeless> its actually the bind I was talkin about
<lifeless> jml: I don't think it will be complex.