Data
| Failure Type | Failure parameter |
|
| Comments |
|---|---|---|---|---|
| Links | Link Down. Link removed | |||
| VM | Deployment/Start Failures:
Post-Deployment/Start failures:
| nova-compute.log nova-api.log nova-scheduler.log libvirt.log qemu/$vm.log neutron-server.log glance/cinder - flavor Node and Core-mapping | cpu: per-core utilization memory Interfaces statistics - sent, recv, drops Disk Read/Write | If possible, Infrastructure metrics and syslogs from within the VM should be collected. Deployment/Start failures can be the first step. |
| Container | Deployment/Start Failures:
Post-Deployment/Start failures:
| cpu: per-core utilization memory Interfaces statistics - sent, recv, drops Disk Read/Write | ||
| Node | A node failure (hardware failure, OS crash, etc) C) Fabric component failure -- N/A, assuming redundant/highly available configuration
D) Failure of other OpenStack services -- N/A, assuming redundant/highly available configuration
| A) node network connectivity failure
B) nova service failure (e.g., process crashed) -- detected and restarted by a local watchdog process
| ||
| Application |
| Crash/Connectivity/Non-Functional | Application Log i.e. If it is Apache then logs of Apache | Packet Drops, Latency, Throughput, Saturation, Resource Usage | Deploy Collectd within the application and collect both application logs and infrastructure metrics | |
| Middleware Services |