Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

at 14:00 UTC

Note time is 14:00 UTC 

Meeting Link:  https://zoom.us/j/719188490

Discussed


  • Recording : zoom_0.mp4
    • Chat Log: 
  • RC2 next :  Frankfurt Milestone Status    
  • Guilin release - functional requirements proposed list  impacts on ExtAPI
  • E2E Network Slicing - two Jira opened 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-449
     Enhancements for Service activation, deactivation, termination (based on TMF 641) and 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-450
     KPI Monitoring e.g., based on TMF 628. Discussion on the requirements for Guilin with Priyadharshini B Swaminathan Seetharaman Guobiao Mo
    • Slides presented: 5GNetworkSlicing_ExtAPI_2020060320200610_v1.0.pptx
    • Actions/updates:
      • @Robert Ludovic recommended to use serviceState (already defined in TMF 641)Briefly discussed reg. the use of TMF 641 APIs for service activation/deactivation instead of a new UpdateType field in the service order request.
      • serviceState to have the same value in the response to service order request. Check ExtAPI code to confirm this. Priyadharshini BAdrian OSullivan
      • For knowing the status of the service order, existing mechanisms supported by ExtAPI to be used. To be checked and confirmed with UUI team. Swaminathan SeetharamanPriyadharshini B
      • For knowing details of NSI/NSSI mapped to service, existing APIs to be used (to fetch relevant details from AAI).
      • DES is not recommended to be part of ExtAPI, based on the discussion during the meeting. However, if needed, we can re-visit this topic together with ArchCom, if a consensus cannot be reached.
      • Share the details of APIs/interface exposed by DES and its usage. Guobiao Mo
      • To take up discussion with @Jack Pugaczewski next week reg. use of TMF 628 or other standard interface for KPI monitoring, based on the details shared by Guobiao. Adrian OSullivan
      • Update ppt/termination. We will go ahead with the proposed approach based on last week's discussion.
      • Discussed with @Jack Pugaczewski reg. use of (modernized) TMF 628 for "On Demand" PM collection.
      • Share DES APIs (that would have been invoked from UUI), as well as the typical response from DES for a KPI monitoring request – can be the draft version. Guobiao Mo LUKAI
      • Get the draft updated TMF 628 swagger from Jack. Adrian OSullivan
      • Try to map the request from UUI to TMF 628 onDemandCollection Priyadharshini B Adrian OSullivan Swaminathan Seetharaman
      • If the mapping looks reasonable, make a simple start w.r.to implementation in Guilin release – this will have impact in UUI and ExTAPI. LIN MENG Swaminathan Seetharaman to confirm resources.
      • Update the ppt with relevant detailsPriyadharshini B/ Swaminathan Seetharaman/Guobiao Mo
      • Last week Items:
  • Update from TMF - MEF - ONAP alignment workshop Adrian OSullivan
  • Macromode for Guilin, 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyEXTAPI-258
      Former user (Deleted) - Support for when SDC instantiationType = macro
  • PTL call update: OOM call for POC with ServiceMesh for RBAC/Certificate management, currently AAF