...
- Follow-up on Documentation Workshop from Jan DTF
- Tooling
Scheduling Thoughts
This is very high level, and may also not be what any of you had in mind.....it's also possible that I'm still trying to fit too much in.....
Proposed Schedule
Day 1 – CNF Vendor Input Summit – I think that this is a full day (4 hour) topic
- Part 1: As a follow up to the January Workshop, several consecutive focused sessions with CNF vendors to gain an understanding of what requirements they need from LFN projects and community to support their workloads and applications. Need to look at the expectations from 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 architectures, requirements, guidelines, and test frameworks or information are needed to achieve these objectives? 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 to the CNF/Operator communities?
- 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 2: Guidance Once the objectives have been identified, develop guidance from CNF vendors on program framework, targeted projects and next steps
- Map out an Infra Platform and Compliance Framework
- 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
Day 1 – Day 2 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 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....
- Interoperability Challenges – Is this separate
- 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)?
- On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
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?
...