[ovs-discuss] [ovn-controller-vtep] Will ovn-controller-vtep write vtep db

Kenneth Østrup kennetho at easyspeedy.com
Thu Feb 2 16:45:45 UTC 2017


----- On 2 Feb, 2017, at 16:02, Macauley Cheng macauley_cheng at accton.com wrote:
> I try to setup the ovn environment with ovn-controller-vtep. But I found
> ovn-controller-vtep won’t write anything to vtep database.
> According to OVN architecture document, the tunnel key in ovnsb-db was filled by
> ovn-controller-vtep and it is as described.
> But I can’t find anyway that ovn-controller-vtep will setup vtep database, is
> this normal?
> 
> Is their any example to use ovs to simulate the hardware switch? Currently I use
> real hardware switch to test.

What kind of switch are you testing?

I have tested OVN Hardware VTEP on Cumulus Linux. L2 connectivity between a logical switch and a physical switch port and VLAN is working for me. One issue I ran into was that the openvswitch-vtep on Cumulus Linux includes vtep schema version 1.3.0. The current vtep schema in openvswitch is version 1.7.0.

In my case, ovn-controller-vtep gave me the following warnings:

|00015|ovsdb_idl|WARN|hardware_vtep database lacks ACL table (database needs upgrade?)
|00016|ovsdb_idl|WARN|hardware_vtep database lacks ACL_entry table (database needs upgrade?)
|00017|ovsdb_idl|WARN|Global table in hardware_vtep database lacks other_config column (database needs upgrade?)
|00018|ovsdb_idl|WARN|Logical_Router table in hardware_vtep database lacks LR_fault_status column (database needs upgrade?)
|00019|ovsdb_idl|WARN|Logical_Router table in hardware_vtep database lacks acl_binding column (database needs upgrade?)
|00020|ovsdb_idl|WARN|Logical_Router table in hardware_vtep database lacks other_config column (database needs upgrade?)
|00021|ovsdb_idl|WARN|Logical_Switch table in hardware_vtep database lacks other_config column (database needs upgrade?)
|00022|ovsdb_idl|WARN|Logical_Switch table in hardware_vtep database lacks replication_mode column (database needs upgrade?)
|00023|ovsdb_idl|WARN|Physical_Locator table in hardware_vtep database lacks tunnel_key column (database needs upgrade?)
|00024|ovsdb_idl|WARN|Physical_Port table in hardware_vtep database lacks acl_bindings column (database needs upgrade?)
|00025|ovsdb_idl|WARN|Physical_Port table in hardware_vtep database lacks other_config column (database needs upgrade?)
|00026|ovsdb_idl|WARN|Physical_Switch table in hardware_vtep database lacks other_config column (database needs upgrade?)

This resulted in ovn-controller-vtep being unable to update the "Ucast_Macs_Remote" table on the vtep database running on Cumulus Linux.

I have tried to simply replace the schema file with the new version. Knowing that I have only updated the schema, this could likely give some trouble down the road. Maybe someone can chime in here on the specifics?

-- 
Best regards
Kenneth Oestrup


More information about the discuss mailing list