[
https://issues.apache.org/jira/browse/CLOUDSTACK-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Sorensen closed CLOUDSTACK-1096.
---------------------------------------
Resolution: Won't Fix
As mentioned, the commit referenced didn't make it into 4.0.1, and as such
4.0.1 is missing support for multiple guest networks on different physical
networks.
> guest traffic types on multiple networks don't work,this bug is not fixed in
> 4.0.1
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1096
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1096
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Install and Setup, KVM
> Affects Versions: 4.0.1
> Environment: ubuntu 12.04 server
> Reporter: terryye
> Labels: guest, kvm, lable, vlan
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> This bug is not fixed .
> commit 915babd970a9b4f209deceb3c4973b7d1c9c0c12
> Author: Marcus Sorensen <shadow...@gmail.com>
> Date: Wed Sep 26 17:14:57 2012 -0700
> 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.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
