[cleanup] Confusing naming convention for bridges

[dougbtv]

While running through some of the Multus CRD stuff, I realized I had made some mistakes due to a wonky naming scheme for the bridges.

bridge_name: br0
bridge_network_name: "br0"

• bridge_name: refers to the name of the bridge in the VM spin up script
• bridge_network_name: refers to the name of the bridge as created on the virt host.

I think that having two different variables here is actually good -- because sometimes you want to create the bridge on the virthost, and optionally use it -- or not. E.g. sometimes you'd create br0 (via bridge_network_name) on the virthost, and then you'd actually specify virbr0 (via bridge_name) to have NAT'd VMs on the virthost, sometimes at least.

In the end, these should maybe get named, or, note here for if/when the virthost plays get broken out otherwise.

[leifmadsen]

hrmmm.... how about...

• host_bridge_name
• virt_bridge_name

?