...

• Harden the OOF platform (Highest priority)
  
  • Deployment scripts, CSIT, CI for different streams, Nexus image cleanup
  • Using Music as a service 
• Maintaining current S3P levels of the project as new functional requirements are supported (Highest priority)
  • Security enhancements progressing towards Silver badge
    • All internal communication encrypted
    • AAF integration - role-based access control and authorization for all calls (depending on Python support from AAF)
    • Code coverage: achieve 60% target code coverage
  • Performance: Creating a plan for performance improvements 
  • Manageability:
    • Adherence to log specification v1.2 - ONAP Application Logging Specification v1.2 (Casablanca)
    • Externalized config management
  • Usability
    • Adherence to ONAP API Common Versioning Strategy (CVS) Proposal
    • move all internal and external facing APIs to Swagger 2.0
• Homing enhancements improving the deployability of the platform (Highest priority)
  • Discovering and reusing shared resources when processing multiple homing requests in parallel
  • Considering Latency Reduction (in addition to geographical distances) for homing optimization 
  • Resource reservation and enhanced capacity checks during VNF homing
• 5G Functional requirements:
  • SON Optimization (High priority)
    
    • POC using OSDF
    • Health Checks, CSIT, Dockerization, K8S HELM Chart, S3P with 60% code coverage
  • Slice Optimization (Stretch goal)
    • POC for slice optimization
    • Health Checks, CSIT, Dockerization, K8S HELM Chart, S3P with 60% code coverage
  • Homing 5G RAN VNFs (High priority)
    
    • Extending the Homing feature developed in R2 for 5G RAN VNFs
• HPA enhancements  (High priority)
• Auto Scale Out Functional requirement (Low priority)
  • Homing in VNF Scale Out 
• Edge Automation through ONAP (High Priority)
  • HAS in Edge Orchestration 
• Change Management (Low priority)
  • Scheduler for CM (schedule VNF instance at specific time)
• OOF POC with Service Mesh (? priority)

...

• vCPE (supporting R2 homing workflows)

Minimum Viable Product

...

• OOF-HAS - Homing Service that can be provides optimized placement based on policy constraints, across multiple clouds and multiple sites

• OOF-OSDF - Optimization Design framework, that supports HAS, the Homing 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.

...

Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspectiveAs 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. 

Vision for OSDF:

OOF-OSDF is envisioned to be a collection of design time optimization libraries along with reusable runtime tools and microservices to facilitate and simplify the creation of new specific runtime optimization functionalities. The goal of OSDF is to avoid siloed optimization tools and associated duplicated efforts and overheads. For instance, the Homing Service, HAS (which was provided in the Beijing release) will not only contribute its reusable components to the framework, but also leverages the framework in its own feature development. Other potential optimization services that can be built using this framework include energy optimization in networks, optimal route selection for various network services, and radio access network (RAN) performance optimization. 

Vision for HAS:

OOF-HAS, or the Homing Service is a distributed resource broker that enables automated policy-driven optimized placement of services on a global heterogeneous platform using ONAP. HAS is architected as an extensible homing service that can accommodate a growing set of homing objectives, policy constraints, data sources and placement algorithms. It is service-agnostic by design and can easily onboard new services with minimal effort. HAS is designed to be used as a building block for both initial deployment, as well as runtime redeployment due to failures or runtime-capacity increase (scale-out). While the immediate deliverable of HAS in Beijing Release is to provide optimized homing/placement of services during the service instantiation workflows in ONAP,  HAS naturally extends to a general policy-driven optimizing placement platform for all platform placement functions, including placements of VMs, containers (e.g., for DCAE micro-services), ONAP Control Loops or VNF specific resources. HAS will also eventually allow placements of additional resource types such as licenses, VNF resources, etc.

Release Deliverables

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

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

...