Agenda:
- Backlog
- PNFD update
- Comparison with latest IFA011
- New requirement for the VNFD
- Root classes
Material:
Minutes:
- Backlog:
- PNFD update:
- swVersionList's cardinality should be 1 instead of 1..N, because the data type supports describing multiple versions already
- the use case (expected behaviour for handling these attributes) is still requested to be provided
- suggest the extensions to the existing SDO specs to be marked (Kevin suggest to have a stereotype for this)
- suggest to align the attribute names in VNFD/PNFD to have the same understanding, e.g., make the "version"/"softwareVersion" attributes have the same name.
- this is related to the root class proposal
- with no consensus on the "swVersionList", it's suggested not to put in R4
- the other attributes/data types would be asked for agreement in subcommittee call
- Comparison with IFA011:
- the page is updated with 3 different colors: red - changes needed in R4 to align with IFA011 v2.5.1; blue - candidates for feedback to ETSI spec; purple - HPA attributes/data types to be deprecated
- recommend people to review the page and give comments
- discuss next week about the contribution plan for Feb ETSI F2F meeting
- Requirement for VNFD
- no comments online
- have 1 week's time for review
- Root class draft
- still under working
- RootEntity→Descriptor/Entity
- BusinessInteraction→ServiceOrder/...
- Do we need to have a single root? Kevin prefer to root classes for those which make sense. (TMF way)
- suggest ETSI to have root classes defined
{"serverDuration": 189, "requestCorrelationId": "421fb99c4dbd4fdc8ec719207a3bea4d"}