delta/NetworkManager.git/man/nm-openvswitch.xml, branch th/fix-python-test

man: update nm-openswitch example

2019-07-09T10:05:32+00:00

Seems that a quite common openswitch basic configuration consist of a
one bridge, one port and one interface, all with the same interface
name. When performing such configuration in NetworkManager you need to
specify the slave-type for the ovs-interface, otherwise the master
interface specified there may match the bridge interface, resulting in
an error.
So, let's specify the slave-type for the ovs-interface, so that the
example will work also when the same interface name is specified for
both the ovs-bridge and the ovs-port.

https://bugzilla.redhat.com/show_bug.cgi?id=1638038

doc,all: fix spelling of Open vSwitch (instead of OpenVSwitch)

2018-11-28T13:26:42+00:00

Also affects documentation and translated strings.

Reported-by: Flavio Leitner

man/openvswitch: advise to use "master" instead of "conn.master"

2018-08-06T16:59:01+00:00

It does some extra magic -- normalizes the value and initializes
slave-type.

https://bugzilla.redhat.com/show_bug.cgi?id=1519176

man/trivial: fix heading comment in nm-openvswitch.xml

2018-07-06T15:28:28+00:00

man/openvswitch: fix type in examples

2017-12-19T09:02:12+00:00

"conn.type" doesn't allow type aliases. Use "type" instead.

https://bugzilla.redhat.com/show_bug.cgi?id=1519173

man: add OpenVSwitch overview

2017-10-30T20:46:55+00:00