Versions Compared

Old Version 8

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

compared with

New Version 9

changes.mady.by.user Shankaranarayanan Puzhavakath Narayanan

Saved on

Key

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

...

  • Harden the OOF platform (Highest priority)
    • Deployment scripts, CSIT, CI for different streams, Nexus image cleanup
  • 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:
    • Usability
  • 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 Low priority)
      • Extending the Homing feature developed in R2 for 5G RAN VNFs
  • HPA enhancements  (High priority)
  • Auto Scale Out Functional requirement (Low priority)
  • Edge Automation through ONAP (High Priority)
  • Change Management (Low High priority)
    • Scheduler for CM (schedule VNF instance at specific time)
  • OOF POC with Service Mesh (? priority)

...

  • vCPE (supporting R2 homing workflows)

Minimum Viable Product

Describe the MVP for this release.Maintaining the current S3P levels, hardening existing functional features. 

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.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance11
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11
  • 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
Resiliency22
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security11 with some progress towards 2
  • 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
Scalability11
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11 with progress on 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
Usability11
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...