LF Staff: @Casey Cain @Ranny Haiby

• Overview of the Service Assurance use cases - @Eddy Fung

• .

• .

• Urgent need to redefine the release process in time for R5

  • @Ciaran Johnston (Ericsson) and @Fiachra Corcoran

• Proposal for release “roles” going forward:

  • Release manager

    • responsible for coordinating each release and encouraging use case owners to deliver content on time

  • Verification infrastructure maintainer

    • responsible for the CI and other infrastructure associated with running Nephio use cases

  • Use case maintainers (per use case)

    • Responsible for maintaining and evolving use case test cases and validating the use case per release

• .

• Next steps in TSC calls

  • Sylva + Nephio Synergy - presentation and discussion

  • Nephio Summit / GenAI Hackathon

Minutes

Release process change

• Need to cover the activity of “cutting the release”:

  • creating new tags, updating the test infrastructure files, pushing packages etc.

  • Current process for making a release is far too complex today

  • The amount of tagging is already very complex

  • For this purpose, the role of “cutting the release” would be between the release manager and the infra maintainer

  • Use case owners would be responsible for making sure their test cases were passing and their dependencies were up to date

  • Use case owners would decide what versions of downstream dependencies - e.g. OAI, Free5GC etc - would be supported in that use case

  • these changes are covered by user stories rather than as part of the release process

  • Current role of SIG release is too broad

• Should do a checklist for the release process

• The prow infrastructure was largely maintained by Fiachra and Rado, with other use case developers contributing on an ad hoc basis (and Bala has done lots of release management activities)

Next steps:

• document the roles and resource them, including the individual use cases and their owners

• develop a checklist for the current process

• put a plan in place to streamline the process

• SIG leads should take a break-out session to identify unfilled roles and strategize on ensuring all needed roles are filled

Broadening community engagement

• Casey will share info with the leads on how to leverage the marketing community (done)

• Need to get a broader community - outreach to different communities and get a view on how we can interwork

  • including Sylva, but also other companies in enterprise

  • Sana will reach out to Arpit and Ranny to set up more meetings

• Need to modernise the architecture and roadmap in SIG Network Architecture

  • Updated comms pack

• Weak points - adoption by operators and vendors, there are no case studies or success stories to showcase as yet

  • All: go back to your companies to see what can be communicated

• Need to start gathering quotes from companies participating in Nephio for the next release - AP on @Sana Tariq and @Ciaran Johnston (Ericsson)

• We can do webinars to build some interest and provide material for the marketing group to use

• In-person meetings - we can do “one-company hosting” - one company provide venue, LFN would provide some support for registration pages etc.

  • Break-out session to be planned on meet ups - @Ciaran Johnston (Ericsson) , @Sana Tariq , @Ranny Haiby

Sylva sync

Sana is discussing with Phillipe to arrange a TSC meeting where we share Sylva’s vision

GenAI Hackathon

We can discuss this in the break-out session

SIG Network Architecture

Planning is ongoing for R6 - assurance story including framework for metrics

Stories for existing themes are also defined.

We should also define a couple of GenAI stories

SIG Automation

3-way merge fix coming in on Porch which will make it a much better product

Lots of very good robustness and scalability changes coming in which will hopefully make it to R5

Strategy for free5gc is under development