Proposal: Introduce EdgeCloudFootprint in EdgeCloudZone (EAM) (follow-up from OED)

[DLondonoD]

Problem description

During the ongoing discussion about including EdgeCloudFootprint in OptimalEdgeDiscovery, several limitations and ambiguities were identified regarding how to define the coverage of an EdgeCloudZone within this API. As a result, it was decided to continue the discussion within the EdgeApplicationManagement (EAM) API, where this functionality is considered a better fit.

Possible evolution

Following the proposal by Mahesh, Kevsy, and the original proposal of Cody, a potential solution within the EAM API is to extend the GET /edge-cloud-zones operation by introducing a new parameter, latencyBudget. This parameter would represent the required latency threshold used to determine the coverage area. A first approximation of this parameter could be:

LatencyBudget:
      type: string
      enum:
        - low
        - medium
        - high
      description: |
        Latency required for an EdgeCloudZone.

Based on Kevsy's proposal, the description of the operation could be:

        List of the operators Edge Cloud Zones and their status, 
        ordered by location. This discovery can be filtered by a 
        specific geographical region (e.g., when data residency is required) 
        and by status (active, inactive, or unknown). It can also optionally 
        return coverage based on a specified latency budget.

This operation returns a list of EdgeCloudZones. The response may optionally include the EdgeCloudFootprint object when the latencyBudget parameter is specified in the request.

Additional context

This issue arises as a continuation of the discussion in the original OptimalEdgeDiscovery repository. A PR with these changes will be created once the new repository for EAM is available.