...
ONAP Component | Life Cycle Phase | Enhancements |
---|
Policy | Design | Define Distributed Cloud Infrastructure Placement Policies (Note 3) - Leverage Standardized Distributed Cloud Infrastructure Object Hierarchy & Capabilities from A&AI
|
Multi-Cloud | Deploy | Support Distributed Cloud Infrastructure Capability Discovery (Note 1, Note 2) For workload instantiation, translate cloud-agnostic Opaque TLVs from SO into cloud-specific placement attributes (Note 7) |
A&AI | Deploy | Support Standardized Distributed Cloud Infrastructure Object Hierarchy & Capability Database - Loose coupling between HW objects (private cloud) and SW objects (private and public clouds)
- Includes Standardized Capabilities across clouds & Capabilities unique to certain clouds
- Note:
- Multi-Cloud Distributed Cloud Infrastructure Capability Discovery process will populate the aforementioned database
|
OOF | Deploy | Execute Distributed Cloud Infrastructure Placement Policies for Optimized Service/VNF Placement across Cloud Regions (Note 4) |
SO | Deploy | Extend SO↔OOF API to support opaque TLVs (Note 5) |
Assumption for Policy, SO, OOF:
...
- This uses the new Network Slicing workflow in SO (todo confirm)
ONAP Component | Life Cycle Phase | Enhancements |
---|
Policy | Design | Configuration Policies for Guaranteed, Burstable & Best Effort Cloud Infrastructure Resource Slices (this will apply to VMs/Containers also) Placement Policies for Resource Slices - Higher (programmable) weight to Cloud Region which supports all three types of resource slices vs only two types of resource slices (Guaranteed/Best Effort)
Network Slice Allocation across several Clouds - Allocate a contiguous network slice for extreme mobile broadband (ref. 1) with a max. latency of 10ms
- Maps to Burstable Resource Slice in the infrastructure with min./max. of CPU, Memory etc.
|
Multi-Cloud | Deploy | Resource Slice Capability Discovery |
A&AI | Deploy | Resource Slice Capability per Cloud Region - Guaranteed/Burstable/Best Effort
Resource Slice Type - Guaranteed/Burstable/Best Effort
|
OOF | Deploy | Execute Resource Slice Placement Policies for Optimized Service/VNF Placement across Cloud Regions |
Aggregation Service
ONAP, as in R2, collects the statistics/alarms/events from workloads (VMs) and take any close loop control actions such as Heal a process, scale-out, restart etc.. In R3, infrastructure related statistics/alarms/events will be collected, generate actionable insights and take life cycle actions on the workloads. Infrastructure statistics normally include performance counters, NIC counters, IPMI information on per physical server node basis. To reduce the load on the ONAP, it is necessary that aggregated (summarized) information is sent to the ONAP from edge-clouds.
...
Impacted projects (development activities)
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 collected 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.
|
AAI & ESR | - Development activities
- 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.
|
PORTAL | ESR portal related changes to take information about the edge-cloud (CA Cert and UN/PWD information) |
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
|