CPS-3194: Cloud Infrastructure Support
References
https://lf-onap.atlassian.net/browse/CPS-3194 — Epic: Cloud Infrastructure Support
CPS 2026 Release Planning — Release Planning (rows 15, 16, 19)
https://lf-onap.atlassian.net/browse/CPS-3241 — Multiple Data Producer IDs (shares the "try next on 5xx" / legacy data path)
https://lf-onap.atlassian.net/browse/CPS-3193 — Cascading Actions Support (sibling study)
https://lf-onap.atlassian.net/browse/CPS-3305 — Legacy interface Alternate Id Encoding (baseline)
https://lf-onap.atlassian.net/browse/CPS-3306 — Longest-match alternate id search (baseline)
CPS-<####>: Implementation Proposal Template — Implementation Proposal Template
Goal
Support E//-managed Cloud Infrastructure (where Cloud RAN is deployed) in CPS-NCMP.
This adds 4 new top-level node types: NetworkElement, CloudInfrastructure, CloudInfrastructureManager, OCloud — in addition to the existing MeContext, SubNetwork, ManagedElement. Discovery, registration and the CM Handle inventory model are unchanged; the new nodes register as ordinary CM Handles.
"Top-level" means: when one of these types is present, it is the last element in the alternate-id (FDN). They behave exactly like the existing specific/terminal types (MeContext/ManagedElement), including the contains(id, ...) search and longest-match resolution. Container segments (e.g. SubNetwork) may precede them.
FDN examples for NetworkElement (the other 3 types follow the same rule):
/NetworkElement=NE1
/SubNetwork=SN1/NetworkElement=NE1
/SubNetwork=SN1/SubNetwork=SN2/NetworkElement=NE1
/SubNetwork=SN1/MeContext=ME1/NetworkElement=NE1
/SubNetwork=SN1/SubNetwork=SN2/MeContext=ME1/NetworkElement=NE1Code analysis — affected areas & changes needed
A codebase-wide search was done for every consumer of alternate-id resolution (all callers of AlternateIdMatcher) and every user of JexParser. The node-type names are hardcoded as a matching rule in only two production spots, both on the data-job read path. Everywhere else the FDN/reference is treated as an opaque string and passed straight to the (type-agnostic) matcher, or built by the generic FDN-prefix parser — so those paths already handle the new types with no change.
Changes needed
File | What / why | Change | |
|---|---|---|---|
| 1 |
| Extracts the search term from a | Add the 4 new types to the alternation |
| 2 |
|
| Add the 4 new types to the alternation |
| 3 |
| Unit coverage (100% rule) | Extend |
| 4 |
| Unit coverage (100% rule) | Add a data-driven test asserting the 4 types classify as specific nodes (routed to DMI, not broadcast) |
The generic FDN-prefix builder JexParser.extractFdnPrefix matches any Name[id="…"] segment, so it already rebuilds all the FDN examples above correctly. Only the two search/specific-node patterns are type-gated.
Verified NOT affected (no change needed)
Consumer | How it resolves the FDN | Why no change | |
|---|---|---|---|
| 1 |
| Uses | No |
| 2 |
| Passes decoded reference string → matcher | Opaque string; no type gate |
| 3 |
| Passes | Opaque string; no type gate |
| 4 |
| Passes DN/ | Path/DN-based; no type gate |
| 5 |
| Uses generic | Already type-agnostic |
| 6 |
|
| Opaque reference; no type gate |
| 7 |
| Longest-match on the FDN string | Segment/type-agnostic by design |
Issues & Decisions
Issue | Notes | Decision | |
|---|---|---|---|
| 1 | Which cloud node types must be supported? | NetworkElement CloudInfrastructure CloudInfrastructureManager OCloud | Agreed Csaba Kocsis |
| 2 | Do the 4 new types require YANG models? | No change for NCMP discovery & registration - register/discover via the existing flow. | Agreed Csaba Kocsis |
| 3 | What identifies a cloud-infra CM Handle (type field, module set tag, property)? | None needed. Discovery/registration unchanged, so the nodes register as ordinary CM Handles; alternate-id resolution keys off FDN segment names, not a type field. | Agreed Csaba Kocsis |
| 4 | Performance / KPI impact | 100k cm handles with use of optimised model |
|
| 5 | DCM read impact | Can be seperated "DCM" = the test-only | Agreed Csaba Kocsis |
Out of scope
Legacy batch and model request handling. Assumes optimised model enabled and ModuleSetTag reused as-is (as IaS).