[BUG] Mirror App Defaults to phenix bridge

[albuwab]

Bug Report

Description

When including the mirror (which is five years old now admittedly) in the scenario file, if each interface in the topology does not include a bridge: key with the appropriate experiment name, those VLANs will be added to a default phenix bridge. The new functionality of creating a new bridge for each experiment is not working with this old paradigm.

Steps to Reproduce

1. Create an experiment with a unique experiment name (other than "phenix").
2. Ensure the mirror app is included in the scenario file.
3. Launch the experiment.
4. Run mm bridge on the host to see the bridges and the associated VLANS.

Expected Behavior

When using the mirrorBridge: key in the mirror app within the scenario file users (my dumb self) expect the mirror interfaces on the target VMs (using the new directGRE functionality in a "recent" update) to be placed on the same bridge as the rest of the experiment.

Actual Behavior

Instead the mirror interface is placed on the name of the experiment (if using the above key), and the rest are placed on the phenix bridge.

Code Snippets

After firing up the experiment:

[REDACTED]@[REDACTED]:/phenix/topologies$ mm bridge
host | bridge | preexisting | vlans | trunks | tunnels | bonds | config
host1 | mega_bridge | false | [] | [] | [] | [] | {}
host1 | | false | [mirror (110)] | [] | [] | [] | {}
host1 | phenix | false | [0 VLAN1 (116) VLAN2 (102) VLAN3 (104) VLAN4 (114) VLAN5 (106) VLAN6 (101) VLAN7 (107) ] | [] | [] | [] | {}