From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Subject: Re: passt & mbuto
Date: Thu, 16 Jun 2022 08:51:49 +0200 [thread overview]
Message-ID: <20220616085149.2056bd28@elisabeth> (raw)
In-Reply-To: <20220614163008.1d1bbf4f@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]
On Tue, 14 Jun 2022 16:30:08 +0200
Stefano Brivio <sbrivio(a)redhat.com> wrote:
> On Tue, 14 Jun 2022 12:57:20 +1000
> David Gibson <david(a)gibson.dropbear.id.au> wrote:
>
> > On Tue, Jun 14, 2022 at 03:33:13AM +0200, Stefano Brivio wrote:
> > > On Fri, 10 Jun 2022 13:50:44 +1000
> > > David Gibson <david(a)gibson.dropbear.id.au> wrote:
> > >
> > > > 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.
> > >
> > > Hmm, yes, in my ideal world mbuto would be already widely distributed
> > > and we could drop the git clone. On the other hand, that's still one
> > > long-term goal of mine, so:
> > >
> > > > 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.
> > >
> > > ...I would prefer this option. Even though if you look at mbuto's git
> >
> > Yeah, I think it looks the best option to me as well, though not
> > necessarily the quickest to implement.
>
> Kind of done actually, I'll share it tomorrow (Wednesday).
...not quite :( and I'm off today, but it's almost there.
--
Stefano
prev parent reply other threads:[~2022-06-16 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 3:50 passt & mbuto David Gibson
2022-06-14 1:33 ` Stefano Brivio
2022-06-14 2:57 ` David Gibson
2022-06-14 14:30 ` Stefano Brivio
2022-06-16 6:51 ` Stefano Brivio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220616085149.2056bd28@elisabeth \
--to=sbrivio@redhat.com \
--cc=passt-dev@passt.top \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).