Re: [sop] [Sdnp] New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services

"Ashish Dalela (adalela)" <adalela@cisco.com> Wed, 29 February 2012 16:58 UTC

Return-Path: <adalela@cisco.com>
X-Original-To: sop@ietfa.amsl.com
Delivered-To: sop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE64921F8793 for <sop@ietfa.amsl.com>; Wed, 29 Feb 2012 08:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.558
X-Spam-Level:
X-Spam-Status: No, score=-7.558 tagged_above=-999 required=5 tests=[AWL=3.041, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 PiJZffMAlNAj for <sop@ietfa.amsl.com>; Wed, 29 Feb 2012 08:58:57 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 9432C21F874A for <sop@ietf.org>; Wed, 29 Feb 2012 08:58:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=2506; q=dns/txt; s=iport; t=1330534736; x=1331744336; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=dJDOF1XajO+6/DTwJnn4lhtaSYj37ovjvwEd+8qNWMs=; b=jGH26WgScilbuPsdgD3Cz3ZyDe5okXFw7FkYzYvbqMJB7SDY3PbGfq0N HPNhRmNVgmqZroR6dY+6F68hL72zn2nTepHeazG4VVOn3prAaag0D9RNY nB2P6y2t0Cw3f7GDFuATXLyaohVACPITML6xCkokMupTul5e6XuZxGt6H c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAO9YTk9Io8UY/2dsb2JhbABDtHaBegEBAQQSAR0+CwwEAgEIEQQBAQEKBhcBBgFFCQgBAQQLCAgah2cLoGcBlzKKAgWCeAIBFgIFAQEMAkAVCQKFDQMKAQcGEQoBDQcEBhqCSWMEiBwxn2uBTQc
X-IronPort-AV: E=Sophos;i="4.73,503,1325462400"; d="scan'208";a="6675129"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 29 Feb 2012 16:58:54 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1TGwsLq007300; Wed, 29 Feb 2012 16:58:54 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 29 Feb 2012 22:28:54 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Feb 2012 22:28:52 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C51031BC3BE@XMB-BGL-416.cisco.com>
In-Reply-To: <ABF3987B-35D7-49A8-ADA5-24FB5E225860@tid.es>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sdnp] New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services
Thread-Index: Acz3AYVskQpZo5kwQFqCDnVu+1ahhQAAbXUA
References: <CB62CCB4.C846D%mmorrow@cisco.com> <470D91CE-5D54-48F8-8889-438DA873A3FA@lucidvision.com> <618BE8B40039924EB9AED233D4A09C5103001E76@XMB-BGL-416.cisco.com> <ABF3987B-35D7-49A8-ADA5-24FB5E225860@tid.es>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: DIEGO LOPEZ GARCIA <diego@tid.es>
X-OriginalArrivalTime: 29 Feb 2012 16:58:54.0463 (UTC) FILETIME=[6B5580F0:01CCF703]
Cc: sop@ietf.org
Subject: Re: [sop] [Sdnp] New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services
X-BeenThere: sop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Service Orchestration and Desciption for Cloud Services <sop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sop>, <mailto:sop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sop>
List-Post: <mailto:sop@ietf.org>
List-Help: <mailto:sop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sop>, <mailto:sop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 16:58:57 -0000

Hi Diego,

We are aware of the IEEE work on Intercloud, but I'm not sure if there is a concrete technical proposal in place. I might not have seen it, in which please do point it out to me.

Thanks, Ashish

-----Original Message-----
From: DIEGO LOPEZ GARCIA [mailto:diego@tid.es] 
Sent: Wednesday, February 29, 2012 10:15 PM
To: Ashish Dalela (adalela)
Cc: sop@ietf.org
Subject: Re: [Sdnp] New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services

Hi,

On 16 Feb 2012, at 16:02 , Ashish Dalela (adalela) wrote:
> SOP has the following main goals -
>
> 1.  Fix interoperability issues with cloud services today. Main examples are inter-cloud, hybrid-cloud, and multi-vendor cloud. All cloud services are being enabled through proprietary APIs today, which don't interoperate. To interoperate across vendors, providers and customers, we need an open standard. Ability to go across administrative domains is a basic requirement.
>
> 2.  A clear separation between service-independent and service-dependent pieces in cloud services. SOP is about service-independent pieces. Using SOP, a variety of services could be accessed or advertized. Separation between service-independent and service-dependent pieces makes the scheme extensible to any type of service - current or future.
>
> 3.  Create a common scheme for service orchestration that can be used across compute, network, storage, security, applications, etc. A common set of constructs that can be applied to any service type whether it is infrastructure or application.

Though I've had no time to make a comparison in depth, I could not avoid noticing that SOP and the Intercloud effort recently started inside the IEEE P2302 Working Group are very much related, if not overlapping. Alignment should be pursued, I think.

Be goode,


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at
http://www.tid.es/ES/PAGINAS/disclaimer.aspx