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

"So, Ning" <ning.so@verizonbusiness.com> Fri, 30 July 2010 14:11 UTC

Return-Path: <ning.so@verizonbusiness.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 CC5393A69F2 for <clouds@core3.amsl.com>; Fri, 30 Jul 2010 07:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level:
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 1iQ1kXep-c87 for <clouds@core3.amsl.com>; Fri, 30 Jul 2010 07:11:58 -0700 (PDT)
Received: from ashesmtp01.verizonbusiness.com (ashesmtp01.verizonbusiness.com [198.4.8.163]) by core3.amsl.com (Postfix) with ESMTP id 510C43A69E1 for <clouds@ietf.org>; Fri, 30 Jul 2010 07:11:58 -0700 (PDT)
Received: from pdcismtp01.vzbi.com ([unknown] [166.40.77.67]) by firewall.verizonbusiness.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0L6D002F3JGMNE50@firewall.verizonbusiness.com> for clouds@ietf.org; Fri, 30 Jul 2010 14:12:22 +0000 (GMT)
Received: from pdcismtp01.vzbi.com ([unknown] [127.0.0.1]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0L6D00JHXJGMQW00@pdcismtp01.vzbi.com> for clouds@ietf.org; Fri, 30 Jul 2010 14:12:22 +0000 (GMT)
Received: from ASHSRV142.mcilink.com ([unknown] [153.39.68.168]) by pdcismtp01.vzbi.com (Sun Java(tm) System Messaging Server 7u2-7.03 32bit (built May 29 2009)) with ESMTP id <0L6D00JD1JGMU400@pdcismtp01.vzbi.com> for clouds@ietf.org; Fri, 30 Jul 2010 14:12:22 +0000 (GMT)
Received: from ASHEVS008.mcilink.com ([153.39.69.129]) by ASHSRV142.mcilink.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 30 Jul 2010 14:12:21 +0000
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-version: 1.0
Content-type: multipart/alternative; boundary="----_=_NextPart_001_01CB2FF1.39E5CC09"
Date: Fri, 30 Jul 2010 14:12:20 +0000
Message-id: <14584D6EE26B314187A4F68BA206060004B46D1D@ASHEVS008.mcilink.com>
In-reply-to: <AANLkTinvqsPzwBDxrj74RXpys21x2BRmJFBcoc8vbRhW@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-topic: [clouds] A cloud ref. framework for your review and comments
Thread-index: Acsv03YlpbyZy8tzRDGhY/JD5pCmCQAHIznw
References: <AANLkTinvqsPzwBDxrj74RXpys21x2BRmJFBcoc8vbRhW@mail.gmail.com>
From: "So, Ning" <ning.so@verizonbusiness.com>
To: Bhumip Khasnabish <vumip1@gmail.com>, clouds@ietf.org
X-OriginalArrivalTime: 30 Jul 2010 14:12:21.0854 (UTC) FILETIME=[3A191FE0:01CB2FF1]
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 14:12:00 -0000

Bhumip and all,

 

Thanks for the excellent work as a starting point.  Here are a couple of
my suggestions,

 

1.	Need at least one layer to represent the underlying networks.
What you have shown so far is the view of cloud purely from the data
center point-of-view.  The fact is that you need to have simple network
infrastructure to connect data centers to data centers (assuming the
data centers cluster is within a short distance, such as a metro area),
and to connect data centers to carrier networks (IP/MPLS/VPN).  In
addition, you need a complicated network to connect data centers with
the users.  
2.	Before inter-Cloud reference model framework, there should be a
reference model showing the inter-data center.  This should be a cluster
of data centers that can share the common resources and share the
protection with each other in case of failure.  Of course the networks
need to be a part of the model. 

 

Regards,

 

Ning So

Lead Engineer

Global Data Network Traffic Planning

Verizon, Inc.

(office) 972-729-7905

(Cell) 972-955-0914

 

________________________________

From: clouds-bounces@ietf.org [mailto:clouds-bounces@ietf.org] On Behalf
Of Bhumip Khasnabish
Sent: Friday, July 30, 2010 5: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)