...
...
...
...
...
...
...
...
...
...
...
Attendees & Representation
...
- 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 information from device object is needed
- NAI might be needed for IoT device cases (having not which have no MSISDN assigned) - but that is a general decision for the project, not specific to QoD
- Action: Provide the above as feedback into the Commonalities' discussion Herbert Damker
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)
- Device object depending on used authentication => separate PR (after decision in Commonalities #171)(have we made a decision on that?)
- Eric will update the PR with documentation for the following points:
- Endpoints which have different behaviour with 2-legged vs 3-legged
- Endpoints which don't require 3-legged token (no user resource involved)
- The dependency of the Device object on the used authentication will be documented in a separate PR (after decision in Commonalities #171)
- Herbert Damker Should we add an explicit "manage" scope which includes all session operations? (can be done also in separate PR)
- PR #296 Consolidation of changes related to session duration by Jose Luis Urien Pinedo
- Ready to be merged (done)
- New issue to discuss format alignment between session and profiles to created (done)
- PR #299 New API QOD Provision
- ...
- Jose introduced the proposed API
- Eric: Does the API still allow to have multiple provisions per device? 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 only one possible use case (hence 'applicationServer' is proposed to be optional)
- Open: 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
- Ready to be merged
- ...
- 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 (done)
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, as backlog issue (done)
- #298 Align phoneNumber with guidelines, with prefix + mandatory
- Closed with 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
- ...discussion to be continued within the issue
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
...
- #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)
- No update, see previous meeting minutes
- #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
- no update (will be done in consistency with #101 by Randy)
- #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.
- Jose Luis Urien Pinedo proposed a list endpoint for provisions within PR #299 and recommends to take this as template.
Further Issues
Any other topics
- Next QoD meeting will be on June 14th28th, at 14:00 CEST / 12:00 UTC
Action items
- Provide the discussion result for https://github.com/camaraproject/QualityOnDemand/issues/300 as feedback into the Commonalities' discussion Herbert Damker