Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Murali.Reddy@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Murali Reddy <Murali.Reddy@citrix.com>
To: Kanzhe Jiang <kanzhe.jiang@bigswitch.com>
CC: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Thu, 31 Jan 2013 11:41:21 +0530
Subject: Re: Review Request: BigSwitch VNS Networking Plugin
Thread-Topic: Review Request: BigSwitch VNS Networking Plugin
Thread-Index: Ac3/eci70bJl0IUXQAiZdYnwEHZiKQ==
Message-ID: <CD300752.2F1EA%murali.reddy@citrix.com>
In-Reply-To: 
 <CA+TbKApDHhqXge8s8BvOhLOShFDzmcMQX=iQ-5jqRoZF77n-SA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.5.121010
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_CD3007522F1EAmuralireddycitrixcom_"
MIME-Version: 1.0

--_000_CD3007522F1EAmuralireddycitrixcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Kanzhe,

Thanks for the detailed explantation. I get the end-to-end flow now. If I u=
nderstand correctly, every flow across the VM's in same virtual network,  a=
t initiation, still needs to go through the controller right?

How do you expect 'shared network' be treated. Do you expect admin to setup=
 the necessary flow information through controller for shared networks?

Regards,
Murali

From: Kanzhe Jiang <kanzhe.jiang@bigswitch.com<mailto:kanzhe.jiang@bigswitc=
h.com>>
Date: Thursday, 31 January 2013 1:28 AM
To: Murali Reddy <murali.reddy@citrix.com<mailto:murali.reddy@citrix.com>>
Cc: "cloudstack-dev@incubator.apache.org<mailto:cloudstack-dev@incubator.ap=
ache.org>" <cloudstack-dev@incubator.apache.org<mailto:cloudstack-dev@incub=
ator.apache.org>>
Subject: Re: Review Request: BigSwitch VNS Networking Plugin

Hi Murali,

When creating network, the plugin will capture the networkUUID, tenantID, v=
lan and send a request to the controller to create a virtual network.
Controller will create an addressSpace construct to match the vlan so that =
all device in the addressSpace has unique mac and ip, then create a virtual=
 network. The membership of the virtualNetwork is based on a tag rule. A ta=
g rule is that any device with the tag will be classified to the virtual ne=
twork.

When a VM is created, BigSwitchVnsElement.java will send a request to the c=
ontroller to create a port and attachment for the VM. The port contains the=
 networkuuid. The attachment contains the VM's mac address. The controller =
then associates the VM with its network tag.

At this point, nothing is happening to the switches yet.

When VM sends packets, the VM's network association is determined based on =
its first packet. If the destination is in the same virtual network, the co=
ntroller will permit the flow and set up a end-to-end flow. When setting up=
 the flow, vlan is programmed on the switches along the route. The switches=
 can be virtual or OF-enabled physical switches.

Then the network is destroyed, the plugin notifies the controller, which th=
en removes the tag and virtual network.

Hope the explanation clarifies the workflow.
Let me know if you have more question.

Thanks,
Kanzhe

--_000_CD3007522F1EAmuralireddycitrixcom_--