| | - Software Status
- 4 People involved in documentation using group reviews of generated HTML
- Logging and monitoring admin guide done by Former user (Deleted) for CPS Temporal will be moved to CPS-Core and made generic by Luke Gleeson (Unlicensed)
Jira Legacy |
---|
server | System Jira |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CPS-645 |
---|
| renu kumari wil investigate option. Stakeholder want clear separation between 'client' and 'internal' interfaces. Although both need to be available for publication, just different target audiences. Preferred Internal interface pre-fix is /ncmpDmi
- Discuss adding CM-Handle for SDN-R (network Slicing) with Ahila P
- Proposal for SDN-R integration: SDN-R Feature for adding cm-handle
- Toine Siebelink clarified that instead of Async flow steps 2&3 a 'temporary' sync option is available right now on DMI-Plugin. Toine wil mail specification links to Ahila
- Steps 4 & 5 are also already developed and test in Jakarta using SDN-C. These might need to be tested in SND-R environment.
- CPS teams prefers NOT to have a third option for adding CM Handles. Instead we agreed on the following possible evolution path:
- SDN-R use synchronous method delivered in release I, mentioned above (can be done now)
- SDN-R publishes event of the same schema and same topic as PNF. This release CPS is delivering the relevant event based API in J which has already been investigated , see
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | CPS-393 |
---|
|
- eventually, post Jakarta, both SDN-R wil use the current A&AI event based interfaces
- At any stage Topic and or Event bus provide could be made configurable as long as te event schema stays the same
- PNF Registration flow is detailed here
|