2018-10-19Meeting notes
Date
10AM EDT
To Join: https://zoom.us/j/287367106
Discuss
- Introductions
- Any Feedback?: VNF Requirements for TOSCA VNF Package Andy Mayer andreik
- see draft : https://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter5/Tosca.html
- Addition review and changes will be made through bug reports via JIRA:
- Update: TOSCA Orchestration in ONAP Topic (need to discuss in architecture) Alex Vul
- TOSCA Task Force created: Wiki link: TOSCA Task Force
- Introduce topic: On-boarding of PNFs Andy Mayer All
- Begin discussion of what the ONAP requirements are from a PNF on-boarding perspective.
Prior notes:
- 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)
VNF Package Security Recomendation