All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: netdev discussion list <netdev@vger.kernel.org>,
	netconf developers list <netconf-devel@lists.alioth.debian.org>
Subject: Re: non-root, non-real network manipulation for netconf testing
Date: Tue, 3 Jun 2008 11:05:14 +0100	[thread overview]
Message-ID: <20080603100513.GA18161@solarflare.com> (raw)
In-Reply-To: <20080603080529.GA9010@lapse.madduck.net>

martin f krafft wrote:
> Dear networking wizards,
> 
> This is a bit of a self-reflexive mail, but I hope some of you might
> have some input...
> 
> In writing netconf[0], we are having a bit of a problem with the
> test suite, since many of netconf's operations require root rights
> (e.g. interface manipulation with /bin/ip). In addition, a test
> suite manipulating the network configuration of the running machine
> is not really something I feel comfortable with.
> 
> 0. http://netconf.alioth.debian.org
> 
> So I am trying to come up with alternative plans, of which there are
> three:
> 
> 1. do not fail tests that need root rights when run as non-root
> 2. set up a VDE network (which still requires root rights)
> 3. write a mock /bin/ip which pretends to be doing what it'd be doing
[...]

Have you considering running the tests in User-Mode Linux or some
other kind of virtualised environment?

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.

  reply	other threads:[~2008-06-03 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  8:05 non-root, non-real network manipulation for netconf testing martin f krafft
2008-06-03 10:05 ` Ben Hutchings [this message]
2008-06-03 10:20   ` martin f krafft
2008-06-03 10:47     ` Ben Hutchings
2008-06-04  9:13       ` martin f krafft
2008-06-03 17:43 ` Bas Wijnen

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=20080603100513.GA18161@solarflare.com \
    --to=bhutchings@solarflare.com \
    --cc=netconf-devel@lists.alioth.debian.org \
    --cc=netdev@vger.kernel.org \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.