Topic Leader(s)

Topic Overview

Slides & Recording

Minutes

  • Release planing
    • Backlog of issues
    • Network orchestration
      • No solution as of today
        • There is an activity in the RM
        • #tug-networking-orchestration is also working on this
    • Multiple interface support
      • There are different approaches to provide multiple connections, not only CNI Multiplexers. Tungsten Fabric way and NSM way are also options
      • Let's investigate if we can find an optimal way to use multiple interfaces and have compatibility on descriptor level
      • Different clusters might have different multi interface support (this is a cluster capability what is not expressed to the external word)
    • Multitenancy
      • For hard multitenancy a separate cluster is needed
      • Support for "soft" multitenancy features within a cluster needed for isolation
        • Define what features we require in a cluster
        • Define a solution when different tenants are separated to different hosts
        • Solutions require network policy support from all components
    • More clarifications to acceleration (and SR-IOV)
      • How accelerators are handled with device plugins?
      • How the activation LCM works
      • Petar Torre volunteered to provide initial text
    • Cluster LCM
      • Is this in or out of scope?
      • 5 out of 16 voted for it
    • Listing of enabled / disabled features in alpha or beta status
      • Include relevant features as in RA2 Ch4
    • Define the Kubernetes version clearly
      • Now RA2 is not consistent on the Kubernetes version
    • Gap analyzis of requirements in Ch2
      • In the "Specification Reference " column we will have either a link to a specification in Ch4 or an N/A
      • Every pr affecting Ch4 should update also Ch2 references and vice versa
  • pr 2252



Action Items