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 1C6D7E40B for ; Wed, 9 Jan 2013 17:47:50 +0000 (UTC) Received: (qmail 32519 invoked by uid 500); 9 Jan 2013 17:47:49 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 32463 invoked by uid 500); 9 Jan 2013 17:47:49 -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 32453 invoked by uid 99); 9 Jan 2013 17:47:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 17:47:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kanzhe.jiang@bigswitch.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-la0-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 17:47:42 +0000 Received: by mail-la0-f47.google.com with SMTP id fh20so2140268lab.20 for ; Wed, 09 Jan 2013 09:47:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=u8pjXtlrmcSh/FBL11DZ03UHSKRT1n2gaJmaVLV1hks=; b=mHdXcIx8YohKWDPeEG31lbCpg1kWa1HGOay9GEZm7Z6WQ64lF8VDWffojXB7zczAQu 0/clFZHiojcnCNqRjKawIduD2bdeMLaayecrvqnw6e+zXC3QVm9urJXNSK8bJ3WYuBuQ yA4bNkafr+VYMCnYR/8kWX3nGzl/bfaNQIzgupc7ayGGpCAaGBrIISQvtsJP02nhcm52 4peQsFS3Y17FHVPifGHLeONknN9hkoSqdtFIlNNn1k9eb2nWDTaHIndSqxwJh2MHbgL6 DrvNTcgs2KZ3yb6bATWB9eoinLEa/y59Brr1385i5WxTsf75Kr4PIr2UWzcWAoLXEZtG Zu4Q== MIME-Version: 1.0 Received: by 10.152.109.146 with SMTP id hs18mr57506585lab.8.1357753642315; Wed, 09 Jan 2013 09:47:22 -0800 (PST) Received: by 10.112.136.194 with HTTP; Wed, 9 Jan 2013 09:47:22 -0800 (PST) In-Reply-To: References: Date: Wed, 9 Jan 2013 09:47:22 -0800 Message-ID: Subject: Re: [PROPOSAL] A networking plugin to integration with BigSwitch network controller platform From: Kanzhe Jiang To: cloudstack-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=bcaec54ee7768aefb104d2dea77b X-Gm-Message-State: ALoCoQm6vnj7PRFaE2ku9ufF0Cu84ZZrbA0m6E31XQQ08nL7AwFfS65yMAMz6MK1LZkUsqvkHbHY X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54ee7768aefb104d2dea77b Content-Type: text/plain; charset=ISO-8859-1 Hi Sebastien, It definitely makes sense to enable Elastic IP and implement Security groups with OpenFlow. It is one of the to-do items we would like to contribute to cloudstack after finishing the basic network isolation. I am new to CloudStack and don't know much about the agent simulator. I would love to discuss it with you once I get to know more about CloudStack. Thanks, Kanzhe On Mon, Jan 7, 2013 at 1:37 AM, Sebastien Goasguen wrote: > Dear Kanzhe, > > Two thought: > > -Would it make sense to also use BVS for CloudStack Basic networking, and > use it to enable Elastic IP and Security Groups in basic zone via open flow > ? > -CloudStack has an agent simulator (which unfortunately I don't know much > about :( )), it would be great to envision a full data center simulation > that would use mininet and the agent simulator. Do you have any thoughts on > how we could use mininet to do CloudStack simulations ? > > Regards, > > -Sebastien > > On Jan 5, 2013, at 8:25 AM, Kanzhe Jiang > wrote: > > > Here is the first draft of the design spec for BigSwitch Networking > > Plugin< > https://cwiki.apache.org/confluence/display/CLOUDSTACK/BigSwitch+Networking+Plugin > > > > . > > > > Thanks, > > Kanzhe > > > > On Thu, Jan 3, 2013 at 12:18 PM, Chip Childers < > chip.childers@sungard.com>wrote: > > > >> On Thu, Jan 3, 2013 at 3:16 PM, Kanzhe Jiang < > kanzhe.jiang@bigswitch.com> > >> wrote: > >>> On Thu, Jan 3, 2013 at 10:53 AM, Chip Childers < > >> chip.childers@sungard.com>wrote: > >>> > >>>> On Thu, Jan 3, 2013 at 1:44 PM, Kanzhe Jiang < > >> kanzhe.jiang@bigswitch.com> > >>>> wrote: > >>>>> Hi Chip, > >>>>> > >>>>> Yes, I will put together a design spec together soon for review. > >>>>> I was informed that the code freeze date for the current release is > >> end > >>>> of > >>>>> January, 2013. > >>>>> My plan is to submit the plugin some time before the deadline for > >> review > >>>> so > >>>>> the plugin would be available in the coming release. > >>>>> > >>>>> Thanks, > >>>>> Kanzhe > >>>>> > >>>> > >>>> OK, thanks for the clarity! > >>>> > >>>> Given your stated goal, I'm going to ask you for a couple of things: > >>>> > >>>> The design doc needs to be a child of this page: > >>>> > >> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.1+Design+Documents > >>> > >>> > >>> I am working on the design spec and will have it available in a day or > >> two. > >>> > >> > >> Fantastic. Please ask for help on this list if you need any advice > >> from the rest of the community! > >> > >>> > >>>> > >>>> > >>>> If you can create yourself an account within issues.a.o, and let me > >>>> know when you are done, I'll add you as a project contributor. This > >>>> will allow us to assign the new feature issue (and any bugs that we > >>>> might find) to you as the process moves forward. > >>>> > >>>> > >>> I have created a Jira account. Username kjiang. > >>> I have also created a "New Feature" item, > >>> CLOUDSTACK-733, > >>> to track the proposal. > >>> > >> > >> I added your account as a contributor for the project, and have > >> assigned 733 to you. Thanks for jumping over the administrivia > >> hurdles a bit for us! > >> > >>> > >>>> Once you have the jira account, please create a "New Feature" item to > >>>> track progress within the CLOUDSTACK project here: > >>>> https://issues.apache.org/jira/browse/CLOUDSTACK > >>>> > >>>> We'll also want to discuss testing the new feature. It's going to > >>>> obviously require access to the BVS application. Are there any > >>>> resources that you will be able to share on that front? > >>>> > >>>> Floodlight would be sufficient to test the new feature. The plugin > >>> supports both the commercial and opensource controller. > >>> > >>> > >>>> Thanks! > >>>> > >>>>> On Thu, Jan 3, 2013 at 6:48 AM, Chip Childers < > >> chip.childers@sungard.com > >>>>> wrote: > >>>>> > >>>>>> On Thu, Jan 3, 2013 at 1:20 AM, Kanzhe Jiang < > >>>> kanzhe.jiang@bigswitch.com> > >>>>>> wrote: > >>>>>>> Hi All, > >>>>>>> > >>>>>>> Happy New Year to Everyone! > >>>>>>> First of all, I am new to the community and very excited to have > >> the > >>>>>>> opportunity to work on the project. > >>>>>>> > >>>>>>> I would like to propose a networking plugin that will support > >>>>>>> openflow-based cloud networking solutions through BigSwitch's BVS > >> (Big > >>>>>>> Virtual Switch) application. > >>>>>>> > >>>>>>> BVS is one of the SDN applications available for the BigSwitch > >> network > >>>>>>> controller. BVS application provides network virtualization, > >> manages > >>>>>>> isolated and virtual networks on top of the underlying physical and > >>>>>> virtual > >>>>>>> switch infrastructure. These virtual networks correspond directly > >> to > >>>> the > >>>>>>> groups of VMs, servers, and other devices that need their own > >> secure > >>>>>>> connectivity. The virtual networks are programmed into the physical > >>>>>> and/or > >>>>>>> virtual switches without having to separately configure individual > >>>>>> network > >>>>>>> devices. > >>>>>>> > >>>>>>> The proposed CloudStack networking plugin will bring the > >>>> OpenFlow-based > >>>>>>> standard network virtualization technology to CloudStack. > >>>>>>> > >>>>>>> There won't be any change to the existing CloudStack workflow. In a > >>>>>> typical > >>>>>>> deployment, all OpenFlow-enabled physical and virtual switches and > >>>> other > >>>>>>> network resources are configured to be managed by the BigSwitch > >>>>>>> controller(s). When a guest network is created, the plugin will > >>>> create a > >>>>>>> corresponding virtual network in the BVS When a guest VM is > >> launched, > >>>>>> the > >>>>>>> VM is automatically assigned to its configured guest network(s). > >>>>>>> The BVS application will provide network isolation and > >> connectivities > >>>>>> among > >>>>>>> VMs. > >>>>>>> > >>>>>>> More detailed product description is available on the > >>>>>>> website > >>>>>>> . > >>>>>>> > >>>>>>> Please let me know if you need more information. > >>>>>>> > >>>>>>> Sincerely, > >>>>>>> > >>>>>>> -- > >>>>>>> Kanzhe Jiang > >>>>>>> MTS at BigSwitch > >>>>>> > >>>>>> This looks like a great addition. Do you have a feel for the timing > >>>>>> that you think it will require to get it done? > >>>>>> > >>>>>> If you can start the process of creating your design document under > >>>>>> the "Design Documents Not Committed to a Release" page ( > >>>>>> > >>>>>> > >>>> > >> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Design+Documents+Not+Committed+to+a+Release > >>>>>> ), we can help work through any design issues and help get a plan in > >>>>>> place to include it in the appropriate feature release. > >>>>>> > >>>>>> -chip > >>>>>> > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> Kanzhe Jiang > >>>>> MTS at BigSwitch > >>>> > >>> > >>> > >>> > >>> -- > >>> Kanzhe Jiang > >>> MTS at BigSwitch > >> > > > > > > > > -- > > Kanzhe Jiang > > MTS at BigSwitch > > -- Kanzhe Jiang MTS at BigSwitch --bcaec54ee7768aefb104d2dea77b--