You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

References

CPS-2155 - Getting issue details... STATUS

Assumptions

<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>

#AssumptionNotes
1The input parameters for async read/write can be jobId and a list of DataSubJobReplacing the list of FNDs with DataSubJob object as defined below.

Issues & Decisions


IssueNotes Decision
1dataaccepttype Do we need to consider this parameter in our NCMP internal Java interface?

2datacontenttype Do we need to consider this parameter in our NCMP internal Java interface?

3attributes This has plural but all examples contain a single String, why?

<Note. use green for closed issues, yellow for important ones if needed>

Proposed Datastructure for Operation

NameDescriptionType
path

It is a unique identifier of a managed object (MO) on a network element. 
Defines the resource on which operation is executed. Typically could be Fully Distinguished Name (FDN).

String
op

Describes the operation to execute. The value can be:

"add",
"replace",
"remove",
"action", 
"read" 

String
operationId

Unique identifier of the operation within the request

Integer
attributesAllows selection of specific fields for attributes with complex data type for the operation. List of String
valueIt is for only WRITE operation.Object
scopeType

ScopeType selects MOs depending on relationships with Base Managed Object.
Only for READ operation.

String
scopeLevel

Only for READ operation.
Only used once the scope type when BASE_NTH_LEVEL.

Integer
filter

The parameter is used to filter the scoped Managed Objects. Only Managed Objects passing the filter criteria will be fetched.

String


DataJob Read request (rAPP -> DCM)


Datajob Write request (rAPP -> DCM)




  • No labels