IETF Logo Mail Archive

Re: [dc] draft-khasnabish-vmmi-problems-00.txt

Christopher LILJENSTOLPE <cdl@asgaard.org> Thu, 19 January 2012 01:00 UTC

Return-Path: <cdl@asgaard.org>
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 CBA6011E80D7 for <dc@ietfa.amsl.com>; Wed, 18 Jan 2012 17:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 72CJmHMZ6dHg for <dc@ietfa.amsl.com>; Wed, 18 Jan 2012 17:00:48 -0800 (PST)
Received: from asgaard.org (odin.asgaard.org [204.29.151.68]) by ietfa.amsl.com (Postfix) with ESMTP id D8C1011E80D1 for <dc@ietf.org>; Wed, 18 Jan 2012 17:00:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by asgaard.org (Postfix) with ESMTP id 5AEB2AE6168; Thu, 19 Jan 2012 01:00:48 +0000 (UTC)
X-Virus-Scanned: amavisd-new at asgaard.org
Received: from asgaard.org ([127.0.0.1]) by localhost (odin.asgaard.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qq8bQ9eWiTHJ; Thu, 19 Jan 2012 01:00:47 +0000 (UTC)
Received: from fenrir.bigswitch.com (74-93-4-129-sfba.hfc.comcastbusiness.net [74.93.4.129]) by asgaard.org (Postfix) with ESMTPSA id 53711AE615A; Thu, 19 Jan 2012 01:00:47 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/signed; boundary="Apple-Mail=_A059F4C4-DF02-46D5-A108-473D06831E15"; protocol="application/pgp-signature"; micalg="pgp-sha1"
From: Christopher LILJENSTOLPE <cdl@asgaard.org>
In-Reply-To: <CANtnpwjexDPazOXLYHHjn3+JDi-o49Bv5ptDExAZHAA8Ra2m-A@mail.gmail.com>
Date: Wed, 18 Jan 2012 17:00:44 -0800
Message-Id: <F6F7A4AA-E0FA-4EF5-8BAF-2941F7F89C93@asgaard.org>
References: <CAH==cJxfmae0u0bSF4cn_haLgY1T-vnw2102PApzYtj5Aty=GQ@mail.gmail.com> <CANtnpwhFJ746ooi9GUCxfBqsOXu14hDka0D9inhh5pPq3U_ZTA@mail.gmail.com> <201201171540.q0HFeNan008591@cichlid.raleigh.ibm.com> <CANtnpwjexDPazOXLYHHjn3+JDi-o49Bv5ptDExAZHAA8Ra2m-A@mail.gmail.com>
To: Bhumip Khasnabish <vumip1@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Thomas Narten <narten@us.ibm.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: Thu, 19 Jan 2012 01:00:49 -0000

Greetings Bhumip,

	
On 17Jan2012, at 22.33, Bhumip Khasnabish wrote:

> Tom,
> 
> Thanks.
> 
> Yes, seamless migration of VM and VNE can be problematic in both intra- and
> inter-data-center environments, especially in multi-hypervisor case.

Agreed, but it's more than just a network problem, is it not?  ESPECIALLY in a multi-hypervisor environment.  So, the big question is, are you interested in just addressing the network portion, or the larger problem (including containers, storage concurrency, etc)?  If the later, do we have the experience and remit to work on that space?  

	Chris

> 
> It may be very helpful to bring one or more of these
> proprietary VM migration approaches to IETF for consideration
> for standardization, if that is appropriate.
> Sure, we'll update the draft to articulate these requirements.
> 
> Best.
> 
> Bhumip
> 
> 
> On Tue, Jan 17, 2012 at 10:40 AM, Thomas Narten <narten@us.ibm.com> wrote:
> 
>> Bhumip,
>> 
>> I skimmed this document and am having trouble figuring out what it is
>> intended to do.
>> 
>> The draft name itself has "problem" in it, but there is no single (or
>> small set of) succinct problems listed. It's all very high level and
>> hand wavy. I need help making the connection to an IETF action that
>> could come out of this document.
>> 
>> For example, it talks about VM migration.
>> 
>> Is VM Migration a "problem" today? There are properietary approaches
>> that the market seems to like OK.
>> 
>> What is wrong with the current approaches? What is "broken" that needs
>> fixing? Why should the IETF get involved in this space? What value
>> would the IETF bring?
>> 
>> Do you want to be able to do VM migration from one vendor's hypervisor
>> to another vendor's?  If so, please just say so. Then we can see
>> whether others here think that is an area the IETF (or some other SDO)
>> should get involved in.
>> 
>> Thomas
>> 
>> 
> _______________________________________________
> dc mailing list
> dc@ietf.org
> https://www.ietf.org/mailman/listinfo/dc

--  
李柯睿
Check my PGP key here: https://www.asgaard.org/~cdl/cdl.asc
Current vCard here: https://www.asgaard.org/~cdl/cdl.vcf

v2.23.0 | Report a Bug | By Email