Agenda

Antitrust Policy

• Action Items Review

• Porch Module versioning: https://github.com/nephio-project/nephio/issues/906 @Nagy Gergely

• Upgrade task: https://github.com/nephio-project/nephio/issues/892

  • PR by @László Mózes https://github.com/nephio-project/porch/pull/252

  • PR review is active

  • What support is needed to get this PR merged in time for R5?

• Free5GC: https://github.com/nephio-project/nephio/issues/926@Girish Kumar @JUNNUTHULA SANJUVARDHAN

• Bare metal support: https://github.com/nephio-project/nephio/issues/875 @Vishwanath Jayaraman

• Async pipeline execution:

  • PIP https://github.com/nephio-project/nephio/issues/922 @Istvan Kispal

  • Deferred command approach: @Kushal Harish Naidu

• Transport Network User Story: https://github.com/nephio-project/nephio/issues/933 @Sagar Arora

• AOB

Minutes

Porch Module Versioning

• SIG Automation and SIG Network architecture Modelling WG has agreed to use “version 1” revision handling in both Nephio and Porch from now on.

• Go module version imports have to be explicitly specified if the major version changes

• Porch will follow it’s own release tagging

  • The next release of Porch will break the sequence and go from 4.1.2 to 1.4.0

  • From then on Porch will follow normal semantic versioning rules

• At the time of the next Nephio release (June 26th)

  • Nephio goes R4->R5

  • Nephio uses whatever the latest Porch release is on June 26th

• We’ll inform SIG-Netowrk Architecture and the TSC of this change at their next meetings

Upgrade Task (3-way merge)

• It’s nearing completion, some minor changes to do

• We should keep backward compatibility with the current “update” way of doing upgrades for at least one release so that user have a chance to migrate to the new approach

• Can we deprecate the “update” in R5 and remove it in R6?

Free5GC

• Bumps of the Golang version and updates of the base alpine images

• Currently, we are using Free5GC images that are built in the Nephio Free5gc repo https://github.com/nephio-project/free5gc/because at the time (3-4 years ago) there were issues with using the Free5GC images

• We should use the images from the Free5gc if it is possible, they may well be working by now

• The Free5GC repo should be kept because this is a “NF” operator rather than a Nephio operator

Bare Metal Support

• Good progress, we have the packages ready and the documentation PR is also in the works

• The next step is to create a Cluster CR and a BareMetalHost CR to make it easier for people to roll out bare metal deployments

• People will need to be aware of how the BareMetalHost CR should be used and this will be documented

Async Pipeline Execution

• Two complimentary proposals are in the works

• The PIP is a solution for asynchronous execution of pipelines

• The deferred command approach makes the commands themselves asynchronously

• We will discuss further next week

Transport Network User Story

• @Sagar Arora presented the Transport Network user story

• The current network code in the Nephio controllers is not supported and is complex

• Potentially reduces the complexity of the Nephio controllers.

• Kubenet is planned to be supported by a foundation

Action items