sink documenation should explain usage alongside ceilometer
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Ok. So, I'm using Ceilometer on my cloud, and I went to add Designate Sink...
Looking at the config, nova's configured to push notifications to the notifications topic. I see a notifications.info in rabbit. It has 0 messages in it though. Digging in, Ceilometer is sitting on the queue consuming messages...
Looking at the rabbit setup, there is no exchange for notifications.info, so by default that means its a direct exchange. (https:/
So, near as I can tell, if I start Designate Sink on the same queue then, both Ceilometer and Designate Sink will race to get messages, causing each other not to see all of the messages, breaking things badly.
I'm not sure this is a Designate bug exactly, but since Ceilometer is much more common at this point, it might affect users adding Designate to their existing clouds.
How should this be handled? A big fat blinky warning in the documentation for how to set it up properly? Some kind of error in Designate Sink's logs if it can detect someone else on the queue? Something else?
Thanks,
Kevin
| Kiall Mac Innes (kiall) wrote | #1 |
| Changed in designate: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| summary: |
- sink notifications ceilometer + sink documenation should explain usage alongside ceilometer |
| Changed in designate: | |
| milestone: | none → kilo-rc1 |
| Changed in designate: | |
| milestone: | kilo-rc1 → liberty-1 |
| milestone: | liberty-1 → kilo-rc1 |
| Changed in designate: | |
| milestone: | kilo-rc1 → liberty-1 |
| tags: | added: low-hanging-fruit |
| Changed in designate: | |
| milestone: | liberty-1 → liberty-2 |
| Changed in designate: | |
| assignee: | nobody → pradeep kumar singh (pradeep-singh-u) |
| Changed in designate: | |
| milestone: | liberty-2 → liberty-3 |
| Changed in designate: | |
| milestone: | liberty-3 → liberty-rc1 |
| Changed in designate: | |
| milestone: | liberty-rc1 → none |
| Changed in designate: | |
| status: | Triaged → Fix Released |
| Shaik Apsar (sa709c) wrote | #2 |
| Shaik Apsar (sa709c) wrote | #3 |
| Changed in designate: | |
| status: | Fix Released → Triaged |
| tags: | added: docs |
| Changed in designate: | |
| assignee: | Pradeep Kumar Singh (pradeep-singh-u) → nobody |
| Changed in designate: | |
| assignee: | nobody → Rudrajit Tapadar (rtapadar) |
| Changed in designate: | |
| assignee: | Rudrajit Tapadar (rtapadar) → Derek Yang (hswayne77) |
| Graham Hayes (grahamhayes) wrote | #4 |
| Changed in designate: | |
| assignee: | Derek Yang (hswayne77) → nobody |
| status: | Triaged → Won't Fix |
You're correct that Ceilometer and Designate will "race" to consume the messages, the correct configuration is to provide Nova with two different notification topics, causing it to emit each notification twice, and allocate one of the topics to Ceilometer, the other to Designate.
We should update our docs to clarify this.