From 0e869da1a3ea0aa790982be87953c263b6cb59a1 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Wed, 28 Jul 2010 14:10:13 -0700 Subject: [PATCH] vswitch: Clarify and expand purpose of external_ids columns. Until now we have intended external_ids for use by external frameworks, but only for storing "identifiers" such as UUIDs and names. But there's no reason that frameworks can't use it for whatever purposes they like. This commit rewords the text describing the external_ids columns to be more expansive. CC: Peter Balland --- vswitchd/vswitch.xml | 52 ++++++++++++++++++++++++++++++++------------ 1 file changed, 38 insertions(+), 14 deletions(-) diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index af85477c..c164eb21 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -25,8 +25,12 @@ - Key-value pairs that identify this Open vSwitch's role in - external systems. The currently defined key-value pairs are: + 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. The currently + defined common key-value pairs are:
system-uuid
A universally unique identifier for the Open vSwitch's @@ -178,8 +182,12 @@ - Key-value pairs that identify this bridge's role in external systems. - The currently defined key-value pairs are: + 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. The currently + defined common key-value pairs are:
network-uuids
Semicolon-delimited set of universally unique identifier(s) for @@ -332,13 +340,21 @@ - Key-value pairs that identify this port's role in external systems. No - key-value pairs native to are currently defined. - For fake bridges (see the column), external - IDs for the fake bridge are defined here by prefixing a - key - with fake-bridge-, - e.g. fake-bridge-network-uuids. +

+ 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 key-value pairs native to are currently + defined. For fake bridges (see the + column), external IDs for the fake bridge are defined here by + prefixing a key with fake-bridge-, + e.g. fake-bridge-network-uuids. +

@@ -547,15 +563,23 @@ -

Key-value pairs that identify this interface's role in external - systems. All of the currently defined key-value pairs specifically +

+ 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. +

+

+ All of the currently defined key-value pairs specifically apply to an interface that represents a virtual Ethernet interface connected to a virtual machine. These key-value pairs should not be present for other types of interfaces. Keys whose names end in -uuid have values that uniquely identify the entity in question. For a Citrix XenServer hypervisor, these values are UUIDs in RFC 4122 format. Other hypervisors may use other - formats.

+ formats. +

The currently defined key-value pairs are:

vif-uuid
-- 2.30.2