...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
DRAFT
...
MINUTES
Attendees & Representation
...
Community: Randy Levensalor Ben Hepworth Thorsten Lohmar Maximilian Laue Eric Murray Akos Hunyadi Ramesh Shanmugasundaram Toshi Wakayama Rafal Artych efezhan Joachim Dahlgren Jorge Garcia Hospital Konstantinos Fragkos Masaharu Hattori Surajj Jaggernath Syed Rehman Akos Hunyadi
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
...
- 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?
- Randy: keeping together for now make sense
Open Pull Requests (open for review)
- PR #295 Add required security scheme and scopes by Eric Murray
- Ready for final review...
- 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?
- ...Maximilian Laue to address comments, afterwards ready for final review
- PR #299 New API QOD Provision
- Name of endpoint to be discussed (see comments from Randy Levensalor within the PR). ..Eric: "provision" is mobile terminology.
- 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
...
- #309 Purpose of
messagesarray in SessionInfo schema is undocumented- ...Ramesh Shanmugasundaram creating PR, if no objection to delete the parameter we will do so.
- #305 Add more HTTP Status Codes for improved Error Handling
- ...see PR
- #302 Providing developers with alternate to QoS profile
- new enhancement proposal by Mahesh Chapalamadugu
- discussion to be continued within the issue
- Proposal to put into backlog for next release => put into the issue as proposal.
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 => Herbert to create
- 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
- PR need to created soon to get it into the release.
- Randy: name of the endpoint to be considered, see comment in PR #299
- #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)
- Randy Levensalor will create PR to add the endpoint (adding device object optional)
- #244 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- see PR #295
- #245 Update and enhance test definition file for QOD API
- add issue to decide if we keep "cucumber" directory or update it
- Request to all to consider to contribute current .feature files
- #257 Error behaviour when session cannot be created due to "time cap" limitation
- PR #297 replaced by PR #306?
...
- #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 28thJuly xx, at 14:00 CEST / 12:00 UTC
- We don't plan to skip meeting until the release (at least for now).