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

Melinda Shore <melinda.shore@gmail.com> Fri, 20 January 2012 23:30 UTC

Return-Path: <melinda.shore@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 C2C3821F8548 for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 15:30:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.322
X-Spam-Level:
X-Spam-Status: No, score=-3.322 tagged_above=-999 required=5 tests=[AWL=0.277, 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 D5VqxTrqYUpa for <dc@ietfa.amsl.com>; Fri, 20 Jan 2012 15:30:53 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0898021F852C for <dc@ietf.org>; Fri, 20 Jan 2012 15:30:52 -0800 (PST)
Received: by ggnq4 with SMTP id q4so31334ggn.31 for <dc@ietf.org>; Fri, 20 Jan 2012 15:30:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ZG2xxX4KWwpk1xRTLQxdFzX4XT+XMdwbTP1knfiqQzc=; b=K1t/K7wqfGftfSS2YLImhQzNtjYClx4CZMXV6zOtUA/V0mn+U9WecpIu01vFLrfXHS /OwLBnVKchBCPVHHQ1KvBSW5b2teIewTrK/jGrYfjyrtUCEj4TvvDFd+FA+y53jClhf3 B+1lJXacgMlSC4nuPmyDqgdWL8m/NKRQ/m+gQ=
Received: by 10.101.141.24 with SMTP id t24mr14614985ann.52.1327102252648; Fri, 20 Jan 2012 15:30:52 -0800 (PST)
Received: from [137.229.12.236] (drake.swits.alaska.edu. [137.229.12.236]) by mx.google.com with ESMTPS id g32sm11699531ann.19.2012.01.20.15.30.51 (version=SSLv3 cipher=OTHER); Fri, 20 Jan 2012 15:30:52 -0800 (PST)
Message-ID: <4F19F939.2020804@gmail.com>
Date: Fri, 20 Jan 2012 14:31:05 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
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> <618BE8B40039924EB9AED233D4A09C5102CB2291@XMB-BGL-416.cisco.com> <406B8B5D-E1E5-4DF4-8DE2-D7D2A699430A@asgaard.org> <4F18CE61.6030002@gmail.com> <618BE8B40039924EB9AED233D4A09C5102CB2330@XMB-BGL-416.cisco.com> <4F18EF4A.3060308@gmail.com> <618BE8B40039924EB9AED233D4A09C5102CB234C@XMB-BGL-416.cisco.com> <4F18FB72.2090900@joelhalpern.com> <618BE8B40039924EB9AED233D4A09C5102CB2380@XMB-BGL-416.cisco.com> <4F19034E.1070802@gmail.com> <CAOyVPHTbxB=QYC3Qw0ybL=5RN7VefSENV4iiBBOpXbCn58oi=Q@mail.gmail.com>
In-Reply-To: <CAOyVPHTbxB=QYC3Qw0ybL=5RN7VefSENV4iiBBOpXbCn58oi=Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 23:30:53 -0000

On 01/20/2012 02:18 PM, Vishwas Manral wrote:
> An interesting thing to note is that the more the functionality you
> put in the hypervisor, the more you stress the single point of failure
> in the virtualized system.

Well, there are a few ways to look at it.  For example,
the fewer components you've got the larger the mean time
between failures.  But aside from that it's been a
general rule of thumb that you want to minimize the
impact of failed components on non-failed components
(the fate sharing principle).

At any rate the hypervisor (at least the ones with which
I'm familiar) basically *are* network devices - they
function as a switch, or even a NAT.  If you're going to
suggest that they can't be used to terminate control plane
sessions I hope there's a more compelling reason for it
than what has been offered so far.

Melinda