As a curiosity, are there any ballpark numbers around the volume of notifications ceilometers can handle? Thinking about large scale swift deployments I expect to see thousands or even 10s of thousands of events per second. And that's with today's technology. Looking longer term I wouldn't be surprised to see 100s or even millions per second. And that's just swift. I'd think other services not yet invented will have their own firehoses of data to contribute.
-mark -----Original Message----- From: Julien Danjou [mailto:jul...@danjou.info] Sent: Thursday, July 31, 2014 5:24 AM To: Chris Dent Cc: OpenStack-dev@lists.openstack.org Subject: Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware On Wed, Jul 30 2014, Chris Dent wrote: > What are other options? Of those above which are best or most > realistic? I'm just thinking out loud and did not push that through, but I wonder if we should not try to use the oslo.messaging notifier middleware for that. It would be more standard (as it's the one usable on all HTTP pipelines) and rely on notification and generates events, as anyway, HTTP requests are events. Then it'd be up to Ceilometer to handle those notifications like it does for the rest of OpenStack. -- Julien Danjou /* Free Software hacker http://julien.danjou.info */ _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
