This page is used for the ONAP R2+ Service IM drafting and discussion.
*******************************************************this section below will be move into the clear page *****************************************************************************************
| Page Tree | |
|---|---|
|
|
...
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.
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
...
The description of the service
Visible when the user hovers over this service in the design studio UI.
...
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
...
The icon path of the service
Process required to add new icon.
...
ServiceInstance
...
ServiceComponentCatalogItem
...
Network Service Descriptor
Inherit from ServiceComponentCatalogItem
...
References the VNFD of a constituent VNF.
...
References the PNFD of a constituent PNF.
...
ServiceComponentInstance
...
ETSI IFA013
(NS)
...
Network Service Instance
Inherit from ServiceComponentInstance
...
ETSI IFA013
(NS)
...
Information on the PNF(s) that are part of this NS.
...
Information on the VLs of thisNS.
...
Represents for each NS scaling aspect declared in the applicable DF, how "big" the NS instance has been scaled w.r.t. that aspect.
**************************************************************Note: this section above will be move into the clear page.***********************************************************************************************
Current Service Information Model UML Documentation: ONAP Service 2017-11-08.docx
1. @ James Forsyth David Shadmi is the AAI and SDC align to the diagram above?
2. @Andy Mayer ServiceDesc's attributes are directly definited, not using the method above. Please confirm it.
3. @ Andy Mayer in the diagram above, there is no ServiceCatalogItemType, but in the document it exits.
ServiceNetworkAssociation and serviceRecipe are the same question.
Please confirm them and update the diagram if needed.
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
...
The description of the service
Visible when the user hovers over this service in the design studio UI.
...
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”.
...
|
...
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
...
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.
This is the technology owner. ATT UID. Future click on UID and launch mail client. Multiple contacts should be supported.
...
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
...
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.
...
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.
...
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
...
Composite ID of contract and entitlement number from myprocurement
...
From contract/entitlement
...
maopeng zhang ServiceCatalogItem-Q11: It is an document from vendor. Should it be moved from design time?
...
Obtain from vendor
...
maopeng zhang ServiceCatalogItem-Q12: It is an document from vendor. Should it be moved from design time?
...
Obtain from vendor
...
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.
...
The icon path of the service
Process required to add new icon.
...
maopeng zhang ServiceCatalogItem-Q14: Do the Service support license?
...
Multiple fields. Categories of licenses planned; type, unit.
...
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
...
maopeng zhang ServiceCatalogItem-Q16: What are the Requirements used for in the use cases and how does it effect the run-time components?
...
Multiple fields. Includes connectivity
...
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.
...
Flat list in 1507. In 1510, UI will be separated to different field from Category.
...
Must accept multiple keywords
...
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.
...
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?
...
Part of the lifecycle management of the artifact.
...
Artifact name stored in Swift. Artifacts are searchable / indexable.
...
Scripts are an artifact, this may be redundant
...
URL to file stored in Glance or Swift, depending upon image vs. binary
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
...
...
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
...
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.
...
References the NSD of a constituent nested NS.
...
References the VNFD of a constituent VNF.
...
References the PNFD of a constituent PNF.
...
Provides the descriptor of a service access point of the network service.
...
Provides the descriptors of the
applicable forwarding graphs.
...
Identifies either a virtualised resourcerelated
performance metric or a VNF
Indicator.
...
Specifies a rule to trigger a scaling action on a NS instantiated according to the NSD.
...
Provides a life cycle management
script written in a Domain Specific Language (DSL).
...
Identifies a DF within the scope of an NSD.
...
Provides a signature to prevent
tampering.
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
...
Reference to the flavour of the NSD used to instantiate this NS.
...
Information on the PNF(s) that are part of this NS.
...
Information on the VLs of thisNS.
...
Information on the VNFFGs of this NS.
...
Information on the SAPs of this NS.
...
Reference to information on nested NSs of this NS.
...
Represents for each NS scaling aspect declared in the applicable DF, how "big" the NS instance has been scaled w.r.t. that aspect.
...
Information on the additional affinity or anti-affinity rule from NS instantiation operation. Shall not conflict with rules already specified in the NSD.
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.
...
Metadata of resources (VFs, VFCs, PNF) will include new field resourceVendorModelNumber. The value for this field is the part number defined by the vendor, e.g. “MX960”.
...
ExternalVirtualLink Instance
...
ETSI IFA013
(VirtualLink)
...
VNF Node
...
VNF Instance
...