[ovs-discuss] [ovn] Port bindings to network

Murali R muralirdev at gmail.com
Mon Oct 12 16:05:50 UTC 2015


In neutron ovs agent, a vlan map was used to associate a network with local
vlan id and an associated tunnel id across hypervisors. I was thinking we
have similar mapping in ovn controller, except I don't find one. So trying
to understand. In a previous email, someone mentioned the south bound api
shows host to interface mapping. I was looking there for such association,
but there is none.

List of sb tables.
  <table name="Chassis" title="Physical Network Hypervisor and Gateway
Information">
  <table name="Encap" title="Encapsulation Types">
  <table name="Logical_Flow" title="Logical Network Flows">
  <table name="Multicast_Group" title="Logical Port Multicast Groups">
  <table name="Datapath_Binding" title="Physical-Logical Datapath Bindings">
  <table name="Port_Binding" title="Physical-Logical Port Bindings">

muralir at mmnc-1:~$ ovn-sbctl list Datapath_Binding
_uuid               : be86f1c8-e48f-476f-9dcd-9047947861e0
external_ids        :
{logical-switch="26213aab-087b-4dcd-891a-27c8a5619532"}
tunnel_key          : 1

_uuid               : d28cd285-2529-4f5b-aa77-573ebd93f46d
external_ids        :
{logical-switch="929b3fa8-506c-4a3a-8a95-c7017040f71a"}
tunnel_key          : 2
muralir at mmnc-1:~$
muralir at mmnc-1:~$
muralir at mmnc-1:~$ ovn-sbctl list Chassis
_uuid               : 04b53423-ff87-4e92-a499-0781b40c1088
encaps              : [7d8d6b66-c6de-4853-8345-63270a8343dc]
name                : "5f45d690-18d5-48f6-b700-58e4e88e3c9d"
vtep_logical_switches: []


Port_Binding

_uuid               : f72ce72c-b402-4405-ab7d-a47626c73be4
chassis             : 04b53423-ff87-4e92-a499-0781b40c1088
datapath            : be86f1c8-e48f-476f-9dcd-9047947861e0
logical_port        : "405571f2-5a5b-49b9-919a-52092b9dda3e"
mac                 : ["fa:16:3e:34:82:dd"]
options             : {}
parent_port         : []
tag                 : []
tunnel_key          : 5
type                : ""

_uuid               : fa767216-f506-4cd8-9945-ad48dfe671fd
chassis             : 04b53423-ff87-4e92-a499-0781b40c1088
datapath            : be86f1c8-e48f-476f-9dcd-9047947861e0
logical_port        : "31b72fb5-7467-4401-827c-8031785c5150"
mac                 : ["fa:16:3e:da:eb:0a"]
options             : {}
parent_port         : []
tag                 : []
tunnel_key          : 4
type                : ""

_uuid               : 390b19bf-625a-4535-af4b-ff671a9bc4be
chassis             : 04b53423-ff87-4e92-a499-0781b40c1088
datapath            : be86f1c8-e48f-476f-9dcd-9047947861e0
logical_port        : "ca437555-b282-4f3f-835b-afda00d63f4c"
mac                 : ["fa:16:3e:e8:18:09"]
options             : {}
parent_port         : []
tag                 : []
tunnel_key          : 6
type                : ""


In the tables above, only tables that has mappings to data path is
port_binding. The "tags" are empty in a functional system. The "tag" field
is supposed to have vlan ids per specs. The first 2 are neutron created
during nova boot. The last one is mine. The first 2 works and mine does not
connect to network.

I created a port for docker container exactly identical to what neutron
port creates, I see the logical flows created exactly identical to that of
neutron ports but I cannot ping the nodes on the network. In OVS, the flow
entries are identical to neutron created ones. The OVS external-ids set
right exactly as the corresponding neutron ports - mac address,
attached-mac, active and iface-id exactly to my values. I can ping between
neutron VMs but not from the docker pid-namespace which I created. So I
realized it could be the vlan-id is missing for traffic from container
which is why. But unable to trace where the vlan ids are saved in runtime
tables. If I knew, I can do necessary mapping in a similar way. Any
pointers to show the vlan id mapping for networks will be really helpful.

Thanks
Murali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20151012/468efa68/attachment-0002.html>


More information about the discuss mailing list