Support more than 2 physical interfaces in template

Bug #1610899 reported by Pavlo Ivanets
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel QA Team
Mitaka
Confirmed
High
Fuel QA Team

Bug Description

Detailed bug description:
    We enabled two physical interfaces in the template (see attached file), but in face only two last interfaces were enabled

Steps to reproduce:

1. We enabled two physical interfaces in the template. See the part below:
---
         private:
           address_pool: private-pool01
           dhcp: false
           stp: false
           parent_iface:
             phys_dev: !os_env BAREMETAL_PRIVATE_IFACE, vmnet2
             phys_dev: !os_env BAREMETAL_PRIVATE_IFACE2, vmnet3
           params:
             vlan_start: 1000
             vlan_end: 1030

         private2:
           address_pool: private-pool02
           dhcp: false
           stp: false
           parent_iface:
             phys_dev: !os_env BAREMETAL_PRIVATE2_IFACE, vmnet4
             phys_dev: !os_env BAREMETAL_PRIVATE2_IFACE2, vmnet5
           params:
             vlan_start: 1031
             vlan_end: 1060
---

2. But in face only vmnet3 and vmnet5 were added:

---
pivanets@tpi56:~$ brctl show
bridge name bridge id STP enabled interfaces
docker0 8000.56847afe9799 no
fuelbr236 8000.525400c04fe1 yes fuelbr236-nic
fuelbr237 8000.5254004c3a45 yes fuelbr237-nic
fuelbr238 8000.525400801a49 yes fuelbr238-nic
fuelbr239 8000.525400d9c63d yes fuelbr239-nic
fuelbr240 8000.525400bdd043 no fuelbr240-nic
virbr0 8000.525400e28f19 yes virbr0-nic
                            vnet0
virbr1 8000.525400d7a249 yes virbr1-nic
virbr2 8000.5254003ab621 yes virbr2-nic
virbr3 8000.52540084933a yes virbr3-nic
virbr4 8000.005056c00003 no virbr4-nic
                            vmnet3
virbr5 8000.005056c00005 no virbr5-nic
                            vmnet5
---

Tags: area-qa
Revision history for this message
Pavlo Ivanets (pivanets) wrote :
Changed in fuel:
importance: Undecided → Wishlist
tags: added: area-qa
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

Since 9.1 we use new workstation snapshots with two interfaces for private network, so we really need this functionality.

Changed in fuel:
importance: Wishlist → High
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

This can be done using veth pair and a bridge:

$ ip link add veth1 type veth peer name veth2
$ ip link add veth3 type veth peer name veth4

$ brctl addbr brpriv
$ brctl addbr brpriv2

$ brctl addif brpriv veth1
$ brctl addif brpriv vmnet2
$ brctl addif brpriv vmnet3

$ brctl addif brpriv veth3
$ brctl addif brpriv vmnet4
$ brctl addif brpriv vmnet5

# in the fuel-devops template use the second peer of veth interfaces:

         private:
           ...
           parent_iface:
             phys_dev: !os_env BAREMETAL_PRIVATE_IFACE, veth2

         private2:
           ...
           parent_iface:
             phys_dev: !os_env BAREMETAL_PRIVATE2_IFACE, veth4

Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

Mistake in the example from previous comment. veth3, vmnet4 and vmnet5 should be added to brpriv2:

$ ip link add veth1 type veth peer name veth2
$ ip link add veth3 type veth peer name veth4

$ brctl addbr brpriv
$ brctl addbr brpriv2

$ brctl addif brpriv veth1
$ brctl addif brpriv vmnet2
$ brctl addif brpriv vmnet3

$ brctl addif brpriv2 veth3
$ brctl addif brpriv2 vmnet4
$ brctl addif brpriv2 vmnet5

Changed in fuel:
status: New → Confirmed
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
milestone: none → 10.0-updates
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Vladimir Kozhukalov (kozhukalov)
Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

Looks like a feature request for fuel-devops. Re-assigning to fuel-qa.

Changed in fuel:
assignee: Vladimir Kozhukalov (kozhukalov) → Fuel QA Team (fuel-qa)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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