...
- 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). Resources from IBM
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).
- Defining Affinity and Anti-affinity rules in Policy. Until this is ready, evaluate with a manual/hard-coded policy.
- Specifying Affinity and Anti-affinity rules in homing/placement request. 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 Resources from Intel
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 integration tests.
- CMSO
- Traffic Migration Workflow Resources from Orange
- Schedule Optimization with Automated Conflict Avoidance (Stretch goal based one resource availability)
- OOF PCI Optimization Resources from WIPRO, AT&T
- OOF PCI Solver and interface shall support at least two optimization objectives (e.g. minimize changes, minimize PCI confusion)
- OOF PCI Solver policy shall use a PCI range specified in the configuration policy
- OOF shall provide a joint PCI/ANR solver which will optimize PCI and also recommend a removal of a neighbor relation if there PCI allocation is difficult for a cell which also has a neighbor link for which the successful_handover KPI is below a pre-specified threshold
Non - Functional Requirements:
No commitments yet due to lack of resources
Stretch goals
- Slice creation and orchestration
- Consistent ID of a Cloud Region
- Non Functional requirements
- Improve documentation. Document as you code. New features must have mandatory documentation along with code.
- S3P: Footprint optimization
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%?
- Improve OOM deployment time for OOF helm charts.
...