Project Name:
- Proposed name for the project:
projectname
- Proposed name for the repository:
reponame
Project description:
- This project will be dedicated to determine how policy is captured and designed 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 aspects related to a VNF/service needs, e.g. for lifecycle management of VNF/service, e.g. scaling, placement, security, fault response, telemetry, SLA, ... including how policies are designed/packaged/onboarded.
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)
- Health
- Control Loops
- Deliver where/how Policies are expressed
- Classification of Policies
- Deliver points of interoperability within ONAP in which captured policies are translated into enforceable actions/outcomes
- Identify how translation works for these types of policies
- Instantiation
- Orchestration
- Remediation
- Control Loop
- Identify how translation will work
- The decision engines/languages used
- The translation tools needed
- Identify the Enforcement points
- Identify how translation works for these types of policies
- Instantiation and Day2Day Operations
- 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.
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?
- 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
- Names, gerrit IDs, and company affiliations of the committers
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- 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
Key Project Facts
Project Name:
- JIRA project name:
- 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: