Return-Path: 
 <dev-return-32267-apmail-cloudstack-dev-archive=cloudstack.apache.org@cloudstack.apache.org>
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 8E96EF2A9
	for <apmail-cloudstack-dev-archive@www.apache.org>;
 Thu,  2 May 2013 18:19:11 +0000 (UTC)
Received: (qmail 80458 invoked by uid 500); 2 May 2013 18:19:11 -0000
Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org
Received: (qmail 80275 invoked by uid 500); 2 May 2013 18:19:11 -0000
Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:dev@cloudstack.apache.org>
List-Id: <dev.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list dev@cloudstack.apache.org
Received: (qmail 80267 invoked by uid 99); 2 May 2013 18:19:11 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 18:19:11 +0000
X-ASF-Spam-Status: No, hits=2.6 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,TRACKER_ID
X-Spam-Check-By: apache.org
Received-SPF: error (nike.apache.org: local policy)
Received: from [209.85.220.179] (HELO mail-vc0-f179.google.com)
 (209.85.220.179)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 18:19:04 +0000
Received: by mail-vc0-f179.google.com with SMTP id hz10so780751vcb.10
        for <dev@cloudstack.apache.org>; Thu, 02 May 2013 11:18:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:x-received:x-originating-ip:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type:x-gm-message-state;
        bh=BSCx293kEwJk2zZEBcdy8oV6qbpvBavSZOZfkpscI1w=;
        b=OvAHrxhQAEBWCArlm46c6qrGi75szcUsPzCtSXswA7YLMlOh69+p45Kw8gszR0gSh4
         dbh7iRZTRYDNmqBx19uTLEIKtCmgWY8MJUWSf10gbeh/vTULA0Sntd7kLhNzkAxjq/Ur
         Hebt6V4hjHVfZT1Mr7aV0jKrM8Up/+OnsglAVNGNLBETGoTnKvl1ZkNyMe2CfNKbyCJ1
         GY1sF2526Z5QsNlt7JF1HbhgeaZX9xfMzZ2JdIrIAe4Dq3+0HJDI4rIt1Ih8q/QPJjIL
         TY2hzDqLRupa455CBD8DdDMQ0UydN+4gIaPQkHH+kqieFfk9rle4P1UhN/4t9HaL/KcU
         4/4A==
MIME-Version: 1.0
X-Received: by 10.52.237.137 with SMTP id vc9mr2220004vdc.102.1367518703213;
 Thu, 02 May 2013 11:18:23 -0700 (PDT)
Received: by 10.58.237.234 with HTTP; Thu, 2 May 2013 11:18:23 -0700 (PDT)
X-Originating-IP: [63.110.51.11]
In-Reply-To: 
 <CA+2rt43iZtySO8ocBqv-UsoLgGtDtT4AtTc1i5DiHv1y+poQjQ@mail.gmail.com>
References: 
 <CA+2rt40M_0-RHnJU5nwpTrLr3_h+GcHpiV8bYY-k2+BN_VAhcw@mail.gmail.com>
	<6DE00C9FDF08A34683DF71786C70EBF02F93BA27@SBPOMB402.sbp.lan>
	<CA+2rt43iZtySO8ocBqv-UsoLgGtDtT4AtTc1i5DiHv1y+poQjQ@mail.gmail.com>
Date: Thu, 2 May 2013 11:18:23 -0700
Message-ID: 
 <CA+2rt41TgOM1mk6UM1qH5XGnCwjG6sB=_EDV9P_=SX7T38fRWQ@mail.gmail.com>
Subject: Re: OVS on KVM
From: Sheng Yang <sheng@yasker.org>
To: Hugo Trippaers <HTrippaers@schubergphilis.com>
Cc: "<dev@cloudstack.apache.org>" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=089e01176751876fda04dbc0429c
X-Gm-Message-State: 
 ALoCoQlEEH21ZTy9XUF3ukoUTyIMlFIt1BqqUyd3UyUMPUZVdHFez2ah+1Vzwm02qgKfRCT7Ys8i
X-Virus-Checked: Checked by ClamAV on apache.org

--089e01176751876fda04dbc0429c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

After searching I found this:

http://libvirt.org/formatnetwork.html

<quote>
Setting VLAN tag (on supported network types only)
  ...
  <devices>
    <interface type=3D'bridge'>
      <vlan trunk=3D'yes'>
        <tag id=3D'42'/>
        <tag id=3D'47'/>
      </vlan>
      <source bridge=3D'ovsbr0'/>
      <virtualport type=3D'openvswitch'>
        <parameters interfaceid=3D'09b11c53-8b5c-4eeb-8f00-d84eaa0aaa4f'/>
      </virtualport>
    </interface>
  <devices>
  ...
If (and only if) the network type supports vlan tagging transparent to the
guest, an optional <vlan> element can specify one or more vlan tags to
apply to the traffic of all guests using this network **Since 0.10.0**.
(openvswitch and type=3D'hostdev' SR-IOV networks do support transparent vl=
an
tagging of guest traffic; everything else, including standard linux bridges
and libvirt's own virtual networks, do not support it. 802.1Qbh (vn-link)
and 802.1Qbg (VEPA) switches provide their own way (outside of libvirt) to
tag guest traffic onto specific vlans.) As expected, the tag attribute
specifies which vlan tag to use. If a network has more than one <vlan>
element defined, it is assumed that the user wants to do VLAN trunking
using all the specified tags. In the case that vlan trunking with a single
tag is desired, the optional attribute trunk=3D'yes' can be added to the vl=
an
element.
</quote>

I am using 0.9.13(with ubuntu 12.10). Does that means we need newer version=
?

--Sheng



On Thu, May 2, 2013 at 10:55 AM, Sheng Yang <sheng@yasker.org> wrote:

> I DO SEE the tag on VM profile when agent start, but I didn't see them on
> OVS ports.
>
> 2013-05-01 18:04:44,702{GMT} DEBUG [kvm.resource.LibvirtComputingResource=
]
> (agentRequest-Handler-5:) starting v-2-VM: <domain type=3D'kvm'>
> <name>v-2-VM</name>
> <uuid>1422832d-be18-352a-a08a-9bbff40e0d14</uuid>
> <description>Debian GNU/Linux 5.0 (32-bit)</description>
> <clock offset=3D'utc'>
> </clock>
> <features>
> <pae/>
> <apic/>
> <acpi/>
> </features>
> <devices>
> <emulator>/usr/bin/kvm</emulator>
> <interface type=3D'bridge'>
> <source bridge=3D'cloud0'/>
> <mac address=3D'0e:00:a9:fe:02:45'/>
> <model type=3D'virtio'/>
> <virtualport type=3D'openvswitch'>
> </virtualport>
> </interface>
> <interface type=3D'bridge'>
> <source bridge=3D'cloudbr0'/>
> <mac address=3D'06:f7:5c:00:00:06'/>
> <model type=3D'virtio'/>
> <virtualport type=3D'openvswitch'>
> </virtualport>
> </interface>
> <interface type=3D'bridge'>
> <source bridge=3D'cloudbr0'/>
> <mac address=3D'06:4c:12:00:00:1a'/>
> <model type=3D'virtio'/>
> <virtualport type=3D'openvswitch'>
> </virtualport>
> <vlan trunk=3D'no'>
> <tag id=3D'1610'/>                            <----------- here
> </vlan></interface>
> <serial type=3D'pty'>
> <target port=3D'0'/>
> </serial>
> <graphics type=3D'vnc' autoport=3D'yes' listen=3D'' />
> <disk  device=3D'disk' type=3D'file'>
> <driver name=3D'qemu' type=3D'qcow2' cache=3D'none' />
> <source
> file=3D'/mnt/20ad978d-a581-3a08-95fd-c2a45417513c/2f12ce26-4e4b-4d6e-b77e=
-1c45afff58e9'/>
> <target dev=3D'vda' bus=3D'virtio'/>
> </disk>
> <disk  device=3D'cdrom' type=3D'file'>
> <driver name=3D'qemu' type=3D'raw' cache=3D'none' />
> <source file=3D'/usr/share/cloudstack-common/vms/systemvm.iso'/>
> <target dev=3D'hdc' bus=3D'ide'/>
> </disk>
> <console type=3D'pty'>
> <target port=3D'0'/>
> </console>
> <input type=3D'tablet' bus=3D'usb'/>
> <channel type=3D'unix'>
> <source mode=3D'bind' path=3D'/var/lib/libvirt/qemu/v-2-VM.agent'/>
> <target type=3D'virtio' name=3D'v-2-VM.vport'/>
> <address type=3D'virtio-serial'/>
> </channel>
> </devices>
> <memory>1048576</memory>
> <vcpu>1</vcpu>
> <os>
> <type  arch=3D'x86_64' machine=3D'pc'>hvm</type>
> <boot dev=3D'cdrom'/>
> <boot dev=3D'hd'/>
> </os>
> <cputune>
> <shares>500</shares>
> </cputune>
> <on_reboot>restart</on_reboot>
> <on_poweroff>destroy</on_poweroff>
> <on_crash>destroy</on_crash>
> </domain>
>
> After this, vnet2 should be tagged with 1610, but:
>
> root@yasker-box1:~# ovs-vsctl list port vnet2
> _uuid               : 012a6140-bd87-4917-84cc-7190829c695a
> bond_downdelay      : 0
> bond_fake_iface     : false
> bond_mode           : []
> bond_updelay        : 0
> external_ids        : {}
> fake_bridge         : false
> interfaces          : [95bcf67b-12c1-44e5-87da-5663c6644da3]
> lacp                : []
> mac                 : []
> name                : "vnet2"
> other_config        : {}
> qos                 : []
> statistics          : {}
> status              : {}
> tag                 : []
> trunks              : []
> vlan_mode           : []
>
> So it cannot access the public network.
>
> After:
>
> root@yasker-box1:~# ovs-vsctl set port vnet2 tag=3D1610
> root@yasker-box1:~# ovs-vsctl list port vnet2
> _uuid               : 012a6140-bd87-4917-84cc-7190829c695a
> bond_downdelay      : 0
> bond_fake_iface     : false
> bond_mode           : []
> bond_updelay        : 0
> external_ids        : {}
> fake_bridge         : false
> interfaces          : [95bcf67b-12c1-44e5-87da-5663c6644da3]
> lacp                : []
> mac                 : []
> name                : "vnet2"
> other_config        : {}
> qos                 : []
> statistics          : {}
> status              : {}
> tag                 : 1610
> trunks              : []
> vlan_mode           : []
>
> It can access the public network with vlan 1610.
>
> --Sheng
>
>
>
> On Thu, May 2, 2013 at 4:34 AM, Hugo Trippaers <
> HTrippaers@schubergphilis.com> wrote:
>
>>  Hey Sheng,****
>>
>> ** **
>>
>> The tagging is done by libvirt. Can you check your agent.log?****
>>
>> ** **
>>
>> I would have expected an entry in the log file looking like this
>> =91s_logger.debug("creating a vlan dev and bridge for public traffic per
>> traffic label " + trafficLabel);=92****
>>
>> ** **
>>
>> Also the XML document for the vif sent to libvirt should have the
>> following tag =91<vlan trunk=3D'no'>\n<tag id=3D'" + _vlanTag + "'/>\n</=
vlan>"=92
>> ****
>>
>> ** **
>>
>> What are your traffic labels set to for kvm? Could you share your
>> agent.properties?****
>>
>> ** **
>>
>> Cheers,****
>>
>> ** **
>>
>> Hugo****
>>
>> ** **
>>
>> *From:* Sheng Yang [mailto:sheng@yasker.org]
>> *Sent:* Thursday, May 02, 2013 3:17 AM
>> *To:* Hugo Trippaers; <dev@cloudstack.apache.org>
>> *Subject:* OVS on KVM****
>>
>> ** **
>>
>> Hi Hugo,****
>>
>> ** **
>>
>> I am trying to use OVS on KVM now, but I found all public ports are not
>> tagged with public vlan as it supposed to be, so any public traffic cann=
ot
>> goes out. I've verified that I am using OvsVifDriver. ****
>>
>> ** **
>>
>> Here is the output of ovs-vsctl show:****
>>
>> ** **
>>
>> <quote>****
>>
>> root@yasker-box1:~/kvm-agent# ovs-vsctl show****
>>
>> 02281b72-131c-4b24-b191-fb1bb7fe186d****
>>
>>     Bridge "cloud0"****
>>
>>         Port "cloud0"****
>>
>>             Interface "cloud0"****
>>
>>                 type: internal****
>>
>>         Port "vnet3"****
>>
>>             Interface "vnet3"****
>>
>>         Port "vnet0"****
>>
>>             Interface "vnet0"****
>>
>>     Bridge "cloudbr0"****
>>
>>         Port "vnet2"****
>>
>>             Interface "vnet2"****
>>
>>         Port "vnet6"****
>>
>>             Interface "vnet6"****
>>
>>         Port "vnet4"****
>>
>>             Interface "vnet4"****
>>
>>         Port "vnet9"****
>>
>>             Interface "vnet9"****
>>
>>         Port "vnet10"****
>>
>>             Interface "vnet10"****
>>
>>         Port "vnet1"****
>>
>>             Interface "vnet1"****
>>
>>         Port "cloudbr0"****
>>
>>             Interface "cloudbr0"****
>>
>>                 type: internal****
>>
>>         Port "eth0"****
>>
>>             Interface "eth0"****
>>
>>         Port "vnet5"****
>>
>>             Interface "vnet5"****
>>
>>     ovs_version: "1.4.3"****
>>
>> </quote>****
>>
>> ** **
>>
>> I've checked the Installation guide, it use different bridge for
>> different vlan. But would that be the only way to work? Because we can h=
ave
>> different public vlans. Maybe I got some setup wrong...****
>>
>> ** **
>>
>> Any comments?****
>>
>> ** **
>>
>> Thanks!****
>>
>> ** **
>>
>> --Sheng****
>>
>
>

--089e01176751876fda04dbc0429c--