Need to implement Prometheus alarm plugin
Bug #1662898 reported by
Peter Razumovsky
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Mirantis OpenStack | Status tracked in 10.0.x | |||||
| 10.0.x |
Invalid
|
Medium
|
Sergey Kraynev | |||
| 9.x |
Invalid
|
Medium
|
Sergey Kraynev | |||
Bug Description
MCP use prometheus for alarming, so need to implement PrometheusAlarm resource plugin in heat. Why PrometheusAlarm should be implemented only in downstream?
1. Prometheus is proprietary service for MCP, so there's no chance to implement it in upstream.
2. Decided, that MCP will be based on mitaka, so need to implement PrometheusAlarm not only in 10.0/newton branch, but in 9.0/mitaka branch.
PrometheusAlarm is similar with original Alarm, but have alarm_type "prometheus" and different metadata building.
| Changed in mos: | |
| milestone: | none → 9.x-updates |
Revision history for this message
| Vitaly Sedelnik (vsedelnik) wrote | #1 |
Revision history for this message
| Fuel Devops McRobotson (fuel-devops-robot) wrote Change abandoned on openstack/heat (9.0/mitaka) | #2 |
To post a comment you must log in.
This is not a valid MOS bug - please file one in MCP bug tracker