CPS-1964 - Support for Async datajobs Write

https://lf-onap.atlassian.net/browse/CPS-2096

CPS-2096: Create implementation proposal for NCMP to provide support for data producer identifier during registration.

https://lf-onap.atlassian.net/browse/CPS-2155

CPS-2155 Java API: The Data Structure for DataJob Write Request

https://lf-onap.atlassian.net/browse/CPS-2141

CPS-2141 Define DMI REST interface for Datajobs

CPS to deliver java-interface only

This affects our Wow in many aspects.

1. Requirements on Java interface instead of REST

   1. REST first or Java first, parallel?

2. How to Test & Demo in CPS Team

Feb 13, 2024 

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.

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 Feb 13, 2024 

Why is NCMP forwarding the response, DMI could do this ?

Involve extra performance cost from CPS 

Feb 13, 2024  Implementation needed because of TBAC 

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 Feb 13, 2024 

Delivery artefacts

Required Artefacts

1. JavaDoc for new interface

2. Jar(s ?) for services support new interface

Aug 27, 2024  AP to confirm with Andreas in team Lightening

Feb 13, 2024 Csaba Kocsis to revert

Characteristics

Need to discuss priority of this. Delivering a functioning MVP for EPIC is important. Discussion and agreement with Peter T needed

Aug 27, 2024  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 

Feb 13, 2024 Csaba Kocsis  to revert

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 

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 : 

Subnetwork=22,MeContext=Kista,ManagedElement=Kista,GNBDUFunction=1,UECC=1

URI FDN example : 

/Subnetwork=22/MeContext=Kista/ManagedElement=Kista/GNBDUFunction=1/UECC=1

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. Feb 15, 2024  Rafael Rocha  ALL  cps

MVP (Minimum Viable Product) for DCM

1. Expected Delivery to EIC  Q3(August) to EIC. (Fossing and Testing)
   
   
   

2. Write Only Should be prioritized for target delivery (Q3). It should include
   - Batch write
   - NCMP should only check the cmhanlde of the first operation 
   - Should Databag be populated or not @kieran mccarthy / @Csaba Kocsis ?

3. Also included is status and results endpoint

4. NCMP should prioritize CPS-2009 Update remaining existing/legacy NCMP APIs to support alternate Id (FDN) - Developer Wiki - Confluence (onap.org) - over datajob Read. New Epic to be created for DataJob Read sperate this from 1964 - > CPS-2189

1. EIC Expected Delivery  Q3(August)Apr 22, 2024

DataJob Read v Write prioritization

Write should be prioritized over read

Apr 22, 2024

Use of '/ ' causes some issues

Not at issue. FDN can support / and ,

Apr 22, 2024

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

Apr 22, 2024

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.

@Kolawole Adebisi-Adeolokun @Peter Turcsanyi @Csaba Kocsis Apr 25, 2024

Decision to add status & result as part of this MVP

No new epic required for write, maintain current priority, wrap up this epic with;

1. Status - (Finished/Ongoing)

2. Result - (Success/Failure)

Jun 26, 2024 @Kolawole Adebisi-Adeolokun 

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 Aug 27, 2024 confirmed dataJobId can be used as the requestId

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.

@Kolawole Adebisi-Adeolokun // The output is currently being define by team Lighting AP @ko to follow-up