Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Tacker team proposal for the L release - Toshi san 15 mins
    1. https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13570027/Tacker%20L-Release_for%20SMO_Jan_rev3.pptx?api=v2
  2. Open MSA introduction session in the next SMO session - 25 mins (continuation from UBiqube).

View file
namevideo1334142195.mp4
height250

Prev Agenda:

  1. https://lf-o-ran-sc.atlassian.net/wiki/download/attachments/13570027/Tacker%20L-Release_for%20SMO_Jan_rev1.pptx?api=v2 - Toshi san
    1. We will revisit the Tacker work load for the K release and evaluate the tasks committed.
  2. Open MSA as a NFO has been brought to the notice of the SMO by Tacker team https://github.com/openmsa 
    1. We need more clarifications on this item - Kuno San to get back with the details.
    2. Some of the key aspects to check would be
      1. Licensing of the Open MSA (GNU license...)
      2. Providers and maintainers of the code base - (UBiqube, Fujitsu... )
      3. Background of the arch, design and integration points with the SMO
      4. NFO should ideally support both K8s and ETSi DMS, this should also be checked in detail
      5. How the existing code can integrate with this tool needs to be clarified
      6. K release would be too short to include it in the main stream, would recommend to clarify these details and then would collectively take the decision
      7. We would look into the details and take further decisions, this could take multiple  iterations as and when needed.
      8. Would like to propose the collective findings to the RSAC and ToC for the approval before we commit it as part of the release.
  3. Open MSA introduction session in the next SMO session - 20 mins (Herve Guesdon from UBiqube).
  4. NFO intro for the demo provided as part of the Montreal F2F - (Vamsi / Vishal) - Open Item
  5. T&IV - K release scope - John K
    1. Model are being refined for the ORAN integration,
    2. Entity groups are being evaluated and worked upon.
    3. WG10 of ORAN spec are being worked upon and recommendations would be provided as we find the updates
    4. N/w Topo generator is being used to fill the topo view and the integrations adapters are being worked upon. - Martin S
    5. Gather logical view from the ETSi profile of the deployed nodes through tacker is being requested. Toshi san
  6. Usecase defined models to be incorporated and showcase the Capabilities once the sample data are available (Stretch)
      1. Topo info is loaded we can showcase of the CNF migration across the subclouds (also at the Geo-Distributed arena)
      2. sync DMS data between Tacker and datastore model (draft version) and show the effects of that on the CNFs - (long run goal)
  7. Secure communication between the modules - this is in general between the OSC components. (Stretch Goal across the ORAN-SC modules)
    1. Dmaap - Kafka messaging
    2. Strimzi based comm as an extension to the above one.
    3. this needs to be implemented across the OSC components (like pub-sub)
    4. SMO (O2) DB
  8. K-Release details
    1. K Release#ServiceManagementandOrchestrationLayer(SMO)

...