You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Project Name:

  • Proposed name for the project: Policy driven VNF orchestration
  • Proposed name for the repository: 
            • policy/api - Policy CRUD and PEP enforcement client code
            • policy/common - common shared modules
            • policy/pdp - Policy Decision Engines
            • policy/pap - Policy Administration (Backend)
            • policy/gui - Policy Administration GUI (Frontend)
            • policy/docker - Policy docker image

Project description:

  • Some VNF products have been optimized to take advantage of hardware platform specific capabilities, such as NUMA or CPU pinning in order to maximize their performance and throughput. 
  • During VNF development, hardware platform requirements for such VNFs are defined in the "VNF descriptor" (i.e. VNF model) and stored in the VNF package (CSAR) as part of the CSAR metadata. 
  • When an "optimized" VNF is on-boarded and subsequently instantiated as part of a network service instance, it has to be deployed on specific compute resources that exhibit required hardware platform capabilities. Furthermore, some VNFs are implemented in a way that allows them to operate both in optimized and non-optimized manner, depending on resource availability, entitlements and licensing.
  • Once instantiated, VNFs may require scaling or other remediation actions in order to maintain service levels. Additional VNF resources may need to be added or removed and existing resources may need to be "re-sized" or entirely replaced, depending on operating events and conditions.
  • This project will extend the ONAP policy framework to enable policy driven resource allocation and placement during VNF instantiation and subsequent operation.

Scope:

  • This project will implement functionality to transcode VNF hardware infrastructure requirements, found in the VNF package metadata, into policy constraints within the ONAP policy framework.
  • This project will implement functionality to transcode VNF vendor supplied VNF operational policies, found in the VNF package metadata, into operational policy constraints within the ONAP policy framework.
  • 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
  • This project will implement appropriate orchestration-time policy enforcement points to guide the allocation and network placement of VNF resources during instantiation, operation and remediatio

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?
    • This project will embrace and extend the already existing ONAP policy framework
    • Please Include architecture diagram if possible
    • What other ONAP projects does this project depend on?
      • Modeling - provide input for Policy Expression
      • A&AI
      • APP-C
      • VNF Design
      • Policy Creation
      • VNF SDK
      • SDC
      • DCAE
      • Orchestration
      • Controllers
  • How does this align with external standards/specifications?
    • ETSI NFV IFA11
    • ETSI NFV SOL01
    • ETSI NFV SOL04

Resources:

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

Other Information:

  • link to seed code (if applicable)
    • N/A
  • Vendor Neutral
    • Yes
  • Meets Board policy (including IPR)
    • Yes

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


Key Project Facts

Project Name:

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

Repo name:
Lifecycle State: incubation
Primary Contact: Alex Vul
Project Lead: Alex Vul
mailing list tag [policy] 
Committers:
pdragosh@research.att.com AT&T

jh1730@att.com AT&T

rs8887@att.com AT&T

jh7358@att.com AT&T

*Link to TSC approval: 

Link to approval of additional submitters: 

  • No labels