Project Maturity Review for VFC

Project Name:

Virtual Function Controller Project

Project Description:

ONAP VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS.

Role	First Name Last Name	Linux Foundation ID	Email Address
PTL	Yuanhong Deng	dengyh	yuanhongdeng@chinamobile.com
Committers	Yan Yang	yangyan	yangyanyj@chinamobile.com
	maopeng zhang	maopengzhang	zhang.maopeng1@zte.com.cn
	hongyu zhao	hongyuzhao	zhao.hongyu@zte.com.cn
	victor gao	g310497	victor.gao@huawei.com
	Haibin Huang	haibin	haibin.huang@intel.com
	Anatoly Andrianov [Nokia]	caa028	anatoly.andrianov@nokia.com

The Virtual Function Controller (VFC) Project has been an active ONAP Project since Amsterdam and has participated in all releases through Frankfurt.

How long the project has been an active: At launch
Release Participation: All ONAP releases
Engagement levels for past releases (up to 3):
- Commits per Release:
- Contributors per Release:
- Companies per release:

VFC is pretty much involved in all use cases, since it's the key module in the runtime execution of any of the usecases.

The key use cases that the VFC project has contributed to are the following:

vCPE

CCVPN

VoLTE

E2E 5G Network Slicing

ONAP - ETSI alignment improvements

Last Architecture Review was for Frankfurt on Jan' 2020 with the results posted here: VF-C Frankfurt Architecture Review and ARC VFC Component Description – Guilin (R7) Release

VFC is divided to several modules each providing an unique functional feature necessary in the orchestration process.

VFC project intends to provide a plug and play architecture based on the business needs of the users.

Details of the VFC components and its functionalities are explained further in the following doc