2018-09-07Meeting notes

Date

Sep 7, 2018 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 (Unlicensed)

  • CSAR section @andreik

  • TOSCA SDC Section @Andy Mayer

  • HPA @Alex Vul

  • VES @alok411 (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

  • @Alex 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
  
  

  • Need to also address VNF Package Requirements based on SOL004
    
    

    • Create JIRA Task

    • Recruit contributors

  • Mapping of VNF Requirements to VNFD on-boarding info model

    • Use of Reference Stereotype in Papyrus

  • Need update to Section 5.1 with numbered requirements;

    • See: https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/index.html

    • need new material by M4 Milestone: 28 September 2018

    • Work on outline for rearrangement of Section 5.1

    • Use JIRA for new text where we can (or point to Wiki for content from JIRA)

    • VNF Test Cases identifies normative requirements. Will need something similar for TOSCA.

      • See: https://onap.readthedocs.io/en/latest/submodules/vnfrqts/testcases.git/docs/index.html

    • See how Section 7.2 maps to model definition (VNF On-boarding and Package Management)

    • VNF Requirement calls are Tuesday at 8AM eastern.

• Previous Items:

• NSD On-boarding  @Gil Bullard
  
  

  • See: Proposed ONAP Runtime Support for Network Service Onboarding.pptx

• Modeling Update @Kevin Scaggs@Former user (Deleted)
  
  

  • 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 @Alex 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 @Alex Vul

  • with a target of Dublin release

  • TOSCAiszation of Use Cases (E2E)

  • Needs to be shared back to ETSI (December meeting for TOSCA)

  • IFA alignment (e.g., split of VDU and VNFC) (provide input into ETSI by IFA meetiings:  November)
    
    

    • Possible team members:
      
      

      • @Lianhao Lu (Deactivated); @Alex Vul; @Priya TG [NEC/Netcracker]; @Andy Mayer; @FREEMAN, BRIAN D; @Thinh Nguyenphu (Unlicensed); @Anatoly Katzman; @Haibin Chu (use case owners);

    • @Alex Vul to set up call.

VNF Package Security Recomendation