Versions Compared

Key

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

...

  • On-boarding: Alignment across ONAP and EMCO, taking into account the role played by k8s.
    • Assumption for ingress: Helm v3 
    • To the extent it needs to be extended/constrained, both groups should define together, and we can determine if and where it belongs upstream.
    • How does this discussion feed into 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....
  • Conceptual flow diagrams
    • Where do the focus areas of both EMCO and ONAP land? What is shared? What is not? What is gray? Beyond marketing......
    • Before we go into powerpoint comparison, I would suggest choosing a discrete set of  applications (including at least RAN and a webapp....mostly b/c those could overlap in a hybrid environment, and then also each group chooses one application that is specifically optimized for them – e.g., Core, and perhaps something that gets close to IOT). Map out for each application how the flow works in ONAP only, EMCO only, and a choice or two in hybrid scenarios. From there we can start to look at how we want to talk to the market, figure out what technical works needs to be done, and how. 


Community Topics

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


Day 1 – first half 

CNF Vendor Input Summit

  • I'm suggesting putting this first as coming out of the Jan CNF discussion, hearing directly from CNF vendors seemed to be a missing piece. If we can use this to get folks from the above list to answer some of the questions/describe what they would need from specifications might be the best use of time.
  • We can look both at onboarding/orchestration and infra platform perspectives
  • Outcome: Guidance from CNF vendors on program framework and next steps


Day 1 – Second Half, and 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 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
  • Track 2 – EMCO/ONAP Architecture alignment Deep Dive


Day 2 – Second Half

  • Community topics on Documentation, etc. – will this be enough?