[jira] [Commented] (CLOUDSTACK-2328) Linux native VXLAN support on KVM hypervisor

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778853#comment-13778853 ] 

ASF subversion and git services commented on CLOUDSTACK-2328:
-------------------------------------------------------------

Commit a45ee749ace84a88e8f0b4c50ade59f71d45e89e in branch refs/heads/master from ynojima
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a45ee74 ]

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 and/or TODO:
- 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"
- Documentation!

Signed-off-by : Toshiaki Hatano <ha...@haeena.net>

                
> 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