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 3 Next »

Problem aiming to solve

Incorporate the changes to the ETSI VNF Descriptor information model from version 2.5.1 to version 2.7.1 .

Changes

Types:

  1. Add new type VipCpd which is a generalization of type Cpd and describes a requirement to allocate one or a set of virtual IP addresses.
  2. Add new type CheckSumData which provides a mechanism to verify SwImages
  3. Add new type VnfInterfaceDetails which specifies the details of an interface produced by the VNF on te Ve-Vnfm  reference point



Other changes:

  1. VDU::configurableProperties - Cardinality changed to 0..1; cardinatlity 0 when the VNFCs do not have configurable properties
  2. CPD::cpProtocol & CPD::trunkMode - Cardinality changed to allow 0
  3. VduCpd::vnicType: Added SMART-NIC as an allowable value
  4. SwImageDesc:Provider - New attribute of type string with cardinality 0..1 which describes the provider of the software image.
  5. VnfDf:supportedVnfInterface - New attribute of type VnfInterfaceDetails with cardinality 0..N which indicates which interfaces the VNF produces and provides additional details on how to access the interface endpoints.
  6. VnfConfigurableProperties::vnfminterfaceinfo - New attribute with cardinality 0..1 which contains info enabling access to the NFV-MANO interfaces produced by the VNFM
  7. VnfConfigurableProperties::vnfmOauthServerinfo - New attribute with cardinality 0..1 which contains info to enable discovery of the authorization server protecting access to the VNFM interfaces
  8. VnfConfigurableProperties::vnfOauthServerinfo - New attribute with cardinality 0..1 which contains info to enable discoveryof the authorization server to validate the access tokens provided by the VNFM when the VNFM accesses the VNF interfaces





  • No labels