2024-04-16: SP-EDC Minutes

Owned by Jhon Javier Loza Lluco
Last updated: Apr 19, 2024 by Reda.Zaza
3 min read

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community:

Cristina Santana Casillas (Chair)

Telefónica

x

Rafal Artych

DT

 

Ricardo Serrano Gutierrez

Telefónica

x

Jhon Javier Loza Lluco

Telefónica

x

Fabrizio Moggio

Telecom Italia Mobile

x

Kevin Xu

5GFF/Verizon Wireless

 

Leo Chely

Cabellabs

 

Deepak Gunjal

Cap Gemini

x

Babu Narayan

Nabstract

 

Vaibhav Mehta

Nabstract

 

Uwe Rauschenbach

Nokia

 

Nicola Cadenelli

Nearby Computing

x

Randy Levensalor

Cablelabs

 

Tom Van Pelt

GSMA

x

Thomas Vits

EdgeXR

x

Kev Smith

Vodafone

x

Joshua Peng

JC Drawn Mobile

 

Mourad Khanfouci

Mitsubishi electric

 

Mark Cornall

GSMA

 

Andrew Wajs

 

 

Navdeep

DT

 

Pablo Montes Moreno

Kyndryl

 

José Manuel Conde

Telefonica

x

Prashant Goswami

 

 

Surajj Jaggernath

Vodacom

 

Jose Domingos

Ori

 

Nikolaos Petropouleas

 

x

Andre Florath

DT

 

Mahesh Chapalmadugu

5GFF/Verizon Wireless

 

Apostolis

Lenovo

 

Reda Zaza

Telus

x

Agenda

The project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

  • Roll Call

  • Action Items Review

  • Agenda Bashing

  • General Topics

    • API current Situation

      • 1.Traffic Influence.

        • Minor changes may be needed to comply with conformance in API guidelines ( Issue 191). 

          Linting rules (spectral) have been updated to be compatible with TI API methods definition. @fabrizio moggiocheck whether the MegaLinter is sufficient to meet the guidelines. 

        • Changes done in documentation (harmonization Discussion 196 to be closed once MegaLinter test is passed.)

        • Addition of 3Legs Auth for Consent Management and xcorrelator as proposed in the Guidelines. To be used as a reference implementation for LCM API

        • PR 167 TI API v0.9.3 for approval and merger. It will be merged once YAML passes the MegaLinter test.

        • Presentation of new requirements (Issue 217 and 218), no questions have been raised.

        2.Life Cycle Management.

        • PR 208 approved and merged.

        • EndPoint Discovery PR 159 closed and proposed the creation of a new API (Discussion 212). A first draft will be contributed by TEF

        • Implementation of Consent Management (3Legs) and X-Correlator to be included.

        3.Simple Edge Discovery.

        • SED API v0.9.4-rc.1 approved and merged.

        • Proposal to move the API to the version 0.9.4 that will contain some updates (X-Correlator, etc)

        • Proposal to create 1.0.0 version as SED API meets all the criteria for a 1st stable version. Anyway is still pending to define the compliance of the API Family as is being discussed in Open issues - CAMARA Project - Confluence. 

        • @Kevin Smithwill raise a new PR for version 1.0.0 which will be held until the next meeting on 30 April to be merged.

        4.Edge Cloud Family.

        • E2E Use case/User Story first draft based on Discussion 206 to be contributed by TEF

        • User Story, Documentation, Gherkin Test per API contributed.

        • New way of documenting an API, @fabrizio moggio will update on the right way to approach this issue.

        • We need to discuss how to comply with the Multiple APIs in one API Sub-project guidelines. Discussion 227 was raised. @Kevin Smith will update us on this topic.

    •  

      Action Points for LCM API

      • A draft for the new API to cover the intent 21 will be contribute by TEF

      • Keep discussing on how to enable the computing selection on Discussion 220

      • Create a new discussion to define the usage of Unique Identifiers

    •  

      Criteria to release the 1st stable version

      • SED API meets all the criteria and was mentioned that it was tested by 2 operators (Telstra and Vodafone)

      • TI API needs to comply with the MegaLinter criteria and to confirm if common datatype is used if needed. Some updates on the API will be contributed by @fabrizio moggio to add new requirements

      • LCM API to implement 3Legs, X-Correlator and check common datatype usage. Some updates on the API will need to be contributed to cover all the intents agreed for the MVP version.

      • Clean the Edge Cloud Repository:

        • Close/recapture old Discussion, PRs and Issues.

        • Reorganize the folders and files.

    •  

    •  

      Other topics

      • @Deepak will ask in Commonalities how to configure MegaLinter to test only the important YAMLs and not all the files and also the availability of a tool to check the common parameters across APIs.

      • @Nicola will raise a discussion to cover new requirements on SED and LCM APIs based on real use cases.

  • Any Other Topics

Minutes

Action Item Review

Topic 1

  • Comments

Action items