Re: [clouds] A cloud ref. framework for your review and comments

Sam Johnston <sj@google.com> Sat, 31 July 2010 09:32 UTC

Return-Path: <sjj@google.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 575DC3A689B for <clouds@core3.amsl.com>; Sat, 31 Jul 2010 02:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.901
X-Spam-Level:
X-Spam-Status: No, score=-105.901 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 zyQ7ykUXSVeH for <clouds@core3.amsl.com>; Sat, 31 Jul 2010 02:32:53 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 55AD73A69F1 for <clouds@ietf.org>; Sat, 31 Jul 2010 02:32:52 -0700 (PDT)
Received: from kpbe13.cbf.corp.google.com (kpbe13.cbf.corp.google.com [172.25.105.77]) by smtp-out.google.com with ESMTP id o6V9XIn4019718 for <clouds@ietf.org>; Sat, 31 Jul 2010 02:33:18 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1280568798; bh=naxU2edliyYPbV/iAi8uvD+dkdg=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=a9HLNoseHrd2ozIWMxgq28ODeLbIqbks1MeqfTOioc/kHgyN5TyUc0ny2m4ZDQbyD IsmBtY01HkTGHFTX8S9DA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=ZwvCoxClSixkaprCm9UXMDU00uqFa7kGI9yMv2zS+8xu0wsjM3kB6bONm2dC23v/2 4QN8FNh1VDiwkLXtb0Mrw==
Received: from bwz6 (bwz6.prod.google.com [10.188.26.6]) by kpbe13.cbf.corp.google.com with ESMTP id o6V9XG0x026002 for <clouds@ietf.org>; Sat, 31 Jul 2010 02:33:16 -0700
Received: by bwz6 with SMTP id 6so1740350bwz.40 for <clouds@ietf.org>; Sat, 31 Jul 2010 02:33:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.162.204 with SMTP id w12mr1983372bkx.135.1280568795837; Sat, 31 Jul 2010 02:33:15 -0700 (PDT)
Received: by 10.204.25.77 with HTTP; Sat, 31 Jul 2010 02:33:15 -0700 (PDT)
In-Reply-To: <25C3B27C-5DF8-4855-A272-BD10591F6B6F@unbehagen.net>
References: <AANLkTinvqsPzwBDxrj74RXpys21x2BRmJFBcoc8vbRhW@mail.gmail.com> <294030129BF751408412C35312657D974E7991B241@qtdenexmbm21.AD.QINTRA.COM> <AANLkTinW9dXdbArLGp2oKRt3QbzHhLL+zm=TdaQK-cCE@mail.gmail.com> <25C3B27C-5DF8-4855-A272-BD10591F6B6F@unbehagen.net>
Date: Sat, 31 Jul 2010 11:33:15 +0200
Message-ID: <AANLkTi=ap4AbXYKq_3ZDqyKR7JOzcx8j9EoLpRqoNxnG@mail.gmail.com>
From: Sam Johnston <sj@google.com>
To: Paul Unbehagen <paul@unbehagen.net>
Content-Type: multipart/alternative; boundary=00032555a4962fb643048caba808
X-System-Of-Record: true
Cc: "clouds@ietf.org" <clouds@ietf.org>, "Fargano, Michael" <Michael.Fargano@qwest.com>
Subject: Re: [clouds] A cloud ref. framework for your review and comments
X-BeenThere: clouds@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Sat, 31 Jul 2010 09:32:54 -0000

On 30 July 2010 20:20, Paul Unbehagen <paul@unbehagen.net> wrote:

> Along that vein of thought the network components are just as important as
> more and more private clouds get built.


Again this is the tail wagging the dog (and assumes you accept the premise
that "private" cloud is even cloud given it lacks multi-tenancy and
therefore requires significant capex, engineering for peak loads, etc.).
Once there is some sanity around emulating legacy (e.g. virtual machines) in
the infrastructure space the focus will quickly shift to platforms (app
runtimes, databases, queues, etc.). The sooner the better if you ask me.

For now let's keep it simple at the upper level and drill down where & when
we need to.

Sam