A service to manage Notifications through APIs

Registered by Kalaswan Datta on 2016-11-24

Summary
=======
Currently Notifications are written in RabbitMQ through different agents. Then these messages are collected from RabbitMQ through collector services of Ceilometer.
Instead of writing the information in RabbitMQ, the information should be passed through the Ceilometer API. This will remove the dependencies of RabbitMQ and it will be highly scalable.

Problem
=======
As mentioned above, the ceilometer collectors collects the information from RabbitMQ and writes the same in Database.
Now suppose if the RabbitMQ service is down, then the information will not captured in the database. IN that case the meterting data will not show for any action performed in any component.
For Example: In swift, if an object is uploaded during the rabbitMQ is down. And after some time the object is deleted from swift container. Then the rabbitMQ server is started.
This complete information will be lost. there will be track of this action.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Kalaswan Datta
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
gordon chung on 2017-06-20

Related branches

Sprints

Whiteboard

i think considering entire openstack has some dependency on MQ being available, i'm not entirely sure what is to be addressed here. please push to openstack-dev ML to discuss more if needed. alternatively, services can push directly to gnocchi if they want. -- gordc (2017.06)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.