Page History

Day 1 Top Level: 

• CNF to specific platform 1:1 as a deployment requirement does not and cannot scale.
• What is the highest priority activity that will reduce the cost due to re-work for end users, platform vendors, workload (CNF) vendors?

• As a follow up to the January Workshop, several consecutive focused sessions with CNF vendors to gain an understanding of what requirements they need the CNF Vendor's requirements are needed from LFN projects and community to support their the Vendors' workloads and applications. Need to look at the expectations from both the Vendor needs from the platform and the the expectations that the Vendors workloads need to include for the onboarding/orchestration, on-going supportability and infra platform perspectives.
  • What are the vendors' priorities, objectives and expected outcomes? Improved time to market?  Ability to use a reference architecture to cut development time? Something else?
  • What are the expectations from the projects on what needs to be included in the workloads to be able to use these standard tools and reference implementation infrastructure architectures? 
  • What architectures, requirements, guidelines, and test frameworks or information are is needed to achieve these objectives? Are we talking how to give provide guidelines and test for them against the platform requirements, or are there specific testing regimes for applications?

• Map out an Infra Platform and Compliance FrameworkOrchestration requirements and frameworkCNF Compliance and Testing Framework
  • Interoperability with infra platform
  • Interoperability with orchestration platform
  • Are the testing tools ready?  Are there feature gaps that the test suites do not cover?
  • What are the gaps. and how can the features be added to the test tools?
• How to map Anuket RA and RC activities to support CNF workloads
  • Is it sufficient to come up with a basic framework to demonstrate functionality on an example RI?
  • Do a discrete set the CNF compliance/platform interop requirements need to be fed directly into Anuket project workstreams?
• How to map ONAP CNF taskforce activities and any EMCO activities to support CNF workloads

Deep Dive: Interoperability Challenges

• Part 4: CNF Interoperability Challenges  between workload/platform and orchestrator/workload
• Networking challenges
  • 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?
  • Layer 4-7 networking (eg., Istio, Envoy)?
• 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)?

• EMCO/ONAP Architecture alignment Deep Dive
  • Part 1: On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
    
    • Infrastructure→Applications>Onboarding>MANO>Infrastructure (end-to-end)
  • Appropriate use cases for EMCO and ONAP, when to use them separately and or together
  • The teams have identified two fundamental configurations, each ideally suited for different high level use cases
  • ONAP is the centralized Service Orchestrator, Service Assurance and Automation Framework, with EMCO fulfilling specific roles as a component (multi cluster support, etc)
  • EMCO is the distributed edge focused Service Orchestrator, with select ONAP Service Assurance components configured as needed.
  • We can draw from the following examples and other supporting material during this session to describe the rationale
  • Review of the EMCO_ONAP Alignment Proposal PPT.
  • Lessons learned from:
    • Magma orchestration with EMCO (2022-01-13 - EMCO: Orchestration of Magma)
    • Magma orchestration with ONAP (https://wiki.onap.org/display/DW/2022+Enterprise+Task+Force?preview=/117743631/117743639/ONAP_Magma%20Integration%20status.pptx)
  • EMCO team overviews the rationale for, deploying an app/service such as Magma as the primary SO
  • Given the different configurations , how can the 5G SBP program demonstrate and delineate the rationale for the two configurations?

• Post-onboarding activities and requirements as products move into production – Day 2  operations handoff and ongoing mgmt– 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
• Time Permitting: Is there a connection to Anuket and Anuket Assured program? Infrastructure→Applications>Onboarding>MANO>Infrastructure (end-to-end)

• 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?