Description of problem:
I am trying to test network isolation in virt, but I am finding that the version of devtest_testenv.sh in instack does not support the right parameters. In the upstream version we can pass multiple baremetal bridge names and vlan IDs and the VMs would have multiple bridges connected to simulate 3 network adapters, and 5 VLANs across the bridges.
Version-Release number of selected component (if applicable):
instack.noarch 0.0.7-1.el7ost @rhelosp-7.0-director-poodle
instack-undercloud.noarch 2.1.2-1.el7ost @rhelosp-7.0-director-poodle
Steps to Reproduce:
1. Before running instack-virt-setup, run
2. export TESTENV_ARGS="--baremetal-bridge-names 'brbm brbm1 brbm2' --vlan-trunk-ids='10 20 30 40 50'"
3. Then run instack-virt-setup
+ eval 'sudo -H -E tripleo devtest_testenv.sh --baremetal-bridge-names="brbm brbm2 brbm3" --vlan-trunk-ids="10 20 30 40 50" instackenv.json'
++ sudo -H -E tripleo devtest_testenv.sh '--baremetal-bridge-names=brbm brbm2 brbm3' '--vlan-trunk-ids=10 20 30 40 50' instackenv.json
devtest_testenv.sh: unrecognized option '--baremetal-bridge-names=brbm brbm2 brbm3'
devtest_testenv.sh: unrecognized option '--vlan-trunk-ids=10 20 30 40 50'
The test environment should be set up with VMs with 3 NICs and 5 VLANs on the baremetal bridges.
This works upstream, so I think we just need a newer version of devtest_testenv.sh downstream.
This is preventing testing in virtual environments of the network configuration code. We can test on bare metal, but it would be really great if we could get broader test coverage on the network isolation code.
FYI since I came across this today, I had to get openstack-tripleo v0.0.7 (I had 0.0.6) to get a clean run for instack-virt-setup (after setting TESTENV_ARGS as above).
---> Package openstack-tripleo.noarch 0:0.0.7-0.1.1664e566.el7ost will be an update
export TESTENV_ARGS="--baremetal-bridge-names 'brbm brbm1 brbm2' --vlan-trunk-ids='10 20 30 40 50'"
After setup is complete:
[stack@lenovo-x3850-02 ~]$ sudo ovs-vsctl show
trunks: [0, 10, 20, 30, 40, 50]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.