Addresses:
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Initial description:
...
It was mentioned several times the xNF Proxy will interact with CPS using Java API. It means the only possible
way of integration is embedding the cps modules as jars int xNF Proxy web application as it's described in
CPS-171 CPS xNF-Proxy Deployment and module dependencies and being implemented via
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Drawio | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
This approach requires confirmation.
...
addresses:
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
It's expected the xNF Proxy has to use predefined dataspace, schema set (set of yang resources) and associated anchor (? see below)
in order to perform proper requests via CPS service API.
...
- is usage of multiple anchors (name to be provided on request via REST API) is expected?
- or the only anchor to be used (MVP) , is the one with name predefined (configured)
...