On Tue, Mar 4, 2014 at 6:17 AM, Cristina Palomo Regidor
<[email protected]> wrote:
> Hello,
>
> Regarding the command ovs-ctl start in the service script under /etc/init.d,
> if I put the option:
>
> --system-id=random
>
> Does it matter that this option was not specified when I installed the
> openvswitch and started it manually using the commands that are specified in
> openvswitch.org:
> http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=INSTALL;hb=HEAD
It is okay if you started the daemons manually. The system-id is
useful for integration with a controller.
The IntegrationGuide has the following information:
The Open_vSwitch table describes the switch as a whole. The
'system_type' and 'system_version' columns identify the platform to the
controller. The 'external_ids:system-id' key uniquely identifies the
physical host. In XenServer, the system-id will likely be the same as
the UUID returned by 'xe host-list'. This key allows controllers to
distinguish between multiple hypervisors.
Most of this configuration can be done with the ovs-ctl command at
startup. For example:
ovs-ctl --system-type="XenServer" --system-version="6.0.0-50762p" \
--system-id="${UUID}" "${other_options}" start
Alternatively, the ovs-vsctl command may be used to set a particular
value at runtime. For example:
ovs-vsctl set open_vswitch . external-ids:system-id='"${UUID}"'
>
> I mean that if you use that commands you don't specify nothing similar to
> that option.
>
> Thanks and BR/
>
>
>
>
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
>
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
