Page History

...

• • • • • • 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 configuration page and invoke it from VID; it would be an option for the post Dublin release): Impact on VID (open issue)
              • 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

...

• • • SO 
      • SO Catalog DB for SOL001/SOL004 support
      • BPMN Workflows and Recipes
      • VNFM Adapter
    • SDC 
      • Support SOL001/SOL004
      • VF Module deduction based on SOL001
    • SDNC
      • VNF-level Network Assignment, instead of VF-Module
    • A&AI
      • VNF-level Inventory Update
      • VNFM location
    • Policy (Stretch goal) - not for Dublin
      • Scale-Out support for ETSI-based scaling
    • Modeling
      • Support SOL001/SOL004
      • ETSI vs. ONAP-compliant VNFD
    • VID
      • External Virtual Link Configuration UI to map External CPs and Virtual Links such as IP Address

• • Open Items

• • • SDC transformation between ETSI and ONAP internal output and storing the original CSAR package.

    • VNF Application Configuration thru VNFM Adapter and VNFM is under discussion 

      • Architecture subcommittee is defining orchestration scenarios for application configuration

    • Better mechanism for VNFM Adapter to locate VNFMs (two methods are suggested)

      • How do we identify which VNFM to use?

    • Modelling for VNF and VF Modules; mapping between VF Modules and VNF

      • Assigning Network resources to SDNC; do we use preload data?

    • Continue to support existing non-ETSI SO workflows along with ETSI-based workflows

    • VNFM Adapter architectural direction; should it work as a thin layer or should it be evolved as a full-fledged NFVO in the future, e.g., handling grant by itself, updating resources in A&AI and SDNC?

      • After the VNF Instantiation, which component does update VNF resources in A&AI? VNFM Adapter or SO?

    • SOL001/SOL004 SO Representation (for Dublin, the second option was chosen)

      • Enhance SO Catalog Database? 

      • VNF_Package (vnfdid, vnfm_info, version, vnf_provider, product, vendor, etc.)

      • VNF_Package_Artifact (child database for VNF_Package, VNFD_URL, SoftwareImage_URL, Additional Files etc)

      • Store minimum reference in TOSCA_CSAR database table? This was chosen for Dublin

    • MultiCloud use (not for Dublin)