...
Assumptions<optional>
<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>
...
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 | Luke Gleeson and Toine Siebelink agreed we do to have consistent pages |
| 3 | This is a very important (blocking issue) |
<Note. use green for closed issues, yellow for important ones if needed>
Mu First NOtes
Changedin Interface: (Initial) regsitartion
TODO Get picture from Somesh Kumar
FDNs Ask Kieran about 3GPP definition or other good documenation
Possibel issueS WITH USING fdnS IN URLs
proably
- schemas set changes (liek mode set ref update , see CPS-1733: Upgrade YANG Schema-Set for CM Handle Using a Module Set Tag)
- interface changes (similar to MOdel set ref udpate, see ASK sourabh)
< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>
Any Other Header
...
Multiple identifiers during registration
The first use case which should be handled is the storing of the new identifier ( called FDN or Fully Distinguished Name).
To achieve this NCMP's CmHandle registration endpoint must be changed to accept a new String parameter which proposed name is fullyDistinguishedName.
Extending RestInputCmHandle object
During registration an object called RestInputCmHandle contains all the information to register new entities in the database.
The object should be extended at the top level with the new property:
RestInputCmHandle | |
|---|---|
| Field name | Type |
| cmHandle | String |
cmHandleProperties | Object |
| publicCmHandleProperties | Object |
| moduleSetTag | String |
| trustLevel | String |
| fullyDistinguishedName | String |