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

Sam Johnston <sj@google.com> Fri, 30 July 2010 16:55 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 831DC3A6A6E for <clouds@core3.amsl.com>; Fri, 30 Jul 2010 09:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level:
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 yyuUJylTCxNk for <clouds@core3.amsl.com>; Fri, 30 Jul 2010 09:55:05 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 7F3403A6A6A for <clouds@ietf.org>; Fri, 30 Jul 2010 09:55:04 -0700 (PDT)
Received: from hpaq6.eem.corp.google.com (hpaq6.eem.corp.google.com [172.25.149.6]) by smtp-out.google.com with ESMTP id o6UGtSEj008577 for <clouds@ietf.org>; Fri, 30 Jul 2010 09:55:28 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1280508928; bh=YAGXg9ag3+I4/X5/VQbPLRJAF1g=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=klvv/gDUFuMYD5N4cXO7kccdyyPFFYI0muK5+nsQK0A0Ba227DzSQA/gMFz6pFLqK EovZnah97pW2Pt6cF0MeA==
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=jmMk8lj1sgXWW/Jaa61/AmspuEPX0uxcphroBwPLXCyqT1Xrdr9RwoxDykH8XnZDE 8D0Bef593p34h22zGi4Zw==
Received: from bwz10 (bwz10.prod.google.com [10.188.26.10]) by hpaq6.eem.corp.google.com with ESMTP id o6UGtCc9030312 for <clouds@ietf.org>; Fri, 30 Jul 2010 09:55:27 -0700
Received: by bwz10 with SMTP id 10so1086761bwz.34 for <clouds@ietf.org>; Fri, 30 Jul 2010 09:55:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.75.81 with SMTP id x17mr1391782bkj.72.1280508927268; Fri, 30 Jul 2010 09:55:27 -0700 (PDT)
Received: by 10.204.25.77 with HTTP; Fri, 30 Jul 2010 09:55:27 -0700 (PDT)
In-Reply-To: <294030129BF751408412C35312657D974E7991B241@qtdenexmbm21.AD.QINTRA.COM>
References: <AANLkTinvqsPzwBDxrj74RXpys21x2BRmJFBcoc8vbRhW@mail.gmail.com> <294030129BF751408412C35312657D974E7991B241@qtdenexmbm21.AD.QINTRA.COM>
Date: Fri, 30 Jul 2010 18:55:27 +0200
Message-ID: <AANLkTinW9dXdbArLGp2oKRt3QbzHhLL+zm=TdaQK-cCE@mail.gmail.com>
From: Sam Johnston <sj@google.com>
To: "Fargano, Michael" <Michael.Fargano@qwest.com>
Content-Type: multipart/alternative; boundary=0016e6db2befbdd719048c9db7c5
X-System-Of-Record: true
Cc: "clouds@ietf.org" <clouds@ietf.org>
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: Fri, 30 Jul 2010 16:55:06 -0000

Every man and his dog is trying to [re]define cloud so I would be quite
happy for us to leave this well alone, which is to say I don't accept the
opening premise that "*Currently there is no Standard Reference Framework
for Cloud Services, so first we need to develop a Reference Framework*".

If we must then I would suggest working with the already well accepted 3
layer stack:

   - Application
   - Platform
   - Infrastructure

If you want a *functional* taxonomy (that is, one which is capable of
categorising everything in the space without polluting these
*service*layers with
*products*) then you can add server and client layers ala:

   - Client (Android, iOS, etc.)
   - Application (Gmail, Salesforce.com, MS BPOS, etc.)
   - Platform (Azure, App Engine, Heroku, etc.)
   - Infrastructure (Amazon EC2, EBS, VPC, etc.)
   - Server (Cisco UCS, SGI CloudRack, etc.)

Note that these two additional layers are typically products (hardware
and/or software) while the three main layers are always services.

There's no need to find/create complexity where there need be none.

Sam

-- 
*Sam Johnston*
*Technical Program Manager*
Site Reliability Engineering
Google Switzerland GmbH

w: +41 44 668 16 79
h: +41 44 536 55 78
m: +41 79 631 25 16



On 30 July 2010 17:41, Fargano, Michael <Michael.Fargano@qwest.com> wrote:

> Bhumip:
>
> I was not at the BoF. I was just wondering how the proposed framework
> relates to commonly understood Cloud terms like IaaS, PaaS, SaaS...??? For
> example see NIST Definition of Cloud:
> http://csrc.nist.gov/groups/SNS/cloud-computing/index.html
>
> I'm sure you discussed this at the BoD. Perhaps an explanation in the slide
> deck would help.
>
> Thanks,
> Mike
>
> ________________________________________
> From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf
> Of Bhumip Khasnabish
> Sent: Friday, July 30, 2010 4:38 AM
> To: clouds@ietf.org
> Subject: [clouds] A cloud ref. framework for your review and comments
>
> Dear All,
>
> After the Clouds bar BoF yesterday, a few of us got together to work on
> developing a simple Cloud reference framework.
> Attached pls find the output of that discussion.
>
> We look forward to your constructive comments and suggestions to improve
> and finalize the ref. framework. Thanks  a lot.
>
> Best Regards.
> Bhumip
>
> Bhumip Khasnabish (Mobile:+001-781-752-8003, vumip1@gmail.com)
>
>
>
> This communication is the property of Qwest and may contain confidential or
> privileged information. Unauthorized use of this communication is strictly
> prohibited and may be unlawful.  If you have received this communication
> in error, please immediately notify the sender by reply e-mail and destroy
> all copies of the communication and any attachments.
> _______________________________________________
> clouds mailing list
> clouds@ietf.org
> https://www.ietf.org/mailman/listinfo/clouds
>