...
the comparision table among ECOMP IM, SDC IM, ETSI NFV IFA, A&AI as below:
ServiceCatalogItem
SDC (Service) | AAI (service) | ECOMP IM (ServiceCatalogItem) | Comments | Confirmed | Description |
| invariantUUID | serviceInvariantUUID | Constant identifier of the service model | |||
| UUID | service-id | ServiceUUID | serviceUUID | Versioned identifier of the service model (this uuid is changed for every major version of the service) | |
| name | ServiceDisplayName | serviceName | The name of the service | ||
| description | service-description | ServiceDescription | serviceDescription | The description of the service Visible when the user hovers over this service in the design studio UI. | |
| type | maopeng zhang ServiceCatalogItem-Q1: what‘s the difference of type and serviceType or category?’ 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”.
| A predefined list which identifies the construct (i.e., service, VF, VFC, CP, VL, etc.). | ||||
| Category | Category | A predefined list which identifies the construct's category. There is a predefined list of service categories and resource categories. Designer cannot define new Category. Process required to add/change/delete | ||
| serviceType | 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”. | ||
| serviceRole | serviceRole | maopeng zhang ServiceCatalogItem-Q2: What's the ServiceRole 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 ifserviceRole - An optional string field for shortcode that defines the function that the service is providing. E.g. “MISVPN” or “AIM”. | 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-version | Version | serviceVersion | The service version in SDC catalog | ||
| 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. |
This is the technology owner. ATT UID. Future click on UID and launch mail client. Multiple contacts should be supported. | |||||
| Capacity | maopeng zhang ServiceCatalogItem-Q6: Please clarify how to use the attribute in the run-time? | Obtain from vendor if available; tester can add additional information | |||
| 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. |
From the TOSCA model. Multiple fields. Could include thresholds and policies. Vendor upgrade requirements should also be included here. | |||||
| Cost | maopeng zhang ServiceCatalogItem-Q8: What's the Cost used for in the use cases and how does it effect the run-time components? | 2015: will be blank and not mandatory. 2016 may be accessed by role (TBD) and will be a mandatory field. | |||
| D2RequirementsChecklist | maopeng zhang ServiceCatalogItem-Q9: What's the Cost used for in the use cases and how does it effect the run-time components? |
Spreadsheet with input constraints, entries will be searchable | |||||
| 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? In the latest document there is no entitlement. is it removed? | Composite ID of contract and entitlement number from myprocurement | |||
| EntitlementUnitNumber | From contract/entitlement | ||||
| EntitlementUnitType | From contract/entitlement | ||||
| FaultRequirements | maopeng zhang ServiceCatalogItem-Q11: It is an document from vendor. Should it be moved from design time? | Obtain from vendor | |||
| Features | maopeng zhang ServiceCatalogItem-Q12: It is an document from vendor. Should it be moved from design time? | Obtain from vendor | |||
| 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. |
Keeping all major events, i.e., creation date, any modification, check in and check out with ATT UID. | |||||
| Icon | icon | The icon path of the service Process required to add new icon. | |||
| LicensingModel | maopeng zhang ServiceCatalogItem-Q14: Do the Service support license? | Multiple fields. Categories of licenses planned; type, unit. | |||
| Performance | maopeng zhang ServiceCatalogItem-Q15: It is an document from vendor. Should it be moved from design time? | Obtain from vendor if available; tester can add additional information | |||
| Requirements | 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.
Multiple fields. Includes connectivity | |||||
| ServiceSystemName | This field will be used in URLs and not exposed in create service UI; will be displayed in design studio. Meaningful service name used in API. The system name is used in the distribution studio (distribution notification and distribution API). - Max length of 25 characters - Allowed characters: alphanumeric, underscore, dash, dot. - Autocreated based upon the Service Display Name: spaces are trimmed, each word starts with a capital letter, on the first letter of abbreviation and acronyms are capitalized. - If the Service Display name changes, the Service System name will automatically be updated. - Service System name is not editable by the designer. - Name must be unique and is searchable. | ||||
| Subcategory | Flat list in 1507. In 1510, UI will be separated to different field from Category. | ||||
| Tags/Keywords | Must accept multiple keywords | ||||
| Template | Need to define a list of templates. Tied to Category. Designer cannot create new template (must be created by development team). Process required to add/change/delete. Could consider designer ability to create / modify template in 1602. | ||||
| TestScripts | |||||
| 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? | Part of the lifecycle management of the artifact. | |||
| VFArtifacts | Artifact name stored in Swift. Artifacts are searchable / indexable. | ||||
| VFConfigParameters | Scripts are an artifact, this may be redundant | ||||
| VFImage | URL to file stored in Glance or Swift, depending upon image vs. binary |
ServiceInstance
| AAI (ServiceInstance) | ECOMP IM (service-instance) | Comments | Confirmed | Description |
| service-Instance-Id | serviceInstanceId | Uniquely identifies this instance of a service | ||
| service-instance-name | serviceInstanceName | The name assigned to the service-instance | ||
| service-type | ||||
| service-role | ||||
| environment-Context | maopeng zhang: ServiceInstance-Q1 Where the workload-Context is got and format? | |||
| workload-Context | maopeng zhang: ServiceInstance-Q2 Where the workload-Context is got and format? | |||
| model-invariant-id | serviceInvariantUUID | Constant identifier of the service model | ||
| model-version-id | maopeng zhang : ServiceInstance-Q3 what's the difference between them? Which is the Service UUID? | ServiceUUID | Versioned identifier of the service model (this uuid is changed for every major version of the service) | |
| persona-Model-Version | ServiceVersion | The service version in SDC catalog | ||
| widget-Model-Id | maopeng zhang : ServiceInstance-Q4 what's the widget-model-id & version? | |||
| widget-Model-Version | ||||
| bandwidth-total | maopeng zhang : ServiceInstance-Q5 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 | URL to endpoint where more details can be gotten | ||
| orchestration-status | status | Orchestration status of the service instance |
...