Agenda:

Meeting Date

Item

Submitted by

Required time

Notes

15 Aug

R1 outstanding items:

  1. VF-C Questions
  2. WAN service model
  3. Workflow Designer
Michael Lando45 min

Weekly calls – cancel the 2nd recurring meeting

Michael Lando5 minnot discussed

Show the community where to add proposed R2 backlog items

Michael Lando5 minNot discussed


discussion points:

  • VFC presentation + questions and SDC response:


  • presentation from VNF-SDK regarding their suggestion for providing meta data to the SO and VNC


  • presentation by Amdocs regarding gaps identified as part of the work to support the importing of Tosca into SDC


Items:

  1. SDC is not storing VNF image(s) in R1.
  2. Need further discussion about image management and information for R1.
  3. SDC integration with VNFSDK's marketplace is currently in lower priority compared to other R1 tasks. Might need volunteers to do the implementation.
  4. Follow-up discussion has been scheduled for Wed Aug-15 6-8 AM PDT (9-11 AM EDT). 
    Items for discussion :
    1. Suppor for Open-O types
    2. TOSCA VNF package format
    3. Support for VNF images in R1 
    4. Workflow designer integration in R1



3 Comments

  1. Here is the image handling suggestion I shared on Wednesday call:

    • During the onboarding process images are not uploaded into SDC catalog
      • In R2 images could be pushed to designated image storage during the onboarding process (based on configuration/driver)
    • Image should be uploaded manually to the desired location
    • Appropriate property should be updated manually during resource onboarding or service design with the image uri
      • sw_image (tosca.artifacts.nfv.SwImage)
      • file_url (tosca.nodes.nfv.ext.ImageFile)
    • VF-C download image from the location specifies in the descriptor
      • sw_image (tosca.artifacts.nfv.SwImage)
      • file_url (tosca.nodes.nfv.ext.ImageFile)

     

    1. Could we add a SwImageDesc.json file as artifacts in the VNF Package? In the SwImageDesc.json, image parameter can be described.

      SwImageDesc.json format suggestion:

      [{  

      "name": "<name>",  

       "version": "<version>",

       "containerFormat": "<containerFormat>",  

      "diskFormat": "<diskFormat>",   

      "minDisk": "<minDisk>",  

      "minRam": "<minRam>",   

      "swImage": "<swImage>”

       }]

      Thanks