Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Day 1 –  CNF Vendor Input Summit – I think that this is a full day (4 hour) topic

  • Session Part 1: Several consecutive focused sessions as a follow up to the January Workshop, with CNF vendors to gain an understanding of what requirements that they need from the LFN projects and community to support their workloadsWe can look both at .  What architectures, requirements, guidelines, and test frameworks or information would improve CNF vendors' outcomes? 
    • What are those outcomes?  Improved time to market?  Ability to use a reference architecture to cut development time? Something else?
    • Are we talking how to give guidelines and test for them against the platform requirements, or are there specific testing regimes for applications?
    • onboarding/orchestration and infra platform perspectives
    • Projects of most interest? 
      • 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
  • Part 2Outcome: Guidance from CNF vendors on program framework, targeted projects and next steps
    • Map out an Infra Platform and Compliance Framework
    • Determine a discrete set the CNF compliance/platform interop issues that will be fed directly into Anuket work


Day 1 – Second Half, and Day 2 first First half 

  • My initial thought here is to break into two tracks (I know we'd discussed keeping everything to single track, but I think we can fairly neatly divide, although I'd appreciate other opinions)
  • Track 1 – Infra Platform and Compliance Framework
    • Taking into account the feedback from CNF vendors, determine a discrete set of questions/topics to answer to make forward progress on the CNF compliance/platform interop issues – feed directly into Anuket work
    2 – EMCO/ONAP Architecture alignment Deep Dive
    • 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)
    • Post-onboarding – Day N – 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....
    Track 2 – EMCO/ONAP Architecture alignment Deep Dive


Day 2 – Second Half

  • Topics of interest to the general community
    • 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?

...