Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5B34E470 for ; Mon, 17 Dec 2012 19:41:45 +0000 (UTC) Received: (qmail 86116 invoked by uid 500); 17 Dec 2012 19:41:45 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 85879 invoked by uid 500); 17 Dec 2012 19:41:44 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 85607 invoked by uid 99); 17 Dec 2012 19:41:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 19:41:33 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sateesh.chodapuneedi@citrix.com designates 203.166.19.134 as permitted sender) Received: from [203.166.19.134] (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2012 19:41:24 +0000 X-IronPort-AV: E=Sophos;i="4.84,304,1355097600"; d="scan'208,217";a="111037" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 17 Dec 2012 19:41:02 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.72]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Tue, 18 Dec 2012 01:10:59 +0530 From: Sateesh Chodapuneedi To: "cloudstack-dev@incubator.apache.org" Date: Tue, 18 Dec 2012 01:10:55 +0530 Subject: [ASF41][DISCUSS] Adding support for VMware dvSwitch Thread-Topic: [ASF41][DISCUSS] Adding support for VMware dvSwitch Thread-Index: Ac3cjT8GtWSPi/rST/mnG9pSqq1vzA== Message-ID: <35F04D4C394874409D9BE4BF45AC5EA9010B2807B39F@BANPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_35F04D4C394874409D9BE4BF45AC5EA9010B2807B39FBANPMAILBOX_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_35F04D4C394874409D9BE4BF45AC5EA9010B2807B39FBANPMAILBOX_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am planning to work on enabling support for VMware native dvSwitch in Clo= udStack. Filed a jira ticket for it, see [1]. Integration of VMware dvSwitch with CloudStack enables orchestration of vir= tual networks in VMware environment over distributed virtual switch inside = vCenter. Background ----------- VMware Distributed Switch is an aggregation of per-host virtual switches pr= esented and controlled as a single distributed switch through vCenter Serve= r at the Datacenter level. vDS abstracts configuration of individual virtua= l switches and enables centralized provisioning, administration, and monito= ring. vDS is integral component of vCenter. Hence the native vDS support makes se= nse for wider and larger deployments of Cloudstack over vSphere. Each Standard vSwitch represents an independent point of configuration that= needs to be managed and monitored. The management of virtual networks requ= ired by instances in the cloud is tedious when virtual networks have to spa= n across large number of hosts. Using distributed vSwitch (vDS) simplifies = the configuration and monitoring. Being standalone implementations, standard vSwitches do not provide any sup= port for virtual machine mobility. So there needed a component to ensure t= hat the network configurations on the source and the destination virtual sw= itch are consistent and will allow the VM to operate without breaking conne= ctivity or network policies. Particularly during migration of VM across hos= ts, the sync up among peers need to be taken care. However in case of dist= ributed vSwitch during VMotion, the vCenter server, would update the vSwitc= h modules on the hosts in cluster accordingly. I'll share an FS for this in the next few days. Please do let me know your thoughts/concerns. [1] CLOUDSTACK-657 - "VMware vNetwork Distributed Virtual Switch support in= CloudStack" Regards, Sateesh --_000_35F04D4C394874409D9BE4BF45AC5EA9010B2807B39FBANPMAILBOX_--