DRAFT
...
MINUTES
Attendees & Representation
...
- #282 Move example outside of allOf in schemas.Duration
- Fixed with PR #283
- #276 Question on the anyOf in DeviceIpv4Addr
- won't fix
New Issues
- #292 Scope definitionof QualityOnDemand for Fall24 CAMARA release
- The issue is required as part of the Release process
- Update: Titel updated (removed the API versions from the title, added them to the content)
- #291 Consolidated issue for duration, extentDuration, startedAt, expiredAt, maxDuration and their formats (to be updated)
- Jose Luis Urien 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 the GitHub action for now, bring only back if we encounter anomalies which are not catched by MegaLinter
- #288 Duration behavior during session extension
- ...see #291
- #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
...
- #281 startedAt y expiredAt do not follow date-time format
- Decision: Should be changed in scope of v0.11.0, label added
- see #291
- #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, ...)
- see #291
- #268 Provision mode for QoD
- To be discussed if it will be in meta release Fall24 (if yes, we need a release candidate until 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
- see new issue
- #291
- #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions
- see addressed with PR #289
- #257 Error behaviour when session cannot be created due to "time cap" limitation
- Will
- will be addressed after the split
- PR #289 is merged
- #245 Update and enhance test definition file for QOD API
- No update
- Previous content:
- 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 Align securitySchemes and security of QOD API spec with IdentityAndConsentManagement
- Create PR after split PR is merged (DT?)
- #166 Extend QoS Profile queries to list profiles based on specific users or devices
- Randy to Levensalor to create a first PR (after split PR is merged)
- #101 List endpoint for active sessions of authenticated user
- Please review latest proposal on this issue: https://github.com/camaraproject/QualityOnDemand/issues/101#issuecomment-2015041284
Any other topics
- (Update: push
- Alignment and collaboration with https://github.com/camaraproject/NetworkSliceBooking/tree/main
- Herbert Damker Thorsten Lohmar Rafal Artych will discuss offline
- Push of "QoS Profiles towards Network Slice Booking as soon we have the split PR
)- If used by other sub projects, QoS Profiles API might need to be carved out in own repository
- Next QoD will be on May 17th, at 14:00 CEST / 12:00 UTC
Action items
- Create a summary issue for "duration" issues (#265, #249, ...) Jose Luis Urien Maximilian Laue
- Create a summary of the scope definition of v0.11.0 within an issue Herbert Damker
Final review and merge of PR #283 (Codeowner & Jose Luis Urien )Create the "split" PR #265 Jose Luis Urien (request review comments before the next call)