Re: [dc] draft-khasnabish-vmmi-problems-00.txt
Vishwas Manral <vishwas.ietf@gmail.com> Fri, 20 January 2012 14:31 UTC
Return-Path: <vishwas.ietf@gmail.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE89921F859F for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 06:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hUM9fcEkMJ3x for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 06:31:10 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E484721F8596 for <dc@ietf.org>; Fri, 20 Jan 2012 06:31:09 -0800 (PST)
Received: by obbwc12 with SMTP id wc12so947570obb.31 for <dc@ietf.org>; Fri, 20 Jan 2012 06:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z1kDO7NjTPtvQn8XFc+o+4DtKpTYWY+XlyYcOi2wvLI=; b=w0XhX6BboGjwrg681zyRpsJsaz/toRehGcaIg7YotD/2pbdOHFImhRlYzDG/bNs7IJ Rv1OO8NNTAdtynnvmTcRh0FkaIIYckfihTJvZM4tka1LCZAdgwX5X1/GCGstEvwowcer q5R+hiLCAwM15vBJK2hNcU9/6WMTcLsNg+PSM=
MIME-Version: 1.0
Received: by 10.182.212.105 with SMTP id nj9mr26799434obc.62.1327069868526; Fri, 20 Jan 2012 06:31:08 -0800 (PST)
Received: by 10.182.28.196 with HTTP; Fri, 20 Jan 2012 06:31:08 -0800 (PST)
In-Reply-To: <OF4387C31B.7EB661BF-ON4825798B.002973A7-4825798B.002C35F9@zte.com.cn>
References: <OF4387C31B.7EB661BF-ON4825798B.002973A7-4825798B.002C35F9@zte.com.cn>
Date: Fri, 20 Jan 2012 06:31:08 -0800
Message-ID: <CAOyVPHTVFT4+r9B1e66u=M5cYiKFZWxn4k0yminqpFAr_DmQCQ@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Lizhong Jin <lizhong.jin@zte.com.cn>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: jmh@joelhalpern.com, adalela@cisco.com, dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 14:31:11 -0000
Hi Lizhong, For most networking technologies I know we interact with the neighbor routers/edge router, which inturn can propagate information through the remaining routers, if required. Thanks, Vishwas On 1/20/12, Lizhong Jin <lizhong.jin@zte.com.cn> wrote: > Hi Vishwas and all, > EVB like technologies currently only focus on the interaction between > hypervisor and ToR. The network control plane may not locate only on ToR. > What's more, the interaction is not happened between hypervisor and its > connected ToR, but maybe between hypervisor and ToR in other site. > > I agree, hypervisor and network based encapsulations are quite different. > But we could consider the design that ToR has same control plane as > hypervisor. Then communication between VM and physical server would have > same control plane. > > Regards > Lizhong > > > > -------------------------------------------------------------------------------- > > From: <vishwas.ietf at gmail.com> > To: "Joel M. Halpern" <jmh at joelhalpern.com>, "Ashish Dalela (adalela)" > <adalela at cisco.com> > Cc: dc at ietf.org > Date: Thu, 19 Jan 2012 22:20:13 -0800 > In-reply-to: <4F19040B.7000901 at joelhalpern.com> > List-id: IETF Data Center Mailing List <dc.ietf.org> > > -------------------------------------------------------------------------------- > Hi Ashish, > > If you look at technologies like EVB you will see the interaction between > the hypervisor and the network control plane. > > _Vishwas > > > > > -- Sent from my HP TouchPad > > -------------------------------------------------------------------------------- > On Jan 19, 2012 10:05 PM, Joel M. Halpern <jmh at joelhalpern.com> wrote: > Several of the proposal use mechanisms that are equally applicable. For > a general description of one class of such approaches, look at the dcop > draft Warren Kumari and I wrote. I am sure that there are other classes > as well. > > Yours, > Joel > > On 1/20/2012 12:52 AM, Ashish Dalela (adalela) wrote: >> Joel, >> >> Hypervisor control is in the hypervisor manager. Switch control is in >> the network control plane. These are parallel silos, that don't >> interact. >> >> Either the hypervisor manager defers control to the network control >> plane, or the switches defer control to the manager. Or, some new third >> entity emerges to control both, and both hypervisor and switch defer >> control to that entity. >> >> We can't have separate control models and expect this to work in the >> same way. >> >> Which of these (or other) models you think presents a reasonable >> approach to reconcile hypervisor control and network control? >> >> Thanks, Ashish >> >> -----Original Message----- >> From: Joel M. Halpern [mailto:jmh at joelhalpern.com] >> Sent: Friday, January 20, 2012 10:58 AM >> To: Ashish Dalela (adalela) >> Cc: dc at ietf.org >> Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt >> >> While one can construct strawman hypothesis in whcih there are reasons >> to have different tunnel control protocols depepnding upon end-point >> location, equally one can construct reasonably hypothesis in which the >> same protocol mechanisms work whether the end-point is at the VM, the >> Hypervisor, the ToR switch, or an aggregation switch. >> >> >> Yours, >> Joel >> >> On 1/20/2012 12:07 AM, Ashish Dalela (adalela) wrote: >>> >>> I would not arrive at the conclusion that hypervisor work should or >>> should not be done in IETF. That's a separate question. VXLAN and >> NVGRE >>> are hypervisor based approaches. But, they don't have control planes >>> (yet). My point is that finding a common map-encap scheme isn't that >>> hard. The harder part is how to make the hypervisor and network based >>> map-encap *control planes* work the same way. >>> >>> If they don't work the same way, then L2-in-L2, L2-in-L3, L3-in-L3 has >> a >>> network flavor and a hypervisor flavor. >>> >>> Thanks, Ashish >>> >>> >>> -----Original Message----- >>> From: Melinda Shore [mailto:melinda.shore at gmail.com] >>> Sent: Friday, January 20, 2012 10:06 AM >>> To: Ashish Dalela (adalela) >>> Cc: dc at ietf.org >>> Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt >>> >>> On 1/19/12 7:26 PM, Ashish Dalela (adalela) wrote: >>>> Bandwidth needs, but they have the >>>> same tunnel. How do I distinguish between them based on the tunnel? >> In >>>> fact, if the tenant isolation is in the hypervisor, then the >>> underlying >>>> network has no clue which tenant needs what policy. >>> >>> Well, that's not true. In the case of IPSec we've got SPIs, and >>> there are similar demultiplexing mechanisms in other technologies. >>> >>> But frankly I think that if you're going to distinguish between >>> tunnel endpoints in the hypervisor and tunnel endpoints in other >>> sorts of network devices I think you're going to be somewhat >>> hard-pressed to make the case for working on the former in >>> the IETF. >>> >>> Melinda >>> _______________________________________________ >>>
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Lizhong Jin
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Vishwas Manral
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt liu.bin21
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt liu.bin21
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt david.black
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Truman Boyes
- Re: [dc] draft-khasnabish-vmmi-problems-00.txt Richard.BoHan liu