References
- CPS-2155Getting issue details... STATUS
Assumptions
# | Assumption | Notes |
---|---|---|
1 |
Issues & Decisions
Issue | Notes | Decision | |
---|---|---|---|
1 | dataaccepttype Do we need to consider this parameter in our NCMP internal Java interface? | The controller should accept/reject dataaccepttype. From the client application | The Controller will validate and set the Default as necessary kieran mccarthy Sourabh Sourabh Kolawole Adebisi-Adeolokun Toine Siebelink |
2 | datacontenttype Do we need to consider this parameter in our NCMP internal Java interface? | NCMP should maintain the content type as received and not modify datacontenttype. | NCMP should maintain what content type as received and not modify kieran mccarthy Sourabh Sourabh Kolawole Adebisi-Adeolokun Toine Siebelink |
3 |
| kieran mccarthy & Rafael to come back with a 'definition' and 'example | Kolawole Adebisi-Adeolokun to follow up with stakeholders on decision by 19/03/2024 |
4 | The study mentions ' | kieran mccarthy & Rafael to come back with a 'definition' and 'example | Read and Write data jobs are 2 deff. objects. Kolawole Adebisi-Adeolokun to follow up with stakeholders on decision by 19/03/2024 |
5 | Combine all java api parameters into 1 parameter object? | There is a limit (sonar quality check) of 7 parameter max for a method | Team |
Data Structures
Proposed Method signature
void processReadDataJob(String dataAcceptType, String datContentType, String dataJobId, List<ReadOperation> readOperations) void processWriteDataJob(String dataAcceptType, String datContentType, String dataJobId, List<WriteOperation> writeOperations, Map<String,String> metadata)
Notes
- 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
Proposed structure for Operation
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 |
attributes | Allows selection of specific fields for attributes with complex data type for the operation. | List of String |
value | It is for only WRITE operation. | Object |
scopeType | ScopeType selects MOs depending on relationships with Base Managed Object. | String |
scopeLevel | Only for READ operation. | Integer |
filter | The parameter is used to filter the scoped Managed Objects. Only Managed Objects passing the filter criteria will be fetched. | String |
Examples from DCM Study
DataJob Read request (rAPP -> DCM)
Datajob Write request (rAPP -> DCM)