...
- How does this project fit into the rest of the ONAP Architecture?
Provides optimization (e.g. homing, scheduling, network, license allocation, and capacity planning) as a service to other ONAP subsystems
Provides adapters to other ONAP systems (e.g. policy, A&AI, SDC, etc.) for optimization application developers
- Uses REST and Data Bus interfaces in a service agnostic manner
- Models and artifacts are specified in SDC format, while rules/constraints are specified in Policy Service
- The homing and license allocation applications are expected to support the Multi-VIM Project
- The scheduling application (change management scheduling) is expected to support the Network Change Management Project
- What other ONAP projects does this project depend on?
- A&AI (e.g. network topology, cloud sites, service instances, scheduling/ticketing data)
- DCAE (e.g. cloud-level resource utilization)
- SDN-C (e.g. network utilization, available capacity in a VNF instance)
- SDC (e.g. available license artifacts)
- Policy Service (e.g. rules/constraints)
- Policy-driven VNF Orchestration
- How does this align with external standards/specifications?
- Are there dependencies with other open source projects?
- Open source optimization solvers (GLPK/CBC, OR-Tools, these are pluggable)
- Python eco-system (modules for schema validation, database adapters, etc.)
- While the code is primarily written in Python, we anticipate it to be a mixture of Java and Python
High level overview of SNIRO
Use case Description:
1. Homing Use Case
...