VF-C supports  vCPE use case in R3,  all VNFs are deployed through VF-C GVNFM . This page will describe describes how to use VF-C to instantiate NS

...

sample NS: 

...

VF-C installation 

VF-C interacts with other components through MSB, so VF-C installation depends on MSB installation

VF-C components need to register to MSB when starting, so MSB components should be installed first, you can ref the following link to install MSB.

http://onap.readthedocs.io/en/latest/submodules/msb/apigateway.git/docs/platform/installation.html

Note: In the following steps, we use ${MSB_IP} as the IP of msb_apigateway component.

1. Install vfc-nfvo-lcm component.
   
   
2. Install vfc-nfvo-gvnfmdriver component
   
   
3. Install vfc-gvnfm-vnflcm component
   
   
4. Install vfc-nfvo-db component

Package Onboarding

VF-C R3 support VNF/PNF/NS csar package upload from local csar file. VNF/PNF csar package should be uploaded first, then NS csar package can be uploaded.

Before onboarding a package,  should create one record first. 

1. Create VNF package record  in catalog DB
   
   
2. Upload VNF package to VF-C catalog
   xx
3. Create NS package record in catalog DB
   
   
4. Upload NS package to VF-C catalog

NS Life Cycle Management

Currently VF-C GVNFM support NS create/Instantiate/terminate/delete/heal.

VF-C R3 healing only suport restart a vm of an VNF. 

1. NS Create 
   
   
2. NS Instantiate
   
   
3. NS Heal
   
   
4. NS Terminate
   
   
5. NS delete