DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Project Name | Enter the name of the project |
---|---|
Target Release Name | Amsterdam |
Project Lifecycle State | Incubation |
Participating Company | Amdocs, AT&T, Bell Canada, Century Link, China Mobile, China Telecom, Ciena, Cisco, Ericsson, Huawei, IBM, Intel, Netcracker, Orange, PCCW Global, Verizon |
Common APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP while using their existing BSS/OSS environment minimizing customization.
Focus: Service Instantiation; License Management; Network Address Space Management
Use Cases
Minimum Viable Product
The MVP allows for the definition of BSS/OSS - ONAP APIs that:
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
The External API Framework project describes and defines the APIs between ONAP and External Systems, including ONAP interfaces targeted on BSS/OSS, peering, B2B, etc. Proposed initial focus may be on the Common APIs between ONAP and BSS/OSS. Common APIs between ONAP and BSS/OSS allow Service Providers to utilize the capabilities of ONAP using their existing BSS/OSS environment with minimal customization.
Scope:
initial focus is likely to be: “Service provisioning configuration & activation”, "License management", and “Address allocation management”
Definition of Use Cases, Interactions, and Information Model engaging service providers and BSS/OSS vendors
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
---|---|
Functional Reference Architecture and Target Capabilities | Functional reference architecture (MEF LSO mapping, Interface Reference Point definition, etc.) Note that the BSS/OSS to ONAP APIs are relevant to the MEF LSO Legato Interface Reference Point. Include deployment scenarios. Functional description of target ONAP capabilities for interactions with BSS/OSS |
Use Cases | Identify BSS/OSS – ONAP Use Cases and interactions |
UML Models | UML Information Models for: Service Instantiation; Licence Management; and Address Space Management |
API Definitions | API Definitions for: Service Instantiation; Licence Management; and Address Space Management |
List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
Service Instantiation | SO Service Instantiation API | Date | Date | Link toward the detailed API description |
Catalog | SDC Catalog API | Date | Date |
API this release is delivering to other releases.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
Service Instantiation API Definition | Revised SO Service Instantiation API. Jointly with SO team. | 24 Aug 2017 | Date | Link toward the detailed API description |
License Management API Definition | License Management API | 24 Aug 2017 | ||
Address Space Management API Definition | Address Space Management API | 24 Aug 2017 |
Only modeling tools, e.g., Eclipse Papyrus.
Only models and API definition. No implementation as part of this project.
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
Gaps identified | Impact |
---|---|
To fill out | To fill out |
Provide a link toward the list of all known project bugs.
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
Risk identified | Mitigation Plan | Contingency Plan |
---|---|---|
To fill out | To fill out | To fill out |
Fill out the Resources Committed to the Release centralized page.
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Date | Project | Deliverable |
---|---|---|
10 JUL 2017 | ExtAPI | Functional Architecture and Target Capabilities |
17 JUL 2017 | ExtAPI | High level Use Cases |
31 JUL 2017 | ExtAPI | UML Model Service Instantiation |
31 JUL 2017 | ExtAPI | UML Model License Management |
31 JUL 2017 | ExtAPI | UML Model Address Space Management |
24 AUG 2017 | ExtAPI | API Definition Service Instantiation |
24 AUG 2017 | ExtAPI | API Definition License Management |
24 AUG 2017 | ExtAPI | API Definition Address Space Management |
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.