Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira
serverONAP Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-2249

Assumptions


AssumptionNotesSign-off
1
  • CPS-E-05
    • Update
    • Create TBC
    • Delete TBC


2

Default boolean in cases CM not available



3Interface uses FDN

Open Issues


IssueNotes Decision
1

Uplift Ericsson source code (need permission)



2

Implement in REST or Service Layer ?



3

Scope details e.g create and delete use-cases



4

Publish public Conflict Interface as part of NCMP ?



5

Could we make this more generic to suit non-colic-management use i.e. tbac...



6Private properties are used to get FDN at the moment,  how will this be handled when alternate ID is fully implemented?

Requirements

Functional


InterfaceRequirementAdditional InformationSignoff
1CPS-E-05
  1. Design (& Publish ?) generic conflict handling interface
    1. Ericsson interface exist just needs to be generalized


2
  1. Intercept CM write requests to allow Conflict Handling Check 
    1. Ericsson have a specialized bean for this, can this be uplifted to Open Source


3
  1. Report HTTP Conflict upon failure
    1. java interface to throw exception
    2. add message details


4



Error Handling


ScenarioExpected BehaviorNotes
1



2



Characteristics


ParameterExpectationNotesSignoff
1



2



3




Solution Proposal


Out of Scope

...