Versions Compared

Key

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

...

  • The main goals of SNIRO are to:

    1. Provide a unified toolkit for developing optimization applications via extensible APIs. This facilitates developing new optimization applications independent of how the underlying optimization modules are implemented.
    2. Provide a library of optimization engines/solvers, data adapters (e.g. to A&AI, policy, SDC, SDN, DCAE). This will include an API for plugging other custom entities (custom data sources; proprietary or open source optimization engines/solvers; etc.)
    3. Provide a library for translation of policies to constraints for an optimization engine.
    4. Provide a resilient, scalable optimization framework for solving optimization/planning problems and constraint satisfaction problems.
    5. Provide a mechanism for interacting with ONAP-C (ONAP controller) to take actions based on the optimization solution.

     

    The term optimization here is used in the context of providing a solution (or set of solutions) for a problem specified in terms of the state (available resources, topology, objective, etc.) and additional constraints specified as a set of policies. This is different the use of optimization in other contexts such as “performance optimization”, “platform stability/reliability”, “scalability”, etc.  While such services may need information from optimization solutions (e.g. “when should one take an action”, “how much additional capacity is needed to ensure meeting a specific SLA”), they can be considered as applications that can utilize the optimization framework.

...

  • How does this project fit into the rest of the ONAP Architecture?
    • Provides optimization (placement, scheduling, network, license, and planning) as a service to other ONAP subsystems

    • Provides adapters to other ONAP systems for optimization application developers 

    • Project depends on A&AI, DCAE, SDC, SDN, and Policy,
      What other ONAP projects does this project depend on?
  • How does this align with external standards/specifications?
    • REST and Data Bus interfaces (service agnostic)
    • Models specified in SDC format
  • Are there dependencies with other open source projects?
    • Open source optimization solvers (GLPK/CBC, OR-Tools, these are pluggable)
    • Integration Testing
    • etc.Python eco-system

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

...