Versions Compared

Old Version 5

changes.mady.by.user Jhon Javier Loza Lluco

Saved on

compared with

New Version 6

changes.mady.by.user Jhon Javier Loza Lluco

Saved on

Key

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

...

  • Roll Call
  • Action Items Review
  • Agenda Bashing
  • General Topics
      • Bi-Directional API whitepaper for MEC presented by 5GFF
        • Mahesh Chapalamadugupresented the whitepaper and the scope of the Bi-Directional API. Seems that those APIs don't fit in the scope of CAMARA EdgeCloud APIs so Cristina Santana (chair of the subgroup) proposed Mahesh Chapalamadugu and Brett Hill to bring the proposal to the GSMA OPG/OPAG group.
      • API current Situation
        • Traffic Influence:

          • Alignment with appId and appInstanceId terminology

          • Introduces EdgeCloudZones in the TI API

          • WIP include corrections for lint issue, some error/warnings don’t produce a problem in the API. Issue 161 in CAMARA Commonalities was created and seems to be solved in CAMARA Commonalities PR 169.

          • To check linter to confirm conformance with the Guidelines and close the PR(?)
        • Lifecycle Management:
          • New PR open to include harmonization results PR 208, documentation and user story included. Updated to abide with the Megalinter workflow.
          • Included first version of Test File (PR 211)
          • Issue 215 EdgeCloudZone harmonization (LCM & SED) to be closed. (To discuss the addition of MNC/MCC parameters in next release which helps identify the operator as properties of the EdgeCloudZone)
          • EndPoint Discovery PR 159 closedand proposedthe creation of a new API (Discussion 212)
        • Simple Edge Discovery:
          • PR 194 updated with the EdgeCloudZone schema to harmonize the API with the LCM API and to comply with Megalinter workflow
      • Ongoing discussions

        • How to enable computing resources selection: Flavors or dynamically (Discussion 220)

          • Flavours are discarded due to the complexity of standardisation. 
          • Dynamically selection is the approach to follow but we need to discuss more in terms of the supporting not only VMs and Containers but also Helm Charts and Docker-Compose files (that will bring some complexity to retrieve the requirements from this file)

        • Proposal for new API for application endpoint discovery case (Discussion 212)

          • Proposal accepted. Now we need a volunteer to be the owner of this new API, this means to be in charge of creating the PR with a draft of the yaml and the minimum requirements to have a first release version in CAMARA #170. All the members of the subgroup will provide feedback and improvements to the draft as we usually do. It would be appreciated to have the volunteer for the next meeting at 9th 16th of April if you want to apply, discussion 220 is the place.
      • Other topics
        • Nicola to present a proposal to improve EdgeCloud APIs at the next meeting.
    • Any Other Topics
        • As this week is a public holiday in many countries, we are cancelling the meeting on 2 April and the next meeting will be on 16 April to keep the slot reserved.
  • Any Other Topics

...

  •  Nicola to present his proposal to improve EdgeCloud APIs 09  
  •  fabrizio moggio to present the new TI API requirements (Discussion 217 and 218) 09