Meeting Minutes:

Session Access

The zoom links are in Team Up calendar link that is located at 2022 LFN DTF Workshop April link.

Topics

Topics

HRK: I'm showing my thought process work here. It's anything resembling a schedule by any stretch of the imagination, and the deep dives into issues and specific questions reflect only my own curiosity and what troubles me. This is merely a starting point, and I hope that the Programming Committee does what it will. We also need to build in time to get to some planning and outcomes.....

CNF Topics 

• Taking Anuket RA and RC activities into workloads
  • Is it sufficient to come up with a basic framework to demonstrate functionality on an example RI?
    • Necessary – is it sufficient?!
    • Tortured metaphor: we've got a good foundation, but need to address plumbing, HVAC, walls, and flooring
  • Where does performance come in?
  • How do we get into more challenging interop?
    • CNI
    • Other networking frameworks (eg., Istio, Envoy)?
    • Networking abstraction – how do we push this past the goal line, publish, and test?
    • Data Plane
      • If performance tuning is a source of interop issues, how do we address these?
      • Are data plane issues as opaque to workloads as claimed (should we do a survey, or testing experiment to have non-anecdotal data)?
    • If this is too much work, what is the highest priority activity that will reduce the cost due to re-work for end users, platform vendors, workload (CNF) vendors?
    • How do we avoid the mistakes of the past? Let's at least avoid those and create new ones.
• Given the previous topic, what is the highest priority testing a badging program and enforce and provide?
• CNF vendor input summit
  • How do we ask better questions to the CNF vendor community? 
  • Bring as many CNF providers as possible (perhaps with a bit of pre-prepared questions)
    • Vendors who have deployed within the 5GSPB context
    • Magma
    • O-RAN SC implementations and vendors
    • OAI
    • Workload BUs rather than platform BUs in our NEP members
    • Active CNF vendors (e.g. Matrixx, Affirmed, Metaswitch)
    • LF Edge application requirements
  • What guidelines, testing, information would be helpful for them such that they don't have to re-do for each platform/end user
  • Are we talking how to give guidelines and test for them against the platform requirements, or are there specific testing regimes for applications?
  • Assumption: CNF to specific platform 1:1 as a deployment requirement does not and cannot scale.

...

• EMCO/ONAP Architecture alignment Deep Dive – 3 hours
  • Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
    • Assumption for ingress: Helm v3 
    • Needs to be jointly defined first, then determine if and where it belongs upstream.
    • Is there a connection to Anuket and Anuket Assured program? Infrastructure→Applications>Onboarding>MANO>Infrastructure (end-to-end)
  • Part 2: Appropriate use cases for EMCO and ONAP, when to use them separately and or together
  • Part 3: Post-onboarding – Day N – onboarding activities and requirements as products move into production – Day 2 – where and how are ongoing metrics collected and how to they feed into relevant parts of the stack....
    • What is considered in or out of the stack in various architectures....
  • Part 34: Interoperability Challenges CNF Interoperability Challenges  between workload/platform and orchestrator/workload
  • CNI – is this the only answer?
  • Other networking frameworks (eg., Istio, Envoy)?
  • Networking abstraction – how do we push this past the goal line, publish, and test?
  • Data Plane
    • If performance tuning is a source of interop issues, how do we address these?
    • Are data plane issues as opaque to workloads as claimed (should we do a survey, or testing experiment to have non-anecdotal data)?

...

•  Topics of interest to the general community – 1 hour
  • Common documentation standardized guidelines – Minimum requirements and expectations, tools, types of documentation required for different types of projects.
  • Common tooling – What is the current set of tools?  Is there a possibility for consolidation?  Is it needed?  Is this even possible?

...

Logistics

• 2 15 minute breaks (instead of 1 30 minute one.
• No summary needed
• Very short intro at the beginning of each day (10 minutes by Heather or someone who is more awake)

Facilitation Ground Rules

• Each Session should have a clearly defined objective and scope statement.
• When offering your thoughts, please be concise. We ask you avoid monopolizing the conversation.
• When someone is speaking, please allow them to complete their thoughts.
• While debate is an underpinning of growth, decorum is the foundation of progress.
• The Facilitator/Presenter and Moderator will work to keep the discussion aligned with objectives and scope. Discussions that are not in alignment with objectives and scope will be deferred.
• The Moderator will record the deferred topics in a topic “Parking Lot” to be addressed by assignment to community representatives at the conclusion of the session.
• Each session should be served by a scribe