2024-05-31 Quality on Demand - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: @Randy Levensalor @Thorsten Lohmar @dominik.fischer @Toshi Wakayama @Jose Luis Urien Pinedo @Ramesh Shanmugasundaram @Eric Murray @Masaharu Hattori @Maximilian Laue @Patrice Conil @Akos Hunyadi , @Konstantinos Fragkos 

Agenda

• Antitrust Policy

• Review of previous meeting minutes

• Overall Topics

• Regular Topics

  • Open Pull Requests

  • New Issues

  • Issues relevant for v0.11.0

• Any Other Topics

Minutes

Review of previous meeting minutes

• Previous meeting minutes: 2024-05-17 Quality on Demand - Meeting Minutes

Overall topics

• TSC: Reactivated discussion Commonalities/issues/171: Revise the device object definition to simplify it 

  • Met last week and the consensus is to use access token to identify the device when applicable

  • Discussion is continuing in the issue

Open Pull Requests

• PR #295 Add required security scheme and scopes by @Eric Murray

  • Agree with fine grained approached

• PR #296 Consolidation of changes related to session duration by @Jose Luis Urien Pinedo

  • Duration in QoS Profile and QoD use a different schema.  This is inconsistent, but doesn't break anything.

• PR #297 Add error 429 QUOTA_EXCEEDED by @Jose Luis Urien Pinedo

  • Discussion on 429 vs 403 moved to commonalities.

  • Changed to draft until above is resolved.

Closed issues

• none

New Issues

• none

Issues relevant for v0.11.0

• #292 Scope of QualityOnDemand for Fall24 CAMARA release
  
  

  • Need to add Issue #268 Provision mode for QoD to this release.

• #268 Provision mode for QoD

  • PR #294 Update README.md

  • @Jose Luis Urien Pinedo working on PR to complete this feature for the release

• #291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)

  • PR is open and being reviewed.

  • Action: Review and merge before next meeting if there are no objections.

  • Previous minutes

    • Covers also #288, #281, #280, #266, #249

    • @Jose Luis Urien Pinedo will make first proposal

    • discussed about maxDuration → establish again as absolute maximum

    • discussed about default for duration 

      • making duration parameter mandatory could be an option

• #257 Error behaviour when session cannot be created due to "time cap" limitation

  • Pending Commonalities discussion on error codes

  • Previous comments:

    • Will be addressed after PR #289 is merged

• #245 Update and enhance test definition file for QOD API

  • Commonalities has an open issue and QoD will align once this is approved. @Jose Luis Urien Pinedo is tracking and will share updates with QoD team.

  • Release management also has different requirements for test cases between released APIs.

  • Previous comments:
    
    

    • Telefonica has a feature file for testing, will adapt it to Commonalities results, and then contribute.

    • Commonalities PR #203 with design guidelines for .feature files and test coverage (sunny/rainy test cases). For first meta-release the full coverage will not be required.

      • CAMARA test cases will only test the correct reactions of the API, not the service (e.g. network performance or SLAs)

    • Sunny test cases have to added before first release candidate of v0.11.0 (mid of June)

• #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement

  • PR is created and waiting for a few more reviewers to merge.

  • @Eric Murray

    • @Eric Murray will create a PR. 

• #166 Extend QoS Profile queries to list profiles based on specific users or devices

  • Will track issue #101 for consistency

  • Previous comments 

    • @Randy Levensalor  will create a first PR

• #101 List endpoint for active sessions of authenticated user

  • Require device properties in the query to align with current session create API.

  • Can adjust to align with commonalities use that would enable three-legged token with optional device properties in a later profile?

  • This endpoint won't be able to get all sessions for a given API invoker and will be limited in scope to a device.

  • Previous comments

    • Please review latest proposal on this issue: https://github.com/camaraproject/QualityOnDemand/issues/101#issuecomment-2015041284

    • Draft PR #228 need to be closed and restarted due to the split and based on the discussion.

Further Issues

• #286 Review Attribute Descriptions with References to External Specifc

  • Further discussion is needed.

  • Adding 3GPP specific descriptions could cause confusion for other access networks and may not be relevant to API consumers. 

  • No update, previous content: 

    • @Herbert Damker check where QoD would be impacted 

    • Maybe into backlog until implementation experiences are available

Any other topics

• Next QoD meeting will be on June 14th, at 14:00 CEST / 12:00 UTC

Action items