summaryrefslogtreecommitdiff
path: root/ovn/ovn-sb.ovsschema
diff options
context:
space:
mode:
authorBen Pfaff <blp@nicira.com>2015-04-20 14:47:31 -0700
committerBen Pfaff <blp@nicira.com>2015-04-20 15:18:12 -0700
commit747b2a45b03e93b0cef8ed631bf92e7afbdd238d (patch)
tree03141e5885763c6d2155d641edbeea31d72f4245 /ovn/ovn-sb.ovsschema
parent363b53302fddc6f8b35522770bf89427b8c9a46c (diff)
downloadopenvswitch-747b2a45b03e93b0cef8ed631bf92e7afbdd238d.tar.gz
ovn: Add logical_datapath concept to schema.
It's possible that we could implement all of the OVN concepts as a single collection of flow tables, but it makes more sense to me if we instead represent each logical switch and logical router separately. This also fits the model described in T. Koponen et al., "Network Virtualization in Multi-tenant Data Centers," NSDI '14, the model that OVN aspires to imitate. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Russell Bryant <rbryant@redhat.com> Acked-by: Justin Pettit <jpettit@nicira.com>
Diffstat (limited to 'ovn/ovn-sb.ovsschema')
-rw-r--r--ovn/ovn-sb.ovsschema2
1 files changed, 2 insertions, 0 deletions
diff --git a/ovn/ovn-sb.ovsschema b/ovn/ovn-sb.ovsschema
index 98662b825..5f2d1a4b9 100644
--- a/ovn/ovn-sb.ovsschema
+++ b/ovn/ovn-sb.ovsschema
@@ -33,6 +33,7 @@
"max": "unlimited"}}}},
"Pipeline": {
"columns": {
+ "logical_datapath": {"type": "uuid"},
"table_id": {"type": {"key": {"type": "integer",
"minInteger": 0,
"maxInteger": 127}}},
@@ -44,6 +45,7 @@
"isRoot": true},
"Bindings": {
"columns": {
+ "logical_datapath": {"type": "uuid"},
"logical_port": {"type": "string"},
"parent_port": {"type": {"key": "string", "min": 0, "max": 1}},
"tag": {