Originally created by @activeshadow on Mon, 14 Dec 2020 04:08:42 GMT
The VM name is used as the name for OVS GRE tunnel ports and mirrors, but OVS is not minimega namespace-aware, so if two different phenix experiments use the same name for the VM traffic should be mirrored to, the OVS commands will fail when the second of the two experiments is started.
One idea is to prepend the VM name with the experiment name, but this fails with the current OVS commands used since OVS OpenFlow port names are truncated to 15 characters.
The other option is to request a random OpenFlow port number between 30000-65535 when creating the GRE tunnel port on the cluster host the mirror VM is created on to use as the value to in_port instead of the port name, which will require tracking the OpenFlow port number in the experiment status for the app since the cleanup stage will need it.
Originally created by @activeshadow on Mon, 14 Dec 2020 04:08:42 GMT
The VM name is used as the name for OVS GRE tunnel ports and mirrors, but OVS is not minimega namespace-aware, so if two different phenix experiments use the same name for the VM traffic should be mirrored to, the OVS commands will fail when the second of the two experiments is started.
One idea is to prepend the VM name with the experiment name, but this fails with the current OVS commands used since OVS OpenFlow port names are truncated to 15 characters.
The other option is to request a random OpenFlow port number between 30000-65535 when creating the GRE tunnel port on the cluster host the mirror VM is created on to use as the value to
in_port
instead of the port name, which will require tracking the OpenFlow port number in the experiment status for the app since thecleanup
stage will need it.