Re: [ovs-discuss] Reg: Ovs-Dpdk Forwarding Plane.

[Darrell Ball]

From:  on behalf of Durai Velan 
Chockalingam 
Date: Sunday, August 20, 2017 at 12:12 PM
To: "ovs-discuss@openvswitch.org" 
Subject: [ovs-discuss] Reg: Ovs-Dpdk Forwarding Plane.

Hello All,
Am trying to look for very comprehensive information on How Packet are Handled 
in Dataplane, for the following communication
1) VM-2-VM in Same compute host ( and both of them are vhostdpdkuser )
I understand that vhostdpdkuser, is nothing but a Unix Socket open, by Ovs-Dpdk 
and VM are Client.
However, I could not undertstand how forwarding of packets are happening 
between the VM via Socket ??
Does OVS Maintains any Forwarding Information bases for DPDK Vhostuser and if 
so what is tool to interact without those fibs ??

>>
At the forwarding layer, it a logical dp port (and at openflow layer, it is a 
of port), similar to other ports. When the packets are
received from a port and sent to a port, there is a difference, which is 
embodied in the netdev layer (in this case, netdev-dpdk),
which has vhost specific support, in addition to dpdk managed physical device 
support.
See the below links as well.
http://docs.openvswitch.org/en/latest/howto/dpdk/
http://docs.openvswitch.org/en/latest/topics/dpdk/vhost-user/
<<<

2) VM (Compute Host Network / or VLAN Say 10.0.0.1)-2-PHY--- L2 DEVICE 2-VM 
(Another Compute Host, Same Network / or VLAN Say 10.0.0.2 )
Similary, how does Packet flow in this Scenario, and what kind of configuration 
should be make in L2 Device
>
check the above links as well.
<






Any References, or Documentation explaining this would be also appreciated.

Thanks and Regards
Durai Velan.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] ovn-bridge-mappings configuration issue.

[Russell Bryant]

Great!  Thanks for following up to confirm that it works for you.

On Tue, Aug 22, 2017 at 6:14 AM, Rana, JaiSingh
 wrote:
> Hi Russel,
>
>
> Thanks for quick reply. Yes i created external network on controller node
> with
>
>
> neutron net-create NET-EXT --provider:network_type flat
> --provider:physical_network br-ex --router:external=true --shared
>
> Once i corrected option '--provider' option with
> '--provider:physical_network provider', its working fine on compute node.
>
> -Jai
>
>
> 
> From: Russell Bryant 
> Sent: 21 August 2017 21:17
> To: Rana, JaiSingh
> Cc: ovs-discuss@openvswitch.org
> Subject: Re: [ovs-discuss] ovn-bridge-mappings configuration issue.
>
> On Mon, Aug 21, 2017 at 7:43 AM, Rana, JaiSingh
>  wrote:
>> Hi,
>>
>> For configuring external gateway, ovn-controller man page says:
>>
>> "
>>
>> external_ids:ovn-bridge-mappings
>>  A list of key-value pairs that map a physical network
>> name to a local ovs bridge that  provides  connectivity
>>  to  that  network.   An  example  value mapping two
>> physical network names to two ovs bridges would be: phys‐
>>  net1:br-eth0,physnet2:br-eth1.
>> "
>>
>>
>> Created bridge br-ex and attached an interface p1p2 having external
>> connectivity.
>>
>>
>> # ovs-vsctl --may-exist add-br br-ex -- set bridge br-ex
>> protocols=OpenFlow13
>>
>> # ovs-vsctl set open . external-ids:ovn-bridge-mappings=provider:br-ex
>> # ovs-vsctl --may-exist add-port br-ex p1p2
>>
>>
>> After configuring Openstack with external networks, ovn-controller on
>> compute actually looks for bridge named "provider" in
>> ovn/controller/patch.c : add_bridge_mappings, which of-course is not
>> created
>> but throws error that "br-ex" not found as can be seen in
>> ovn-controller.log
>>
>> "2017-08-18T11:20:30.477Z|04536|patch|ERR| bridge not found for localnet
>> port 'provnet-03bf-ad69-4225-b69c-0cd23d7969af' with network name
>> 'br-ex'"
>>
>> When this external-id is defined as ovn-bridge-mappings=br-ex:br-ex, it
>> works fine and no error is thrown.
>>
>>
>> Is this a bug or the field before ":" in this external-id represents
>> bridge
>> name.
>
> The error message indicates that a "localnet" was created with a
> "network_name" of "br-ex".  The "network_name" should be set to
> "provider" in this example.
>
> --
> Russell Bryant



-- 
Russell Bryant
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] ovn-bridge-mappings configuration issue.

[Rana, JaiSingh]

Hi Russel,


Thanks for quick reply. Yes i created external network on controller node with

neutron net-create NET-EXT --provider:network_type flat 
--provider:physical_network br-ex --router:external=true --shared

Once i corrected option '--provider' option with '--provider:physical_network 
provider', its working fine on compute node.

-Jai



From: Russell Bryant 
Sent: 21 August 2017 21:17
To: Rana, JaiSingh
Cc: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] ovn-bridge-mappings configuration issue.

On Mon, Aug 21, 2017 at 7:43 AM, Rana, JaiSingh
 wrote:
> Hi,
>
> For configuring external gateway, ovn-controller man page says:
>
> "
>
> external_ids:ovn-bridge-mappings
>  A list of key-value pairs that map a physical network
> name to a local ovs bridge that  provides  connectivity
>  to  that  network.   An  example  value mapping two
> physical network names to two ovs bridges would be: phys‐
>  net1:br-eth0,physnet2:br-eth1.
> "
>
>
> Created bridge br-ex and attached an interface p1p2 having external
> connectivity.
>
>
> # ovs-vsctl --may-exist add-br br-ex -- set bridge br-ex
> protocols=OpenFlow13
>
> # ovs-vsctl set open . external-ids:ovn-bridge-mappings=provider:br-ex
> # ovs-vsctl --may-exist add-port br-ex p1p2
>
>
> After configuring Openstack with external networks, ovn-controller on
> compute actually looks for bridge named "provider" in
> ovn/controller/patch.c : add_bridge_mappings, which of-course is not created
> but throws error that "br-ex" not found as can be seen in ovn-controller.log
>
> "2017-08-18T11:20:30.477Z|04536|patch|ERR| bridge not found for localnet
> port 'provnet-03bf-ad69-4225-b69c-0cd23d7969af' with network name
> 'br-ex'"
>
> When this external-id is defined as ovn-bridge-mappings=br-ex:br-ex, it
> works fine and no error is thrown.
>
>
> Is this a bug or the field before ":" in this external-id represents bridge
> name.

The error message indicates that a "localnet" was created with a
"network_name" of "br-ex".  The "network_name" should be set to
"provider" in this example.

--
Russell Bryant
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Hashing to megaflow entry

[Sara Gittlin]

Thank you Justin,
i understand from the article, that generating megaflows and
installing in the kernel cache is already implemented in userspace -
ovs.
Before reading this article, i thought that megaflows were implemented
only for L2 normal mode.
Sara

On Tue, Aug 22, 2017 at 1:09 AM, Justin Pettit  wrote:
>
>> On Aug 21, 2017, at 8:19 AM, Sara Gittlin  wrote:
>>
>> One more - I did not see in the article that if a match is found in
>> megaflow cache - then a microflow is generated to be installed in the
>> microflow cache to improve performance for subsequnce packets
>
> An exact-match cache (microflow cache) is an implementation of the datapath.  
> The userspace and out-of-tree OVS Linux kernel module that ships as part of 
> OVS contain an exact-match cache that's managed by the datapath.  The 
> upstream OVS kernel module that ships with the Linux kernel was rejected by 
> the Linux upstream community, so it does not contain one.
>
> --Justin
>
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss