Paul,
Yes I’ll send one -… (I’m waiting for the webex to be setup and then I’ll send the meeting maker)
The first meeting is more discovery, and socialization than anything else… we may have to re-calibrate what has to be done depending on what we learn there.
Agenda wise the current idea is..
- project orientation (starfish) – User portal Object & framework
- Reviewing the models each group have (User portal or Network Resource types) so we get a good picture of what is out there.
- ONAP user / network resource model
- TOSCA Template resource model
And basically how do they all align, or not align..
I think we’ll find most groups have “network resource models establish, but not necessarily any User Portal / Template Objects for the customer level interface.
The framework here shows how all of those link together (template to portal user object, and telemetry which is mapped from the Network Resource objects)
Essentially we would like all of the groups Information model patterns for the UI objects to align so they are portable from a machine readable perspective.
So it’s wise to reach out IMO so that we make sure they align… by taking the best work from each group and having Starfish test those patterns for breakage as the project
Moves forward and we start opening up these items..
From: "Lipton, Paul C" <Paul.Lipton@ca.com>
Date: Friday, February 2, 2018 at 1:45 PM
To: "Bugenhagen, Michael K" <Michael.K.Bugenhagen@centurylink.com>, Chris Lauwers <lauwers@ubicity.com>, Paul Knight <paul.knight@oasis-open.org>
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>,
"Vul, Alex" <alex.vul@intel.com>, Andy Mayer <am803u@att.com>
Subject: RE: TOSCA / User Portal Object patterns alignment (Starfish is setting up a open call with ONAP, and TOSCA if you guys care to join)
Mike,
Thanks for reaching out. If you would be so kind as to send logistical information, short summary, and proposed agenda to Chris (TOSCA TC Co-chair), Alex Vul (TOSCA
NFV Ad Hoc Workgroup Co-leader), and me, we will be glad to distribute the information to any TOSCA TC member who expresses interest.
Regards,
Paul
From: Bugenhagen, Michael K [mailto:Michael.K.Bugenhagen@centurylink.com]
Sent: Friday, February 2, 2018 2:27 PM
To: Chris Lauwers <lauwers@ubicity.com>; Lipton, Paul C <Paul.Lipton@ca.com>; Paul Knight <paul.knight@oasis-open.org>
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>; Vul, Alex <alex.vul@intel.com>;
Andy Mayer <am803u@att.com>
Subject: TOSCA / User Portal Object patterns alignment (Starfish is setting up a open call with ONAP, and TOSCA if you guys care to join)
Chris, & Paul’s,
Starfish and ONAP have been what the universal Portal object pattern should be, and we have found some similarities so we’re going to have an open Discussion call / Meeting Feb 12th.
I would also like to see if we can’t see if there are “common TOSCA” object patterns for User Portals….
Whom on your team should I invite that handles TOSCA resource patterns ?
For that matter any of the TOSCA team members are more than welcome to attend the call, we’re just trying to figure out the landscape right now.
Thanks,
Mike
From: <tosca-comment@lists.oasis-open.org> on behalf of "Bugenhagen, Michael K"
<Michael.K.Bugenhagen@centurylink.com>
Date: Monday, January 22, 2018 at 2:54 PM
To: Chris Lauwers <lauwers@ubicity.com>, "Lipton, Paul C" <Paul.Lipton@ca.com>, Paul Knight <paul.knight@oasis-open.org>
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
Chris,
We just gave our project a name = Starfish (Redfish, Swordfish, ..)
Let me know if your team is having any calls and I and or Ron can present (I’ll probably ask John Leung from Redfish to provide some backup) at one of your calls so we can get better awareness of where the projects are at.
Oddly enough (how did that happen) Redfish that is based on Compute / Cloud has all of these.. provided we observe a) below.
Starfish is really following the Win-win-win-win from cloud.
- Customer wins: Customer centric Network resource abstractions
- Application useable resources, that are portal / template ready, that DO NOT need adaptation for the presentation layer,
these should control the Framework CIM just as they do in Compute /Cloud.
- Coders win: Standard algorithms in code for standard vendor neutral resources
- Vendor neutral core resource models (standardized functional network resource CIM’s)
Following the prioritiy, these should be consumer centric.
- Vendors win: OEM flexibility
- The framework we consider must provide the capability to
- Provider wins: Full Automation vs. automating for Op’s, w/ a back office on top
- Machine readable models at both the Controller / Orchestrator and the Customer Portal levels…
Zero touch really means Zero if you can automate up to the customer vs. provider
The team is really keyed onto these, and is expanding rapidly (making standardize network resources that are vendor neutral for “performance agents” has triggered the Test system vendors to show up to write
applications….
So – let me know what meetings, and or Face to faces meetings you have and we’ll do some cross pollination. (Aka – looking for a win-win with orchestration templates).
BTW – I’m one of the few “inter-carrier” ordering Subjet experts so this thing is already aligned for Inter-carrier Ordering, I just haven’t flipped that switch just yet.
Best,
Mike
From: Chris Lauwers <lauwers@ubicity.com>
Date: Monday, January 22, 2018 at 1:10 PM
To: "Bugenhagen, Michael K" <Michael.K.Bugenhagen@centurylink.com>, "Lipton, Paul C" <Paul.Lipton@ca.com>, Paul Knight <paul.knight@oasis-open.org>
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>,
Chris Lauwers <lauwers@ubicity.com>
Subject: RE: [tosca-comment] Invitation to comment on TOSCA Simple Profile in YAML v1.2 - ends February 18th
Hi Michael,
I’m not that familiar with Redfish (and in fact Oasis TOSCA hasn’t focused much on APIs), but we are engaged in a number of efforts to make sure that TOSCA is aligned with efforts in the telecom industry to define standardized abstractions
and information models:
- We’re working with the ONF Information Modeling group to encode their models into TOSCA, very similar to how Project Eagle encodes some of their models into YANG, and hopefully within
the context of IISOMI as well.
- Since ONF models are also used in MEF, this could create potential alignment between TOSCA and MEF as well (I know that Pascal Menezes wants to standardize on TOSCA, even though others
inside MEF are not quite on board yet
😊 )
- As you know, the ONF models include a “specification pattern” that can be used to map their based models onto domain-specific technologies. We’re starting to investigate whether this pattern
could be used to align with lower-level OpenConfig models, which would then create an opportunity to drive alignment of TOSCA models with OpenConfig YANG models
- We’re working closely with both ETSI NFV and ONAP (both of whom have adopted TOSCA as the basis for their models) to minimize divergence between their models and core TOSCA.
I’d love to participate in any discussions that can further harmonize various efforts in the industry.
Best regards,
Chris Lauwers
Co-Chair, TOSCA TC
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
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
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.
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
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
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.
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.
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.
The prose specification document and related files are available here:
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:
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:
--
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.
--
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.
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.
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.