Page History

...

• Proposed name for the project: projectnamePolicy Framework
• Proposed name for the repository: reponamepolicy/framework

Project description:

• This project will be dedicated to determine how policy is captured, translated, deployed and designed updated when designing and on-boarding VNF's and network services.
• Specification of Policy aspects related to a VNF/service during design and on-boarding.

FROM THE DEEP DIVE:

...

• .

Policy repository for storage and lifecycle management of policy

• Conflict Detection

Scope:

• 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)
  • Deliver requirements for Policy Conflict Detection and mitigation
  • Deliver requirements for capturing vendor-embedded policy
• 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
  • Identify how policy translation works
    • The A common framework for the decision engines/languages used
    • The translation tools needed
  • Identify the Enforcement points within ONAP
    • Common API design to support enforcement
• Deliver points of interoperability for Day2Day Operations
  • Identify how operations teams can update and deploy Policies
• Deliver points of interoperability to support Adaptive Policy (Stretch)
  • Reverse planning, inference rules, machine learning
• Specify any interface/API specification proposed,
• Identity a list of features and functionality will be developed.
• Identify what is in or out of scope. During the development phase, it helps reduce discussion.
  
  

...

• 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 - require models
    • 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?
  • APIs/Interfaces
  • Integration Testing
  • etc.

Resources:

• Primary Contact Person
  • Pamela Dragosh - AT&T
• Names, gerrit IDs, and company affiliations of the committers
  • Pamela Dragosh - AT&T
  • Jorge Hernandez-Herraro - AT&T
• Names and affiliations of any other contributors
  • Alex Vul - IBM
  • Avinash S - Huawei
  • Nermin Mohamed - Huawei
  • Bobby Mander - AT&T
• Project Roles (include RACI chart, if applicable)

Other Information:

• policy/common
• policy/engine
• policy/drools-pdp
• policy/drools-applications
• policy/docker
• link to seed code (if applicable)
• Vendor Neutral
  • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
• Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

...

Project Name:

• JIRA project name: Policy Framework
• JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: