summaryrefslogtreecommitdiff
path: root/ovn
diff options
context:
space:
mode:
authorHan Zhou <hzhou8@ebay.com>2018-12-18 14:18:34 -0800
committerBen Pfaff <blp@ovn.org>2018-12-27 11:45:27 -0800
commitb6413ae4728e94d1656e0769910afcccae116f59 (patch)
tree116dc8bab59574e6a0321421daffcd2e95528f80 /ovn
parenteca4cde025f7f061973fd1c511c34344ce57acd0 (diff)
downloadopenvswitch-b6413ae4728e94d1656e0769910afcccae116f59.tar.gz
ovn-sb.ovsschema: Avoid duplicated IPs in Encap table.
When adding a new chassis, if there is an old chassis with same IP existed in Encap table, it is allowed to be added today. However, allowing it to be added results in problems: 1. The new chassis cannot work because none of the other chassises are able to create tunnel to it, because of the IP confliction with already existed tunnel to the old chassis. 2. All the other chassises will continuously retry creating the tunnel and complaining about the error. So, instead of hiding the problem, it is better to expose it while trying to add the second chassis with duplicated IP. This patch ensures it from the ovsdb schema. Signed-off-by: Han Zhou <hzhou8@ebay.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'ovn')
-rw-r--r--ovn/ovn-sb.ovsschema7
1 files changed, 4 insertions, 3 deletions
diff --git a/ovn/ovn-sb.ovsschema b/ovn/ovn-sb.ovsschema
index 5b9537f6c..e4412c006 100644
--- a/ovn/ovn-sb.ovsschema
+++ b/ovn/ovn-sb.ovsschema
@@ -1,7 +1,7 @@
{
"name": "OVN_Southbound",
- "version": "1.17.0",
- "cksum": "3217981733 15045",
+ "version": "2.0.0",
+ "cksum": "3109267860 15085",
"tables": {
"SB_Global": {
"columns": {
@@ -50,7 +50,8 @@
"min": 0,
"max": "unlimited"}},
"ip": {"type": "string"},
- "chassis_name": {"type": "string"}}},
+ "chassis_name": {"type": "string"}},
+ "indexes": [["type", "ip"]]},
"Address_Set": {
"columns": {
"name": {"type": "string"},