You probably need an IP address on the physical network that you're running vxlan on, since this host needs to communicate with other hosts to send vxlan packets. Where prevously you could just bring up a bridge on an ethernet interface with no config, you can put all of your hosts on one untagged vlan, give them all ip addresses, and then the vxlan networks will flow over that. You can also use your physical interface name for the traffic label, if you have no other need for that bridge.
It looks like there's been a bit of documentation checked in for 4.3, so there should be at least some published along with the release of the feature, and here are some links to the design docs and such. I haven't reviewed the docs in detail. http://www.slideshare.net/haeenajp/asfccc2013-toshiaki-release https://cwiki.apache.org/confluence/display/CLOUDSTACK/Linux+native+VXLAN+support+on+KVM+hypervisor oot@devcloud-kvm-u:~/cloudstack-docs# grep -r -i vxlan * vxlan/en-US/CloudStack_VXLAN_Guide.xml: <bookinfo id="cloudstack_plugin_vxlan"> vxlan/en-US/CloudStack_VXLAN_Guide.xml: <title>&PRODUCT; Plugin Guide for the VXLAN Plugin</title> vxlan/en-US/CloudStack_VXLAN_Guide.xml: Plugin Guide for the VXLAN Plugin. vxlan/en-US/CloudStack_VXLAN_Guide.xml: <xi:include href="plugin-vxlan-about.xml" xmlns:xi="http://www.w3.org/2001/XInclude"; /> vxlan/en-US/CloudStack_VXLAN_Guide.xml: <xi:include href="plugin-vxlan-requirements.xml" xmlns:xi="http://www.w3.org/2001/XInclude"; /> vxlan/en-US/CloudStack_VXLAN_Guide.xml: <xi:include href="plugin-vxlan-configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude"; /> vxlan/en-US/CloudStack_VXLAN_Guide.xml: <xi:include href="plugin-vxlan-revision-history.xml" xmlns:xi="http://www.w3.org/2001/XInclude"; /> vxlan/en-US/plugin-vxlan-configuration.xml:<chapter id="How-to-configure-VXLAN-Plugin" > vxlan/en-US/plugin-vxlan-configuration.xml: <title>Configure &PRODUCT; to use VXLAN Plugin</title> vxlan/en-US/plugin-vxlan-configuration.xml: <xi:include href="plugin-vxlan-config-hypervisor.xml" xmlns:xi="http://www.w3.org/2001/XInclude";></xi:include> vxlan/en-US/plugin-vxlan-configuration.xml: <xi:include href="plugin-vxlan-config-management.xml" xmlns:xi="http://www.w3.org/2001/XInclude";></xi:include> vxlan/en-US/plugin-vxlan-config-management.xml:<section id="plugin-vxlan-config-management"> vxlan/en-US/plugin-vxlan-config-management.xml: <title>Setup zone using VXLAN</title> vxlan/en-US/plugin-vxlan-config-management.xml: The only thing you have to do is configure the physical network to use VXLAN as the isolation method for Guest Network. vxlan/en-US/plugin-vxlan-config-management.xml: <section id="plugin-vxlan-config-management-zone"> vxlan/en-US/plugin-vxlan-config-management.xml: <imagedata fileref="./images/vxlan-physicalnetwork.png"/> vxlan/en-US/plugin-vxlan-config-management.xml: <phrase>vxlan-physicalnetowkr.png: physicalnetwork configuration for VXLAN</phrase> vxlan/en-US/plugin-vxlan-config-management.xml: CloudStack needs to have one physical network for Guest Traffic with the isolation method set to "VXLAN". vxlan/en-US/plugin-vxlan-config-management.xml: <imagedata fileref="./images/vxlan-trafficlabel.png"/> vxlan/en-US/plugin-vxlan-config-management.xml: <phrase>vxlan-trafficlabel.png: traffic label configuration for VXLAN</phrase> vxlan/en-US/plugin-vxlan-config-management.xml: See <xref linkend="plugin-vxlan-config-hypervisor-kvm-ip"/> for details. vxlan/en-US/plugin-vxlan-config-hypervisor.xml:<section id="plugin-vxlan-config-hypervisor"> vxlan/en-US/plugin-vxlan-config-hypervisor.xml: <section id="plugin-vxlan-config-hypervisor-kvm"> vxlan/en-US/plugin-vxlan-config-hypervisor.xml: <section id="plugin-vxlan-config-hypervisor-kvm-ip"> vxlan/en-US/plugin-vxlan-config-hypervisor.xml: This plugin requires an IPv4 address on the KVM host to terminate and originate VXLAN traffic. vxlan/en-US/plugin-vxlan-config-hypervisor.xml: <section id="plugin-vxlan-config-hypervisor-kvm-centos"> vxlan/en-US/plugin-vxlan-config-hypervisor.xml: <section id="plugin-vxlan-config-hypervisor-kvm-ubuntu"> vxlan/en-US/plugin-vxlan-requirements.xml:<chapter id="vxlan-requirements"> vxlan/en-US/plugin-vxlan-requirements.xml: <title>System Requirements for VXLAN</title> vxlan/en-US/plugin-vxlan-requirements.xml: <section id="vxlan-table-of-requirement"> vxlan/en-US/plugin-vxlan-requirements.xml: <title>System Requirements for VXLAN</title> vxlan/en-US/plugin-vxlan-requirements.xml: <title>Hypervisor Requirement for VXLAN</title> vxlan/en-US/plugin-vxlan-requirements.xml: <entry>version >= 3.7, VXLAN kernel module enabled</entry> vxlan/en-US/plugin-vxlan-requirements.xml: <entry>It is recommended to use kernel >=3.9, since Linux kernel categorizes the VXLAN driver as experimental <3.9.</entry> vxlan/en-US/plugin-vxlan-requirements.xml: <section id="vxlan-req-distribution"> vxlan/en-US/plugin-vxlan-requirements.xml: <section id="vxlan-confirm"> vxlan/en-US/plugin-vxlan-requirements.xml:$ sudo modprobe vxlan && echo $? vxlan/en-US/plugin-vxlan-requirements.xml:# If it's non-0 value or error message, your kernel doesn't have VXLAN kernel module. vxlan/en-US/plugin-vxlan-requirements.xml:$ ip link add type vxlan help vxlan/en-US/plugin-vxlan-requirements.xml:# Confirm the output is usage of the command and that it's for VXLAN. vxlan/en-US/plugin-vxlan-requirements.xml:# If it's not, your iproute2 utility doesn't support VXLAN. vxlan/en-US/plugin-vxlan-requirements.xml: <section id="vxlan-req-build"> vxlan/en-US/plugin-vxlan-requirements.xml: Even if your system doesn't support VXLAN, you can compile the kernel and iproute2 by yourself. vxlan/en-US/plugin-vxlan-requirements.xml: <section id="vxlan-build-kernel"> vxlan/en-US/plugin-vxlan-requirements.xml:# then select "Virtual eXtensible Local Area Network (VXLAN)" and hit space. vxlan/en-US/plugin-vxlan-requirements.xml: <section id="vxlan-build-iproute2"> vxlan/en-US/plugin-vxlan-introduction.xml:<section id="Introduction-to-the-VXLAN-Plugin"> vxlan/en-US/plugin-vxlan-introduction.xml: <title>Introduction to the VXLAN Plugin</title> vxlan/en-US/plugin-vxlan-introduction.xml: <para>The VXLAN plugin adds VXLAN as one of the guest network isolation methods in &PRODUCT;.</para> vxlan/en-US/plugin-vxlan-features.xml:<section id="Features-of-the-VXLAN-Plugin"> vxlan/en-US/plugin-vxlan-features.xml: <title>Features of the VXLAN Plugin</title> vxlan/en-US/plugin-vxlan-features.xml: By the nature of VXLAN's MAC-in-IP encapsulation, the MAC addresses of VMs are encapsulated and concealed in the MAC addresses of Hypervisors. vxlan/en-US/plugin-vxlan-revision-history.xml:<appendix id="plugin-vxlan-revision-history"> vxlan/en-US/plugin-vxlan-about.xml:<chapter id="About-the-VXLAN-Plugin" > vxlan/en-US/plugin-vxlan-about.xml: <title>The VXLAN Plugin</title> vxlan/en-US/plugin-vxlan-about.xml: <xi:include href="plugin-vxlan-introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude";></xi:include> vxlan/en-US/plugin-vxlan-about.xml: <xi:include href="plugin-vxlan-features.xml" xmlns:xi="http://www.w3.org/2001/XInclude";></xi:include> vxlan/publican.cfg:docname: CloudStack_VXLAN_Guide On Sun, Jan 19, 2014 at 6:51 AM, Nux! <n...@li.nux.ro> wrote: > Hi, > > I'm currently trying to play with VXLAN on 4.3.0 SNAPSHOT. I am however > encountering some issues: > https://issues.apache.org/jira/browse/CLOUDSTACK-5908 > > Besides this, I did not find any documentation for this feature at all. What > are the requirements of getting this to work? > Clearly we need VXLAN support in kernel, but other than this? I see OVS is > not required, but I'm mostly stabbing in the dark here. > > Help :) > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro
