Content Comparison

• Resource commitment:

  • Ericsson: primary contact: Byung-Woo Jun

• Usecase Lead:

  • Ericsson: Byung-Woo Jun

• TSC Contact:

  • Ericsson: Stephen terrill

• Participating ONAP Projects:

  • Implementation: SO, AAI, SDC (not in Dublin)

...

• • Vendor SVNFM must be "SOL003-compliant"
  • Providing SOL003 APIs for VNFM LCM, based on ETSI VNFLifecycleManagement
    • Use https://forge.etsi.org/gitlab/nfv/SOL002-SOL003/2.5.1/master/src/SOL003/VNFLifecycleManagement swagger for providing services
    • Create
    • Instantiate
    • Query
    • Grant request to SO VNFM Adapter, as a client
    • Life cycle notification
    • Terminate
  • Registration itself to ONAP (thru A&AI ESR) - Name, Type, Vendor, Version, URL, VIM, Username and Password
  • Providing Subscription Services for Life-cycle Management Notifications
  • Support of the "Direct Mode" of Resource Management only
    • After receiving a grant permission, the VNFM sends requests for resources directly to VIM
    • Invoking MultiCloud from VNFM is under discussion, but not for Dublin
    • The "Indirect Mode" of Resource Management is being discussed, but not for Dublin

...

• User Stories

  • TBD

• Use Cases

...

• Use Cases

• • Choose a use case for demonstrating the VNFM Adapter capabilities
  • Ericsson Internal Test:
    • A vendor provides their VNF Package and SVNFM for managing the vendor-specific VNF package. 
    • For the SO VNFM Adapter NBI and SOL003-SBI interface validation, Ericsson SVNFM is used for the internal testing
  • Integration Test:
    • For the integration testing, generic/dummy VNF package and VNFM simulator are provided.
    • The generic/dummy VNF package is to test onboarding and SOL001 parameters extraction during SOL003-based API parameters, such as descriptor_id, flavor, etc. 
    • VNFM simulator is a vendor-neutral SOL003-compliant VNFM, which supports SOL003 responses and message exchanges.

• VNFM Adapter Sub-components

  
  

  

  • 
    
    • SO VNFM Adapter component is a sub component of SO; utilizing docker image and container manged.
    • North Bound Interface (NBI)
      • RESTful APIs that support createVnf, instantiateVnf, queryVnf, grantVnf, TerminateVnf
      • Its APIs are SO specific; i.e., not SOL003-based ones
    • Business Logic layer
      • It is invoked by the NBI and provides business logic for createVnf, instantiateVnf, queryVnf, terminateVnf
      • SDNC and A&AI access to collect assignment and VimConnectionInfo
      • Accesses SdcPackageProvider for getting SOL003 package(s) and parameters
      • SdcPackageProvider
        • Supports SOL001/SOL004 package management
        • Provides getPackage, getVnfdId, getFlavorId, getVnfNodeProperty
        • Provides getPackage(s), getVnfd, getArtifactFile for SVNFM
        • Uses SDC Tosca Parser
      • GrantManager
        • Provides requestGrantForInstantiate REST API for SVNFM
        • Invokes OOF for homing decision; HPA support, and/or non-OOF decision
      • SOL003Lcn APIs
        • Supports VnfIdentifierCreationNotification, VnfIdentifierDeletionNotification, VnfLcmOperationOccurrenceNotification
    • SOL003 Communication Layer
      • It is a thin REST client layer, which sends SOL003-compliant requests to SVNFMs and receives responses/notifications from SVNFM.
      • For Grant, it provides the Grant REST endpoint for SVNFMs.

...