Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 8 Next »

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

sample VNF:

sample NS: 

VF-C installation 

If you want to  try VF-C,  the small project set should include: VF-C , Multicloud, MSB, A&AI.

VF-C components need to register to MSB when starting, so MSB components should be installed first, you can refer 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-db component
    docker run -d -p 3306:3306 -p 6379:6379 --name vfc-db -v /var/lib/mysql nexus3.onap.org:10001/onap/vfc/db
    we use  ${VFC_DB_IP} as the IP of vfc-db component.

  2. Install vfc-nfvo-lcm component.
    docker run -d -p 8403:8403 --name vfc-nslcm -e MSB_ADDR=${MSB_IP}:80 -e MYSQL_ADDR=${VFC_DB_IP}:3306 nexus3.onap.org:10001/onap/vfc/nslcm

  3. Install vfc-nfvo-catalog component.
    docker run -d -p 8806:8806 --name vfc-catalog -e MSB_ADDR=${MSB_IP}:80 -e MYSQL_ADDR=${VFC_DB_IP}:3306 nexus3.onap.org:10001/onap/vfc/catalog

  4. Install vfc-nfvo-gvnfmdriver component.
    docker run -d -p 8484:8484 --name vfc-gvnfmdriver -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/gvnfmdriver

  5. Install vfc-gvnfm-vnflcm component.
    docker run -d -p 8801:8801 --name vfc-vnflcm -e MSB_ADDR=${MSB_IP}:80 -e MYSQL_ADDR=${VFC_DB_IP}:3306 nexus3.onap.org:10001/onap/vfc/vnflcm

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

    Pub/Sub Test
    curl -X POST \
      http://172.30.3.104:30280/api/vnfpkgm/v1/vnf_packages \
      -H 'Postman-Token: f9c45dea-b7bb-4acd-89e1-b9b1c3d70d8a' \
      -H 'accept: application/json' \
      -H 'cache-control: no-cache' \
      -H 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \
      -F 'userDefinedData= "key2": "value2"'
  2. Upload VNF package to VF-C catalog

    Pub/Sub Test
    curl -X PUT \
      http://172.30.3.104:30280/api/vnfpkgm/v1/vnf_packages/38037a12-a0d4-4aa4-ac50-cd6b05ce0b24/package_content \
      -H 'Postman-Token: 88ada218-86fd-4cd7-a06e-cc462f5df651' \
      -H 'cache-control: no-cache'
  3. Create NS package record in catalog DB

    Pub/Sub Test
    curl -X POST \
      http://172.30.3.104:30280/api/nsd/v1/ns_descriptors \
      -H 'Postman-Token: 71b11910-1708-471c-84bb-5b0dd8d214a2' \
      -H 'accept: application/json' \
      -H 'cache-control: no-cache' \
      -H 'content-type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW' \
      -F 'userDefinedData= "key1": "value1"'
  4. Upload NS package to VF-C catalog

    Pub/Sub Test
    curl -X PUT \
      http://172.30.3.104:30280/api/nsd/v1/ns_descriptors/79ca81ec-10e0-44e4-bc85-ba968f345711/nsd_content \
      -H 'Postman-Token: f16e4a54-a514-4878-b307-9b80c630166e' \
      -H 'cache-control: no-cache'

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 

    Pub/Sub Test
    xx
  2. NS Instantiate

  3. NS Heal

  4. NS Terminate

  5. NS delete



  • No labels