Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SDC

(Service)

AAI
(service)
ECOMP IM
(ServiceCatalogItem)
Comments
invariantUUID

serviceInvariantUUID
UUIDservice-idServiceUUID serviceUUID
name
ServiceDisplayName serviceName 
descriptionservice-descriptionServiceDescription serviceDescription 
type

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”.

Category
Category  
serviceTypeserviceType
serviceRoleserviceRole

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”.

serviceEcompNaming

maopeng zhangServiceCatalogItem-Q3: What's the naming used for in the use cases and how does it effect the run-time components?

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?

ecompGeneratedNaming

namingPolicy

service_naming


service-versionVersion serviceVersion

resource-version

maopeng zhang ServiceCatalogItem-Q4: What's the resource-version meaning here? The version of resource are related to the resource. Why is it as a service attribute?



AT&TContact 

maopeng zhang ServiceCatalogItem-Q5: Is it the service designer? If consider multi-designers, the attributes should be array type.




Capacity 

maopeng zhang ServiceCatalogItem-Q6: Please clarify how to use the attribute in the run-time?



Constraints

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.



Cost

maopeng zhang ServiceCatalogItem-Q8: what What's the Cost used for in the use cases and how does it effect the run-time components?



D2RequirementsChecklist 

maopeng zhang ServiceCatalogItem-Q9: What's the Cost used for in the use cases and how does it effect the run-time components?



EntitlementID 

maopeng zhang ServiceCatalogItem-Q10: What's the EntitlementId, UnitNumber, and unitType used for in the use cases and how does it effect the run-time components?




EntitlementUnitNumber 


EntitlementUnitType 


FaultRequirements 

maopeng zhang ServiceCatalogItem-Q11: It is an document from vendor. Should it be moved from design time?



Features 

maopeng zhang ServiceCatalogItem-Q12: It is an document from vendor. Should it be moved from design time?



History 

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.



Icon 


LicensingModel 

maopeng zhang ServiceCatalogItem-Q14: Do the Service support license?



Performance 

maopeng zhang ServiceCatalogItem-Q15: It is an document from vendor. Should it be moved from design time?



Requirements 

maopeng zhang ServiceCatalogItem-Q16: What are the Requirements used for in the use cases and how does it effect the run-time components?



ServiceSystemName 


Subcategory 


Tags/Keywords 


Template 

maopeng zhang: Please clarify why it is needed.



TestScripts 

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.



VendorTestResults 

maopeng zhang: It is an document from vendor. Should it be moved from design time?



VF-SpecificPolicies 

maopeng zhang: should be those VF related attributes moved to VNF, not in the service?



VFArtifacts 


VFConfigParameters 


VFImage 

...

AAI
(ServiceInstance)
ECOMP IM
(service-instance)
Comments
service-Instance-Id
serviceInstanceId
service-instance-name
serviceInstanceName
service-type
ServiceInstance

maopeng zhang: same with the ServiceCatalogItem-Q1

:

Is it the

same with the

SDC service?

ServiceCatalogItem-Q2


service-role
environment-Context

maopeng zhang: Where the workload-Context is got and format?

workload-Context

maopeng zhang: Where the workload-Context is got and format?

model-invariant-id
serviceInvariantUUID
model-version-idServiceInstance-Q2: is it the UUID in the SDC

maopeng zhang : what's the difference between them? Which is the Service UUID?

persona-Model-Version
widget-Model-Id

maopeng zhang : what's the widget-model-id & version?

widget-Model-Version
bandwidth-total

maopeng zhang : If the service is an general service, why only define these bandwidth attributes?





bandwidth-up-wan1
bandwidth-down-wan1
bandwidth-up-wan2
bandwidth-down-wan2
vhn-portal-url

maopeng zhang: What's "vhn-portal-url"?

service-instance-location-id

maopeng zhang: Where the locationId is got? and How to use it?

resource-version

maopeng zhang: Same with ServiceCatalogItem-Q4

selflink
SelfLink
orchestration-status
orchestrationStatusstatus


  • ServiceComponentCatalogItem

...