On 06/13/2015 09:47 PM, Ben Pfaff wrote:
> On Fri, Jun 12, 2015 at 02:29:38PM -0400, Russell Bryant wrote:
>> On 06/11/2015 03:14 AM, Ben Pfaff wrote:
>>> On Wed, Jun 10, 2015 at 11:53:47PM -0700, Ben Pfaff wrote:
>>>> I want to report progress I've made tonight on an extended form of the
>>>> OVS sandbox that I expect to be useful for testing OVN.  The main point
>>>> of the extension is to make it easy to start up multiple sandboxed
>>>> instances of OVS and then connect them together.
>>>>
>>>> What I have is at:
>>>>         https://github.com/blp/ovs-reviews/tree/ovn-sandbox
>>>>
>>>> Please don't bother to review it; the code and its history is a mess.
>>>> But I want to demonstrate some of the potential.  If you check this out
>>>> and build, then run a command like this (assuming that you keep your
>>>> build directory as a subdirectory of your source directory as I do;
>>>> otherwise adjust the path on --init):
>>>>
>>>>         utilities/ovs-sandbox --ovn --init=../ovn/sbtest
>>>
>>> If you use something like the following instead of the script from my
>>> previous email , you get a 50 "hypervisor" simulated scale test (on my
>>> laptop it starts in 3 seconds!):
>>>
>>>     net_add n1
>>>     ovn-nbctl lswitch-add br0
>>>     for i in `seq 50`; do
>>>         (sb_add hv$i
>>>         ovn_attach n1 hv$i br-phys 192.168.0.$i
>>>         as hv$i ovs-vsctl add-port br-int vif$i -- set Interface vif$i 
>>> type=dummy external-ids:iface-id=lp$i) &
>>>     done
>>>     for i in `seq 50`; do
>>>         xx=`printf %02x $i`
>>>         ovn-nbctl lport-add br0 lp$i
>>>         ovn-nbctl lport-set-macs lp$i f0:$xx:$xx:$xx:$xx:$xx
>>>     done
>>>     wait
>>
>> I gave this a try and even with 50 I get a few ports that don't come up.
>>  As far as I can tell it's not an OVN bug, though.  Every time I have a
>> port that doesn't come up, the VIF didn't get added to the switch for
>> that hypervisor so OVN is behaving as expected.
>>
>> So, for example I have ...
>>
>>   $ for n in `seq 50` ; do echo -n "$n : " && ovn-nbctl lport-get-up
>> lp$n ; done | grep down
>>   29 : down
>>   30 : down
>>   38 : down
>>   41 : down
>>   48 : down
>>
>>   $ ovs-vsctl --db=unix:/home/rbryant/src/ovs/sandbox/hv1/db.sock show |
>> grep vif
>>         Port "vif1"
>>             Interface "vif1"
>>
>>
>>   $ ovs-vsctl --db=unix:/home/rbryant/src/ovs/sandbox/hv29/db.sock show
>> | grep vif
>>   (nothing)
>>
>>
>> I haven't quite figured out what causes it yet, though.
> 
> I found the problem:
>         http://openvswitch.org/pipermail/dev/2015-June/056351.html
> 

Great!  So it was an OVN issue after all.  :-)

Thanks for the explanation of the issue.  That makes sense.

-- 
Russell Bryant
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to