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

"Ashish Dalela (adalela)" <adalela@cisco.com> Thu, 16 February 2012 15:02 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 4E0C621F865A for <sop@ietfa.amsl.com>; Thu, 16 Feb 2012 07:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.455
X-Spam-Level:
X-Spam-Status: No, score=-6.455 tagged_above=-999 required=5 tests=[AWL=4.143, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 4ZI9Xy8KLcuf for <sop@ietfa.amsl.com>; Thu, 16 Feb 2012 07:02:46 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id E4BD521F864D for <sop@ietf.org>; Thu, 16 Feb 2012 07:02:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=26563; q=dns/txt; s=iport; t=1329404564; x=1330614164; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=PTOKjugHbkwJ++Q4w8hZzeOw/06+gKzR5W9kSx285XA=; b=c62qNBOVdzyZo4B4FDVt1D3Tsrw+bsGZyutc5CxDFVOx6pcoAXbiiFTA xbv0yJn7AkB8I2oFuQxOV9K7d1/viS115Zk2kv+NqipRmuTwzBGpHGJgb m4jSxJ9S2TyOjpTfhZOIvidXFPAC/GIZX5RY2/KQ49M1v3/qwm8aHVGmv Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AucHAMoZPU9Io8UY/2dsb2JhbABEgk2FLpgMiBMBiU2BcgEBAQQBAQEPAQkRAz4EBwwEAgEIDgMBAwEBCwIEEAMEAQYBJh8DBQEIAQEEAQoICAEZh2aaHQGeQ4tkCQEDAQQDGAgCAjGDWyQBCQYRAgMCBAECBAMEBQIFAwOCR2MEiEyeJYE2
X-IronPort-AV: E=Sophos;i="4.73,430,1325462400"; d="scan'208,217";a="5724146"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 16 Feb 2012 15:02:41 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1GF2fdY014676; Thu, 16 Feb 2012 15:02:41 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Feb 2012 20:32:41 +0530
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_01CCECBC.0764D7F1"
Date: Thu, 16 Feb 2012 20:32:39 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5103001E76@XMB-BGL-416.cisco.com>
In-Reply-To: <470D91CE-5D54-48F8-8889-438DA873A3FA@lucidvision.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sdnp] FW: New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services
Thread-Index: AczsvAafYHhYIbkMQ2SZTphXY1FR6w==
References: <CB62CCB4.C846D%mmorrow@cisco.com> <470D91CE-5D54-48F8-8889-438DA873A3FA@lucidvision.com>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: "Thomas Nadeau" <tnadeau@lucidvision.com>, "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
X-OriginalArrivalTime: 16 Feb 2012 15:02:41.0271 (UTC) FILETIME=[079E1870:01CCECBC]
Cc: sdnp <sdnp@lucidvision.com>, sop@ietf.org, Ping Pan <ping@pingpan.org>, robert@raszuk.net
Subject: Re: [sop] [Sdnp] FW: 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: Thu, 16 Feb 2012 15:02:53 -0000

 

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.

 

http://tools.ietf.org/html/draft-dalela-orchestration-00

 

The above draft describes the problems SOP is aimed to address. This is
the "requirements" draft.

 

The other drafts are:

 

http://tools.ietf.org/html/draft-dalela-sop-architecture-00 - describes
the use-cases and network deployments with the protocol

http://tools.ietf.org/html/draft-dalela-sop-00 - describes the
protocol's messages 

http://tools.ietf.org/html/draft-dalela-sdf-00 - describes service
naming, workflow construction, etc.

http://tools.ietf.org/html/draft-dalela-sop-flows-00 - describes some
message flows

 

Thanks, Ashish

 

 

From: Thomas Nadeau [mailto:tnadeau@lucidvision.com] 
Sent: Thursday, February 16, 2012 7:59 PM
To: Monique Morrow (mmorrow)
Cc: Ping Pan; robert@raszuk.net; sdnp; sop@ietf.org
Subject: Re: [Sdnp] FW: New Non-WG Mailing List: sop -- Service
Orchestration and Desciption for Cloud Services

 

 

            Can you please explain what the purpose of SOP is and what
its goals are?

People on this list have been also asking how it differs from SDN(p), so
it

might be helpful to include that as well. 8)

            

            --Tom

 

 

 

On Feb 16, 2012, at 9:09 AM, Monique Morrow wrote:





Guys 

Please join the SOP mailer 


List address: sop@ietf.org <x-msg://551/sop@ietf.org> 
Archive: http://www.ietf.org/mail-archive/web/sop/
To subscribe: https://www.ietf.org/mailman/listinfo/sop


TIA

Monique


On 2/14/12 10:45 PM, "Ping Pan" <ping@pingpan.org
<x-msg://551/ping@pingpan.org> > wrote:




Where does OpenStack Quantum fit?

OpenStack Quantum is to have agents in controllers and networking
devices for the purpose of better transport. This is well within the
goal of SDN.

Ping

On Tue, Feb 14, 2012 at 1:37 PM, Robert Raszuk <robert@raszuk.net
<x-msg://551/robert@raszuk.net> > wrote:




Actually I think those are quite separate problem spaces.

SOP aim to address the requirement of cloud to cloud communication
(hybrid or multi-domain). The way I think about this is how to
standardize and synchronize OpenStack to OpenStack instrumentation
signaling. The next step would be to actually also provide cloud to
cloud communication layer. Simple example: How to launch N VMs in
various data centers to be part of common resources for customer X.

On the contrary SDNx seems to me of totally different caliber. One way
to look at this is what and how we could use APIs exposed by existing
network control planes to define and accomplish new network services. I
quite do not see current network element control planes nor their APIs
as much relevant to cloud services.

My own personal view ;)

Regards,
R.





I'd like to get some clarification (from anyone who might know or
have an opinion) on how this would interact with/be distinct from any
of the SDNP (or whatever name we decide upon) proposed work. Is this
duplication/people striking out on their own from the nascent SDNP
effort, a companion effort that became clear as we have begun
segmenting the problem space, or something else entirely? Since this
is the first I've heard of the list, I'm thinking it's a separate
effort, but I figured I would raise the topic for discussion.

Thanks,

Wes George

-----Original Message----- From: ietf-announce-bounces@ietf.org
<x-msg://551/ietf-announce-bounces@ietf.org> 
[mailto:ietf-announce-bounces@ietf.org
<mailto:ietf-announce-bounces@ietf.org> ] On Behalf Of IETF
Secretariat Sent: Tuesday, February 14, 2012 2:25 PM To: IETF
Announcement list Cc: sop@ietf.org <x-msg://551/sop@ietf.org> ; Monique
Morrow Subject: New
Non-WG Mailing List: sop -- Service Orchestration and Desciption for
Cloud Services



A new IETF non-working group email list has been created.

List address: sop@ietf.org <x-msg://551/sop@ietf.org>  Archive:
http://www.ietf.org/mail-archive/web/sop/
<http://www.ietf.org/mail-archive/web/sop/>  To subscribe:
https://www.ietf.org/mailman/listinfo/sop
<https://www.ietf.org/mailman/listinfo/sop> 

Purpose: Cloud services need to interoperate across cloud providers,
service vendors and private/public domains. To enable this
interoperability, there is need for a standard wire-format for
exchanging service information. This mailing lists is for discussing
protocols, data formats and server descriptions formats that allow
cloud services to be discovered and used across private and public
domains. Using these, it would be possible to interoperate diverse
APIs and cloud services across service providers, service vendors and
service users.

For additional information, please contact the list administrators.
_______________________________________________ IETF-Announce mailing
list IETF-Announce@ietf.org <x-msg://551/IETF-Announce@ietf.org> 
https://www.ietf.org/mailman/listinfo/ietf-announce
<https://www.ietf.org/mailman/listinfo/ietf-announce> 

This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or
subject to copyright belonging to Time Warner Cable. This E-mail is
intended solely for the use of the individual or entity to which it
is addressed. If you are not the intended recipient of this E-mail,
you are hereby notified that any dissemination, distribution,
copying, or action taken in relation to the contents of and
attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.
_______________________________________________ SDNP mailing list
SDNP@lucidvision.com <x-msg://551/SDNP@lucidvision.com>
http://lucidvision.com/mailman/listinfo/sdnp
<http://lucidvision.com/mailman/listinfo/sdnp> 




_______________________________________________
SDNP mailing list
SDNP@lucidvision.com <x-msg://551/SDNP@lucidvision.com> 
http://lucidvision.com/mailman/listinfo/sdnp
<http://lucidvision.com/mailman/listinfo/sdnp> 

 

________________________________

_______________________________________________
SDNP mailing list
SDNP@lucidvision.com <x-msg://551/SDNP@lucidvision.com> 
http://lucidvision.com/mailman/listinfo/sdnp

_______________________________________________
SDNP mailing list
SDNP@lucidvision.com
http://lucidvision.com/mailman/listinfo/sdnp