From e96d74409128c6a977e31f24fad9b267d2feb9a1 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Fri, 9 Aug 2024 18:57:15 +0200 Subject: New upstream version 1.48.8 --- docs/api/html/nm-openvswitch.html | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'docs/api/html/nm-openvswitch.html') diff --git a/docs/api/html/nm-openvswitch.html b/docs/api/html/nm-openvswitch.html index 42f15f5f..3f1b8460 100644 --- a/docs/api/html/nm-openvswitch.html +++ b/docs/api/html/nm-openvswitch.html @@ -47,12 +47,12 @@

  • NetworkManager only ever talks to a single OVSDB instance via an UNIX domain socket.

  • The configuration is made up of Bridges, Ports and - Interfaces. Interfaces are always enslaved to Ports, and Ports are always - enslaved to Bridges.

    • + Interfaces. Interfaces are always attached to Ports, and Ports are always + attached to Bridges.

  • NetworkManager only creates Bridges, Ports and Interfaces you ask it to. Unlike ovs-vsctl, it doesn't create the local interface nor its port automatically.

    • -

  • You can't enslave Interface directly to a Bridge. You +

  • You can't attach Interface directly to a Bridge. You always need a Port, even if it has just one interface.

  • There are no VLANs. The VLAN tagging is enabled by setting a ovs-port.tag @@ -69,7 +69,7 @@ type. Due to the limitations of OVSDB, "empty" Bridges (with no Ports) can't exist. NetworkManager inserts the records for Bridges into OVSDB when a Port is - enslaved. + attached.

    @@ -80,17 +80,17 @@ Due to the limitations of OVSDB, "empty" Ports (with no Interfaces) can't exist. Ports can also be configured to do VLAN tagging or Bonding. NetworkManager inserts the records for Ports into OVSDB when an Interface is - enslaved. Ports must be enslaved to a Bridge.

    + attached. Ports must be attached to a Bridge.

    Interfaces

    -

    Interfaces are represented by a connections enslaved to a Port. The +

    Interfaces are represented by a connections attached to a Port. The system interfaces (that have a corresponding Linux link) have a respective connection.type of the link (e.g. "wired", "bond", "dummy", etc.). Other interfaces ("internal" or "patch" interfaces) are of ovs-interface type. The OVSDB entries are - inserted upon enslavement to a Port.

    + inserted upon attachment to a Port.

    @@ -100,10 +100,10 @@ 
    $ nmcli conn add type ovs-bridge conn.interface bridge0
 Connection 'ovs-bridge-bridge0' (d10fc64d-1d48-4394-a1b8-e1aea72f27d5) successfully added.
-$ nmcli conn add type ovs-port conn.interface port0 master bridge0
+$ nmcli conn add type ovs-port conn.interface port0 controller bridge0
 Connection 'ovs-port-port0' (5ae22bae-bba4-4815-9ade-7e635633e1f0) successfully added.
-$ nmcli conn add type ovs-interface slave-type ovs-port conn.interface iface0 \
-  master port0 ipv4.method manual ipv4.address 192.0.2.1/24
+$ nmcli conn add type ovs-interface port-type ovs-port conn.interface iface0 \
+  controller port0 ipv4.method manual ipv4.address 192.0.2.1/24
 Connection 'ovs-interface-iface0' (3640d2a1-a2fd-4718-92f1-cffadb5b6cdc) successfully added.

    As said above, you need to create a Port even for a single interface. @@ -115,9 +115,9 @@ Connection 'ovs-interface-iface0' (3640d2a1-a2fd-4718-92f1-cffadb5b6cdc) success

    Example 21. Adding a Linux interface to a Bridge

    -
    $ nmcli conn add type ovs-port conn.interface port1 master bridge0
+
    $ nmcli conn add type ovs-port conn.interface port1 controller bridge0
 Connection 'ovs-port-port1' (67d041eb-8e7b-4458-afee-a1d07c9c4552) successfully added.
-$ nmcli conn add type ethernet conn.interface eth0 master port1
+$ nmcli conn add type ethernet conn.interface eth0 controller port1
 Connection 'ovs-slave-eth0' (d459c45c-cf78-4c1c-b4b7-505e71379624) successfully added.
 
    
 
    Again, you need a port.
    
@@ -126,9 +126,9 @@ Connection 'ovs-slave-eth0' (d459c45c-cf78-4c1c-b4b7-505e71379624) successfully
 
    
 
    Example 22. Creating a VLAN
    
 
    
-
    $ nmcli conn add type ovs-port conn.interface port2 master bridge0 ovs-port.tag 120
+
    $ nmcli conn add type ovs-port conn.interface port2 controller bridge0 ovs-port.tag 120
 Connection 'ovs-port-port2' (3994c093-4ef7-4549-a4fd-627b831c3cb8) successfully added.
-$ nmcli conn add type ethernet conn.interface eth1 master port2
+$ nmcli conn add type ethernet conn.interface eth1 controller port2
 Connection 'ovs-slave-eth1' (099be06e-71ad-484d-8d5a-fcadc5f207f5) successfully added.
 
    
 
    It's just a port with a tag.
    
@@ -137,11 +137,11 @@ Connection 'ovs-slave-eth1' (099be06e-71ad-484d-8d5a-fcadc5f207f5) successfully
 
    
 
    Example 23. Creating a Bond
    
 
    
-
    $ nmcli conn add type ovs-port conn.interface bond0 master bridge0
+
    $ nmcli conn add type ovs-port conn.interface bond0 controller bridge0
 Connection 'ovs-port-bond0' (d154ebf9-e999-4e1b-a084-a3de53d25d8a) successfully added.
-$ nmcli conn add type ethernet conn.interface eth2 master bond0
+$ nmcli conn add type ethernet conn.interface eth2 controller bond0
 Connection 'ovs-slave-eth2' (475ac1bf-30b2-4534-a877-27f33f58b082) successfully added.
-$ nmcli conn add type ethernet conn.interface eth3 master bond0
+$ nmcli conn add type ethernet conn.interface eth3 controller bond0
 Connection 'ovs-slave-eth3' (8dedeecb-ed12-482b-b77a-24a4fb835136) successfully added.
 
    
 
    It's just a Port with multiple interfaces. See nm-settings-nmcli manual for
-- 
cgit 1.3.0-6-gf8a5