[Openstack-operators] [openstack-dev][tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

Joshua Harlow harlowja at fastmail.com
Mon Nov 9 16:37:00 UTC 2015

+1 from me (although I've already contributed to osprofiler so my vote
might not count, ha). Anyway, people can poke me as well if they have
any questions about osprofiler and boris isn't around. I'm happy to
answer any questions as well...

Thanks boris for getting this rolling again...

Another question, do we need to talk with the people doing the
request_id integration into clients to make sure that the trace_id (or
whatever its called) is returned to clients...

I believe that was one of the original complaints/questions, is that
with osprofiler there is now 2 trace like headers
and such being sent around, should we nail that down now and put that
complaint/question to bed?


On Mon, Nov 9, 2015, at 02:57 AM, Boris Pavlovic wrote:
> Hi stackers,
> Intro
> -------
> It's not a big secret that OpenStack is huge and complicated ecosystem of different
> services that are working together to implement OpenStack API. 
> For example booting VM is going through many projects and services: nova-api, nova-scheduler, nova-compute, glance-api, glance-registry, keystone, cinder-api, neutron-api... and many others. 
> The question is how to understand what part of the request takes the most of the time and should be improved. It's especially interested to get such data under the load. 
> To make it simple, I wrote OSProfiler which is tiny library that should be added to all OpenStack 
> projects to create cross project/service tracer/profiler. 
> Demo (trace of CLI command: nova boot) can be found here: http://boris-42.github.io/ngk.html
> This library is very simple. For those who wants to know how it works and how it's integrated with OpenStack take a look here: https://github.com/openstack/osprofiler/blob/master/README.rst
> What is the current status? 
> -----------------------------------
> Good news: 
> - OSprofiler is mostly done 
> - OSprofiler is integrated with Cinder, Glance, Trove & Ceilometer 
> Bad news: 
> - OSprofiler is not integrated in a lot of important projects: Keystone, Nova, Neutron 
> - OSprofiler can use only Ceilometer + oslo.messaging as a backend 
> - OSprofiler stores part of arguments in api-paste.ini part in project.conf which is terrible thing
> - There is no DSVM job that check that changes in OSprofiler don't break the projects that are using it 
> - It's hard to enable OSprofiler in DevStack
> Good news: 
> I spend some time and made 4 specs that should address most of issues: 
> https://github.com/openstack/osprofiler/tree/master/doc/specs
> Let's make it happen in Mitaka!
> Thoughts?
> By the way somebody would like to join this effort?) 
> Best regards,
> Boris Pavlovic 
> _________________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

More information about the OpenStack-operators mailing list