From: Ben Pfaff Date: Wed, 28 Jul 2010 21:10:43 +0000 (-0700) Subject: vswitch: Add external_ids column to every table. X-Git-Tag: v1.1.0pre1~127 X-Git-Url: http://git.onelab.eu/?a=commitdiff_plain;h=13008eb3dd6b52905156389032e9251fd692c7c0;p=sliver-openvswitch.git vswitch: Add external_ids column to every table. It seems potentially useful for system integrators to have this available, and doesn't cost much. --- diff --git a/tests/ovs-vsctl.at b/tests/ovs-vsctl.at index 72090d020..56fc1ce2d 100644 --- a/tests/ovs-vsctl.at +++ b/tests/ovs-vsctl.at @@ -584,6 +584,7 @@ active_timeout : 0 add_id_to_interface : false engine_id : [] engine_type : [] +external_ids : {} targets : ["1.2.3.4:567"] ]], [ignore], [test ! -e pid || kill `cat pid`]) AT_CHECK([RUN_OVS_VSCTL([list interx x])], diff --git a/vswitchd/vswitch.ovsschema b/vswitchd/vswitch.ovsschema index 5df97b913..7f5863fa7 100644 --- a/vswitchd/vswitch.ovsschema +++ b/vswitchd/vswitch.ovsschema @@ -136,7 +136,10 @@ "ephemeral": true}, "statistics": { "type": {"key": "string", "value": "integer", "min": 0, "max": "unlimited"}, - "ephemeral": true}}}, + "ephemeral": true}, + "external_ids": { + "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}}}, "QoS": { "columns": { "type": { @@ -150,11 +153,17 @@ "min": 0, "max": "unlimited"}}, "other_config": { "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}, + "external_ids": { + "type": {"key": "string", "value": "string", "min": 0, "max": "unlimited"}}}}, "Queue": { "columns": { "other_config": { "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}, + "external_ids": { + "type": {"key": "string", "value": "string", "min": 0, "max": "unlimited"}}}}, "Mirror": { "columns": { @@ -187,7 +196,10 @@ "type": {"key": {"type": "integer", "minInteger": 1, "maxInteger": 4095}, - "min": 0, "max": 1}}}}, + "min": 0, "max": 1}}, + "external_ids": { + "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}}}, "NetFlow": { "columns": { "targets": { @@ -207,7 +219,10 @@ "type": "boolean"}, "active_timeout": { "type": {"key": {"type": "integer", - "minInteger": -1}}}}}, + "minInteger": -1}}}, + "external_ids": { + "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}}}, "sFlow": { "columns": { "targets": { @@ -219,7 +234,10 @@ "header": { "type": {"key": "integer", "min": 0, "max": 1}}, "agent": { - "type": {"key": "string", "min": 0, "max": 1}}}}, + "type": {"key": "string", "min": 0, "max": 1}}, + "external_ids": { + "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}}}, "Controller": { "columns": { "target": { @@ -254,7 +272,10 @@ "controller_burst_limit": { "type": {"key": {"type": "integer", "minInteger": 25}, - "min": 0, "max": 1}}}}, + "min": 0, "max": 1}}, + "external_ids": { + "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}}}, "SSL": { "columns": { "private_key": { @@ -264,5 +285,8 @@ "ca_cert": { "type": "string"}, "bootstrap_ca_cert": { - "type": "boolean"}}, + "type": "boolean"}, + "external_ids": { + "type": {"key": "string", "value": "string", + "min": 0, "max": "unlimited"}}}, "maxRows": 1}}} diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index c164eb216..6bcc0a244 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -700,6 +700,14 @@ Mbps. + + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. + @@ -741,6 +749,14 @@ values are unimportant; only relative ordering matters. + + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. +
@@ -822,6 +838,16 @@ in the appropriate table or tables.

+ + + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. + +
@@ -1009,6 +1035,16 @@ this network has no gateway. + + + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. + +
@@ -1050,6 +1086,14 @@ disambiguate the traffic.

When this option is enabled, a maximum of 508 ports are supported.

+ + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. +
@@ -1082,6 +1126,14 @@ SSL connection to a man-in-the-middle attack obtaining the initial CA certificate. It may still be useful for bootstrapping. + + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. +
@@ -1116,6 +1168,14 @@ sFlow targets in the form ip:port. + + + Key-value pairs for use by external frameworks that integrate with Open + vSwitch, rather than by Open vSwitch itself. System integrators should + either use the Open vSwitch development mailing list to coordinate on + common key-value definitions, or choose key names that are likely to be + unique. No common key-value pairs are currently defined. +