Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community: 

NameOrganisationPresent?
Cristina Santana Casillas (Chair)TelefónicaX
Rafal ArtychTelefónicaX
Sergio Francisco OrtizTelefónicaX
Ricardo Serrano GutierrezTelefónicaX
Jhon Javier Lozal LucoTelefónicaX
Fabrizio MoggioTelecom Italia MobileX
Kevin Xu5GFF/Verizon WirelessX
Leo ChelyCabellabsX
Deepak GunjalCap GeminiX
Babu NarayanNabstractX
Vaibhav MehtaNabstractX
Uwe RauschenbachNokiaX
Nicola CadenelliNearby ComputingX
Randy LevensalorCablelabsX
Tom Van PeltGSMAX
Thomas VitsEdgeXRX
Kevin Smith (minutes, aka 'Kev')5GFF/VodafoneX
Joshua PengJC Drawn MobileX


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
    • Item 1 How to progress a Edge Cloud MVP (ref PR154)
      This is to help accelerate the implementation of an MVP which covers the Edge Cloud lifecycle (including Discovery and Lifecycle management)
      Option 1 is to maintain a sub-api separate API along with the existing APIs

      Option 2: merge PR54 with Simple Edge Discovery to produce a new MVP API for Edge Cloud

      Discussed by Sergio, Kev, Thomas, Deepak.

      Agreement: Proposed to go with option 2, but do not remove Simple Edge Discovery. . Result will be one new API (name to be decided) that includes 'MVP' lifecycle management and discovery (extending the functionality seen in the Simple Edge Discovery API)

    • Item 2 Discussion on Application vs Artefact

      Discussed by Sergio, Thomas, Deepak, referring to Jon's comments in PR 154
       
      Agreement: Combine Artifact and Application into a single type and update the PR with a new commi

  • Any Other Topics
    • Discussion led by Sergio on the topics raised in PR 159 on the addition of more granular discovery parameters in the Sime Edge Discovery API

      Discussed by Sergio, Kev, Kevin, Thomas, Cristina

      To be continued, general thought is that a way of discovering the application endpoint is needed for the 'MVP' API
    • Fabrizio raised issue 140, and whether we need  these branches 0.9.0, 1.0.0, 2.0.0 . If not they should be deleted.

Minutes

Action Item Review

DescriptionDue dateAssigneeTask appears on
  • Mahesh Chapalamadugu created PRs for the new 3 funcionalities that Edge Discovery Services could bring to the group.
Mahesh Chapalamadugu2024-10-01 EdgeCloud Minutes
  • Mahesh Chapalamadugu create some documentation about the flow and the interaction of the Edgecloud APIs.
Mahesh Chapalamadugu2024-10-01 EdgeCloud Minutes
nicolacdnll@nearbycomputing2024-10-01 EdgeCloud Minutes
  • Mahesh Chapalamadugu still pending the feedback from commonalities about how to proceed with Application Profiles API.
Mahesh Chapalamadugu2024-10-01 EdgeCloud Minutes
  • 1.SED official v1.0

    2.Open Topics: Edge Discovery Services (Functionalities)

    3.Update Edge Application Mangement API

    4.Approve and merge  PR-266 AED User story

    5.AOB

2024-09-17 EC Minutes
Mahesh Chapalamadugu2024-06-11 EC Minutes

Topic 1

  • Comments

Action items

  •  
  • No labels