+++ This bug was initially created as a clone of Bug #1412361 +++
Description of problem:
Need to understand how health of replication path can be monitored and exposed in day 2 operations. Areas of importance include:
- Health and status (running? Last completion? etc)
- Notification of need for manual failover -> Plug into Ops Tools Alarm mechanism (general alarm/event needs for all services), CF, and USM?
Sources of trigger include ceph, cinder, service and application level issues
This is needed in support of multi-site deployments, specifically for DR based use cases.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: