...
- A mechanism to handle ingestion of VNF vendor supplied operational policies specified in the VNF Model, and their federation with Operator-specified policies
- Policy DSL support for specification of VNF centric policy constraints for:
- Handling of VNF resource inventory/optimization
- Homing and placement of VNF components
- Allocation of VNF compute, storage and network resources
- Handling of VNF remediation actions, including VNF scaling
- This project will implement programmatic and declarative interfaces required to support:
- Management of VNF related policies, including creation, modification and deletion
- Ability to override/modify policies supplied as part of the VNF package metadata
Architecture Alignment:
NOTE - Functional components in RED DOTTED LINES denote project scope and dependencies
- How does this project fit into the rest of the ONAP Architecture?
NOTE - Functional components in RED DOTTED LINES denote project scope and dependenciesThis project will embrace and extend the already existing ONAP policy framework
- What other ONAP projects does this project depend on?
Modeling - provide input for Policy Expression
| Project | Dependency |
|---|---|
| Policy Framework | Closed loop policy specifications |
| Multi-VIM | Discovery of available VIM level compute resource capabilities |
| A&AI | Persistence of VIM supplied compute resource hardware platform capabilities. Interfaces for access to persisted data. |
| SO | Enforcement of VNF instantiation policies |
| APP-C |
...
| Enforcement of VNF operation and remediation policies | |
| VF-C | Enforcement of VNF instantiation, operation and remediation policies |
| DCAE/Holmes | Collection of data relevant to health and state of compute resource hardware platform level capabilities |
| SNIRO | Enforcement of VNF resource optimization policies |
| SDC | Extraction and persistence of VNF vendor supplied hardware platform requirements |
...
- How does this align with external standards/specifications?
- ETSI NFV IFA11
- ETSI NFV SOL01
- ETSI NFV SOL04
- How does this align with external standards/specifications?
- XACML (github.com/att/xacml)
- Drools (drools.org)
Resources:
- Primary Contact Person
- Alex Vul - Intel
- Pamela Dragosh - AT&T
- Names, gerrit IDs, and company affiliations of the committers
- Pamela Dragosh - AT&T
- Jorge Hernandez-Herrero - AT&T
Names and affiliations of any other contributors
Pamela Dragosh pdragosh AT&T pdragosh@research.att.com Bedminster, NJ USA, EST, UTC-4 Jorge Hernandez-Herrero jhh AT&T jh1730@att.com USA, CST Alex Vul avul Intel alex.vul@intel.com Pacific Avinash S Huawei avinash.s@huawei.com Bangalore, India, UTC +5:30 Nermin Mohamed Huawei nermin.mohamed@huawei.com Bobby Mander AT&T bobby.mander@att.com Middletown, NJ USA, EST, UTC -4 Brian Hedstrom ARM Ankit Patel AT&T ankit@research.att.com Bedminster, NJ USA, EST, UTC -4 Ralph Straubs AT&T rs8887@att.com USA, CST Jim Hahn AT&T jrh3@att.com Ding Yi
ZTE ding.yi5@zte.com.cn Beijing, China, UTC +8 Xinyuan Wang
ZTE wang.xinyuan1@zte.com.cn Beijing, China, UTC +8 - Project Roles (include RACI chart, if applicable)
- Primary Contact Person
Other Information:
- link to seed code (if applicable)
- N/A
- Vendor Neutral
- Yes
- Meets Board policy (including IPR)
- Yes
- link to seed code (if applicable)
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: Policy Driven VNF Orchestration
- JIRA project prefix: policy-vnf
Repo name:
Lifecycle State: incubation
Primary Contact: Alex Vul, Pamela Dragosh
Project Lead: Alex Vul, Pamela Dragosh
mailing list tag [policy-vnf]
Committers:
pdragosh@research.att.com AT&T
jh1730@att.com AT&T
*Link to TSC approval:
Link to approval of additional submitters: