On Thu, Feb 13, 2014 at 08:26:25PM +0400, Andrey Korolyov wrote:
> On 02/13/2014 07:44 PM, Ben Pfaff wrote:
> > On Thu, Feb 13, 2014 at 11:57:57AM +0400, Andrey Korolyov wrote:
> >> Looking on very old thread[0], things are still the same since those
> >> times - e.g. I cannot set datapath_id directly and only one possible way
> >> to modify this value is to set override via other_config. It would be
> >> awesome if this behavior can be rewritten in more straightforward way
> >> because people may rely not on 'get bridge br datapath_id' output but on
> >> value in the OVSDB or be just unaware of this specific quirk.
> >
> > I don't actually understand the problem you see. As long as you read
> > the documentation, why doesn't everything work OK?
> >
>
> Actually it is undocumented, at least I am not able to find explicit
> notation for 'set datapath_id' in the current source. Looks like all
> other bridge-specific options, for example, 'fail_mode', can be set
> directly, so kind of doing datapath_id change is a white crow.
Here is what ovs-vswitchd.conf.db(5) says in the Bridge table
documentation:
datapath_id: optional string
Reports the OpenFlow datapath ID in use. Exactly 16 hex digits.
(Setting this column has no useful effect. Set other-con-
fig:datapath-id instead.)
other_config : datapath-id: optional string
Exactly 16 hex digits to set the OpenFlow datapath ID to a spe-
cific value. May not be all-zero.
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
