ONAP R3 Resource IM Call 2018-8-6
- Xu Yang
General Information:
Date and Time: 2018, August 6, 9pm~10pm Beijing Time, 9am~10am US Eastern
Meeting Room: https://zoom.us/j/645982535
Agenda:
Model Freeze Status
Next steps
update from ETSI spec
Material:
Minutes:
Model Freeze Status
VNFD/VNF run time model:
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
suggest to remove them
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:
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)