Agenda:
- Run time model proposal review and discussion: VNF instance and VNFC instance
- Initial lifecycle state of the current/future model
- CCVPN resource IM proposal
- Papyrus for NSD
- composite/recursive pattern
Material:
Minutes:
- run time model (VNF instance & VNFC instance)
- consumer of the run time model: SDC&AAI
- faulty - means proposing to remove: one reason is that the information could be referenced from the VNFD, not defined in the run time model directly
- should not be marked as faulty
- plan to add run time model for VL, CP in the future
- call for comment
- lifecycle stereotype
- use "preliminary" as the current state of the clean model, recommend other groups to use the same approach
- need to define the criteria/rule/metrics for changing the state of the model: Jessie will confirm with Nigel, suggest to ask other projects for feedback
- mark new proposals for completely new use cases/functionalities as "experimental"; proposals from standard input can be marked as "preliminary" as the starting state
- use "obsolete" for the deprecating proposal, call for agreement on Tuesday
- CCVPN resource IM
- design time model for the CCVPN use case
- comments:
- (related to service discussion) site DC service, SOTN VPN Infra Service and Site Enterprise Service are instances of "Service Atomic" class, suggest to modify the diagram (change generalization association to realization)
- suggest to use ONF model for the network, e.g., site LAN/WAN port
- difference with ONF model: CCVPN model is not about network topology, but about customer requirement
- resource name will be revised to be clearer
- call for comment on the wiki
- papyrus for NSD
- suggest to compare with IFA spec to see the difference
- call for comment
{"serverDuration": 166, "requestCorrelationId": "c21cab2301074f789ebd07b15c2d3ac6"}