Comment 3 for bug 1610899

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