<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
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
<Note. use green for closed issues, yellow for important ones if needed>
Proposed 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
Proposed 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. Defines the resource on which operation is executed.
String
Y
operation
Describes the operation to execute. The value can be:
"add", "replace", "remove", "action", "read"
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
scope
ScopeType selects MOs depending on relationships with Base Managed Object.
String
N
filter
The parameter is used to filter the scoped Managed Objects. Only Managed Objects passing the filter criteria will be fetched.
