2024-08-23 Quality on Demand - Meeting Minutes
Attendees & Representation
Type @ and your name to indicate your attendance
Â
LF Staff:Â
Community: @Ben Hepworth @Herbert Damker @Randy Levensalor @Maximilian Laue @Masaharu Hattori @Akos Hunyadi @Toshi Wakayama @Eric Murray @Rafal Artych @Joachim Dahlgren @efezhan @Konstantinos Fragkos @Surajj Jaggernath @Nick VrionisÂ
Agenda
Review of previous meeting minutes
Overall Topics
Regular Topics
Closed PRs and Issues
Open Pull Requests
New Issues
Open Issues
Any Other Topics
Minutes
Review of previous meeting minutes
Previous meeting minutes:Â 2024-08-09 Quality on Demand - Meeting Minutes
no comments
Overall topics
Target: plan next steps until final release (release PR due on August 26th, last prerequisited PRs merged August 30th)
Current status:Â
Open Pull Requests
#348 Updating names qos-profile of endpoints
Comments addressed:
GET /qos-profiles/{name} kept unchanged
`/qos-profiles` is now `/retrieve-qos-profiles`
Ready for final review by Codeowners
 #349 QoD Test definitions
This will be the base PR for the .feature files
Request to review to all
Please comment also on the points within README if you think they can be resolved now or should be postponed to later
DT will compare with #350, if some scenarios should be added from #350
Last comments should be available until Wednesday August 28th eob
@Jose Luis Urien Pinedo will with priority address comments
PR has to be merged August 30th eob
#350 Update QoD_API_Test.feature
potential cherry-picks into #349
#353 Release PR for public release r1.2 (M4)
Draft release PR, will be opened for review on Monday August 26th
New Issues
#341 Add user story for QoS Profiles
no PR yet (@Randy Levensalor )
#342 Review and update User Story for Quality On Demand
not PR yet (@Herbert Damker )
#345 Operation to get qos-profiles for a device MUST use a verb and needs a security object
will be fixed by PR #348 (see above)
#351Â Behaviour when extending not AVAILABLE session
Expected response unclear, needed for test plan and by implementations
Important to define the behaviour to have consistencies across implementations
Tendency towards 200 with recommendation that the API Client checks the outcome of the request (qosStatus and resulting duration)
Action Request: Please add your opinions in the issue
#352 Create PR for public release r1.2 (M4)
see PR #353
Review scope and time plan for Release Candidate
#292 Scope of QualityOnDemand for Fall24 CAMARA release
Plan remaining task for public release of v0.11.0 & qod-provisioning:
Test definition files: see #245, see PR #349
User Stories (as of last QoD call - no PRs yet)
qos-profiles @Randy Levensalor (issue #341)
quality-on-demand @Herbert Damker (issue #342)
Any other topics
Next QoD meeting will be on September 6th, at 14:00 CEST / 12:00 UTC