It is not clear how multicloud could help on "Normalize from of cloud agnostic event/alert/fault" and dispatching them from edge to central ONAP (will multicloud has SBI to a "analytic as a service"? Will there be some mandatory API should be imposed to those "analytic as a service" so that multicloud could consume?
As depicted in the architecture slide 6, multi cloud micro service will present a consistent Northbound API to ONAP components. Southbound api to multi cloud in analytics application dependent. The multi cloud micro service can be distributed in the edge or central or both. It is highly desired to be fully distributed to minimize communication across latency/bandwidth sensitive WAN.
For Dublin our thoughts are,
Infra objects of interest:
Infra resources of interest:
1) Threshold crossing Alert - Leverage VES DRAFT
2) Supply additional details for Policy to perform scale out action
3) Supply additional details for OOF to perform fine grained placement action
What confuses me is exactly the statement: "Southbound api to multi cloud in analytics application dependent". Due to this dependency, it implicates that whenever some analytics application exposes new API to multicloud (plugin?), multicloud (plugin?) source code should be updated (hence re-deployed) to consume that new API? If I does not get the proposal wrong, that multicloud (plugin) is not part of analytic applications.
How much resources a typical analytic apllication based on PNDA consumes? The estimation from PDNA seems pretty big, any plan to test it over integration lab?
Powered by a free Atlassian Confluence Open Source Project License granted to The Linux Foundation. Evaluate Confluence today.