Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • SO-ETSI-VNFM Adapter for Dublin Presentation slide deck at ONAP Paris 2019

...

    • Vendor SVNFM must be "SOL003-compliant"
    • Providing SOL003 APIs for VNFM LCM, based on ETSI VNFLifecycleManagement
    • 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

...

          • extVirtualLinks data population
            • VNFD does not define external virtual links, but it lists the external virtual links as requirements for the VNF.
            • If the connection point ip_address_assignment is set to false, no extVirtualLinks ip address assignment is necessary.
            • In this case, VIM will assign IP addresses dynamically.
            • This could be an option for the Dublin release for simplifying the solution.

...

            • If the connection point ip_address_assignment is set to true, set extVirtualLink ip address assignment with configuration data from the user input or a preload file.
              • UI solution (need to build an UI; it would be an option for the post Dublin release)
                • Parse VNFD and extract a list of external virtual links
                • Map the external virtual links to the corresponding connection points, and read ip_address_assignment and number_of_ip_address value
                • Render the external virtual links
                • For each external virtual link, render the ip_address_assignment entry fields based on the number_of_ip_address value
                • User configures the mapping and the UI stores the mapping in the database
                • VNFM Adapter retrieves the mapping from database and fill up the extVirtualLink parameters based the mapping
              • Preload configuration solution (it would be an option for the Dublin release)
                • For the VNFD, pre-configure the mapping between the external virtual links and the ip addresses
                • VNFM Adapter retrieves the mapping from preload data and fill up the extVirtualLink parameters based on the mapping

...