| Page Tree | |
|---|---|
|
|
Products are made up of services (ServiceCatalogItems on the design side, ServiceInstances on the runtime side).
Services are made up of service components. A service component is not seen or known to products like SID ResourceFacingServices are not seen by products. Services can be composed of other Services and may be referred to as complex services. One Service is a E2E service. Network Service, or WAN service can be the service components in the E2E service.
ServiceComponents are made up of ServiceComponents or resources.
Take the ONAP R1 VoLTE use case as an example. The E2E VoLTE service can be designed as the service; The IMS, EPC, and WAN can be designed as the service components. The HSS, CSCF, TAS, SBC, MME, and SPGW etc, and the link between them can be design as the resources.
the comparision table among ECOMP IM, SDC IM, ETSI NFV IFA, A&AI as below:
ServiceCatalogItem
...
SDC
(Service)
...
Versioned identifier of the service model (this uuid is changed for every major version of the service)
...
The name of the service
...
maopeng zhang ServiceCatalogItem-Q1: what‘s the difference of type and serviceType or category?’
Category - A predefined list which identifies the construct's category. There is a predefined list of service categories and resource categories.
Type - A predefined list which identifies the construct (i.e., service, VF, VFC, CP, VL, etc.).
serviceType - An optional string field defining a generic type (like category) of the service. E.g. this field can be used for defining the service as “TRANSPORT”.
...
maopeng zhang ServiceCatalogItem-Q2: What's the ServiceRole used for in the use cases and how does it effect the run-time components?
serviceRole - An optional string field for shortcode that defines the function that the service is providing. E.g. “MISVPN” or “AIM”.
...
The naming fields are used to define if the service instance name is auto-generated by the runtime components (SO and SDNC).
Need to refer to the use case owners to understand if and how these fields are used.
maopeng zhang: ServiceEcompNaming and ecompGeneratedNaming are two flags to indentify whether the ONAP service name auto-generated.
For the user, there are too many parameters to be inputted if using this feature. could it be possible that if namingPolicy is provided and serviceName is empty, the ONAP will auto-generate service name?
...
|
...
maopeng zhang ServiceCatalogItem-Q5: Is it the service designer? If consider multi-designers, the attributes should be array type.
...
maopeng zhang ServiceCatalogItem-Q6: Please clarify how to use the attribute in the run-time?
...
maopeng zhang ServiceCatalogItem-Q7:
ECOMP IM: From the TOSCA model. Multiple fields. Could include thresholds and policies. Vendor upgrade requirements should also be included here.
TOSCA: A constraint clause defines an operation along with one or more compatible values that can be used to define a constraint on a property or parameter’s allowed values when it is defined in a TOSCA Service Template or one of its entities.
The constraints is not a attribute.
...
maopeng zhang ServiceCatalogItem-Q8: What's the Cost used for in the use cases and how does it effect the run-time components?
...
maopeng zhang ServiceCatalogItem-Q9: What's the Cost used for in the use cases and how does it effect the run-time components?
...
maopeng zhang ServiceCatalogItem-Q11: It is an document from vendor. Should it be moved from design time?
...
maopeng zhang ServiceCatalogItem-Q12: It is an document from vendor. Should it be moved from design time?
...
maopeng zhang ServiceCatalogItem-Q13: History is used for Keeping all major events, i.e., creation date, any modification, check in and check out with ATT UID. The type is only char. Suggest to be specified.
...
maopeng zhang ServiceCatalogItem-Q14: Do the Service support license?
...
maopeng zhang ServiceCatalogItem-Q15: It is an document from vendor. Should it be moved from design time?
...
maopeng zhang ServiceCatalogItem-Q16: What are the Requirements used for in the use cases and how does it effect the run-time components?
...
maopeng zhang: Please clarify why it is needed.
...
maopeng zhang: are the test scripts for the service? If it is true, other scripts also are needed, such as workflow scripts or plans and should be considered.
...
maopeng zhang: It is an document from vendor. Should it be moved from design time?
...
maopeng zhang: should be those VF related attributes moved to VNF, not in the service?
...
ServiceInstance
...
maopeng zhang: same with the ServiceCatalogItem-Q1
same with the ServiceCatalogItem-Q2
...
maopeng zhang: ServiceInstance-Q1 Where the workload-Context is got and format?
...
maopeng zhang: ServiceInstance-Q2 Where the workload-Context is got and format?
...
maopeng zhang : ServiceInstance-Q3 what's the difference between them? Which is the Service UUID?
...
maopeng zhang : ServiceInstance-Q5 If the service is an general service, why only define these bandwidth attributes?
...
maopeng zhang: What's "vhn-portal-url"?
...
maopeng zhang: Where the locationId is got? and How to use it?
...
maopeng zhang: Same with ServiceCatalogItem-Q4
...
ServiceComponentCatalogItem
...
...
same with the ServiceCatalogItem-Q3
...
same with the ServiceCatalogItem-Q4
...
ServiceComponentCatalogItem
...
ServiceComponentCatalogItem-Q1
suggest these parameters to the service component(NS).
Put the ServiceComponent as an abstract definition, and some specific domain service components can inherit from it and add their own attributes, such as NS or WAN, or others.
...
ServiceComponentInstance
...
ECOMP IM
(service component)
...
ETSI IFA013
(NS)
...
...
same with the ServiceInstance-Q1
...
same with the ServiceInstance-Q2
...
...
same with the ServiceInstance-Q4
...
same with the ServiceInstance-Q5
...
same with the ServiceComponentCatalogItem-Q1
...
ExternalVirtualLink Description
...
is the resource instance referred to the run-time resource instance? If it is in the run-time, why is it in the design time?
...
Identifier of the resource instance (uuid of the specific use of the resource model in this service). This identifier is regenerated whenever a user makes a change on the resource instance.
...
ExternalVirtualLink Instance
...
ETSI IFA013
(VirtualLink)
...
VNF Node
...
VNF Instance
...