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

"Ashish Dalela (adalela)" <adalela@cisco.com> Fri, 20 January 2012 01:20 UTC

Return-Path: <adalela@cisco.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 4991521F85E7 for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 17:20:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level:
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599]
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 HmeJ4CK5Cq7V for <dc@ietfa.amsl.com>; Thu, 19 Jan 2012 17:20:26 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBC821F85E4 for <dc@ietf.org>; Thu, 19 Jan 2012 17:20:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=2278; q=dns/txt; s=iport; t=1327022426; x=1328232026; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=1vPpnep2hsJjOI+cfVcUaMkJKaGbbZYBTGxu4UcRICg=; b=ghHCTcpJZkoUWGCMFVJelE/vyn4aEtJkbYY7SbznHra9SnC3vyLqKjKc 8HXGyytZsK80u2V9EGmQt3pdrKh0zX07yaJ8bVvUKhbUy5K3puhYiN+eH k6NZfP1l/eN7SQ6eFESLABCOl/6FpMg1z32+jjm7BEnTRlcbdFuLE4SrP o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAIDAGE9Io8UY/2dsb2JhbABDrHuCA4FyAQEBAwEBAQEPAR0KNAsFBwQCAQgRBAEBCwYXAQYBJh8JCAEBBAEJAQgIFgSHWgiaTwGeOgSJNzYBBVABBAcBCwECAQEIAQEBAQJJCkqBaDkeFgEBAQKCR2MEiDmfMA
X-IronPort-AV: E=Sophos;i="4.71,539,1320624000"; d="scan'208";a="3789957"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 20 Jan 2012 01:20:24 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q0K1KOm3011509; Fri, 20 Jan 2012 01:20:24 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Jan 2012 06:50:24 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Jan 2012 06:50:22 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5102CB2304@XMB-BGL-416.cisco.com>
In-Reply-To: <201201191747.q0JHlS5J015128@cichlid.raleigh.ibm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dc] draft-khasnabish-vmmi-problems-00.txt
Thread-Index: AczW0qaLHjfaIrIARQ+n0SUnPfoMjQAPVYSw
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><201201191419.q0JEJTLF010649@cichlid.raleigh.ibm.com><1326989277.2513.4.camel@ecliptic.extremenetworks.com> <201201191747.q0JHlS5J015128@cichlid.raleigh.ibm.com>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: Thomas Narten <narten@us.ibm.com>, Steven Blake <sblake@extremenetworks.com>
X-OriginalArrivalTime: 20 Jan 2012 01:20:24.0613 (UTC) FILETIME=[AF864550:01CCD711]
Cc: 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 01:20:27 -0000

I think it is fair to say that there is a difference between mobility
and portability. Mobility is live migration, but portability is
specifying a VM's properties, delete in one location and create in
another. The new location can be another hypervisor. In many cases, you
don't need mobility, just portability. E.g. if you have a disaster
recovery situation, then you aren't going to get mobility anyway.

DMTF has specified a standard called OVF (Open Virtualization Format)
that addresses the "description" of the VM. This format is supported by
various hypervisor vendors. So, some level of VM migration
standardization has already happened (albeit portability and not
mobility). 

The questions are:

- Do we need a "control plane" to transfer VM state from point A to B -
the mobility problem?
- Do we need a "control plane" to transfer OVF specification from point
A to B - the portability problem?

The problem is relevant in the inter-datacenter, public-private, or
inter-cloud spaces, where there will be more than one hypervisor
controller by definition. Are we hitting the live migration issue today?
Maybe not. Is it conceivable that we will hit this issue? I think so.

However, the question has to be asked to the provider/operators and not
to the vendors.

Thanks, Ashish


-----Original Message-----
From: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] On Behalf Of
Thomas Narten
Sent: Thursday, January 19, 2012 11:17 PM
To: Steven Blake
Cc: dc@ietf.org
Subject: Re: [dc] draft-khasnabish-vmmi-problems-00.txt

Steven,

> Several system vendors (myself included) stood up in Taipei and said
> "one encapsulation, please".  If IETF can facilitate industry
> convergence on a small set of NVO3 encapsulations (preferably one),
that
> would be a big win for Ethernet switch vendors.

I agree completely.

But my questions were asking about the apparent lack of  interest from
operators/implementers/market players regarding Bhumip's draft and the
apparent desire to have some sort of standards work related to the
general VM migration problem.

Is there such interest?

Thomas

_______________________________________________
dc mailing list
dc@ietf.org
https://www.ietf.org/mailman/listinfo/dc