503a9417de
The INTERNAL and EXTERNAL networks configured by destroy and setup network scripts are inverted with reference to the default config_controller selections as well as the wiki StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage. The most pressing concern in this is that what was actually the internal management network was being nat'd. Also, under normal testing it is not recommended to address the internal management network from the virtualization host. There are unlikely to be configurations that will have external devices addressing the management network. Delete what was "EXTERNAL", actually internal, and rename "INTERNAL" to be EXTERNAL. Related-Bug: #1790716 Change-Id: I08f9e7712fed120001c864903880e13e9478764d Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
14 lines
404 B
Bash
Executable File
14 lines
404 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr}
|
|
EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24}
|
|
EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24}
|
|
|
|
for i in {1..4}; do
|
|
BRIDGE_INTERFACE_NAME=${BRIDGE_INTERFACE}$i
|
|
if [ -d "/sys/class/net/${BRIDGE_INTERFACE_NAME}" ]; then
|
|
sudo ifconfig ${BRIDGE_INTERFACE_NAME} down
|
|
sudo brctl delbr ${BRIDGE_INTERFACE_NAME}
|
|
fi
|
|
done
|