...
<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>
| # | Assumption | Notes |
|---|---|---|
| 1 | The input parameters for async read/write can be jobId and a list of DataSubJob | Replacing the list of FNDs with DataSubJob objec as defined below. |
Issues & Decisions
| # | Issue | Notes | Decision | ||
|---|---|---|---|---|---|
| 1 | This is an open issue | ||||
| 2 | Do we need a analysis template? | is convention for (new) developers to guide them | Toine Siebelink agreed we do to have consistent study pages | ||
| Agreement on DataJob and DataSubJob formats with the team | The CPS team agreed on the fields for both objects as given below. | ||||
| 2 | Agreement with stakeholders is also required | 3 | This is a very important (blocking issue)
<Note. use green for closed issues, yellow for important ones if needed>
Class Diagram
...
Datastructure for DataJob
| Name | Description | Type | Mandatory |
|---|---|---|---|
| jobId | The id of the data job | String | Y |
| dataSubJobs | The object that contains fdn, operation and other details as shown in the table below | List of DataSubJob | Y |
Datastructure for DataSubJob
| Name | Description | Type | Mandatory |
|---|---|---|---|
| fdn | Fully Distinguished Name (FDN) is a unique identifier of a managed object (MO) on a network element. | String | Y |
| operation | Describes the operation to execute. The value can be: "add", | String | Y |
| operationId | Unique identifier of the operation within the request | String | N |
| attributes | Allows selection of specific fields for attributes with complex data type for the operation. | List of String | N |