OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [tosca-comment] Invitation to comment on TOSCA Simple Profile in YAML v1.2 - ends February 18th


Paul, and Paul,

 

      Ron Insler & I are running the project – and we have discussed how to engage with both groups.

 

At the end of the day we want a protocol / API / Template neutral schema for a NFV (WAN resource) that can be used everywhere, so we definitely will be engaging as part of solving that … what is the common industry schema / pattern, that is machine readable / consumable (suitable for automation).

 

    As a provider I’m also aligning this with a framework for Ordering between providers so that the NFV environement is not only frictionless for a customer in one provider, but in all providers…   so long terms we’ll also pull in ONAP, and ZSM to make sure everyone is on the same page.

 

I’ll circle the architects from each domain and see what they think in terms of proceeding.

 

Best

Mike

 

From: "Lipton, Paul C" <Paul.Lipton@ca.com>
Date: Friday, January 19, 2018 at 11:26 AM
To: "Lipton, Paul C" <Paul.Lipton@ca.com>, Paul Knight <paul.knight@oasis-open.org>, "Bugenhagen, Michael K" <Michael.K.Bugenhagen@centurylink.com>
Cc: "tosca-comment@lists.oasis-open.org" <tosca-comment@lists.oasis-open.org>, "Leung, John" <john.leung@intel.com>, "Autor, Jeff" <jeff.autor@hpe.com>, "Hilland, Jeff" <jeff.hilland@hpe.com>, Ron Insler <RON_i@rad.com>, Chet Ensign <chet.ensign@oasis-open.org>
Subject: RE: [tosca-comment] Invitation to comment on TOSCA Simple Profile in YAML v1.2 - ends February 18th

 

Also, Paul Knight’s comment about representatives from companies, e.g.., Intel’s Alex Vul, being good sources of information is well-taken.

 

- Paul

 

From: tosca-comment@lists.oasis-open.org [mailto:tosca-comment@lists.oasis-open.org] On Behalf Of Lipton, Paul C
Sent: Friday, January 19, 2018 12:22 PM
To: Paul Knight <paul.knight@oasis-open.org>; Bugenhagen, Michael K <Michael.K.Bugenhagen@centurylink.com>
Cc: tosca-comment@lists.oasis-open.org; Leung, John <john.leung@intel.com>; Autor, Jeff <jeff.autor@hpe.com>; Hilland, Jeff <jeff.hilland@hpe.com>; Ron Insler <RON_i@rad.com>; Chet Ensign <chet.ensign@oasis-open.org>
Subject: RE: [tosca-comment] Invitation to comment on TOSCA Simple Profile in YAML v1.2 - ends February 18th

 

Hi Mike,

 

I will forward your comment to the TC to see if any member is interested in responding. To my knowledge, there has been no exploration of RedFish within the TC. As you know, TOSCA is a topological, intent model expressed most commonly in a YAML DSL. We are working, and have members from, a large number of NFV-focused organizations, e.g., ONAP, ETSI, etc.

 

Regards,

Paul

 

From: tosca-comment@lists.oasis-open.org [mailto:tosca-comment@lists.oasis-open.org] On Behalf Of Paul Knight
Sent: Friday, January 19, 2018 12:02 PM
To: Bugenhagen, Michael K <
Michael.K.Bugenhagen@centurylink.com>
Cc:
tosca-comment@lists.oasis-open.org; Leung, John <john.leung@intel.com>; Autor, Jeff <jeff.autor@hpe.com>; Hilland, Jeff <jeff.hilland@hpe.com>; Ron Insler <RON_i@rad.com>; Chet Ensign <chet.ensign@oasis-open.org>
Subject: Re: [tosca-comment] Invitation to comment on TOSCA Simple Profile in YAML v1.2 - ends February 18th

 

CAUTION: This email originated from outside of CA. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Mike,

 

Thanks for your thoughtful suggestions on likely synergies with TOSCA.

 

As a member of the OASIS staff, I'm not personally a member of the TOSCA Technical Committee (TC), and can't contribute meaningfully to that discussion. Perhaps one or more of the TC members may respond to you directly.

 

I would like to suggest that you consider engaging with the TC personally by becoming a member of OASIS. I note that Intel and HPE (employers of individuals you've copied in your message) are currently members of the TOSCA TC. (OASIS members are listed at https://www.oasis-open.org/member-roster.)

 

I'll also note that OASIS supports and provides an environment for open source software development associated with our TCs.

 

I've copied our director of TC Administration, Chet Ensign, who can help with any questions you might have about engaging with OASIS and  the TOSCA TC.

 

Best regards,

Paul

 

On Fri, Jan 19, 2018 at 10:50 AM, Bugenhagen, Michael K <Michael.K.Bugenhagen@centurylink.com> wrote:

Paul,

 

      Are there any efforts to align TOSCA YAML service objects in TOSCA with the emerging Telecom NFV Domain service schemas (CSDL used by Redfish, and or YANG from the Op’s controller side)?

 

    The Open Source project I’m helping lead takes existing Telecom network Resources and makes them a Service under Redfish …. And exposes them in that Native Cloud API service to the customer…

 

       Ideally, we should be able to take those same resources and make them part of an Orchestration template, which would require a “machine readable” service schema for standardized functions (customer defined top down standardized functions vs. bottom up technology glip that makes no sense to the customer) …    i.e.  the customer fills out the template – raw YANG is not something Grandma is going to understand.

 

  Anyway – the question.    So, Has your team recognized the need for aligning on atomic native cloud host services from the compute side / NFV / Telecom sides… 

 

I think we need to have a sit down on what standard pattern / Schema makes these objects readable by templates as well as the Native Cloud API service.

 

                BTW -  Many of the groups are finally figuring out that if you right an API for everything you build service wise, you’re actually doing MORE work coding that telecom does today (more IT not less) so moving to a standard Customer facing service API like Redfish not only makes sense, it’s somewhat a no-brainer if you are moving to zero touch (want machine readable).

 

Thanks,

Mike

 

From: <tosca-comment@lists.oasis-open.org> on behalf of Paul Knight <paul.knight@oasis-open.org>
Date: Thursday, January 18, 2018 at 4:52 PM
To: "
tc-announce@lists.oasis-open.org" <tc-announce@lists.oasis-open.org>, "members@lists.oasis-open.org" <members@lists.oasis-open.org>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>, "tosca-comment@lists.oasis-open.org" <tosca-comment@lists.oasis-open.org>
Subject: [tosca-comment] Invitation to comment on TOSCA Simple Profile in YAML v1.2 - ends February 18th

 

 

We are pleased to announce that the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC members have recently approved a Committee Specification Draft (CSD) and submitted it for a 30-day public review:

 

TOSCA Simple Profile in YAML Version 1.2

Committee Specification Draft 02 / Public Review Draft 01

07 December 2017

 

This is the first public review for Version 1.2, although TOSCA Simple Profile in YAML Version 1.1 is currently a Candidate OASIS Standard.

 

Overview:

 

YAML is a human friendly data serialization standard with a syntax much easier to read and edit than XML. The TOSCA Simple Profile in YAML specifies a rendering of TOSCA which aims to provide a more accessible syntax as well as a more concise and incremental expressiveness of the TOSCA DSL (Domain Specific Language) in order to minimize the learning curve and speed the adoption of the use of TOSCA to portably describe cloud applications. The TOSCA TC approved this draft on 07 December 2017.

 

Public Review Period:

 

The public review starts 19 January 2018 at 00:00 UTC and ends 18 February at 23:59 UTC.

 

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

 

Note that you must be subscribed to the comment mailing list before sending feedback. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=tosca

 

URIs:

 

The prose specification document and related files are available here:

 

PDF (Authoritative):

 

HTML:

 

Editable source:

 

For your convenience, OASIS provides a complete package of the prose document and related files in a ZIP distribution file. You can download the ZIP file here:

 

 

Additional information about the specification and the TOSCA TC can be found at the TC's public home page:

 

 

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC's "Send A Comment" page, or directly at:

 

 

Public Review Period:

 

OASIS and the TOSCA TC value your feedback. We solicit feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

 

This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

 

 

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of "TOSCA Simple Profile in YAML Version 1.2", we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this Technical Committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification.

 

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.

 

========== Additional references:

 

 

RF on Limited Terms Mode

 

Best regards,

Paul

--

Paul Knight  - Tel: +1 781-883-1783
OASIS - Advancing open standards for the information society - Document Process Analyst

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.



 

--

Paul Knight  - Tel: +1 781-883-1783
OASIS - Advancing open standards for the information society - Document Process Analyst

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]