DRAFT AGENDA
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff: na
Community: Randy Levensalor Ben Hepworth Thorsten Lohmar Maximilian Laue Eric Murray Akos Hunyadi Ramesh Shanmugasundaram
- 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-06-14 Quality on Demand - Meeting Minutes
- No comments
Overall topics
- Commonalities and ICM release candidates:
- Commonalities Release 0.4.0-rc.1 (draft PR)
- Identity and Consent Management Release 0.2.0-rc (PR in review)
- Any new issues for QualityOnDemand?
- Create new issue to make Device object optional and add text according to (merged) Commonalities PR #233 Proposal to simplify device object and improve interoperability
- ...
- Governance: Sub Project can have multiple API repositories going forward
- Update of ProjectStructureAndRoles to allow Sub Projects (API families) with multiple API repositories
- QoS Profiles and/or QoD Provision into own repositories?
- ...
Open Pull Requests (open for review)
- PR #295 Add required security scheme and scopes by Eric Murray
- ...
- From last meeting:
- 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)
- Eric will update the PR with documentation for the following points:
- PR #306 Add HTTP-status-codes for better Error Handling
- PR for new issue #305
- Add additional HTTP status codes 405, 406, 429
- Supersedes also the (draft) PR #297 Add error 429 QUOTA_EXCEEDED?
- ...
- PR #299 New API QOD Provision
- ...
- From last meeting:
- 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
Closed issues
- #310 Remove terms of service and contact from APIs
- Done with PR #311
New Issues
- #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
- New additions?
- Issue to make device object optional
- Issue #305
- Issue #309?
- #101 List endpoint for active sessions of authenticated user
- Jose Luis Urien Pinedo proposed a list endpoint for provisions within PR #299 and recommends to take this as
- #166 Extend QoS Profile queries to list profiles based on specific users or devices
- no update (will be done in consistency with #101 by Randy)
- #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- see PR #295
- #257 Error behaviour when session cannot be created due to "time cap" limitation
- PR #297 replaced by PR #306?
- #268 Provision mode for QoD
- See PR 299
- #300 Simplification of Device object - short term solution
- Commonalities PR #233 Proposal to simplify device object and improve interoperability is merged and will be part of 0.4.0
- => new issue to be created
Further Issues
- #302 Providing developers with alternate to QoS profile
- new enhancement proposal by Mahesh Chapalamadugu
- discussion to be continued within the issue
Any other topics
- Next QoD meeting will be on June 28th, at 14:00 CEST / 12:00 UTC