TABLE OF CONTENTS:

R6 5G-SPECIFIC USE CASES (Frankfurt Release)

Release 6 will be a "normal" release but with an extended M1 from June to Aug 29.

5G U/C COMMITMENTS BY PROJECT:

The following table indicates commitment by project. The impacts have been accepted and are supported by the PTL of each ONAP Platform component and corresponding Jira Tickets are in place. There are three states:

N/A = A "N/A" means that there is no interaction, no dependency, and no work for that Use Case for that component.

? = A "?" means that there is not final commitment from the PTL for that project, and no Jira ticket exists yet.

YES = This means that (1) PTL INFORMED & COMMITTED - has agreed to support the changes needed for that Use Case, (2) DEVELOPMENT SUPPORT - there is development (company) support (3) JIRA TICKETS - and a Jira ticket exists. Please see the corresponding WIKI page for that Use Case to find out more details on impact, PTL support and Jira Ticket(s).

NOTE: The CTRLR column includes CC-SDK, CDS, SDN-C, APP-C. Including what used to be SDN-R has been under the SDN-C "umbrella".

REQ = VNF Requirements Project. The VNF-RQTS project applies to both VNFs and PNFs. A "YES" here means that there are new requirements for the vendors.

Model S/C = Modelling Subcommittee. This U/C impacts the ONAP Platform Information and/or Data Model.

Ctrlr = This includes all of the controllers in ONAP including SDN-C, SDN-R, APP-C and VF-C

Stretch Goal (N/A) but if extra resources are available some changes may be made.

Note (1): x

Note (2): x 

5G USE CASE ASSESSMENT:

The following table was to assess whether use cases are related to 5G (are 5G specific) or whether they are general PNF use cases.

The General PNF use cases have been moved to their own wiki: General PNF Support Use Cases

5G Use Case MEETINGS:

Links to the 5G Meetings & recordings:

SUPPORTING DOCUMENTS:

R5 El Alto Release

EUAG has decided that R5 El Alto will be a "maintenance/technical debt" release.

https://wiki.lfnetworking.org/display/LN/EUAG+2019-04-09+meeting+minutes

The El Alto release will be shortened (3-month cycle) and focused on internal (tech) debt and defect backlogs. And every 5th ONAP release will be a maintenance release.

PTLs had taken short cuts to meet deadlines, working but want to make the platform more robust. PTL driven code fixes and code hardening.

S/W Enhancements (e.g. GUI enhancements) would be pushed to R6. Feature enhancements would be pushed to R6

R5 will be focused on Refactoring, JIRA backlog reduction, vulnerability issues, Test Coverage, Test Automation (CI/CD pipeline), Deployment procedure, Documentation.

R5 - Security Scans, scan code reports sent to PTL for major things to fix. Vulnerabilities have been built. Vulnerability management process. Security gates checklist.

SUMMARY: There will be no new Software development for new functionality in R5; but there will be Jira tickets worked on (PCI/SON); and modeling work for 5G RAN.