Networking ML2 Generic Switch

[RFE] Configure switch ports for control plane hosts

Bug #1690115 reported by Mark Goddard
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Networking ML2 Generic Switch
Fix Committed
Undecided
Mark Goddard

Bug Description

Trunk ports are necessary to support connectivity of VLAN networks between multiple switches and to extend L2 networks to control plane nodes for higher layer services (routing, DHCP, etc.). For inter-switch links we may be able to use a dynamic protocol such as GVRP to ensure VLAN membership on trunk ports. For ports attached to control plane nodes this is not always possible.

Currently only switch ports corresponding to neutron ports are configured by the generic switch driver. This is a problem for some switches that do not support adding a port to a VLAN that has not been created on the switch.

For example, with Dell Force10 switches (at least the S6010-ON), it does not appear to be possible to add an interface to all VLANs, or to have an interface be a member of a VLAN when the corresponding VLAN interface has not been created. Since NGS manages the creation and destruction of these VLAN interfaces, it must also manage tagged membership of them for ports that require it.

This RFE proposes adding support to the generic switch driver for configuration of a static set of ports on each switch as tagged members of each network managed by the generic switch driver. On deletion of networks, these ports will be removed.

The proposed configuration mechanism is via a new per-switch configuration option, ngs_trunk_ports. The option format would be a comma-separated list of ports. For example:

[genericswitch:switch1]
device_type = acme
ip = 1.2.3.4
username = bob
password = drowssap
ngs_trunk_ports = port1,port2

Tags: rfe
Mark Goddard (mgoddard)
Changed in networking-generic-switch:
assignee: nobody → Mark Goddard (mgoddard)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-generic-switch (master)

Fix proposed to branch: master
Review: https://review.openstack.org/524135

Changed in networking-generic-switch:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/524138

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-generic-switch (master)

Reviewed: https://review.openstack.org/524135
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=16c50b691bbe67c267f0ebfde8a79a54f19ea0cd
Submitter: Zuul
Branch: master

commit 16c50b691bbe67c267f0ebfde8a79a54f19ea0cd
Author: Mark Goddard <email address hidden>
Date: Thu May 11 09:45:54 2017 +0100

    Support configuration of trunk ports

    Trunk ports are necessary to support connectivity of VLAN networks between
    multiple switches and to control plane nodes. Currently only switch
    ports corresponding to neutron ports are configured by the generic
    switch driver. This is a problem for some switches that do not support
    adding a port to a VLAN that has not been created on the switch.

    This change adds support for configuration of trunk ports when networks
    are created and destroyed. These trunk ports are configured via the
    per-switch configuration option 'ngs_trunk_ports', which is a
    comma-separated list. Currently no drivers support this option.

    Change-Id: I6c40f7f31058bc6e5e893743b6cdcd896d4850d1
    Partial-Bug: #1690115

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/524138
Committed: https://git.openstack.org/cgit/openstack/networking-generic-switch/commit/?id=d8d58a81565116a8fae796d55ab5ee6fe90d83c7
Submitter: Zuul
Branch: master

commit d8d58a81565116a8fae796d55ab5ee6fe90d83c7
Author: Mark Goddard <email address hidden>
Date: Thu May 11 10:39:05 2017 +0100

    Add support for trunk ports on Dell switches

    On Dell Force10 switches, interfaces are added as tagged members of a
    VLAN using the following commands:

    interface vlan <id>
    tagged <if>

    They can be removed similarly:

    interface vlan <id>
    no tagged <if>

    This change uses these commands to support configuration of trunk ports
    for all networks.

    Change-Id: I77f57ac1730eac2869fbdfeb112d1a9ea2b55fb1
    Partial-Bug: #1690115

Mark Goddard (mgoddard)
Changed in networking-generic-switch:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.