Agenda:
- Model Freeze Status
- Next steps
Material:
Minutes:
- Model Freeze Status
- VNFD/VNF run time model:
- Link: R3 Resource Clean Draft (Papyrus Based)
- Content:
- R2 Clean with appropriate Classes changed to Datatypes
- R3 Vnf and Vnfc Instance Classes
- Discussed Classes and Attributes designated as Obsolete
- Items not updated from R2 are designated as Preliminary
- New Items designated as Experimental
- UML diagrams + tables
- Question:
- how to represent "deprecate": using "Obsolete" in the stereotypes column
- has change of storage descriptor in IFA spec reflected in the current page: not yet
- "faulty" is not appropriate, intended to be removed
- can papyrus documents show differences between IFA spec and ONAP model, like in R2: color is shown in UML diagrams, not in tables
- suggest to find a way to show it
- 1 week review, and please leave your comments on the wiki page
- NSD:
- Link: Proposed Network Service Descriptor Model
- Content:
- currently based on IFA014/015 v2.4.3
- using "_" before attribute name to show association (different from IFA)
- Question:
- a typo of "NDS", should be "NSD"
- suggest to first include VNF, VL, PNF into the NSD model; NsDf and Vnffg for future discussion
- what's the desired behaviour for ONAP to process NS: VFC is currently in charge of it
- what's the desired behaviour of configuration of NS: no application level configuration; should we have a higher level service which include application level configuration information?
- For design time, vendors may provide NS into ONAP
- For run time, should ONAP do application level configuration for NS, if so, how?
- what's the component doing VNF level application configuration?
- 1 week review, and please leave your comments on the wiki page
- Next steps:
- will update the clean page once the drafts are agreed
- will do bug fix before model final milestone (including update with latest IFA spec)
Video and Audio:
video
audio
{"serverDuration": 374, "requestCorrelationId": "c406c03bcf9f8289"}
