...
- The order of Operations is important and needs to be maintained hence the use of 'List'
- The output is 'void' for the scope in this user story, it will be defined later
dataaccepttype
anddatacontenttype
might be needed too, see issue #1 and #2. If required we could combine them to reduce the number of parameter in an object likeRestProtocolParameters
Datajob read request
Name | Description | Location | Type | Mandatory |
---|---|---|---|---|
destination | The destination of the results. ( e.g. S3 Bucket) | Query | string | N |
dataaccepttype | Define the data response accept type. Passible values: · application/vnd.3gpp.object-tree-hierarchical+json (default) · application/vnd.3gpp.object-tree-flat+json | request body | enum | N |
datacontenttype | Define the data request content type. Passible values: · application/3gpp-json-patch+json (default) | request body | enum | N |
data | List of operations to be executed. | request body | List of 3gppReadOperation | Y |
3gppReadOperation
Name | Description | Type |
---|---|---|
path | It is a unique identifier of a managed object (MO) on a network element. | String |
op | Describes the operation to execute. The value can be: "read" | String |
operationId | Unique identifier of the operation within the request | Integer |
attributes | This parameter specifies the attributes of the scoped resources that are returned. | List of String |
fields | This parameter specifies the attribute fields of the scoped resources that are returned. This should be used if an attribute is a struct and only a subset of its fields should be returned. | List of String |
filter | The parameter is used to filter the scoped Managed Objects. Only Managed Objects passing the filter criteria will be fetched. | List of String |
scopeType | ScopeType selects MOs depending on relationships with Base Managed Object. | enum[BASE_ONLY, BASE_ALL, BASE_NTH_LEVEL, BASE_SUBTREE] |
scopeLevel | Only used when the scope type is BASE_NTH_LEVEL | Integer |
Datajob write request
Name | Description | Location | Type | Mandatory |
---|---|---|---|---|
destination | The destination of the results. ( e.g. S3 Bucket) | Query | string | N |
dataaccepttype | Define the data response accept type. Passible values: · application/vnd.3gpp.object-tree-hierarchical+json (default) · application/vnd.3gpp.object-tree-flat+json | request body | enum | N |
datacontenttype | Define the data request content type. Passible values: · application/3gpp-json-patch+json (default) | request body | enum | N |
data | List of operations to be executed. | request body | List of 3gppPatchOperation | Y |
3gppPatchOperation
Name | Description | Type |
---|---|---|
path | It is a unique identifier of a managed object (MO) on a network element. | String |
op | Describes the operation to execute. The value can be: "add", | String |
operationId | Unique identifier of the operation within the request | Integer |
value | TO BE UPDATED | Object |
Examples from DCM Study
DataJob Read request (rAPP -> DCM)
...
Priority | Component | Description | JIRA | Estimates | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | NCMP | Create implementation proposal for NCMP to provide support for Data jobs qualifier during registration |
| |||||||||||||
2 | NCMP | NCMP to provide support for data producer identifier during registration |
| |||||||||||||
3 | NCMP | Support of Datajobs qualifier during registration |
| |||||||||||||
4 | NCMP | Modify the get cmHandle api to return dataProducerIdentifier, moduleSetTag, and alternateId |
| |||||||||||||
5 | NCMP | Modify lcm events to include dataProducerIdentifier and moduleSetTag |
| |||||||||||||
6 | NCMP | Create implementation proposal for NCMP to provide Java interface that can support Data jobs request |
| |||||||||||||
7 | NCMP | Define a java based datastructure for DataJob |
| |||||||||||||
8 | NCMP | Handle Datajob request |
| |||||||||||||
9 | NCMP | Handle Async Datajob Response |
| |||||||||||||
10 | DMI | Response schema for DMI dataJob response |
| |||||||||||||
11 | DMI | Define DMI REST interface for Datajobs |
| |||||||||||||
12 | NCMP | Forward dataJob response from DMI to Client Topic |
| |||||||||||||
13 | DMI | Move DMI Stub from NCMP to DMI-Plugin |
| |||||||||||||
14 | End to End Demo Story |
|
...