Agenda

Antitrust Policy

1. GitOps for Transport

2. Swim Lines for Transport

3. Data Center + Transport

4. Multus-CNI vs CNI-DRA-Driver (Kubernetes v1.33)

5. White Paper

Minutes

1. GitOps for Transport

   • Evgeniy: In R4 Summit we had some concerns about GitOps for Transport Domain. Can we discuss more detail?

   • Wim: Sure! GitOps principles implementation in Kubenet Transport Domain is different than the FluxCD or ArgoCD implementation. Nature of Transport network require simultaneous updates on multiple network elements, and tool like Config Sync already implemented for that in Kubenet. It is not a blocker for development of our Transport Network User Story.

2. Swim Lines for Transport

   • Wim: Each Domain has its own Swim Lines.

   • Evgeniy: Ok, than updateв Transport User Story file to be updated with this picture:

     •  

       Open

       

        

3. Data Center + Transport

   • Evgeniy: Horizontal Scaling of the Bare Metal Nephio - will require IP Fabric for connectivity between Servers. “Leafe and Spine” Fabric (aka CLOS) - is a modern chose for Data Centers. So, the design for Data Center and Transport connectivity to be connected over the “Border Leaf”:

     •  

       Open

       

        

   • Wim: Ok, that’s correct, and possible for implementation.

4. Multus-CNI vs CNI-DRA-Driver (Kubernetes v1.33)

   • Evgeniy: Multus to be replaced with Kubernetes defaults? Is there any impact for Transport User Story?

   • Wim: It is not a blocker. Kubenet is ok for any of them, and Transport Domain here depends on O-RAN Domain preferences.

5. White Paper

   • Evgeniy: I’ll create Confluence Page with some draft for Nephio Transport White Paper. It will be open for contributions.

Action items