Date

10AM EDT

To Join: https://zoom.us/j/287367106

Discuss

  • Introductions
  • VNF Requirements Outline for TOSCA VNF Package Andy Mayer
    • Requirements should be tied to platform support for the current release
    • May use "objectives" for future looking capabilities that do not interfere with platform in current release
    • May use "guidelines" section to describe future capabilities without specific requirements.
    • Focus is on Casablanca platform support.
    • Need developers guide addendum (based on SOL001)
    • Use VNF SDK to provide guidance
    • Some manual on-boarding will still be necessary
    • Need to describe limitations in Introduction of guidelines Thinh Nguyenphu
    • CSAR section Andrei Kojukhov
    • TOSCA SDC Section Andy Mayer
    • HPA Alexander Vul
    • VES Alok Gupta (See guidelines section 7.4)
    • Andy Mayer will create wiki page
    • Need initial content by M4 (stable outline and numbered requirements, can bug fix and work informative text afterwards)
  • TOSCA Orchestration in ONAP Topic (need to discuss in architecture)
    • Cloudify orchestration will no longer be used.
    • ONAP needs one single TOSCA Parser
    • Need to decide on how SO will perform TOSCA Parsing and Orchestration
    • This topic needs to further discussion in the Architecture Sub-committee
    • Agree on single format of VNF Package and Descriptor
    • Alexander Vul to put together problem statement
    • F2F end of October Arch meeting at IBM in Montreal (29 and 30th)


Last Time

  • VNF Requirements Tasks Steven Wright and Andy Mayer
  • Previous Items:
  • NSD On-boarding  Gil Bullard
  • Modeling Update Kevin ScaggsJessie S Jewitt
    • References across sub-models is having issues (may be Papyrus issue). For now, remove circular references in models.
    • R2 model is in Papyrus, R3 updates are in progress
    • Runtime contribution on VNF and VNFC being modeled
    • About 90% of VES model is incorporated.
    • Doing updates in working branch (does not indicate any level of approval)
      • But needs commits into repo
      • May need additional committers for model repo (ONAP Modeling Project)
      • Master branch commits need to follow review process before commits.
      • Whole sub-model needs to move to Master branch (Gerrit "Cherrypick") when "approved"
      • Need process to use stereotypes to represent maturity of pieces of sub-model.
  • Discussion on ETSI VNFD on External Connection Points Arun Gupta
    • VNF Ext CPD maps to either VDU CPD or Virtual Link Desc
    • In cases where Ext CPD Maps to Virtual Link Desc, how is this Ext CPD realized? Is it a CP on an internal Router
    • First check SOL001 to understand DM representation. Perhaps follow-up with ETSI SOL and Editor of IFA015 to see get better understanding.
  • Resource definition in HEAT and TOSCA Alexander Vul
    • vCPE VNFs being translated from HEAT to TOSCA. There is infrastructure flavor id for VNF in HEAT.
    • How is this infrastructure flavor transformed into TOSCA VNFD (encoding of infrastructure is not present)?
    • Flavor ID should be mapped to TOSCA VNFD requirements.
  • Tiger team to recommend updates to SOL001 for on-boarding based on vCPE Alexander Vul




VNF Package Security Recomendation