...

• F-GPS - Main purpose of F-GPS (a.k.a. ONAP-Valet) is, with considering new placement policies, to precisely check capacity & capability of target Cloud Region and then, to determine VNF placements (i.e., target zone for each workload (VDU) of VNF). Resources from IBM
  • Capacity & Capability checking for an OpenStack cloud
  • Checking the number of zones of the target Cloud Region to solve the Anti-affinity rules.
    • Checking available capacity of each zone to solve Affinity rule.
• Upgrade to new Policy lifecycle API Resources from Intel, AT&T
  
  • Enhancements to policy specification: Estimated changes in Policy specification in R5
  • Enhancements in policy retrieval: Estimated changes in policy retrieving
• CMSO 
  
  • Schedule Optimization with Automated Conflict Avoidance
    
• 5G Network Slicing
  • Support 5G slice instantiation workflows, by providing selection decisions (5G - Network Slicing)
• SON Optimization Resources from WIPRO
  • OOF shall provide a joint PCI/ANR solver which will optimize PCI and also recommend a removal of a neighbor relation if there PCI allocation is difficult for a cell which also has a neighbor link for which the successful_handover KPI is below a pre-specified threshold. 
  • Evolve the PCI optimizer to use ML/AI techniques (stretch)

...

• Approved New use cases:
  • 5G Network Slicing
  • Component Upgrades to new Policy Lifecycle API
  • CCVPN - Route optimization
• Hardening/Test Only
  • HPA - Hardening, Testing and Automation of vFW, vDNS, vCPE, VoLTE
  • Traffic Distribution
• Extensions of existing use cases
  • 5G OOF-SON (low priority)
  • Change Management Frankfurt Extensions (low priority)
  • Fine-Grained Placement Service (low priority)

Minimum Viable Product

...

• OOF-HAS - Homing/Placement Service 

• OOF-OSDF - Optimization Design framework

• OOF-CMSO - Change Management Schedule Optimizer
• OOF-FGPS - Fine grained placement service

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 perspective.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

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

...

Sub-Components

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

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Architecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.

Image Added

Platform Maturity

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

...

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

...

• Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.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.

...

Please update any risk on the centralized wiki page - Frankfurt Risks

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...