| Table of Contents |
|---|
...
| Priority | JIRA | Confluence | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
| |||||||||
| 2 |
| |||||||||
| 3 |
|
Issues & Decisions
| Issue | Notes | Decision | ||
|---|---|---|---|---|
| 1 | CPS to deliver java-interface only | This affects our Wow in many aspects.
|
Csaba Kocsis proposed that CPS Team will deliver Java impl. first and then E// will take our code and wrap and a REST interface around it. Toine Siebelink CPS team will work out during Grooming how to demo withour REST interface, most like using Groovy (semi) Integartion Tests. Daniel Hanrahan his about to complete a test framework for test NCMP services. | |
| 2 | Validation in REST or Java Service | Balance between early validation and common code | Continue with current process. Review case by case Toine Siebelink Csaba Kocsis | |
| 3 | Why is NCMP forwarding the response, DMI could do this ? | Involve extra performance cost from CPS | Implementation needed because of TBAC | |
| 4 | Are Java doc expected to be published | Yes. Agreed to deliver as a separate artefact (Shall be versioned ... where should it go ?) | Versioning of the interface shall be the same as the service delivered by CPS. New v should not affect the interface, version numbers could change and shall be documented | |
| 5 | Delivery artefacts | Required Artefacts
AP to confirm with Andreas in team Lightening | Csaba Kocsis to revert | |
| 6 | Characteristics | Need to discuss priority of this. Delivering a functioning MVP for EPIC is important. Discussion and agreement with Peter T needed |
Csaba Kocsis to revert
Still needed, might not get response because the new team are yet to start any integration. AP Kolawole Adebisi-Adeolokun to get a decision from Peter/David | Csaba Kocsis to revert | |||
| 7 | Results - Why can't DMI send result after completion of job with be told to do so | Simply less work if DMI can decide itself, no additional interface in other components needed to trigger this.... | tbc with Kieran Mccarthy A / Rafael Rocha | |
| 8 | Exact form of Alternate ID(s) FDNs | uri-FDN and LDNs should contain "/" and not "," as delimiters at the start of the naming attribute FDN example :
URI FDN example :
Should be compliant with 3GPP, should start with '/ ' https://github.com/jdegre/5GC_APIs/blob/Rel-18/TS28532_ProvMnS.yaml | Kieran Mccarthy A Users are advised to use URI-FDNs for alternate IDs to minimize performance impacts of conversions etc. Rafael Rocha ALL cps | |
| 9 | MVP (Minimum Viable Product) for DCM |
|
| |
| 10 | DataJob Read v Write prioritization | Write should be prioritized over read | ||
| 11 | Use of '/ ' causes some issues | Not at issue. FDN can support / and , | ||
| 12 | Prioritize CPS-2009 Update remaining existing/legacy NCMP APIs to support alternate Id (FDN) - Developer Wiki - Confluence (onap.org) - over Read. | New Epic requested for DataJob Read sperate this from 1964. Expected even earlier than q3 Agreed to move higher on R14 - #17 | ||
| 13 | NCMP still need to convert Legacy Event to Cloud Event before we can Update the Legacy APIs to support AlternateId | Re-prioritise [CPS-1704] Separation of Headers from Event Payload for Legacy Events - ONAP JIRA over CPS-2009 Update remaining existing/legacy NCMP APIs to support alternate Id (FDN). Kolawole Adebisi-Adeolokun to get agreement with stakeholders | Currently ETH are only consuming the LCM event and we agreed shall remain Legacy event for MVP delivery. | |
| 14 | Decision to add status & result as part of this MVP | No new epic required for write, maintain current priority, wrap up this epic with;
| ||
| 15 | Is the requestId in the southbound request equal to the dataJobId coming in from the northound interfaces? (see writeJob for example) | Can the dataJobId used as the requestId? | Kolawole Adebisi-Adeolokun confirmed dataJobId can be used as the requestId | |
| 16 | Define & agree on a Java interface (do we need a different method for |
write |
) The output should be defined | We need a clarification on the response. |
Requirements
Kolawole Adebisi-Adeolokun // The output is currently being define by team Lighting AP @ko to follow-up |
Requirements
E2E Requirement (for context)
...
Functional Requirement | Error Scenario | Expected Behavior | Sign-off | |
|---|---|---|---|---|
| 1 | #2 | Non Responding DMI during new DataJob Request | NCM shall send asynchronous message containing:
Client is responsible for retry. Wait for implantation proposal | Csaba Kocsis , CPS |
| 2 | #2 | Unmatched Alternate IDs | Toine Siebelink : Not discussed yet but I would suggest similar behavior as legacy bulk interface (async response with failed FDNS) - If an unmatched alternated (1 or more), send a response back to client saying no jobs or 0 subjob If request contains none-exited alternateid ? - Goes to client | Csaba Kocsis, all cps |
| 3 | #3 | Non Responding DMI during new status update | Error handling just by HTTP timeout (java interface will throw an exception) | Csaba Kocsis all cps |
| 4 | #4 | Not existing Topics | NCMP is NOT responsible for checking or handling messages to non existing (client) topics Also 'internal' topics are assumed to be set up correctly | Csaba Kocsis all cps |
| 5 | Misc. | Other Robustness
|
| Agreed to revisit robustness once basic happy and standard error scenarios (DMI not responding) have been implemented |
AP Kolawole Adebisi-Adeolokun To follow-up and check the possibility of merging this with the read & write
High Level Solution
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
...
- Conflict management, DATAJOBS are BATCH OPERATION.
Comment
CPS will need to leave epic open, @kola organise a sync with team lighting on their current progress
dev wise, CPS has fulfilled all functional aspect of this epic
Should we consider demo ? - Check with team lighting if we could arrange a demo