Marcus Sorensen 915babd970 fix kvm traffic labels (guest traffic types on multiple networks don't ...

work)

Cloudstack seems to let you create guest traffic types on multiple
physical networks. However, when I try this with KVM I end up always
bridging to whatever device is used for guest.network.device. This pulls
the traffic label (NicTO.getName()) and uses that bridge to ensure that
we get on the correct physical network, rather than just always using
the guest.network.device.

This also changes the bridge naming scheme from cloudVirBr + vlanid to
br + physicalinterface + "-" + vlanid. This is because we should be able
to support the same vlan numbers per physical network, and the previous
bridge name would not support this and collide.

Signed-off-by: Edison Su <sudison@gmail.com>

2012-09-26 17:14:57 -07:00

..

installer

license header changes for scripts folder from Chip Childers

2012-06-23 00:58:00 -04:00

network

Patch from Gavin Lee: Change license to ASL2.0 in server and tools

2012-08-30 10:36:29 -04:00

storage

t-templateid-to-bypass-db-access-during-cloud-instal

2012-09-17 11:27:38 -07:00

util

license header changes for scripts folder from Chip Childers

2012-06-23 00:58:00 -04:00

vm

fix kvm traffic labels (guest traffic types on multiple networks don't

2012-09-26 17:14:57 -07:00

.pydevproject

License header updates for the scripts folder.

2012-08-03 09:38:28 -04:00