Agenda

Antitrust Policy

1. Edge Discovery Service

2. Application Endpoint Discovery

3. Edge Application Management

4. New API Application Endpoint Registration

5. Simple Edge Discovery

6. AOB

Minutes

Agreed new name Edge Discovery Service, new name: Optimal Edge Discovery

Analyze Application Endpoint Discovery alignment with other APIs.

Close the existing PRs before create a new PR to align Edge Application management with new APIs.

• PR-316, is related to:

•Deploy an AppInstance to a single Zone instead of multiple zones.

•Assign a name to the AppInstance.

•Adds more necessary information to the returned AppInstanceInfo, including the AppId (previously no way to figure out which App the AppInstance was an instance of).

• PR-318, is related to:

•Addresses a comment in #280 regarding the addition of the KubernetesClusterRef, and how users would expect to find it. While the KubernetesClusterRef can be found in the AppInstanceInfo, there may be clusters present without any AppInstances. The only way to see those clusters is via a cluster API to list the clusters.

•   PR-319, related to:

  • Clarifies the behavior of the GET appinstances API if there are no matching instances to return. Implementors may consider returning 404 in this case, but I believe it is more correct to return 200 with an empty list.

Topic 1

• Comments

Action items

•  Closed PR263, Jose Conde
•  Mahesh Chapalamadugu Feedback from Backlog group about Application Profiles.