| Table of Contents | ||
|---|---|---|
|
Overview
...
What is this release trying to address
- Support TSC must have ONAP requirements mandatory Global Requirements Honolulu Release Requirements
implements as much TSC must feature as possibleScope Priority Committer Lead Resources Committed Epic Dependencies TSC Must haveSupport Global Requirement and selected Best practices as per Honolulu Release Requirements and Honolulu Impact View per Component high Adrian O'Sullivan, Priyadharshini B Rakesh Girija Ramesan Nair
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-533 - Stretch Goal in association with E2E Network Slicing -
- EXT-API impacts for support of TMF 628 APIs for KPI monitoring andJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-450 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-440 - Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
- Specification & modelling work on (modernized) TMF 628 for "On Demand" PM collection and future mapping to DES API's
- Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
...
- Slides presented covering the NBI requirement for E2E External API Framework: 5GNetworkSlicing_ExtAPI_20200610_v1.0.pptx
- Specification aspects only of the mapping to be covered during Honolulu Release within Honolulu Release
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key EXTAPI-450
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
...
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) |
|---|---|---|---|---|
| SDC: Catalog API | Exposes Service Catalog | TBD | TBD | https://wikidocs.onap.org/display/DW/SDC+API/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html |
| SO: Service Instantiation API | Requests for Service Instantiation | TBD | TBD | https://docs.onap.org/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html |
| AAI: Service Inventory API | Query for Service Inventory | TBD | TBD | https://docs.onap.org/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html |
| DMaaP: Events API | Query for AAI_EVENTS and SDC Distribution Events | TBD | TBD | https://docs.onap.org/projects/onap-externalapi-nbi/en/latest/consumedapis/consumedapis.html |
API Outgoing Dependencies
...
Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| TBD | TBD | TBD |
Resources
Please see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:externalapi
...
The milestones are defined at the Release Planning: Honolulu and all the supporting project agreed to comply with these dates.
...
Each project must edit its project table available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.