Page History

...

• 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).
  Goals 
  • 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.
    • Checking available host profiles of each zone to solve flavor matching (i.e., Host-Aggregates) (Stretch Goal).
  • Placement decisions for Affinity and Anti-Affinity among zones of target Cloud Region. Optionally, decisions go into compute hosts (for private cloud case).
  Stretch Goals
  • Defining Affinity and Anti-affinity rules in Policy (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded policy.
  • Specifying Affinity and Anti-affinity rules in homing/placement request (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded specification.
  • Distributed cloud modelling immediately relevant to F-GPS - a single cloud control plane (Cloud Region) to be able manage several distributed DC locations/zones. 

  • Leverage capacity alerts (significant change in capacity) from Model-driven Distributed Analytics work.

• Policy Tosca model API and ONAP CLI integration
  Goal 
  
  • Develop APIs in Policy for uploading policy tosca models for OOF.
  • Develop CLI for creating the policies including templates using ONAP CLI project. This will be extremely valuable in automating policy creation, one of the major pain points in Casablanca during integration tests.
• CMSO
  • Schedule Optimization with Automated Conflict Avoidance
  • Traffic Migration Workflow
• OOF PCI Optimization
• Slice creation and orchestration - Reach out to N.K. Shankaranarayanan
• Non Functional requirements
  Goals
  • Defining Affinity and Anti-affinity rules in Policy (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded policy.
  Stretch Goals
  
  • Defining Affinity and Anti-affinity rules in Policy (Stretch Goal). Until this is ready, evaluate with a manual/hard-coded policy.

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

Minimum Viable Product

...

• • Improve documentation. Document as you code. New features must have mandatory documentation along with code.

  • CII Silver badge; internal communication encrypted; role based access control and authorization for all calls

  • Move Helm Chart (OOM) at project level
  • CI/CD enhancement - Continuous Deployment (Comply with the requirements from Task force). Enhance existing CI jobs for Dublin.
  • Unit test coverage to 60% or 70%?
  Stretch Goals
  
  • Improve OOM deployment time for OOF helm charts. 

Use Cases

• Fine-Grained Placement Service (F-GPS)

• HPA - Hardening, Testing and Automation of vFW, vDNS, vCPE, VoLTE
• CCVPN ? 
• Change Management Dublin Extensions
• Consistent ID of a Cloud Region (Dublin)

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

• OOF-CMSO - ??

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.

...