...
| ONAP Component | Enhancements |
|---|
| Overall | - Define models to represent summation information (Alerts/statistics/Events) for various groups
- Defining various groups such as CPU usage, Memory usage, file descriptor usage, NIC utilization, various HPA features etc...
|
| Multi-Cloud | - Development activities:
- Prometheus based monitoring & summation
- Support for collectd for statistics collection from NFVI nodes.
- Support for VES agent to send the aggregate data to DCAE (Used when the aggregate service is instantiated outside of ONAP control)
- Support for DMAAP agent to send the aggregate data to DCAE (Normally used if the aggregate service is instantiated at the ONAP-Central.
- Provide ability to add new plugins (to collect statistics as well as to export aggregation information)
- Provide ability to upload the recording and alert rules (on per edge-cloud basis or set of edge-clouds basis)
- Ability to auto-cleanup of time series DB (based on size allocated for this micro-service)
- Edge-Cloud registration time (as part of ESR)
- Check whether registration data indicates whether the aggregation service to be brought up). If so, inform the aggregation micro service to authentication and listen for statistics from that edge-cloud.
- Run time
- Collects the information (support for both pull/push).
- Apply rules
- Generate alarms
- Export them via VES or DMAPP or any other plugins in future.
- Update A&AI HPA (Resources and health)
|
| AAI & ESR | - ESR Development activities (Need to be done when Edges started to send aggregated data, so future requirement)
- Enhancements to ESR to indicate whether aggregation service is required for this edge-cloud at the ONAP.
- Enhancements to ESR to indicate Multi-Cloud for Multi-Cloud to listen for connections and statistics requests from the edge-clouds. Information such as CA cert to use to authenticate the remote party or any other UN/PWD method.
- HPA Enhancements
- On per cloud-region, provide a a way to indicate whether a given HPA feature (that needs resources) resources are available and if so, the number of resources available.
- On per cloud-region, provide a way to indicate the health of the HPA feature.
|
| PORTAL | ESR portal related changes to take information about the edge-cloud (CA Cert and UN/PWD information) - Future when the edges started to send aggregate data) |
| OOF | HPA Enhancements - Current HPA filter only consider whether the cloud-region supports HPA capabilities via profiles. Enhancements to consider "availability of resources" and "health of HPA" on the cloud-region.
| DCAE & DMAPP | None expected?? |
Life Cycle stages related functions
| ONAP Component | Life cycle phase | Activities |
|---|
| AAI and ESR | Deploy & Run time | - Add/Modify/Delete recording and alerting rules
|
| AAI and ESR | Run time | - Add/Modify/Delete Edge-cloud information
|
|
|
|
| Multi-Cloud | Run time | - Get Edge information from A&AI whenever Edge-Cloud is added or removed.
- Prepare to wait for information from that Edge-cloud
- Receive information from edge-cloud and put it in the time series DB.
- Summation based on recording & alerting rules
- Export information to DCAE via DMAPP or VES
|
| OOF | Run time | - HPA filter changes to accommodate health of the hardware/software on a feature and availability of resources.
|
High level architecture slides:
...
