Re: [sop] [dc] Service Orchestration Protocol

Bhumip Khasnabish <vumip1@gmail.com> Fri, 17 February 2012 02:45 UTC

Return-Path: <vumip1@gmail.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 6F36321E8028; Thu, 16 Feb 2012 18:45:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.026
X-Spam-Level:
X-Spam-Status: No, score=-3.026 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
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 2dQqQAuAkHR1; Thu, 16 Feb 2012 18:45:20 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1CEDF21E801C; Thu, 16 Feb 2012 18:45:20 -0800 (PST)
Received: by iagf6 with SMTP id f6so4467795iag.31 for <multiple recipients>; Thu, 16 Feb 2012 18:45:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YUXKDioiZZRJGTxRHWHoCBOoSmpmReOgFZV0X1YX/eQ=; b=qeRy5Z87tmAMPu7V0bZCTiaIDk00AhgWm6cL3xSeohf+SegiYOqTvyoOo9CfuF304H r+9trt5VNy98p6QSIITaipm8rgDzaxGV4I5xapzk5nFKaRdo0JmJB6NSNRmuzwHxwmQh aQa9HJP3NYPjlkc8/RNrdFnAaLlJB4stoALlw=
MIME-Version: 1.0
Received: by 10.43.51.135 with SMTP id vi7mr5210181icb.5.1329446719796; Thu, 16 Feb 2012 18:45:19 -0800 (PST)
Received: by 10.50.213.68 with HTTP; Thu, 16 Feb 2012 18:45:19 -0800 (PST)
In-Reply-To: <618BE8B40039924EB9AED233D4A09C5103001F72@XMB-BGL-416.cisco.com>
References: <618BE8B40039924EB9AED233D4A09C5103001EEA@XMB-BGL-416.cisco.com> <CANtnpwher+9jQxwbHAN9H5anVJB679exXJU0H_fSPkqwamv9MQ@mail.gmail.com> <618BE8B40039924EB9AED233D4A09C5103001F72@XMB-BGL-416.cisco.com>
Date: Thu, 16 Feb 2012 21:45:19 -0500
Message-ID: <CANtnpwhFvnYo2joh5GANSa=EEGtsSWAKojizX0D+=+bdzAg8JA@mail.gmail.com>
From: Bhumip Khasnabish <vumip1@gmail.com>
To: "Ashish Dalela (adalela)" <adalela@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec52e62177b33ee04b91fef18
Cc: shao.weixiang@zte.com.cn, sop@ietf.org, hu.jie@zte.com.cn, dc@ietf.org
Subject: Re: [sop] [dc] Service Orchestration Protocol
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: Fri, 17 Feb 2012 02:45:24 -0000

Thanks for your quick comments Ashish. I am cc:ing my co-authors for
reviewing your comments and suggestions, and the SOP drafts for further
discussion.

Best.

Bhumip



On Thu, Feb 16, 2012 at 9:32 PM, Ashish Dalela (adalela)
<adalela@cisco.com>wrote;wrote:

>  Bhumip,****
>
> ** **
>
> Thanks, I’m aware of this draft. We should discuss it on the SOP alias as
> not to clutter everyone’s email with a topic that may not be of interest.
> I’m cross posting this to SOP alias for now.****
>
> ** **
>
> One of things that the first draft describes is limitations of HTTP (and
> by implication web-services) for doing cloud – HTTP does not have
> constructs to do service discovery, pub-sub, commit-cancel, transaction
> forking, interactive prompts, etc. These capabilities are
> service-independent (applicable to all services) and very important to
> build complex, multi-tiered, or cross-domain services. ****
>
> ** **
>
> So, we did not want to add just a new content-type to HTTP, and layer
> basic capability into the controller application. The idea here is that if
> there are service independent capabilities, they should be part of a basic
> protocol scheme, which can be used by every type of service. But we
> preserved the text-based nature of well-known L7 protocols – SIP, HTTP,
> SMTP, etc. ****
>
> ** **
>
> To the specific issue of broker, you might want to refer to the
> architecture draft, where we described different types of brokers (we call
> them proxies). The functionality in the broker differs depending on where
> you place the broker – in the service edge, customer edge, provider edge,
> etc. We expect that different domains (compute, storage, network ..) will
> have different domain controllers. You still need to find an interoperable
> scheme to stitch these domain controllers.****
>
> ** **
>
> Thanks, Ashish****
>
> ** **
>
> *From:* Bhumip Khasnabish [mailto:vumip1@gmail.com]
> *Sent:* Friday, February 17, 2012 2:27 AM
> *To:* Ashish Dalela (adalela)
> *Cc:* dc@ietf.org
> *Subject:* Re: [dc] Service Orchestration Protocol****
>
> ** **
>
> Hello Ashish,****
>
>  ****
>
> There is also a Cloud Service Broker draft****
>
>  ****
>
> http://tools.ietf.org/id/draft-shao-opsawg-cloud-service-broker-02.txt ***
> *
>
> Thanks.****
>
>  ****
>
> Best.****
>
>  ****
>
> Bhumip****
>
>
>  ****
>
> On Thu, Feb 16, 2012 at 12:06 PM, Ashish Dalela (adalela) <
> adalela@cisco.com> wrote:****
>
> Folks,****
>
>  ****
>
> This may not be completely relevant to the DC topic, but thought that some
> of you might be interested in it.****
>
>  ****
>
> We have a few drafts posted on a “Service Orchestration Protocol”, with
> the intent to enable cloud interoperability.****
>
>  ****
>
> http://tools.ietf.org/html/draft-dalela-orchestration-00 - talks about
> why we need a protocol, a.k.a. requirements****
>
> 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 scheme for
> service naming, workflows, etc.****
>
> http://tools.ietf.org/html/draft-dalela-sop-flows-00 - describes some
> message flows****
>
>  ****
>
> A discussion alias https://www.ietf.org/mailman/listinfo/sop is setup for
> you to participate in case you find it interesting.****
>
>  ****
>
> Thanks and look forward to discussing there.****
>
>  ****
>
> -Ashish****
>
>  ****
>
>
> _______________________________________________
> dc mailing list
> dc@ietf.org
> https://www.ietf.org/mailman/listinfo/dc****
>
>
>
>
>   ****
>