passt & mbuto

[David Gibson <david@gibson.dropbear.id.au>]

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

Hi again,

I realized I wasn't quite right when I said that qrap problems where
what was currently stopping me running the passt (not pasta) tests.  I
did hit qrap issues somewhere, but the current stumbling block is that
mbuto looks for udhcpc to put into the guest image, which I can't
easily put onto my host system.

Now, in the short term, once my patch to remove usage of udhcpc from
the passt/pasta tests is applied, we could just remove udhcpc from the
mbuto profile as well.  However, that raises a wider scope issue:

The passt testing profile for mbuto appliances is in the mbuto tree,
not the passt tree.  That doesn't realy make sense, since it means any
change to what we need for the passt tests requires a synchronized
change with mbuto.  Particularly for a pretty young and project like
passt, that's not really tenable.  Plus, slurping an external tool
from some random URL in the tests is just kinda ugly.

I'm not immediately sure how best to to address this:

 * We could make mbuto take the profiles as some sort of external
   file, so they can be provided by the user, rather than built into
   the mbuto repository.

 * We could just fork a copy of mbuto into the passt tree, making
   local modifications for the profile, and only manually updating it
   to match upstream mbuto changes.

 * We could use an entirely different and more established tool for
   building our testing guest images in passt (e.g. supermin,
   buildroot or just picking a standard distro guest image)

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]