Let two consenting transport nodes choose how they want to talk; we
don't need to be so prescriptive in the supported encap types for OVN.

Signed-off-by: Justin Pettit <jpet...@nicira.com>
---
 ovn/ovn.ovsschema |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/ovn/ovn.ovsschema b/ovn/ovn.ovsschema
index 5597df4..c9f2af4 100644
--- a/ovn/ovn.ovsschema
+++ b/ovn/ovn.ovsschema
@@ -4,8 +4,7 @@
         "Chassis": {
             "columns": {
                 "name": {"type": "string"},
-                "encap": {"type": {"key": {"type": "string",
-                                           "enum": ["set", ["stt", "vxlan", 
"gre"]]}}},
+                "encap": {"type": "string"},
                 "encap_options": {"type": {"key": "string",
                                            "value": "string",
                                            "min": 0,
-- 
1.7.5.4

_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to