Versions Compared

Old Version 10

changes.mady.by.user Pamela Dragosh

Saved on

compared with

New Version 11

changes.mady.by.user xinyuan wang

Saved on

Key

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

...

  • Deliver points of interoperability within ONAP for VNF and network service On-boarding to capture policy/rule expressions VNF vendor specific policies and network service policies.
    • Classification of Policies
      • Placement
      • Resource allocation
      • Remediation Actions (eg. Scaling)
      • Compliance Checking (eg. Security)
      • SLA
      • Health
      • Control Loops
      • Platform Level Policies
      • Governance
        • Users
        • Customers
    • Deliver where/how Policies are expressed
      • Policy Domain Specific Language(s) (DSL) - work with the Modeling project to define how policy expressions are captured
      • Policy Design GUI - work with SDC project to integrate the Policy Design GUI during VNF/Service design for capturing Policy Expressions
    • Deliver requirements for Policy Conflict Detection and mitigation
    • Deliver requirements for capturing vendor-embedded policy (Stretch)
  • Deliver points of interoperability within ONAP in which captured policies are translated into enforceable actions/outcomes
    • Identify how translation of DSL will work
      • Instantiation
      • Orchestration
      • Remediation
      • Controllers
      • Control Loop
        • Analytics, Collectors and Microservices
        • CLAMP
    • Identify how policy translation works
      • A common framework for the decision engines/languages used
      • The translation tools needing development
    • Identify the Enforcement points within ONAP to support the Use Cases
      • Common API design to support enforcement
    • Deliver points of interoperability for Day2Day Operations
      • Identify architecture, flow and API's for how operations teams can update/deploy/un-deploy Policies
    • Deliver points of interoperability to support Adaptive Policy (Stretch)
      • Reverse planning, inference rules, machine learning
    • Deliver architecture and points of interoperability for Policy Distribution
      • How Policy Decision Engines are deployed/un-deployed
      • What policies are supported in the various Decision Engines
      • Deliver API and flow for updating policy with the decision engines and the enforcement points
  • Support new policy related to the scaling and healing in VoLTE use case
    • Auto-scaling
    • Auto-healing

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possible
    • What other ONAP projects does this project depend on?
      • Modeling - provide input for Policy Expression
      • VNF SDK
      • SNIRO
      • SDC
      • Control Loop
      • CLAMP
      • DCAE
      • Orchestration
      • Controllers
      • Basically every component in ONAP should be policy-enabled
  • How does this align with external standards/specifications?
    • APIs/Interfaces
    • Information/data models
  • Are there dependencies with other open source projects?
    • XACML (github.com/att/xacml)
    • Drools (drools.org)

...