From: sugeshch <sugesh.chand...@intel.com>
This patch contains changes for OVN southbound DB schema to expose Openvswitch/
hypervisor details. A new table named "PN_sysinfo" is created in the OVN
Southbound DB to store the information of each chassis.
Signed-off-by: Sugesh Chandran <sugesh.chand...@intel.com>
---
ovn/ovn-sb.ovsschema | 14 ++++++++++++++
ovn/ovn-sb.xml | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
diff --git a/ovn/ovn-sb.ovsschema b/ovn/ovn-sb.ovsschema
index 1ffd1b4..83397d0 100644
--- a/ovn/ovn-sb.ovsschema
+++ b/ovn/ovn-sb.ovsschema
@@ -12,6 +12,20 @@
"max": "unlimited"}}},
"isRoot": true,
"indexes": [["name"]]},
+ "PN_sysinfo": {
+ "columns": {
+ "hostname": {"type": "string"},
+ "chassis": {"type": {"key": {"type": "uuid",
+ "refTable": "Chassis",
+ "refType": "strong"},
+ "min": 0, "max": 1}},
+ "ovn_bridge": { "type": "string"},
+ "ovn_bridge_type": {"type": {"key": {
+ "type": "string",
+ "enum": ["set", ["netdev", "system"]]}}},
+ "port_types": { "type": "string"}},
+ "isRoot": true,
+ "indexes": [["hostname"]]},
"Encap": {
"columns": {
"type": {"type": {"key": {
diff --git a/ovn/ovn-sb.xml b/ovn/ovn-sb.xml
index 57e9689..deb5f91 100644
--- a/ovn/ovn-sb.xml
+++ b/ovn/ovn-sb.xml
@@ -177,6 +177,59 @@
</group>
</table>
+ <table name="PN_sysinfo" title="Physical Chassis Capability Information">
+ <p>
+ Each row in this table represents a chassis with its capability
+ information on a physical network. The purpose of this table is to
provide
+ enough information to CMS via Northbound DB for starting the Virtual
+ machine on the specific Chassis. OVN northd populates the <code>Sys_Info
+ </code>table in Northbound DB using the information from this table.
+ </p>
+
+ <column name="hostname">
+ <p>
+ A hostname is the unique name assigned to every chassis/hypervisor.
+ </p>
+ </column>
+
+ <column name="chassis">
+ <p>
+ A chassis name which is taken from <ref key="system-id" table=
+ "Open_vSwitch" column="external_ids" db="Open_vSwitch"/> in the
+ Open_vSwitch database's <ref table="Open_vSwitch" db="Open_vSwitch"/>
+ table. The chassis name must have a one to one mapping to <code>
+ hostname</code>.
+ </p>
+ </column>
+
+ <column name="ovn_bridge">
+ <p>
+ An integration bridge name which is taken from the <ref
key="ovn_bridge"
+ table="Open_vSwitch" column="external_ids" db="Open_vSwitch"/>
+ in the Open_vSwitch database's <ref table="Open_vSwitch"
+ db="Open_vSwitch"/> table. The logical ports are connected to this
+ bridge on a chassis.
+ </p>
+ </column>
+
+ <column name="ovn_bridge_type">
+ <p>
+ An entry based on the integration bridge datapath which can be either
+ system or netdev. The netdev refers to userspace datapath and system
+ refers to kernel datapath.
+ </p>
+ </column>
+
+ <column name="port_types">
+ <p>
+ VIF types supported by the integration bridge in a specific chassis. It
+ is taken from the <ref column="iface_types" table="Open_vSwitch" db=
+ "Open_vSwitch"/> in the Open_vSwitch database's <ref
table="Open_vSwitch"
+ db="Open_vSwitch"/> table.
+ </p>
+ </column>
+ </table>
+
<table name="Encap" title="Encapsulation Types">
<p>
The <ref column="encaps" table="Chassis"/> column in the <ref
--
2.1.4
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
