Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Bug/Improvement needed for Ric Repository operations

Description

  1. Insufficient query parameter checks for getRic
    Currently allows unsupported query parameters.

    1. V2 AP1:
      https://docs.onap.org/projects/onap-ccsdk-oran/en/latest/offeredapis/pms-api.html#tag/NearRT-RIC-Repository/operation/getRic

    2. V3 API:
      https://docs.onap.org/projects/onap-ccsdk-oran/en/latest/offeredapis/pms-api-v3.html#tag/NearRT-RIC-Repository/operation/getRic

  2. Remove getRic query parameter ”managedElementId” for v3 getRic operation
    https://docs.onap.org/projects/onap-ccsdk-oran/en/latest/offeredapis/pms-api-v3.html#tag/NearRT-RIC-Repository/operation/getRic

  3. Explain what happens when the same managedElementIds is set for multiple ‘ric’s in the config. And the expected behaviour when that “managed_element_id” is passed to v2 getRic operation

  4. Make ”managedElementIds” configuration field for each ‘ric’ optional (will affect v2 & v3)
    Dynamic Configuration of A1-PMS - Wiki - Oslo
    /config/application_configuration.json (oslo) - Sample Config
    application_configuration_schema.json (oslo) - Config schema

  5. Change getRic query parameter ”ricId” into a path parameter for v3 getRic operation
    https://docs.onap.org/projects/onap-ccsdk-oran/en/latest/offeredapis/pms-api-v3.html#tag/NearRT-RIC-Repository/operation/getRic

  6. Document all of the above!

Activity

Show:

Saul Gill February 26, 2025 at 5:12 PM

For number 2 above. If the “managedElementId” is removed for the V3 API call to getRic, this breaks the call to the V2 API ric controller. All V3 does in this case is forward a call to V2

Why does it break? V2 expects a call to include “managedElementId”.

We could

  1. Pass in a null

  2. Re-implement the actual getRic logic in V3

Passing in a null may be the better option in this case - it will avoid duplication and will allow easier rejection of extra redundant query parameters

Saul Gill February 26, 2025 at 4:37 PM

For the above:

Explain what happens when the same managedElementIds is set for multiple ‘ric’s in the config. And the expected behaviour when that “managed_element_id” is passed to v2 getRic operation

In this case, in the V2 API, if multiple RICs are configured for the same managedElementId and a call is made to getRic, only one RIC is returned in the response. It will NOT return an array of RICs.

Done

Details

Assignee

Reporter

Labels

Due date

Fix versions

Priority

Parent

Created February 26, 2025 at 12:14 PM
Updated April 8, 2025 at 9:25 AM
Resolved April 8, 2025 at 9:25 AM