CPS-3241: Support Multiple Data Producer IDs — Requirements Gathering Prep
References
https://lf-onap.atlassian.net/browse/CPS-3241 — Epic: Support Multiple Data Producer IDs (Open, Highest priority, assignee Toine Siebelink, no child stories yet)
CPS-3241: Support Multiple Data Producer IDs — Existing analysis page (assumptions, decisions, proposed stories, costs)
CPS 2026 Release Planning — Release Planning (EIC Delivery 26 Q4, ~10 dev weeks, Lead TBD)
Summary
Today a CM Handle has a single dataProducerIdentifier; CPS-3241 requires to add a list of alternative producer identifiers and fails over to the next one when the primary returns a server-side (5xx) error, promoting the working one and emitting an LCM event.
Requirements
Scope | Current | Requirement | Open issues | Decisions | |
|---|---|---|---|---|---|
| 1 | Registration model | CM Handle holds a single No concept of alternative producers. ( | Add |
|
|
| 2 | Registration - Create | Bulk operation; each CM Handle succeeds/fails independently with per-handle error responses. | Persist |
|
|
| 3 | Registration - Update |
| Full-replace semantics for the list (consistent with existing collection fields). Emit LCM event only when the list changes. New value rides along in the existing LCM V2 payload map, no event schema change. |
| Agreed, same behaviour as current Csaba Kocsis |
| 4 | CM Handle read / query output | CM Handle GET (full and lightweight) and the lightweight query service return the single | Decide whether the | Include the "others" list in GET / query output, or only the primary? |
|
| 5 | Legacy data; try-other | Synchronous single-handle read/write resolve one CM Handle and call DMI once; on failure a | Minimal change: same read/write behaviour, only add failover. On primary failure, retry against the next If all fail → unchanged error (last attempt's error surfaces as today). Batch/async out of scope. |
| Minimal-change behaviour
|
| 6 | Promote primary / other & LCM event | Swap + LCM-emit logic exists only inside the registration-update flow ( | Provide a reusable "promote/swap primary ↔ other, persist, emit LCM event" operation callable from both registration-update and the try-other data paths. |
| Swap triggers LCM event Csaba Kocsis |
| 7 | ProvMnS - intercept error, then try-other | ProvMnS is forward-only: NCMP does not inspect the DMI result, so it cannot react to a 5xx. Retrieval requires a non-blank | First make NCMP intercept/detect the DMI error (stop being forward-only). Then apply the same try-other + promote mechanism as the legacy path. | (1) Intercepting the error is a prerequisite for try-other — confirm the two are sequenced (intercept first) and the reaction mirrors the legacy path. | Sequence intercept before try-other; reuse legacy mechanism. To be confirmed. |
| 8 | DCM- promote primary / other (Java) | DCM groups sub-jobs via | NCMP provides a new Java method DCM calls to promote the next "other" (incl. LCM event). DCM implements its own try-other and invokes it. REST outside our scope.? |
| NCMP provides the Java method only (signed off: model interfaces not affected). |
| 9 | Other events | LCM V2 payload is a generic map; adding a tracked property needs no schema change (verified in | Confirm which existing events (beyond LCM) are affected and whether any schema impact exists. | Are any non-LCM events affected? | Csaba Kocsis expects none - To be verified. |
| 10 | Documentation | Docs describe the single | Document the new field, registration contract, try-other / promotion behaviour, and REST output changes. | - |
|
| 11 | YANG registry schema | leaf data-producer-identifier {
type string;
} | backward compatible |
|
|
| 12 | REST output
|
|
| expose otherDataProducerIdentifiers in GET and query responses, or keep it registration-only and return just the primary on read? |
|
Routing note (important for how "try-other" works): within NCMP the DMI endpoint is resolved from the CM Handle's dmi-service-name (DmiServiceNameResolver.resolveDmiServiceName(...)), not from dataProducerIdentifier. The producer id is carried in the request payload and used as a grouping key (ProducerKey = dmiServiceName#dataProducerIdentifier). So swapping to an "other" producer id changes the payload/grouping NCMP sends, but the NCMP→DMI route is unchanged - whether that actually redirects to the other E// depends on how the DMI/adapter uses the producer id (adapter changes are out of scope).
Out of scope
Legacy Batch (fire & forget, async, Kafka results).
Model endpoint / model interfaces.
DCM implementation costs (NCMP provides the Java method only).
Adapter changes to support ProvMnS use cases.