2018-07-20 Meeting notes

Date

Jul 20, 2018 10AM EDT

To Join:

https://zoom.us/j/4996638718





Discuss

  • Introductions

  • Papyrus Update @Kevin Scaggs

    • Model repo is available in Gerrit in model spec repo, may need to be committed.

    • ACTION: Need Model Spec committers for Gerrit Model Spec Repo. Need this on the agenda for the Modeling Sub-committee (@Hui Deng)

    • Testing pulling model back to local environment from Repo

    • ACTION: Need process for updates back to working tree with quick committs, vs approving final release. Need this on the agenda for the Modeling Sub-committee (@Hui Deng)

    • ACTION: Use of GenDoc format for Readthedocs version of the model. Need this on the agenda for the Modeling Sub-committee (@Hui Deng)

  • Review ONAP VNF Descriptor Data Modeling Collaborative Proposal for Casablanca @Andy Mayer

  • Review vCPE R2 data model gaps @Lianhao Lu (Deactivated)

    • ACTION: Form Tiger team to recommend updates to SOL001 for on-boarding based on vCPE (2 week window)

      • 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.

  • Last time:

  • ONAP Modeling Approach Proposal Discussion @Andy Mayer

    • Reviewed ONAP as a black box

    • ONAP has a broader functional scope than ETSI MANO, therefore  the ETSI Data Model is not sufficient to drive ONAP behavior

    • ONAP needs to be agile and move quickly

    • ONAP as a Black Box supports Standards at the edges  (e.g., ETSI, TM Forum, HEAT)

    • Introduce idea of transforming Standards based packages into ONAP model, while preserving on-boarding artifacts to enable southbound adaptation

  • ETSI SOL Update @Thinh Nguyenphu (Unlicensed)

    • Undergoing preparing final technical update IFA and SOL 2.5.1. SOL001 will sync with IFA011 v2.5.1; VNF SOL Package Version 2.5.1

    • SOL001 is stable on VNF Descriptor parts

      • Three known gaps include:  monitoring parameters (from VIM); VNF Indicator (used for lifecycle operations); Security Group;

      • Will go through constant review and resolution over next 4 weeks. Then stable draft will be available.

      • Network Service Descriptor will still be work in progress

      • SOL001 machine readable VNF Types across all VNFs

      • Clean document should be available 4 weeks from now.

      • Will try to push forward in IM and DM: Placement group policy, guideline for single service template, lifecycle operation scripts (how to use)

      • HPA Registry, will be used in short term (wiki page)

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

    • Thanks to @Chris Donley

    • Papyrus will be available for use in Gerrit repo

  • No meeting next week (6 July 2018)



  • LAST TIME"

  • Plans for Casablanca:



    • Work with VNF Package Requirements to update TOSCA Guidelines

    • Apply SOL004 v2.4.2 in a consistent for VNF Package Extensions (e.g., VES specifications)

    • Alignment of On-boarding VNF Descriptor with Stable draft of SOL001 expected by 31 May (except for monitoring capabilities and indicator capabilities)

      • ETSIVNF Descriptor should be compete by July / August timeframe

    • Explore HEAT and TOSCA on-boarding into SDC alternatives

      • Gap assessment HEAT vs. TOSCA descriptors (e.g., flavors, scaling)

      • Identify alternatives

    • Team discussed and agreed to draft plan for Casablanca

  • Status updated of Scaling Model @Xu Yang @Thinh Nguyenphu (Unlicensed)

    • Scaling Aspect policy type contribution to ETSI

  • Papyrus Update @Kevin Scaggs

    • Papyrus is working with Gerrit!!!

      • Thanks to @Chris Donley, @Kevin Scaggs, and @Former user (Deleted)

    • Process for reviewing and approving modeling (Kevin, Jessie)

      • Modeling sub-committee needs to settle on the role of Papyrus

      • Proposal for Tuesday's Modeling sub-commttee call

      • Each modeling sub-team may have a Papyrus modeler to capture resulting model into Papyrus tool

      • VNF SDK will use Papyrus for VNF Descriptor Information Model for Casablanca

      • Process for reviewing and commit model into Gerrit  within scope of VNF SDK Project @Former user (Deleted) and @Kevin Scaggs will work this

    • See: Modeling Governance Proposal

    • Papyrus use with Geritt: @Former user (Deleted)@Kevin Scaggs@Chris Donley

      • can use VNF SDK repo to test out

    • Papyrus tutorial:

      • Need to present background on use of Papyrus (informational) to ONAP Community

      • Scheduled for Wednesday 13 June at 6:00AM Pacific US;

      • https://zoom.us/j/987452560


    • VNF SDK will use Papyrus for VNF Descriptor Information Model for Casablanca

    • Explore reference to IFA011 classes and deltas to IFA011 (what is added or subtracted) @Former user (Deleted)

  • Finalize Next time: Plans for Casablanca

  • ETSI Update





  • Next time: Directory Structure for CSAR package @andreik

    • Apply ETSI SOL004 for ONAP CSAR structure

    • VNF SDK working on open source solution for CSAR signature

    • Need to register ONAP specific keyword with ETSI for ONAP specific extensions (e.g., VES)

    • VNF SDK Modeling will define guidelines for directory structure for ONAP extensitions

    • ONAP will need to maintain registry for CSAR directory structure (start with VNF SDK project)

  • Next time: Papyrus Update @Former user (Deleted)

    • Porting difficult, so moving in manually VNFDesc model is being put in manually

    • Push & Get URLs within Gerrit, could Papyrus work with that. @Andrew Grimberg and @Former user (Deleted) to work together to see if Papyrus can be set-up to work via Gerrit (need to update URL for repo interactions)

    • Gerrit Repo is: Vnfsdk/model



  • Next Time: Need proposal for Information Model Element Stability Levels (based on IISOMI StereoTypes) @Kevin Scaggs @Andy Mayer

  • Next Time Element Group Discussion. See: Element Groups

    • Provide examples of how Element Groups are used on wiki @Kevin Scaggs@Andy Mayer

    • Evaluate as optional approach within the VNF Descriptor

    • Continue Discussion next time

  • Next Time: Continue Discuss VDU vs VNFC Descriptor and relationship to deployment flavors











Recording:GMT20180309-145752_VNFSDK-mod_1920x1200.mp4





Upcoming:

  • Next call 4 MAY 2018

  • Papyrus port - version, schedule.

  • Model driven approach discussion (@Alex Vul)

  • Model walkthrough

  • SDC IM Gap assessment

  • Discuss VDU vs VNFC Descriptor and relationship to deployment flavors

  • VoLTE VNF Descriptor to latest release of IFA011

  • Gap analysis of HEAT templates

  • Event descriptors alignment with DCAE

  • New Action items

 





VNF Package Security Recomendation