Re: [clouds] Clouds and / vs. virtualization

Tim Bray <tbray@textuality.com> Mon, 22 February 2010 18:11 UTC

Return-Path: <timbray@gmail.com>
X-Original-To: clouds@core3.amsl.com
Delivered-To: clouds@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4BE83A7982 for <clouds@core3.amsl.com>; Mon, 22 Feb 2010 10:11:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6j961nCoe04H for <clouds@core3.amsl.com>; Mon, 22 Feb 2010 10:11:05 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id DA1373A79A3 for <clouds@ietf.org>; Mon, 22 Feb 2010 10:10:27 -0800 (PST)
Received: by gwb10 with SMTP id 10so617268gwb.31 for <clouds@ietf.org>; Mon, 22 Feb 2010 10:12:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=A7VON+K13kH2NgRg2PeDksoWAjuLpWWKOj/bkYSWaug=; b=uwEp3dE14nsAY8BvngxJ4e2Ji6UbFM21Ty88W8EtWOvsfiNHlhhsLLo2yKVLuW6PA7 RO7w4cMYCK2jZT2sI153MCAiePKVykATw+8O26JAEPgby7vcaKpd5a43ixMeCRUgAkqF DlEgmALWFNxXTZtcZ1E80/j87urCJG2UACpJQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=d/cJn23oZLfdi83soX5Vne+rvA36yLhC+BkJZQ0IWU1WJ+4c6yvPUcIOdCpkfBl8dW vH5aqsOvRMFB8xFrDG25CoHwDaWSAgeWtpjuT2IJoQG82jTMCi2CZd97JFoaZLLp1xZg sAuT8zfh7YtgHN89nwUUesi5lHfwjp7Dwakok=
MIME-Version: 1.0
Sender: timbray@gmail.com
Received: by 10.91.18.5 with SMTP id v5mr1757036agi.62.1266862340863; Mon, 22 Feb 2010 10:12:20 -0800 (PST)
In-Reply-To: <p06240849c7a8733308d2@10.20.30.158>
References: <p06240849c7a8733308d2@10.20.30.158>
Date: Mon, 22 Feb 2010 10:12:20 -0800
X-Google-Sender-Auth: 0ba6a3522bf59bea
Message-ID: <517bf111002221012q622903bcl46a4ea5833304521@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: clouds@ietf.org
Subject: Re: [clouds] Clouds and / vs. virtualization
X-BeenThere: clouds@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tbray@textuality.com
List-Id: Clouds pre-BOF discussion list <clouds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/clouds>, <mailto:clouds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clouds>
List-Post: <mailto:clouds@ietf.org>
List-Help: <mailto:clouds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clouds>, <mailto:clouds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2010 18:11:42 -0000

On Mon, Feb 22, 2010 at 9:56 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>
> An earlier definition of "cloud" was a virtualized computer that was managed by an entity outside one's own enterprise. Later, "private clouds" were invented, which eliminated the "outside one's own enterprise" but also significantly changed the security model. Later still, "XaaY" (for many values of X and Y) latched onto the "cloud" buzzword, describing applications and services by themselves, not virtualized computers.

I think there's reasonably good agreement on the values of X and Y.  Y
is "S".  X is I for infrastructure, meaning roughly "like what Amazon
does", P for Platform, meaning roughly "like what Google App Engine
and Heroku do", and S for Software meaning roughly "like what
Salesforce.com does".

I'm not convinced that there's a value-add for the IETF here, but if
there were, it'd be at the IaaS level.

> An IETF effort that tries to cover XaaY seems doomed to failure due to over-generality, while wasting a lot of participant effort. Instead, I think defining a cloud as "one or more virtualized computers where many components of each computer are managed separately" gives us a reasonable basis from which to work on how to provision such clouds and the networks over which the clouds run.

The big value of IaaS is that it lets you fire up servers and
configure them without involving Mordac the Preventer of IT, using
only some Web forms and your credit card.  Amazon's API for doing this
is kinda klunky, but tons of people are doing it anyhow so it's
plausible that there really is a big market for this kind of stuff.
Thus there are lots of proposals for APIs that are better and don't
belong to anyone, and a handful of efforts under way in various
standards orgs out there; a few are enumerated at
http://www.tbray.org/ongoing/When/200x/2009/04/28/Cloud-Standards and
also check out VMware's vCloud.

 -Tim