2024-10-01 EdgeCloud Minutes

Owned by Jose Conde, created
Last updated: Oct 02, 2024
2 min read

Community Attendees:

@Jose Conde @cristina.santanacasillas @Gerasimos Papanikolaou @Ben Hepworth @fabrizio moggio @Reda.Zaza @Mahesh Chapalamadugu @Kevin Smith @deepak gunjal

Community Attendees:

LF Staff:

Agenda

Antitrust Policy

  • Action Items Review

  • Agenda 1

  1. Edge Dicovery Services API

  2. Update Edge Application Mangement API

  3. TI API Improvements

  4. AOB

ย 

Minutes

The evolution of Edge Dicovery Service API:

1.Still pending to merge PR263, update old exposure and experience management API to Edge Discovery Services. Any news about the question to have an API for several Camara groups (Application Profiles )??

2.Once we have the PR approved, we can start with the next steps:

1.Create a PR to update AED with EDS.

2.Create a PR for Application Endpoints functionality to be a new API.

3.The Possibility of Application Profiles as a multi group API.

ย 

We have some PRs to update EAM:

New comments from Jon in the PR280 about the update of Required resources. All solved, one approval, Merge?? New comment of adding disk space.

Four PRs to update the API:

  1. PR252ย  Add the missing AppProvider to the AppManifest model. This is the oldest one, I think we can Merge it.

  1. PR298ย  Add Get/Apps to retrieve created applications.

  1. PR302 Removes appId from the appinstances path.

  1. PR305ย  Change AppManifest version from int to string

Also there are some PRs to improve TI API:

  1. PR287 Improvement of the Test .feature file.

  1. PR296 Resource modification while action is still in progress.

This last PR originates a discussion 309 about the TI API, the API documentation is not clear enough about who is responsible to target the service data flow to right EAS.

โ€ขAny other topic?

Pending to merge PR266 user story of AED.

New PR308 (Correction of GitHub username in MAINTAINERS.MD). Deepakโ€™s username.

Disscusion 306 created by Reda about the potential benefits and challenges of incorporating serverless functions.

Action items

@Mahesh Chapalamadugu still pending the feedback from commonalities about how to proceed with Application Profiles API.
@Mahesh Chapalamadugu created PRs for the new 3 funcionalities that Edge Discovery Services could bring to the group.
@Mahesh Chapalamadugu create some documentation about the flow and the interaction of the Edgecloud APIs.
@nicolacdnll@nearbycomputing @deepak gunjal@fabrizio moggio as codeowners, please review the PRs, and give your feedback.