[ovs-discuss] JSON RPC Requests -mutate and "where" condition

[Ben Pfaff]

Please don't drop the list.

The UUIDs are random.  The OVSDB server generates them, not the OVSDB
client.

What documentation says that they are only relevant for a given
transaction?

On Thu, Jul 18, 2013 at 06:22:23PM -0400, Dmita Levy wrote:
> Are the UUID's arbitrarily generated or they are a compilation of values
> that are meaningful to OVS. Essentially can they be decoded to provide info
> on what they are referencing. I ask because I see that I need to generate
> UUID's and will use a Java class to do so if necessary but I assume they
> are just random generated identifiers. Is this assumption correct? Also,
> some of the documentation I'm reading says the UUID values are only
> relevant for each transaction?
> 
> On Thu, Jul 18, 2013 at 6:06 PM, Ben Pfaff <blp at nicira.com> wrote:
> 
> > On Thu, Jul 18, 2013 at 05:52:58PM -0400, Dmita Levy wrote:
> > > Hello,
> > >
> > > I was looking through the IETF draft document for making JSON RPC request
> > > to OVS and noticed the following:
> > >
> > > *"where": [<condition>*]       required*
> > >
> > > I don't quite understand what should be in the [<condition>*] array
> > > that is sent with the request.  This mutate request is doing what
> > > exactly?
> > >
> > >             "op" : "mutate",
> > >             "table" : "Bridge",
> > >             "where" : [
> > >                 [
> > >                     "_uuid",
> > >                     "==",
> > >                     [
> > >                         "uuid",
> > >                         "18d02a5e-6150-4ddf-9446-a8e7e87f7955"
> > >                     ]
> > >                 ]
> > >             ],
> >
> > This "where" clause says to match only rows that have UUID
> > 18d02a5e-6150-4ddf-9446-a8e7e87f7955 in the _uuid column (which will
> > be exactly zero or one rows).
> >