DRAFT MINUTES

Agenda

Antitrust Policy

1.LS from ETSI MEC

2.API current Situation

3.Changes on Traffic Influence API

4.Changes on Edge Operations Management API

5.Criteria to release the 1st stable version

6.Edge Cloud Repository Maintenance

7.Other topics

Minutes

1.LS from ETSI MEC

• • LS from ETSI MEC received and forwarded to the Edge Cloud mailing list
  • An acknowledgment has been sent to ETSI
  • No more action required on CAMARA side

2.API current Situation

1.Traffic Influence.

• • • PR 214 TI API v0.9.4-wip for approval and merge. Includes Documentation in the YAML.
    • New Discussion 230 Potential requirement: Device Source IP Port

2.Edge Operations Management.

• • • New PR 224 Edge-Operations-Management API v0.9.3-wip with corrections to pass Megalinter and Spectral tests, addition of X-Correlator and includes Consent Management.

3.Simple Edge Discovery.

• • • New repositoryhas been created as resolved by Commonalities/TSC to release a v1.0.0.

4.ApplicationEndpoint Discovery.

• • • EndPoint Discovery PR 159 closedand proposedthe creation of a new API (Discussion 212)
    • A first contribution has been made by TEF in PR 245, to be reviewed by all the participants.

5.Edge Cloud Family.

• • • E2E Use case/User Story first draft based on Discussion 206 to be contributed by TEF
    • Guidelinestorelease v1.0.0
    • Repository Maintance
      • Releases in Discussion 227
      • New folder structure
      • Review pending PRs, Issues and Discussions

3.Changes on Traffic Influence API

Device Source IP Port - Discussion 230

Issue: Currently the TI API doesn't support a Device with source port number.

Proposal: To clarify in TI Documentation de UE Identification, based on

4.Changes on Edge Operations Management API

In PR  224:

• • • New name to better identify the capabilities offered by the API
    • Addition of x-correlator
    • Corrections to pass Mega Linter and Spectral
    • Documentation in the YAML
    • New version format following Commonalities: 0.9.3-wip and URL edge-operations-management/vwip

Next Steps (Add enhanced functions):

• • • How to enable computing resources selection: Flavors or dynamically (Discussion 220)
    • Agree on dynamically approach
    • LCM API v0.9.3 contains the selection of resources based on parameters
    • Implementation of an orchestrated deployment based on files to be defined
    • Discuss on the usage of Unique Identifiers

5.Criteria to release the 1st stable version

EdgeCloud Group Next Steps Proposal

• • • Wait until Commonalities version 0.4.0 is released to start working on the new requirements
    • Meanwhile, we can work on WIP YAML versions that complies with commonalities v0.3.0

6.Edge Cloud Repository Maintenance

The Structure has been updated and the following needs to be consider:

• • • To release a first version of an Edge Cloud API it is necessary to create a specific repository that means Edge Cloud Repository will not host any v1.x.x API.
    • We would need to update README.md describing how the API’s are managed and the reference to the corresponding Repository if is the case.
    • We need to define a process to describe how to manage the current API YAMLs/related-docs:
    • Current versions:

1.Keep working normally

• • • API ready for a v1.0.0 release:

1.Ask the creation of a new repository

2.Move YAML and Test_Definitions. Kevin Smith to move SED.test to the new repository

3.Create a .md with the link of the new Repo

Topic 1

• Comments

Action items