2024-07-12 Quality on Demand - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: @Toshi Wakayama  @Ben Hepworth @Jose Luis Urien Pinedo @Nick Vrionis@Eric Murray@Akos Hunyadi  @Herbert Damker @Thorsten Lohmar @efezhan @Gervais-Martial Ngueko @Joachim Dahlgren @Masaharu Hattori @Rafal Artych @Ramesh Shanmugasundaram @Randy Levensalor @Surajj Jaggernath 

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-06-28 Quality on Demand - Meeting Minutes

  • no comments

Overall topics

• Commonalities and ICM release candidates available

  • https://github.com/camaraproject/Commonalities/tree/r0.4.0-rc.1

  • https://github.com/camaraproject/IdentityAndConsentManagement/tree/v0.2.0-rc.1

• All Sub Projects are asked to prepare for the meta-release, including creating API release trackers for their APIs under their wiki pages, preparing their release-candidate API version and their API readiness checklist items.

• Target: First release-candidates of API Sub Projects to be provided by 07-21

Open Pull Requests (open for review)

• PR #306 Add HTTP-status-codes for better Error Handling

  • After discussion reduced to add HTTP-status-code 429

  • Supersedes also the (draft) PR #297 Add error 429 QUOTA_EXCEEDED?

  • @Jose Luis Urien Pinedo will do a cross-check of the PR, also with other APIs like DeviceLocation

  • Target to get it close within next week

• PR #318 Add query to qos-profiles to query profiles available on a given device

  • Addresses #166

  • Open question: one endpoint for all cases?

    • no objections to go with one POST endpoint

    • @Randy Levensalor will update the PR

• PR #299 New API QOD Provision

  • Name of API changed to qod-provisioning

  • Request to all to review the latest version within the Pull Request. Please add your comments (or approval) until end of next weeks

• PR #320 New API Readiness Checklists for quality-on-demand and qos-profiles

  • Created and prefilled to check the current status

  • Need to be updated as part of each release PR

Closed issues

• #309 Purpose of messages array in SessionInfo schema is undocumented

  • Closed with PR #312

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

  • Closed with the merge of PR #295 Add required security scheme and scopes

New Issues

• #313 Align with Commonality decision about optional device object and respective documentation

  • To be done together with #315 and #316

  • @Herbert Damker volunteered to do the PR after #306 is merged

• #314 Adding notificationUrl as an optional property in CloudEvents

  • Discussion open, DT will check the proposed alternative from Eric

• #315 Return 422 instead of 501 if the service is not implemented for specified device

  • Together with #313

• #316 Align error responses for Device Object with v0.4.0 of Design Guidelines

  • Together with #313

• #317 Application IPs are not shared by OTT for QOD API

  • Backlog item if an enhancement at all

  • Discussion to be continued in the issue

• #321 Remove unresolved reference within quality-on-demand documentation

  • @Herbert Damker to create PR, minor change

• #322 Remove cucumber code from the repository - decision request

  • no objection to delete the code => PR to be created

Issues relevant for v0.11.0 (if not yet covered by PRs)

• #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 template

  • Use same pattern as above in qos-profiles and change the getSessions from GET to POST with device optional in the body

  • @Jose Luis Urien Pinedo to create the PR.

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

  • Regarding cucumber code, see #322

  • @Jose Luis Urien Pinedo will check if internal test definitions can be adapted

  • Most probably we won't have a sufficient test .feature file at M3

  • Target to have it in advance of M4.

• #286 Review Attribute Descriptions with References to External Specifc

  • For quality-on-demand there is only one reference (to be deleted), see #321

  • Proposal to move the issue to backlog - agreed

Review scope and time plan for Release Candidate

• #292 Scope of QualityOnDemand for Fall24 CAMARA release
  
  

  • Review scope in light of short-term deadline

• PR #320 New API Readiness Checklists for quality-on-demand and qos-profiles
  
  

  • Current open "to be dones":

    • API Definition (open Issues/PRs)

    • Design guidelines from Commonalities applied (open Issues/PRs)

    • Basic API test cases & documentation (see #245!)

    • Changelog update (will be done in release PR)

  • User stories and Enhanced API test cases are not mandatory for  0.x API versions

• Target to have the release candidate PR ready within the next QoD call on July 26th.

• We will go for the Meta-Release with an "Initial" API Version, which means to keep v0.11.0

  • Why we don't go for "Stable":

    • Lack of prerequisites (test cases, certification of previous version)

    • Too many changes between v0.10.0 and v0.11.0, we should have one cycle where we don't introduce breaking changes

Any other topics

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

• We don't plan to skip meetings until the release (at least for now).

Action items