Open vSwitch concepts in OpenStack Installation Guide for openSUSE and SUSE Linux Enterprise Server - icehouse

[Sean M. Collins]

I believe the following sentences are confusing:
"The external bridge, called br-ex, connects to the external network. Finally, the VLAN configuration of the Open vSwitch plug-in uses bridges associated with each physical network."

Depending on how you read it - you may come away thinking that it creates a bridge per VLAN. Perhaps we should include some configuration dumps to clarify?

The different networks in OpenVSwitch are realized via VLAN tags on each port:

stack@oscomp-cc38-b01sudo ovs-vsctl show
9a25c837-32ab-45f6-b9f2-1dd888abcf0f
    Bridge br-int
        Port "tap18945187-26"
            tag: 1
            Interface "tap18945187-26"
        Port "tap48d5b5bf-f7"
            tag: 2
            Interface "tap48d5b5bf-f7"
        Port int-br-ex
            Interface int-br-ex
        Port br-int
            Interface br-int
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth1"
            Interface "eth1"
        Port phy-br-ex
            Interface phy-br-ex
    ovs_version: "1.10.2"

stack@oscomp-cc38-b01:~$ sudo ovs-ofctl dump-flows br-int
NXST_FLOW reply (xid=0x4):
 cookie=0x0, duration=1160.772s, table=0, n_packets=276, n_bytes=32752, idle_age=1, priority=3,in_port=1,dl_vlan=2010 actions=mod_vlan_vid:2,NORMAL
 cookie=0x0, duration=1259.305s, table=0, n_packets=17, n_bytes=2022, idle_age=1243, priority=3,in_port=1,dl_vlan=3001 actions=mod_vlan_vid:1,NORMAL
 cookie=0x0, duration=360797.75s, table=0, n_packets=1626629, n_bytes=262664072, idle_age=0, hard_age=65534, priority=2,in_port=1 actions=drop
 cookie=0x0, duration=360799.078s, table=0, n_packets=39, n_bytes=4102, idle_age=1144, hard_age=65534, priority=1 actions=NORMAL

Port table
_uuid bond_downdelay bond_fake_iface bond_mode bond_updelay external_ids fake_bridge interfaces lacp mac name other_config qos statistics status tag trunks vlan_mode
------------------------------------ -------------- --------------- --------- ------------ ------------ ----------- -------------------------------------- ---- --- ---------------- ------------ --- ---------- ------ --- ------ ---------
6c21f760-57d6-445c-8884-52bfecd82474 0 false [] 0 {} false [ebeb2887-67cb-4b1b-bf51-c7c81736f5b7] [] [] br-ex {} [] {} {} [] [] []
a16287be-840c-45e9-aa2c-0640f8ff7394 0 false [] 0 {} false [c260138d-0584-42df-be84-51fa60536d6e] [] [] br-int {} [] {} {} [] [] []
d8a64a3b-6f08-4868-a5c7-d8c85701c58c 0 false [] 0 {} false [b64cc0fa-a2ed-4bb4-99c6-873c3a8b3426] [] [] "eth1" {} [] {} {} [] [] []
5c70268b-2133-439b-b617-da5145b5eb09 0 false [] 0 {} false [5a254b35-eeb2-4f6a-b522-498388f258e0] [] [] int-br-ex {} [] {} {} [] [] []
db4d2498-b7df-412a-906b-916e02990e12 0 false [] 0 {} false [ad3dbb76-72c6-4e24-9fbd-912dce5f6739] [] [] phy-br-ex {} [] {} {} [] [] []
036500e9-d720-42aa-8343-39640b713e08 0 false [] 0 {} false [c392d626-b6d2-409d-a551-2e480b7011ff] [] [] "tap18945187-26" {} [] {} {} 1 [] []
3b5a232e-e3d5-4337-9792-8fd0caf87cd8 0 false [] 0 {} false [7f119223-df5b-46fb-bf97-4c75e67de453] [] [] "tap48d5b5bf-f7" {} [] {} {} 2 [] []

Now, there are settings in the OVS agent config file (network_vlan_ranges and bridge_mappings) where you can define multiple mappings - and here is the following in our ovs_neutron_plugin.ini:

bridge_mappings = default:br-ex

Perhaps we should make a section with an example of more than one value for bridge_mappings ?

-----------------------------------
Built: 2014-03-13T02:52:47 00:00
git SHA: 7013528ea5de4710e963abe414c6429145960b5f
URL: http://docs-draft.openstack.org/00/80100/3/check/gate-openstack-manuals-tox-doc-publish-checkbuild/20b7a1d/publish-docs/trunk/install-guide/install/zypper/content/concepts-neutron.openvswitch.html
source File: file:/home/jenkins/workspace/gate-openstack-manuals-tox-doc-publish-checkbuild/doc/install-guide/section_neutron-concepts.xml
xml:id: concepts-neutron.openvswitch

[Sean M. Collins (scollins)]

One of the networks uses the provider extensions:

stack@osctrl-cc38-b01:~/devstack$ neutron net-show default
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 278ab8be-31c2-497d-9d60-bd8791d146c7 |
| name | default |
| provider:network_type | vlan |
| provider:physical_network | default |
| provider:segmentation_id | 2010 |
| router:external | True |
| shared | True |
| status | ACTIVE |
| subnets | 2df2111c-1941-474d-8dfa-c12d6cb77f10 |
| tenant_id | 03617a4b4b444f209a1057f983c3ccb5 |
+---------------------------+--------------------------------------+

[Matt Kassawara (ionosphere80)]

Sean,

We're only supporting the "provider router with tenant networks" architecture using GRE tunnels in Icehouse. The Cloud Admin Guide or future networking guide will handle more complex configurations. At any rate, this section still needs some work.

[Sean M. Collins (scollins)]

OK - I will fork and submit patches for VLAN equivalents, and some more advanced configurations that we run in production

[Sean M. Collins (scollins)]

ah - when you say supporting only GRE - you mean for SUSE. I thought you mean the cloud admin guide in total, but that stuff has been covered. Sorry for the confusion.

[Andreas Jaeger (jaegerandi)]

supporting only GRE means: In the Install guide for the various distributions - so not only for SUSE but also for Debian etc.

[Matt Kassawara (ionosphere80)]

I would appreciate if someone else can improve the content of this section.

[Matt Kassawara (ionosphere80)]

We deprecated this section after removing the Open vSwitch plug-in from the installation guide.

https://review.openstack.org/#/c/88657/