Participants:
AT&T, Orange, Fujitsu (member list below)
Description:
Provide end to end multi-operator L1 services orchestrated by ONAP across multiple optical transport domains
Goals:
- Incorporate & harmonize with MEF L1 Subscriber and Operator service definitions
- E2E optical service work flow definitions & on-boarding of network resources
- Align, harmonize, reconcile common information/data models in ONAP to enable Optical Transport services design & instantiation
- Optical Transport domain management through standard models / APIs. Eg: OpenROADM, Transport API
BUSINESS DRIVER
This section describes Business Drivers needs.
Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case).
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Initial use-case proposal:
ONAP-optical-usecase-proposal.pptx
Business requirements:
L1 interconnect business reqts agreed 5-16.pptx
CDS based Workflows updates:
ONAP-optical-usecase-proposal-with-cds
ONAP-optical-usecase-proposal-with-cds-4/29
| Member Name | Company | |
|---|---|---|
| david.allabaugh@us.fujitsu.com | Fujitsu | |
| olivier.augizeau@orange.com | Orange | |
Martin Birk | mb4962@att.com | AT&T |
| eric.debeau@orange.com | Orange | |
| bf1936@att.com | AT&T | |
| denise.provencher@us.fujitsu.com | Fujitsu | |
| Ravi.Rao@us.fujitsu.com | Fujitsu | |
| Olivier Renais | olivier.renais@orange.com | Orange |
| raghavan.subramanian@us.fujitsu.com | Fujitsu |
Functional Requirements:
| ONAP Components | PTL Commitment | Comments |
|---|---|---|
| CDS | N | Started Discussion with CDS group to identify the required changes to support this blue print. Have provided the initial sequence flow. |
| SDC | N | Have to start discussions. Mostly for now we will just be using existing features of SDC. May require small tweaks. |
| SO | N | Will need some changes in SO to accomplish the decomposition of end to end optical service. More details need to be ironed out. |
| SDN-C | N | Have done some prototyping in Dublin for adding new DGs to extract topology from external domain controllers and map them to A&AI schema. Will need additional work to integrate this with proposed CDS workflow |
| A&AI | N | Have done some prototyping in Dublin to ingest topology from external controllers and show them in A&AI. Will need more work to act on notifications from controllers and keep the topology in sync |
| OOF | N | Need more detailed discussions with OOF PTL to understand how we can use OOF to provide the intermediate endpoints for domain specific services that will eventually form our end to end service |
| Policy | N | Need to understand how we can use the policy to store inter SP agreements which can later be translated by OOF to determine the partner SP and also the end points at the partner side |
| EXT-API | N | Need to have alignment on how we can use the MEF interlude API for inter SP interactions. EXT-API and SO communications also has to be flushed out. |
| Modeling | N | Need to define the extensions to the currently agreed upon service model so that we can use it to represent an end to end Layer1(L1) Optical service. This L1 Optical service can span across multiple service providers which are controlled by one or more ONAP instances. Every SP can in turn have multiple domains that are controlled by external domain controllers. |