Versions Compared

Old Version 12

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

compared with

New Version Current

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DRAFT PROPOSAL FOR COMMENTS

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

...

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 the deployability of the platform (Highest priority)Discovering and reusing shared resources when processing multiple homing requests in parallelServices Using ONAP platform
    • Homing multiple simultaneous instances of the service: queueing homing requests based on discovering dependency on shareable resources (resources from AT&T)
    • Considering Latency Reduction (in addition to geographical distances) for homing optimization 
    • Resource reservation and enhanced capacity checks during VNF homing
    5G Functional requirements:
  • 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 coverageSlice Optimization (Stretch goal)
    • POC for slice optimization
      • 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)

...

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

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

...

  • 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

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 Archiecture 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


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


Image Added


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. 


Gliffy
nameCasablanca dependencies
pagePin3

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
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11NA
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

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 NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)StatusTo fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out
Link toward the detailed API descriptionPolicyPolicy Client API to create, update and retrieve homing policies.Beijing ReleaseTBD

work in progress

AAIREST Web Service provided by AAI, to query available cloud-regions, and existing service instances where a new order can be placed.Beijing ReleaseTBD

   


work in progress
MultiCloudAPI to retrieve VIM capacities (infrastructure metrics model)Beijing ReleaseTBD
work in progress
MusicMusic client REST APIBeijing ReleaseTBD


  • API Outgoing Dependencies

API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description
Status
HAS APIAPI to submit homing requests, and retrieve homing solutions.Beijing ReleaseTBD


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, ...).

...

The following link shows the dependencies and their license information: Project FOSS dependencies for OOF.

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

...

  • 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: Target level 60% 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.

To fill out
Gaps identifiedImpactTo fill out
Homing - Capacity checks and capability checks are treated independent of each otherCannot guarantee capacity of a certain resource with a specific capability
Support for resource reservation not availableContention of resources can result in a homing recommendation not being realized during the actual spin up.

  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

Insufficient resources for delivering the functional features in the scope:

  • 5G - SON, Slice optimization
  • VNF Auto scale out
  • Change management scheduler

Limit the functional features to use Beijing features for homing

Prioritize the items in the scope into different priority levels and stretch goals


  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...