Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-08-08 Thread Osanai, Hisashi
Hi, Is there any way to proceed ahead the following topic? Best Regards, Hisashi Osanai On Friday, August 01, 2014 7:32 PM, Hisashi Osanai wrote: I would like to follow this discussion so I picked up points. - There are two way to collect info from swift, one is pollster and the other

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-08-01 Thread Osanai, Hisashi
I would like to follow this discussion so I picked up points. - There are two way to collect info from swift, one is pollster and the other is notification. And we discussed about how to solve the performance degradation of swift_middleware here. pollster: - storage.objects -

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-31 Thread Eoghan Glynn
Swift is already emitting those numbers[1] in statsd format; could ceilometer consume those metrics and convert them to whatever notification format it uses? The problem with that approach, IIUC, is that the statsd metrics provide insufficient context. Ceilometer wants to meter usage on a

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-31 Thread Julien Danjou
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

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-31 Thread Seger, Mark (Cloud Services)
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

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-31 Thread Chris Dent
On Thu, 31 Jul 2014, Julien Danjou wrote: 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

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-31 Thread Eoghan Glynn
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

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-31 Thread Samuel Merritt
On 7/31/14, 1:06 AM, Eoghan Glynn wrote: Swift is already emitting those numbers[1] in statsd format; could ceilometer consume those metrics and convert them to whatever notification format it uses? The problem with that approach, IIUC, is that the statsd metrics provide insufficient

[openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-30 Thread Chris Dent
ceilometer/objectstore/swift_middleware.py[1] counts the size of web request and reponse bodies through the swift proxy server and publishes metrics of the size of the request and response and that a request happened at all. There are (at least) two bug reports associated with this bit of code:

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

2014-07-30 Thread Samuel Merritt
On 7/30/14, 8:06 AM, Chris Dent wrote: ceilometer/objectstore/swift_middleware.py[1] counts the size of web request and reponse bodies through the swift proxy server and publishes metrics of the size of the request and response and that a request happened at all. There are (at least) two bug