...
- 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
vnf-o
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.
...
- JIRA project name: Policy FrameworkDriven VNF Orchestration
- JIRA project prefix: Policyvnf-o
Repo name:
Lifecycle State: incubation
Primary Contact: Alex Vul
Project Lead: Alex Vul
mailing list tag [policyvnf-o]
Committers:
pdragosh@research.att.com AT&T
...