2018-05-11 Meeting notes

Date

May 11, 2018 10AM EDT

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

Discuss

Introductions
Review of Action Items

Please respond to the Resource Information Model working group meeting time poll: https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16286359
Continue discussion of deprecated attributes in Resource Information Model @Alex Vul
Papyrus Update @Kevin Scaggs
- See: Modeling Governance Proposal
- @Former user (Deleted) to schedule a Papyrus tutorial and advertise during the Modeling Subcommittee call.
- Need updated Papyrus installation instructions on wiki
- Explore reference to IFA011 classes and deltas to IFA011 (what is added or subtracted)
Review of ETSI Scaling Model @Xu Yang @Thinh Nguyenphu (Unlicensed)

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
- Proposal for extending the model to include deployment flavors at the VNFC/VDU level
- See annex in the ETSI document to be further discussed next week:
  https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL001_TOSCA_desc/NFV-SOL001v040.zip
Last time:
ETSI SOL001 Update and Update of VNF Descriptor Design Time Data Model (need update from @Thinh Nguyenphu (Unlicensed))
Move to Papyrus Update
- ACTION: In LA set up GIT repo for Papyrus @Andy Mayer, @Former user (Deleted), @Brian Hedstrom, @Hui Deng, Jess Wagantall (Linux Foundation), @Gildas Lanilis Gmail
TSC Update on Resource Design Model @Alex Vul
- See: https://lf-onap.atlassian.net/wiki/download/attachments/15468089/HPA-TSC-Modeling.pdf?version=1&modificationDate=1520534498000&api=v2
- It is not apparent that an ONAP decision has been made for Beijing on SOL001 or OASIS TOSCA Simple Profile for NVF v1 wd5 rev3.
- What is the VNF Descriptor TOSCA model for beyond Beijing?
- The list of HPA Capabilities may be found at: https://wiki.onap.org/pages/viewpage.action?pageId=25439922
ETSI Update @Thinh Nguyenphu (Unlicensed)
- ETSI decision of having a single NFV profile document (SOL001) and not relate on further progress of TOSCA NFV Profile
- SOL001 may be found at:
  https://docbox.etsi.org/ISG/NFV/SOL/05-CONTRIBUTIONS/2018//NFVSOL(18)000102_SOL001_Draft_GS_NFV-SOL001v060_contribution.zip
- Team discuss aligning the ONAP TOSCA with the current SOL001 work
- ONAP Data model for Beijng based on most recent OASIS NFV Profile with additional alignment with SOL001 and ONAP needs.
- Specific pieces of data model applicable to Beijing will be identified and mapped (focus on getting the recommendation draft for next week)
- Begin approval of standalone spec SOL001 by ETSI starting March 20th (for 1 week)
Discuss clean version wiki tables for reviewing information model classes for Beijing and
- Monitoring Parameters updates for VES. See: http://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/files/VESEventListener.html VES Specification
  - Work in putting VES TOSCA into SOL001 form and structure. Work with @Alex Vul and @andreik to bring updates back into ETSI.
  - Relationship to Multi-VIM
  - Auto-discovery use case
  - Possible need for event type registry
  - See: Class: MonitoringParameterDesc
  - TOSCA constructs to implement the Monitoring feature
  - @andreik, @alok411, @Andy Mayer to work a use case to support addition of attribute (EventDesc) to IFA011 in early April
Discuss move to Papyrus (status and approach) and Git @Former user (Deleted)
- Need to create sub-models in order for teams to work concurrently(e.g., Service, Resource, etc.)
- Need to discuss model governance
- Stereotypes on model can be used to indicate element stability / stage (using IISOMI Open Model Profile)
- Need wiki based proposal for Modeling proposal during release cycle (need discussion during face to face) @Kevin Scaggs on Modeling sub-committee page
  - Should be presented to Architecture sub-committee (next week @Kevin Scaggs)
  - Updated here: Proposed ONAP Release Process Updates for Information and Data Modeling
Next TIme
Continue Discuss VDU vs VNFC Descriptor and relationship to deployment flavors
- Proposal for extending the model to include deployment flavors at the VNFC/VDU level
- See annex in the ETSI document to be further discussed next week:
  https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL001_TOSCA_desc/NFV-SOL001v040.zip

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