Can't use tagged VLAN interfaces in ext-port configuration

Bug #1546930 reported by Björn Tillenius on 2016-02-18
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack neutron-gateway charm
Wishlist
Unassigned
neutron-gateway (Juju Charms Collection)
Wishlist
Unassigned

Bug Description

With MAAS 1.9, having ports in access mode isn't officially supported, it expects ports to be in trunk mode in order to model the network configuration. This means that in order to have the ext-port network be separate from the data network, we need to give ext-port a tagged VLAN interface, e.g. eth1.1234.

Looking at the code, virtual interfaces are ignored, so specifying eth1.1234 won't work. Furthermore, for Landscape we need to specify the interface by MAC address, since specifying the interface by name is troublesome when you have multiple neutron-gateway units. Both eth1 and eth.1234 will have the same MAC address.

So we need a way to specify both the physical NIC and which VLAN tag to use.

tags: added: kanban-cross-team landscape
James Page (james-page) wrote :

Confirmed

        for nic in list_nics():
            # Ignore virtual interfaces (bond masters will be identified from
            # their slaves)
            if not is_phy_iface(nic):
                continue

Resolver code will skip virtual interfaces....

Changed in neutron-gateway (Juju Charms Collection):
status: New → Confirmed
tags: removed: kanban-cross-team
James Page (james-page) on 2017-01-05
Changed in neutron-gateway (Juju Charms Collection):
importance: Undecided → Wishlist
status: Confirmed → Triaged
James Page (james-page) on 2017-02-23
Changed in charm-neutron-gateway:
importance: Undecided → Wishlist
status: New → Triaged
Changed in neutron-gateway (Juju Charms Collection):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers