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

[Monique Morrow <[e-mail]>]

Guys 

Please join the SOP mailer


List address: [e-mail]
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" <[e-mail]> 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 <[e-mail]> 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: [e-mail]
>>> [mailto:[e-mail]
>>> <mailto:[e-mail]> ] On Behalf Of IETF
>>> Secretariat Sent: Tuesday, February 14, 2012 2:25 PM To: IETF
>>> Announcement list Cc: [e-mail]; 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: [e-mail] 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 [e-mail]
>>> 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
>>> [e-mail] http://lucidvision.com/mailman/listinfo/sdnp
>>> <http://lucidvision.com/mailman/listinfo/sdnp>
>>> 
>>> 
>> 
>> _______________________________________________
>> SDNP mailing list
>> [e-mail]
>> http://lucidvision.com/mailman/listinfo/sdnp
>> <http://lucidvision.com/mailman/listinfo/sdnp>
> 
> 
> 
> _______________________________________________
> SDNP mailing list
> [e-mail]
> http://lucidvision.com/mailman/listinfo/sdnp