...

• MDONS use case

  Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-325

  Resources from Fujitsu
  • Extend the existing route optimization in OOF to support the MDONS use case. (MDONS use case)
• 5G Network Slicing

  Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-342

  Resources from Wipro, Huawei
  • Support 5G slice instantiation workflows, by providing selection decisions (5G - Network Slicing)
• SON Optimization 

  Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-345

  Resources from Wipro
  
  • Evolve the PCI optimizer to use ML/AI techniques
• CCVPN Transport Slicing

  Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-347

  (Basic TN NSSI Selection to be covered under 5G - Network Slicing use case)

Non - Functional Requirements:

Resources from Wipro (Huawei, Fujitsu to support where needed)

• Containers must have no more than one main process (REQ-365)
• ONAP projects must use only approved and verified base images for their containers (REQ-379)

• Each ONAP project shall define code coverage improvements and achieve at least 55% code coverage (REQ-349)

• Containers must crash properly when a failure occurs (REQ-366)
• Each project will update the vulnerable direct dependencies in their code base codebase (REQ-323)
• No root access to the database from application container (REQ-358)
• OOF to use cert initializers for certificates(REQ-361)
• Apply common Swagger style and documentation generation tools(REQ-386)

Stretch goals

• Functional requirements
  • CCVPN Transport Slicing - Impacts related to TN NSSI not covered under 5G - Network Slicing use case.

• Non Functional requirements
  
  • Python 3.6 to 3.8 migration (REQ-373)
  • Improve documentation. Document as you code. New features must have mandatory documentation along with code.

  • CII Silver badge; internal communication encrypted

  • Move Helm Chart (OOM) at project level
  • Unit test coverage beyond 55%
  • Improve OOM deployment time for OOF helm charts. 

...

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

...

Please fill out the centralized wiki page: Guilin 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.

...

Please refer to Guilin Defect Status.

• Risks

...

• • Meeting the non-functional requirement for CMSO project. There are no active contributers for the project right now. Requests have been sent for supporting to meet the non-functional requirements. 

Please update any risk on the centralized wiki page - Guilin Risks.

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...