From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Lucas Bates <lucasb@mojatatu.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Marcelo Ricardo Leitner <mleitner@redhat.com>,
Vlad Buslov <vladbu@mellanox.com>,
Davide Caratti <dcaratti@redhat.com>,
kernel@mojatatu.com
Subject: Re: [RFC net-next 1/1] tdc.py: Introduce required plugins
Date: Fri, 12 Apr 2019 17:42:15 +0200 [thread overview]
Message-ID: <d8de9c6a-f1e5-a43e-4b6e-e20c3cd3e7d9@6wind.com> (raw)
In-Reply-To: <CAMDBHYK_06eddrLuWvhhGw8CCU0=+Tkgk90aSQppMu-QNgbfFQ@mail.gmail.com>
Le 12/04/2019 à 17:21, Lucas Bates a écrit :
> On Fri, Apr 12, 2019 at 4:31 AM Nicolas Dichtel
> <nicolas.dichtel@6wind.com> wrote:
>>> in our tri-weekly tc test meeting and the general consensus to address
>>> what you brought up is leaning towards the following:
>>>
>>> - adding a symlink to nsPlugin
>> I don't understand why a symlink is needed. Just load it by default and use it
>> when needed. A property can be added to each test to tell which plugin (in fact,
>> which topology) is needed to run it.
>> Thus, if a new complex test is added, it can define another topology.
>
> I'm loathe to hard-code it into the script, but we can avoid the
> symlink if we specify some default plugins to load in the
> tdc_config.py file.
Why is it a problem to specify the plugin in the test description? The fw tests
depend on a specific topology, thus it's better explicitly state that.
>
>>> - Changing default behaviour so that unless an option is explicitly
>>> specified, all the tests will be run under a namespace with automatic
>>> creation of the ports
>> Yes.
>>
>>> - If the user chooses /not/ to use namespaces, it will still create
>>> the veth pair to use.
>> In fact, I would say an option so that the user can choose another topology.
>
> Quite possibly, but for traffic generation (upcoming using scapy)
> we're just reusing the simple topology right now.
I was thinking you were arguing for this option. If nobody need it, let's just
remove it.
>
>>>> After your patch, I got the following error:
>>>> $ ./tdc.py
>>>> Traceback (most recent call last):
>>>> File "./tdc.py", line 740, in <module>
>>>> main()
>>>> File "./tdc.py", line 734, in main
>>>> set_operation_mode(pm, args)
>>>> File "./tdc.py", line 692, in set_operation_mode
>>>> check_required_plugins(pm, alltests)
>>>> File "./tdc.py", line 583, in check_required_plugins
>>>> os.chown('plugins/{}'.format(fname), uid=int(os.getenv('SUDO_UID')),
>>>> TypeError: int() argument must be a string or a number, not 'NoneType'
>>>
>>> That would be expected if you aren't running tdc with sudo or as root
>>> or as a user with network admin capability.
>> I was root for the test.
>
> Ah. That environment variable is probably not present on your system.
> Out of curiosity, what shell/distribution are you using?
>
It was on a debian 8.11 / bash.
Regards,
Nicolas
next prev parent reply other threads:[~2019-04-12 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 21:44 [RFC net-next 1/1] tdc.py: Introduce required plugins Lucas Bates
2019-04-10 14:33 ` Nicolas Dichtel
2019-04-11 20:54 ` Lucas Bates
2019-04-12 8:31 ` Nicolas Dichtel
2019-04-12 15:21 ` Lucas Bates
2019-04-12 15:42 ` Nicolas Dichtel [this message]
2019-04-12 16:07 ` Lucas Bates
2019-04-12 23:37 ` Nicolas Dichtel
2019-04-16 15:19 ` Lucas Bates
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=d8de9c6a-f1e5-a43e-4b6e-e20c3cd3e7d9@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=lucasb@mojatatu.com \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vladbu@mellanox.com \
--cc=xiyou.wangcong@gmail.com \
/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.