2024-05-03 Quality on Demand - Meeting Minutes

Attendees & Representation

Type @ and your name to indicate your attendance

LF Staff: na

Community: @Herbert Damker @Jose Luis Urien Pinedo @Surajj Jaggernath @Thorsten Lohmar @Akos Hunyadi @Joachim Dahlgren  @Eric Murray @Randy Levensalor  @Maximilian Laue @Ramesh Shanmugasundaram@Masaharu Hattori

Agenda

• Antitrust Policy

• Review of previous meeting minutes

  • No comments - remove DRAFT

• Overall Topics

• Regular Topics

  • Open Pull Requests

  • New Issues

  • Issues relevant for v0.11.0

  • Scope definition

• Any Other Topics

Minutes

Overall topics

• Meta-release Fall-24 - timeplan updated

  • https://lf-camaraproject.atlassian.net/wiki/x/FwDe

  • Expected Deliverables 

    • M0 - approved, but communication delayed (expected begin of next week)

    • M1 - 30/04

      • Scope of Commonalities finalised: 

      • Scope of ICM in work, focus on OIDC profile

      • The release process definition expects here already an alpha release of Comm & ICM, but they will come only later, at latest 2 weeks before the release candidates (for review by API Sub Projects)

    • M2 - 15/06

      • (Release candidate of Commonalities + ICM)

    • M3 - 15/06

      • First release candidate of QoD, starting of test implementations

        • Won't fit if there are last minutes changes from Commonalities + ICM

      • Instead an v0.11.0-alpha.1 release as milestone target?

    • M4 - 31/08

      • Last (stable) release candidate of target release from QoD

      • Release Criteria fulfilled (incl validation of the release candidate by two independent implementation of the API)

    • M5 - 15/09

      • public release done

• PRs #273 and #283 merged

• License file added to the repository (copy from template repository)

• EasyCLA deactivated on the repository (until a final decision about EasyCLA vs DCO, see TSC Minutes)

• New GitHub teams @camaraproject/quality-on-demand_maintainers and @camaraproject/quality-on-demand_codeowners - please accept the invitation to the camaraproject organization.

Open Pull Requests

• PR #289 Split QoD in Quality-On-Demand and QoS Profiles APIs

  • New PR, addressing issue #265 – need to merged before other PRs can be created

  • Naming will be accepted as proposed 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

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

Existing Issues

• #281 startedAt y expiredAt do not follow date-time format

  • see #291

• #280 Clarification of session creation and startedAt

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

• #265 Proposal to split QoS Sessions and QoS Profiles into two separate API definitions

  • addressed with PR #289 

• #257 Error behaviour when session cannot be created due to "time cap" limitation

  • will be addressed after 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 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

• Alignment and collaboration with https://github.com/camaraproject/NetworkSliceBooking/tree/main

  • 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