Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Julien Danjou
On Thu, Aug 01 2013, Sam Morrison wrote: OK so is it that ceilometer just leaves the message on the queue or only consumes certain messages? Ceilometer uses its own queue. There might be other processes consuming this notifications, so removing them may be not a good idea. The problem may be

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Mark McLoughlin
On Thu, 2013-08-01 at 10:36 +0200, Julien Danjou wrote: On Thu, Aug 01 2013, Sam Morrison wrote: OK so is it that ceilometer just leaves the message on the queue or only consumes certain messages? Ceilometer uses its own queue. There might be other processes consuming this

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Sandy Walsh
On 08/01/2013 07:02 AM, Mark McLoughlin wrote: On Thu, 2013-08-01 at 10:36 +0200, Julien Danjou wrote: On Thu, Aug 01 2013, Sam Morrison wrote: OK so is it that ceilometer just leaves the message on the queue or only consumes certain messages? Ceilometer uses its own queue. There might be

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Julien Danjou
On Thu, Aug 01 2013, Sandy Walsh wrote: Hmm, if notifications are turned on, it should fill up. For billing purposes we don't want to lose events simply because there is no consumer. Operations would alert on it and someone would need to put out the fire. So currently, are we're possibly

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Sandy Walsh
On 08/01/2013 09:19 AM, Julien Danjou wrote: On Thu, Aug 01 2013, Sandy Walsh wrote: Hmm, if notifications are turned on, it should fill up. For billing purposes we don't want to lose events simply because there is no consumer. Operations would alert on it and someone would need to put out

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Julien Danjou
On Thu, Aug 01 2013, Sandy Walsh wrote: Right, that is a concern. Within RAX we have two downstream services that consume notifications (StackTach and Yagi) and we've configured nova to write to two queues. --notifications_topics can take a list. Fair enough. So IIUC that means we should

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Sandy Walsh
On 08/01/2013 10:25 AM, Julien Danjou wrote: On Thu, Aug 01 2013, Sandy Walsh wrote: Right, that is a concern. Within RAX we have two downstream services that consume notifications (StackTach and Yagi) and we've configured nova to write to two queues. --notifications_topics can take a

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Rosa, Andrea (HP Cloud Services)
HI AFAIK, amqp only uses the exchange as a dispatcher and all storage is done in the queue ... but I could be wrong. I vaguely recall there being a durable exchange setting as well as durable queue. AFAIK if a message can't be routed there are three options: - the message is discarded (I think

Re: [openstack-dev] [Openstack] Ceilometer and notifications

2013-08-01 Thread Doug Hellmann
On Thu, Aug 1, 2013 at 9:25 AM, Julien Danjou jul...@danjou.info wrote: On Thu, Aug 01 2013, Sandy Walsh wrote: Right, that is a concern. Within RAX we have two downstream services that consume notifications (StackTach and Yagi) and we've configured nova to write to two queues.