[
https://issues.apache.org/jira/browse/CLOUDSTACK-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749237#comment-13749237
]
ASF subversion and git services commented on CLOUDSTACK-2328:
-------------------------------------------------------------
Commit 34ae32e0c24777f9ac9cf265447688a3e21680c7 in branch refs/heads/master
from [~toshiaki.hatano]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=34ae32e ]
CLOUDSTACK-2328: Linux native VXLAN support on KVM hypervisor
Initial patch for VXLAN support.
Fully functional, hopefully, for GuestNetwork - AdvancedZone.
Patch Note:
in cloudstack-server
- Add isolation method VXLAN
- Add VxlanGuestNetworkGuru as plugin for VXLAN isolation
- Modify NetworkServiceImpl to handle extended vNet range for VXLAN isolation
- Add VXLAN isolation option in zoneWizard UI
in cloudstack-agent (kvm)
- Add modifyvxlan.sh script that handle bridge/vxlan interface manipulation
script
-- Usage is exactly same to modifyvlan.sh
- BridgeVifDriver will call modifyvxlan.sh instead of modifyvlan.sh when VXLAN
is used for isolation
Database changes:
- No change in database structure.
- VXLAN isolation uses same tables that VLAN uses to store vNet allocation
status.
Known Issue:
- Some resource still says 'VLAN' in log even if VXLAN is used
- in UI, "Network - GuestNetworks" dosen't display VNI
-- VLAN ID field displays "N/A"
> Linux native VXLAN support on KVM hypervisor
> --------------------------------------------
>
> Key: CLOUDSTACK-2328
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2328
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Network Controller, Network Devices
> Environment: Linux kernel 3.7 or later required
> Reporter: Toshiaki Hatano
> Assignee: Toshiaki Hatano
> Priority: Minor
> Fix For: Future
>
>
> Adding new network isolation mode which uses Linux kernel VXLAN tunneling
> interfaces
--
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
