DRAFT AGENDA

...

PR #289 Split QoD in Quality-On-Demand and QoS Profiles APIs
- new, addressing issue #265
- Naming will be accepted for this PR ... can be discussed separately and changed if needed
- One week of review ... will be merged on next Friday if no open comments
PR #228 and #217 still in draft mode.

Closed issues

...

#291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)
- ...Jose Luis Urien Pinedo to make first proposals
- discussed about maxDuration → establish again as absolute maximum
- discussed about default for duration
  - making duration parameter mandatory could be an option
#290 Current CI expects certain fixed name for yaml spec
- ...Drop for now, bring only back if we encounter anomalies which are not catched by MegaLinter
#288 Duration behavior during session extension
- ...
#286 Review Attribute Descriptions with References to External Specifc
- Herbert Damker check where QoD would be impacted
- Maybe into backlog until implementation experiences are available

Existing Issues

#281 startedAt y expiredAt do not follow date-time format
- Decision: Should be changed in scope of v0.11.0, label added
#280 Clarification of session creation and startedAt
- Need to be addressed
- Potential further issues to be derived from discussion within issue (relation of Session Resource Object vs Network Session)
- Create a summary issue for "duration" issues (#265, #249, ...)

#268 Provision mode for QoD
- To be discussed if it will be in meta release Fall24 (if yes, we need a release candidate until mid of June!) Jorge Garcia Hospital
- Previous content
  - PR to add it into the scope within README Jorge Garcia Hospital
  - Do we need a User Story for that? Yes. Jorge Garcia Hospital
  - If new API, it can be added within the repository as long as we always release it together. New versioning guidelines under discussion in ReleaseManagement allow APIs with different versions in one repository.
#266 Duration in QoS Session and QoS Profile
#249 Duration in QosProfile and SessionInfo
- We need a new issue to discuss the use cases and the expected behavior consistently and together with the extend duration endpoint behavior
- See action item below - the consolidated issue should also include #280 Clarification of session creation and startedAt
- see new issue
#265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
- see PR #289

#257 Error behaviour when session cannot be created due to "time cap" limitation
- Will be addressed after the split
#245 Update and enhance test definition file for QOD API
- Waiting for close of issue within Commonalities (to be able to align contribution with them)
- Sunny test cases have to added before first release candidate of v0.11.0 (mid of June)
#244
- Create PR after split PR is merged (DT?)
#166
- Randy to create a first PR (after split PR is merged)
#101
- Please review latest proposal https://github.com/camaraproject/QualityOnDemand/issues/101#issuecomment-2015041284

Any other topics

Alignment and collaboration with https://github.com/camaraproject/NetworkSliceBooking/tree/main
- Herbert Damker Thorsten Lohmar Rafal Artych will discuss offline
- (Update: push of "QoS Profiles towards Network Slice Booking as soon we have the split PR)
Next QoD will be on May 17th, at 14:00 CEST / 12:00 UTC

...

Versions Compared