cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-5697) multiple public ranges don't work with vxlan on KVM
Date Wed, 08 Jan 2014 00:07:53 GMT


ASF subversion and git services commented on CLOUDSTACK-5697:

Commit 5a8ea8ae7171bff3c0cc79517b330bf8321c0c4c in branch refs/heads/4.3 from [~mlsorensen]
[;h=5a8ea8a ]

CLOUDSTACK-5697 This patchset fixes a bug with the recently merged
vxlan code. Users can set a physical network to isolation type 'vxlan',
put public traffic on that physical network, and it will still attempt
to use 'vlan' isolation on the KVM hosts. This is going to be an issue
for other isolation types as well, but I'm not familiar with them, so
I'm just fixing vxlan for now.

> multiple public ranges don't work with vxlan on KVM
> ---------------------------------------------------
>                 Key: CLOUDSTACK-5697
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.3.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.3.0
> You can add multiple VLAN/VNI network ranges to your public traffic in cloudstack, these
don't work with VXLAN on KVM. In other words, only guest traffic type creates VNI interfaces
and bridges. Tested a solution and will push shortly.

This message was sent by Atlassian JIRA

View raw message