2024-02-06: SP-EDC Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff:

Community:

Agenda

• Roll Call
• Action Items Review
• Agenda Bashing
• General Topics
  
  • Goal before MWC. Have an agreement on first version on LCM and Discovery APIs.

                     Reminder of comments in previous meeting:

• • • Confirmed we do not require a v1.0 for MWC
    • APIs should at least conform to CAMARA Commonalities and Identity & Consent management guidelines

• • Changes on MVP EdgeCloud_LcM.yaml pending approval

    oPR 165: Add location header in POST app response

                              Fabrizio to double check the us of header Location also in Traffic Influence other tant that ready for merging if no further comments.

oPR 166: Virttype and image types options   

                              Deepak will review last comment to check if there is something else to change.

oPR 168: Improving descriptions of schema related with artifacts URI

Ready for merging if no further comments.

oPR 188: New. Simplify and establish relationship between some of the parameters like Uri and component and componentSpec

        Several comments already taken into account. Giving some more time for comments as there are several changes before approving.

oPR 189: New. Added componentEndpointInfo and AccessEndpoint

      Giving some more time for comments as there are several changes before approving.

• • • Criteria for stable release ( Discussion #170)
      •  Confirm conformance with API Design Guidelines: run the CAMARA linter locally and fix any errors reported.
        • Issue 190. Simple edge discovery
        • Issue 191. Traffic Influence

                                               Fabrizzio will have a look.

• • • • Issue 192. Edgecloud_Lcm

                      Rafal, commented that current drat spectral version will be moved to main branch commonalities soon, and tests should be rerun. Warnings may be skipped if there are a justification for it ( for example descriptions very obvious in context or existing at other level).

• • • Add the CAMARA consent code and documentation

      • After revision of Authorization and authentication common guidelines, the code section in Mandatory template for info.description in CAMARA API specs needstobeincludedin all APIs.
        
        

    • Check for any common datatypes to reuse from commons.json

      • Non compulsory, as a good practice it should be checked before delivering candidate release version.

    • A Gherkin .feature file in Test definitions

      • TI OK in main branch. https://github.com/camaraproject/EdgeCloud/blob/main/code/Test_definitions/Traffic_Influence_Test.feature
      • Simple Edge Discovery . Existing test file to be located ( and moved to code/Test_definitions?)
      • Edgecloud_LcM. Pending to generate .feature file

• • Harmonization of concepts/items among Simple  Edge Discovery/MVP/Traffic Influence
    • Existing issue move to discussion https://github.com/camaraproject/EdgeCloud/discussions/196.
    • A Poll is created just after the meeting to vote on options https://github.com/camaraproject/EdgeCloud/discussions/197, the resultant naming should be incorporated to existing yamls and documentation.
• Any Other Topics

Minutes

Action Item Review

Topic 1

• Comments

Action items

• Sergio Francisco Ortiz generate Poll to vote for naming options after discussion on https://github.com/camaraproject/EdgeCloud/discussions/196. 07 Feb 2024 Voting to end by next week 15 Feb 2024 
• @Thomas Vits, to create new discussion to clarify all possible discovery and actors involved in each case, before next meeting 20 Feb 2024