Overview

Scope

What is this release trying to address?

Committed: 

Functional Requirements

• 5G Network Slicing REQ-440 - Getting issue details... STATUS Resources from Wipro, Huawei
  • Support 5G slice instantiation workflows, by providing selection decisions (5G - Network Slicing)
• SON Optimization  REQ-429 - Getting issue details... STATUS Resources from Wipro
  
  • Updated to existing ML models in PCI optimization.

Non - Functional Requirements:

Resources from Wipro, AT&T (Huawei to support where needed)

• ONAP projects must use only approved and verified base images for their containers (REQ-379)
• Each project will update the vulnerable direct dependencies in their codebase (REQ-439)
• Removal of GPLv3 from docker images ( OPTFRA-853 - Getting issue details... STATUS )
• Externalize configuration via consul ( OPTFRA-875 - Getting issue details... STATUS )

Stretch goals

• Functional requirements

• Non Functional requirements
  
  • Improve documentation. Document as you code. New features must have mandatory documentation along with code.

  • CII Silver badge; internal communication encrypted

   

Use Cases

• Hardening/Test Only
  • HPA - Hardening, Testing and Automation of vFW, vDNS, vCPE, VoLTE
  • Traffic Distribution
  • Change Management
• Extensions of existing use cases 
  • 5G E2E Network Slicing
  • 5G OOF-SON

Minimum Viable Product

• OOF-HAS - Homing/Placement Service 

• OOF-OSDF - Optimization Design framework

• OOF-CMSO - Change Management Schedule Optimizer

Functionalities

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.

Epics

Stories

Longer term roadmap

As the ONAP platform matures and new capabilities are introduced over time, the need for platform optimization services will grow along with it. The ONAP Optimization Framework is envisioned to handle this need as effectively as possible, by enabling creation of new optimization services with minimal or little new code development. The goal of OOF is to provide a growing set of core platform optimization services such as VNF placement and resource allocation (OOF-HAS), change management scheduling (OOF-CMSO), etc. OOF also supports many critical 5G Services' needs including SON optimizations and Network Slicing Optimizations. 

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

Sub-Components

• Homing and Allocation Service (HAS)
• Optimization Service Design Framework 
• Change Management Scheduling Optimizer (CMSO)

Architecture

High level architecture diagram

Platform Maturity

Please fill out the centralized wiki page: Honolulu Release Platform Maturity

• API Incoming Dependencies

List the API this project is expecting from other projects.
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 Outgoing Dependencies

API this project is delivering to other projects.

• Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

• Testing and Integration Plans

The following testing will be planned for OOF in this release:

• Unit Tests and Code Coverage: Maintain 55% code coverage 
• Continuous System Integration Testing (CSIT): Enhance existing CSIT functional tests to cover new features

• Gaps

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.

• Known Defects and Issues

Please refer to Guilin Defect Status.

• Risks

  • Meeting the non-functional requirement for CMSO project. There are no active contributers for the project right now. Requests have been sent for supporting to meet the non-functional requirements. 

Please update any risk on the centralized wiki page - Honolulu Risks.

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

• Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

• Documentation, Training

Please update the following centralized wiki: Honolulu Documentation.

That includes

• Team contributions to the specific document related to he project (Config guide, installation guide...).
• Team contributions to the overall Release Documentation and training asset
• High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
• Documentation includes items such as:
  • Installation instructions
  • Configuration instructions
  • Developer guide
  • End User guide
  • Admin guide
  • ...

Other Information

• Vendor Neutral

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.

• Free and Open Source Software

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.