Jump straight into discussion on slides ... see next ...
Martin, All: Target/Reference architecture - Integration with ONAP - based on diagrams used in WG documents etc
Draft Slides
Focus on Slide 5 - clearest picture
Are we only using REST for A1? - Yes ... except maybe for A1-EI part - may use a streaming interface - no decision made yet.
Action: John Keeney Need a couple of sentences about why A1 uses REST on wiki
Should we split out constituent parts of A1? - Not yet ... perhaps wait until A1-EI is a bit clearer.
What is O1* interface .... ? Action Martin Skorupski - David Kinsey is the best guy to ask.
May need to consider non-event-bus NBIs between components in the OAM space - In practice these non-event (e.g. REST, streaming etc) interfaces will be needed, but would just overly-complicate the diagram.
Does CDS etc need to be included. Or APPC etc? ... Probably. Will become clearer, esp when O1* interface is a bit clearer.
Tracy: Reminder about call for demos for ONS and MWC (others?).
Dongho: Have we plans/procedures in place for upstreaming changes back to ONAP? - Not yet. Discussion/Planning ongoing.
Good potential to engage with ONAP 5G usecases for ONAP Frankfurt - still time to engage with Frankfurt planning.
Action: Could Tommy CarpenterChris Lott please present a short update on the A1 parts of the NearRTRIC dashboard etc next week? - Yes.
Call cut short at T+58mniutes due to bridge reuse.
Action items
Need to coordinate with Tommy CarpenterChris LottJohn Keeney about RIC dashboard & A1 mediation scope in NONRTRIC. Organise call to discuss further
John Keeney Need a couple of sentences about why A1 uses REST on wiki
Clarify what is O1*: Martin Skorupski - David Kinsey is the best guy to ask.
Tommy CarpenterChris Lott Present a short update on the A1 parts of the NearRTRIC dashboard etc next week.
