/
OOF Casablanca M1 Release Planning Template

OOF Casablanca M1 Release Planning Template

DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.


Overview

Project NameEnter the name of the project
Target Release NameCasablanca
Project Lifecycle StateIncubation
Participating Company AT&T, Huawei, Intel, OAM Technologies, VMWare

Scope

What is this release trying to address?

Committed: 

  • Harden the OOF development 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 (Frank Sandoval)
      • AAF integration - role-based access control and authorization for all calls (depending on Python support from AAF) (Frank Sandoval)
      • Code coverage: achieve 60% target code coverage
    • Performance: Creating a plan for performance improvements 
    • Manageability:
    • Usability

Functional Requirements:

  • HPA enhancements (resources from Intel)
    • Service Assurance - streaming telemetry about health of platform (CPU pinning, and NUMA) - primarily from OpenStack
  • Homing enhancements improving the deployability of Services Using ONAP platform
  • 5G SON Optimization (resources from Wipro, TechM, AT&T, Reliance Jio)
    • PCI optimization POC using OSDF
    • Health Checks, CSIT, Dockerization, K8S HELM Chart, S3P with 60% code coverage
  • Change Management (resources from AT&T)
    • VNF/PNF support - scheduler for Change Management. 
    • Targeting support for 5G use case.
  • CCVPN (resources from Huawei)

Stretch goals:

Use Cases

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

Epics

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Stories

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh


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. 

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.

Deliverable NameDeliverable Description
OOF-HAS

Executable, and source code for the Homing Service for the ONAP platform

OOF-OSDFExecutable and source code that provides optimization design framework support to optimizers like HAS

Sub-Components

  • 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 helps create new types of policy- and model-driven optimizers.

Architecture

High level architecture diagram


Sequence Diagram showing OOF interaction with other ONAP components during the Homing workflow:



ONAP Dependencies

The following are the dependencies for the project based on the scope for the Casablanca Release. The required dependencies have been identified based on the homing workflow requirements of Casablanca release. 


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.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance1

1

  • create plans for performance improvement

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11NA
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency22NA
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security1

1 with some progress towards 2

  • 60% code coverage
  • encrypted communication between components
  • AAF integration (depends on support for Python projects)

  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability11NA
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11 with progress on adherence to Logging v1.2 spec