In order to fit everything into available 10G ports to do the Ceph buildout and rack cloudvirt replaces in tasks (T242133 and T243471), we would like to test using vlan tagging to split traffic for control and hypervisor use over a single 10G interface instead of splitting that traffic by using two interfaces (and therefore 2 ports on the switches).
This task is to try this out in CODFW as a proof of concept.
Today the cloudvirts are configured with 2 network interfaces. These interfaces have the following configuration in codfw.
| Host port | Config type | VLAN | Traffic type |
| -- | -- | -- | -- |
| eno1 | access port | 2118 (cloud-hosts1-b-codfw) | server management and monitoring, disk image migrations |
| eno2 | trunk port | 2105 (cloud-instances2-b-codfw) | Virtual machine instance traffic |
In order to reduce the amount of 10Gb ports and better utilize the existing infrastructure we'd like to consolidate these 2 interfaces into 1.
Initial testing requests (we're totally open to discuss/change this!)
* **physical switch side**, we'd like to reconfigure eno1 to a trunk port with VLAN 2118 as default (untagged) and VLAN 2105 in the member list.
* **host side** we'll leverage the already existing 8021q module and configuration to create a new tagged interface eno1.2105. Once that is complete, this new interface will be mapped in neutron (on the local host) to `physical_interface_mappings = cloudinstances2b:eno1.2105`