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

Version 1 Current »


VNF Developer

Responsibilities:

  • Develops VNF products, including those that may require hardware assisted acceleration.
  • Creates VNF descriptors (VNFDs) for inclusion into VNF packages with the help of VNFSDK.
  • Creates VNF packages with the help of VNFSDK.
  • Validates created VNFDs and VNF packages using VNFSDK.
  • Uploads VNFs to the Marketplace.

Desired Outcomes:

  • Being able to specify HPA capability requirements as part of the VNFD.
  • Being able to check correctness of requirement specifications using VNFSDK.

ONAP Service Designer

Responsibilities:

  • Ingests upload VNFs from the Marketplace.
  • On-boards downloaded VNFs.
  • Creates network services from downloaded VNFs and/or other network services.
  • Makes network services available through the SDC catalog.

Desired Outcomes:

  • Being able to ingest and onboard VNFs with HPA requirements
  • Being able to modify the VNFD content, including the HPA requirement settings
  • Being able to store HPA requirement information in the SDC catalog

ONAP Service Provider

Responsibilities:

  • Instantiates network services (and VNFs) selected from the SDC catalog.
  • Operates instantiated network services (and VNFs) and performs remediation actions as needed.

Desired Outcomes:

  • Being able to instantiate VNFs with specific HPA requirements using SO.
  • Being able to store HPA requirements associated with instantiated network services (and VNFs).
  • Being able to optimize VNF homing and component placement based on specified HPA capability requirements using OOF.
  • Being able to scale VNFs in compliance with specified HPA capability requirements using APP-C or VF-C.
  • Being able to create homing and placement policies that enable association of VNFs with pools of available infrastructure resources.
  • Being able to create homing and placement policies that enable association of users (parties) with pools of available infrastructure resources.

ONAP infrastructure Provider

Responsibilities:

  • Onboards and registers VIMs.
  • Manages available resource capacity.
  • Creates OpenStack flavors and host aggregates.

Desired Outcomes:

  • Being able to discover available HPA capabilities from on-boarded VIMs.
  • Being able to persist discovered HPA capability information in the AAI inventory database for use by OOF.
  • Being able to update stored HPA capability information in AAI, as conditions change.
  • No labels