search

sandialabs / sceptre-phenix

phenix is an orchestration tool and GUI for Sandia's minimega platform
https://sandialabs.github.io/sceptre-docs/
GNU General Public License v3.0
17 stars 23 forks source link

[UI] Disconnect->Connect Interface Does Not Work #183

Open eric-c-wood opened 3 months ago

eric-c-wood commented 3 months ago

In the RunningExperiment view (i.e. RunningExperiment.vue), disconnecting an interface and then attempting to reconnect the interface will connect the interface to the default bridge (i.e. mega_bridge). The reason is that the optional bridge argument in the util/mm/minimega.go:ConnectVMInterface function is not provided. Since the interface is not connected to a bridge since it was disconnected and no bridge argument is provided, the interface is connected to the default mega_bridge.

It seems reasonable that when an interface is not connected to any bridge, the destination VLAN will be used to locate the destination bridge. The destination bridge can then be specified in the util/mm/minimega.go:ConnectVMInterface function.

Alternatively, the destination bridge could just be hardcoded to phenix since the action is originating from the Phenix UI. If the destination bridge is not hardcoded, how should conflicts be resolved if the destination VLAN exists on multiple bridges? Perhaps, if multiple bridges with the same VLAN tag exist, then perhaps the bridge name could be passed to the UI with the VLAN tag.

activeshadow commented 4 weeks ago

Sorry for the delay @eric-c-wood I'll look into this. As always, thank you for your detailed issue description!