Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA15110013 for ; Sun, 19 Jan 2014 14:38:11 +0000 (UTC) Received: (qmail 48038 invoked by uid 500); 19 Jan 2014 14:38:10 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 48007 invoked by uid 500); 19 Jan 2014 14:38:10 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 47998 invoked by uid 99); 19 Jan 2014 14:38:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Jan 2014 14:38:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shadowsor@gmail.com designates 209.85.217.172 as permitted sender) Received: from [209.85.217.172] (HELO mail-lb0-f172.google.com) (209.85.217.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Jan 2014 14:38:03 +0000 Received: by mail-lb0-f172.google.com with SMTP id c11so4231296lbj.17 for ; Sun, 19 Jan 2014 06:37:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ez7XBQAazHvZi9Zg0JwKWV6V0gnoplaAqlqfdWhg5Fo=; b=g4P5bnCOrMBg3Du9v+hUbI0RqR+wAgJalpkJabZTg/oCn0qriboWWRklN21MRCWFed GfhiPipw9z7a1gLzDApAOoIt9qCGA+bbg/idw0sZpWFb4c30gIfbuaJ6s0gMYXrCa3fe j7epWK97zvZHZD+UQl/C1zWWL0TJaqI33pqdJytpnOljmVYkT1k7TxXqyzQDMDrMMhjQ y83Ih953UFsPAH0uc7/1mLz/3a7MNBP/SuCzFBvGpFhqm/VttIgztl3Dq6k12uw4/nGP jXy9rEojuf6LIEWxrhstU4uB0OFL2CF2c/QyXVoUYS4dfbzLNLV1aStSiPvZ8RdUuQVv 7l0Q== MIME-Version: 1.0 X-Received: by 10.112.53.201 with SMTP id d9mr8010943lbp.26.1390142263012; Sun, 19 Jan 2014 06:37:43 -0800 (PST) Received: by 10.114.18.143 with HTTP; Sun, 19 Jan 2014 06:37:42 -0800 (PST) In-Reply-To: References: Date: Sun, 19 Jan 2014 07:37:42 -0700 Message-ID: Subject: Re: VXLAN problems From: Marcus Sorensen To: "dev@cloudstack.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org 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: vxlan/en-US/CloudStack_VXLAN_Guide.xml: &PRODUCT; Plugin Guide for the VXLAN Plugin vxlan/en-US/CloudStack_VXLAN_Guide.xml: Plugin Guide for the VXLAN Plugin. vxlan/en-US/CloudStack_VXLAN_Guide.xml: vxlan/en-US/CloudStack_VXLAN_Guide.xml: vxlan/en-US/CloudStack_VXLAN_Guide.xml: vxlan/en-US/CloudStack_VXLAN_Guide.xml: vxlan/en-US/plugin-vxlan-configuration.xml: vxlan/en-US/plugin-vxlan-configuration.xml: Configure &PRODUCT; to use VXLAN Plugin vxlan/en-US/plugin-vxlan-configuration.xml: vxlan/en-US/plugin-vxlan-configuration.xml: vxlan/en-US/plugin-vxlan-config-management.xml:
vxlan/en-US/plugin-vxlan-config-management.xml: Setup zone using VXLAN 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:
vxlan/en-US/plugin-vxlan-config-management.xml: vxlan/en-US/plugin-vxlan-config-management.xml: vxlan-physicalnetowkr.png: physicalnetwork configuration for VXLAN 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: vxlan/en-US/plugin-vxlan-config-management.xml: vxlan-trafficlabel.png: traffic label configuration for VXLAN vxlan/en-US/plugin-vxlan-config-management.xml: See for details. vxlan/en-US/plugin-vxlan-config-hypervisor.xml:
vxlan/en-US/plugin-vxlan-config-hypervisor.xml:
vxlan/en-US/plugin-vxlan-config-hypervisor.xml:
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:
vxlan/en-US/plugin-vxlan-config-hypervisor.xml:
vxlan/en-US/plugin-vxlan-requirements.xml: vxlan/en-US/plugin-vxlan-requirements.xml: System Requirements for VXLAN vxlan/en-US/plugin-vxlan-requirements.xml:
vxlan/en-US/plugin-vxlan-requirements.xml: System Requirements for VXLAN vxlan/en-US/plugin-vxlan-requirements.xml: Hypervisor Requirement for VXLAN vxlan/en-US/plugin-vxlan-requirements.xml: version >= 3.7, VXLAN kernel module enabled vxlan/en-US/plugin-vxlan-requirements.xml: It is recommended to use kernel >=3.9, since Linux kernel categorizes the VXLAN driver as experimental <3.9. vxlan/en-US/plugin-vxlan-requirements.xml:
vxlan/en-US/plugin-vxlan-requirements.xml:
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:
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:
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:
vxlan/en-US/plugin-vxlan-introduction.xml:
vxlan/en-US/plugin-vxlan-introduction.xml: Introduction to the VXLAN Plugin vxlan/en-US/plugin-vxlan-introduction.xml: The VXLAN plugin adds VXLAN as one of the guest network isolation methods in &PRODUCT;. vxlan/en-US/plugin-vxlan-features.xml:
vxlan/en-US/plugin-vxlan-features.xml: Features of the VXLAN Plugin 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: vxlan/en-US/plugin-vxlan-about.xml: vxlan/en-US/plugin-vxlan-about.xml: The VXLAN Plugin vxlan/en-US/plugin-vxlan-about.xml: vxlan/en-US/plugin-vxlan-about.xml: vxlan/publican.cfg:docname: CloudStack_VXLAN_Guide On Sun, Jan 19, 2014 at 6:51 AM, Nux! 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