This page is used for the ONAP R2+ Service IM drafting and discussion.
ServiceDesc (ServiceCatalogItem)
SDC (Service) | AAI ( | ECOMP IM (ServiceCatalogItem) | Comments | Confirmed | Description |
maopeng zhang: needs to describe the function attribute | function (From Andy Mayer) |
ServiceInstance
| AAI (ServiceInstance) | ECOMP IM (service-instance) | Comments | Confirmed | Description |
maopeng zhang: needs to describe the function attribute | function (From Andy Mayer) |
ServiceCatalogItem vs ServiceComponentCatalogItem
ServiceInstance vs ServiceComponentInstance
In the current Ecomp IM ONAP Service Archive 2017-11-08.docx, Service and ServiceComponent classes are defined either at run and design time (i.e ServiceComponentDesc/ServiceComponentCatalogItem, ServiceComponentInstance, ServiceInstance, ServiceDesc/ServiceCatalogItem) even if no attribute is defined (to be added).
According to tables above, both SDC and A&AI do not differ Service and ServiceComponent.
Do we need to split a Service as an aggregation of ServiceComponent in the IM? Considering that a Service may be also a composition of Services as well.
NfVirtualLink, LinkPort, VirtualNetwork
InECOMP IM UML documentation: ONAP Resource 2017-11-08.docx and ONAP Service 2017-11-08.docx no class definition about Virtual Link, NSVirtualLInk, LinkPort, VirtualNetwork defined in ETSI IFA.