Uploaded image for project: 'Near Realtime RAN Intelligent Controller'
  1. Near Realtime RAN Intelligent Controller
  2. RIC-58

O1-CM (not using ConfigMap) for the RIC platform and xApps, including MO (managed object) model.

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Medium Medium
    • ZZZ_future
    • None
    • o1
    • O1-CM (not using ConfigMap) for the RIC platform and xApps, including MO (managed object) model.

      xApp part already working.

      Thoralf: Still to be discussed, but it seems to be that platform components ask via RMR during their startup from O1 mediator (or RIC CM service) their config and Mediator responds with RMR message. Later changes are notified via RMR. Another good option is to do this via SDL and SDL notifications. Preferred solution: SDL.

      Testing is a bit more complex as now RMR/SDL needs to work to test this. So fallback to configmap for component testing might still make sense. 

      Note that earlier we promoted configmap, but that woudl (1) mean that platformcomponents must be managed by xApp manager (xapp!=platform). Another reason is (2) we need K8S security roles in O1 mediator that it currently does not need (yet).

       

      This item also includes  the use of the netconf yang RFC that allows dynamic addition of yang models.

       

      xApps will continue to use configmap (or at least in Bronze-R4), and we can decide later if they move to SDL as well in the future.

       

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            anpuhakk Antti Puhakka
            czichy Thoralf Czichy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: