Date
10AM EDT
To Join: https://zoom.us/j/287367106
Discuss
- Introductions
- Review of Action Items
- Directory Structure for CSAR package Andrei Kojukhov
- 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)
- Papyrus Update Jessie S Jewitt
- 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 Jessie S Jewitt 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)
- Move to Papyrus Update
- ACTION: In LA set up GIT repo for Papyrus Andy Mayer, Jessie S Jewitt, Brian Hedstrom, Hui Deng, Jess Wagantall (Linux Foundation), Gildas Lanilis
- TSC Update on Resource Design Model Alexander Vul
- See: https://wiki.onap.org/download/attachments/25434810/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
- 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:
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 Alexander Vul and Andrei Kojukhov 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
- Andrei Kojukhov, Alok Gupta, Andy Mayer to work a use case to support addition of attribute (EventDesc) to IFA011 in early April
- Monitoring Parameters updates for VES. See: http://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/files/VESEventListener.html VES Specification
- Discuss move to Papyrus (status and approach) and Git Jessie S Jewitt
- 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 6 APR2018
- Papyrus port - version, schedule.
- Model driven approach discussion (Alexander 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
here is the link, if you have access to ETSI NFV, https://docbox.etsi.org/ISG/NFV/IFA/05-CONTRIBUTIONS/2018//NFVIFA(18)000152_IFA011_ONAP_recommendation_changes.docx
VNF Package Security Recomendation
3 Comments
Jenny Huang
Hi,
I noticed much of the current discussions have been focused on the functional descriptors, is this project or any other ONAP project looking at nonfunctional areas (yellow shaded areas) to help facilitate onboarding automation and lifecycle management from operational perspectives?
Andrei Kojukhov
Hi Jenny, as I presented in our last VNF-SDK modeling call yesterday the Amsterdam release CSAR VNF package includes:
I'm not sure about SLA field - what is you expectation from an orchestration entity in handling SLA? My understanding it should be defined as part of VNF descriptor by some threshold/constraints.
Andrei
Jenny Huang
Thanks Andrei, I will look into more on the info that you provided.
On SLA, most vendors will provide some SLA information but they need to be aggregated at service level that the SP provides. i.e Orchestrator needs to coordinate with Service Assurance which usually resides in the BSS layer.
There are some vendors, SPs and Catalyst (PoC) inputs from the TM Forum on those nonfunctional fields. I'm trying to sort out when and where to synchronize with the ONAP community. Looks like this project is the right place and perhaps I can coordinate with Andy on when and how to introduce additional inputs?