DRAFT AGENDA
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff: na
Community: Eric Murray Thorsten Lohmar Randy LevensalorBen Hepworth Akos Hunyadi Rafal Artych Mahesh Chapalamadugu Joachim Dahlgren Ramesh Shanmugasundaram Toshi Wakayama Syed Rehman Ria Das Konstantinos Fragkos Ben Hepworth Jose Luis Urien Pinedo
Agenda
- Antitrust Policy
- Review of previous meeting minutes
- Overall Topics
- Device object definition discussion
- 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-31 Quality on Demand - Meeting Minutes
- No comments
Overall topics
- GitHub Teams @camaraproject/quality-on-demand_codeowners and @camaraproject/quality-on-demand_maintainers available
- Please use them to notify especially the Maintainers about PRs which should be reviewed
- Note: you can add the Maintainer team also as a reviewer ... but GitHub will drop it from the list as soon one Maintainer has done a review "on behalf" of the team. On the positive side all Maintainers have then got a notification of the PR and that they can/should have a look on it
- Discussion Commonalities/issues/171: Revise the device object definition to simplify it
- See also the issue opened within QoD: https://github.com/camaraproject/QualityOnDemand/issues/300
- Commonalities is waiting for feedback
- Discussion:
- Device object will be made optional, but we need to document the cases in which it can be omitted by the API consumer, and it which cases the additional from device object is needed
- NAI might be needed for IoT device cases (having not MSISDN assigned) - but that is a general decision for the project, not specific to QoD
Open Pull Requests
- PR #295 Add required security scheme and scopes by Eric Murray
- Herbert Damker Should we add an explicit "manage" scope which includes all session operations? (can be done also in separate PR)
- Points to document:
- Device object depending on used authentication => separate PR (after decision in Commonalities #171)
- Endpoints which have different behaviour with 2-legged vs 3-legged
- Endpoints which don't require 3-legged token (no user resource involved)
- Eric will update the PR
- PR #296 Consolidation of changes related to session duration by Jose Luis Urien Pinedo
- Ready to be merged
- New issue to discuss format alignment between session and profiles
- PR #299 New API QOD Provision
- Jose introduced the proposed API
- Eric: the API still allows to have multiple provisions? Or should it be restricted to one, and enhance the complete traffic of the device (would simplify the API a lot)
- Jose: all traffic is one use case (hence applicationServer as optional proposal)
- Are there use cases to provision QoD for specific flows (defined by applicationServer)? - Jose will ask on product side
- PR #301 Make + prefix mandatory for phoneNumber
- Merged
- PR #302 fix for enhancement proposal #302
- Background material for issue #302, see below
- Herbert Damker proposal to change to draft until the issue is discussed
Closed issues
- #291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)
- Closing also: #288, #281, #280, #266, #249
- Should we create a new issue to the format alignment with Commonalities? Yes → Herbert Damker
- #298 Align phoneNumber with guidelines, with prefix + mandatory
- see PR #301 above
New Issues
- #300 Simplification of Device object - short term solution
- see discussion above
- #302 Providing developers with alternate to QoS profile
- new enhancement proposal by Mahesh Chapalamadugu
- ...
Issues relevant for v0.11.0
- #292 Scope of QualityOnDemand for Fall24 CAMARA release
- From last call: Need to add Issue #268 Provision mode for QoD to this release (Herbert Damker done)
- ...
- #268 Provision mode for QoD
- See PR 299
- #257 Error behaviour when session cannot be created due to "time cap" limitation
- PR #297 still in draft or ready for review?
- #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
- see PR #295
- #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
Any other topics
- Next QoD meeting will be on June 14th, at 14:00 CEST / 12:00 UTC