Friday, 2016-11-04

openstackgerritDina Belova proposed openstack/performance-docs: Add new summit recaps part of documentation  https://review.openstack.org/39353800:05
*** harlowja has joined #openstack-performance00:11
*** dimtruck is now known as zz_dimtruck00:20
*** victorhe has joined #openstack-performance00:33
*** lezbar has quit IRC00:44
*** victorhe has quit IRC00:56
*** markvoelker has quit IRC00:57
*** victorhe has joined #openstack-performance00:57
*** victorhe has quit IRC01:00
*** victorhe has joined #openstack-performance01:01
*** jkilpatr has quit IRC01:07
*** zz_dimtruck is now known as dimtruck01:08
*** lezbar has joined #openstack-performance01:37
*** markvoelker has joined #openstack-performance01:57
*** victorhe has quit IRC02:02
*** markvoelker has quit IRC02:02
*** victorhe has joined #openstack-performance02:13
*** victorhe has quit IRC02:28
*** dimtruck is now known as zz_dimtruck02:41
*** zz_dimtruck is now known as dimtruck03:07
*** dimtruck is now known as zz_dimtruck03:25
*** zz_dimtruck is now known as dimtruck03:48
*** markvoelker has joined #openstack-performance03:58
*** markvoelker has quit IRC04:03
*** dimtruck is now known as zz_dimtruck04:19
*** zz_dimtruck is now known as dimtruck04:35
*** anilvenkata has joined #openstack-performance05:48
*** markvoelker has joined #openstack-performance05:59
*** markvoelker has quit IRC06:04
anilvenkataDinaBelova, Hi06:43
*** markvoelker has joined #openstack-performance07:00
*** markvoelker has quit IRC07:04
*** pcaruana has joined #openstack-performance07:33
*** ad_rien_ has joined #openstack-performance08:11
*** xek has joined #openstack-performance08:38
*** anilvenkata has quit IRC09:31
*** ad_rien_1 has joined #openstack-performance09:36
*** ad_rien_ has quit IRC09:40
*** ggherdov- has quit IRC10:42
*** kun_huang has quit IRC10:43
*** kun_huang has joined #openstack-performance10:46
*** openstackgerrit has quit IRC10:47
*** openstackgerrit has joined #openstack-performance10:48
*** anilvenkata has joined #openstack-performance10:51
anilvenkataDinaBelova, ping10:51
*** ad_rien_1 has quit IRC10:57
*** ad_rien_ has joined #openstack-performance10:58
*** ad_rien_ has quit IRC10:58
*** ggherdov- has joined #openstack-performance10:58
*** rfolco has joined #openstack-performance11:05
*** jkilpatr has joined #openstack-performance11:07
*** klindgren has joined #openstack-performance11:10
*** bvanhav_ has joined #openstack-performance11:18
*** klindgren has quit IRC11:42
*** ad_rien_ has joined #openstack-performance11:59
*** ad_rien_ has quit IRC11:59
*** xek has quit IRC12:17
*** markvoelker has joined #openstack-performance12:23
*** bvanhav_ has quit IRC12:54
*** ad_rien_ has joined #openstack-performance13:02
*** ad_rien_ has quit IRC13:02
*** ad_rien_ has joined #openstack-performance13:02
*** ad_rien_ has quit IRC13:02
*** ad_rien_ has joined #openstack-performance13:02
*** ad_rien_ has quit IRC13:03
*** dimtruck is now known as zz_dimtruck13:04
*** ad_rien_ has joined #openstack-performance13:04
*** ad_rien_ has quit IRC13:04
*** bvanhav_ has joined #openstack-performance13:11
*** zz_dimtruck is now known as dimtruck13:16
*** ad_rien_ has joined #openstack-performance13:21
*** victorhe has joined #openstack-performance14:21
*** hieulq_ has joined #openstack-performance14:23
DinaBelovaanilvenkata o/14:37
anilvenkataDinaBelova, wanted to check if OSProfiler supports nested functional call tracing14:38
anilvenkataDinaBelova, for example, "neturon port-create" does it record all nested functions(neutron private functions) which are called in plugin.py?14:38
DinaBelovaanilvenkata you can add osprofiler points to all functions for instance :) by default osprofiler is logging all api, rpc, DB calls14:40
DinaBelovabut if you'd like to debug something specific and trace everything - you'll need to add @trace decorators to interesed funstions or @trace_cls to needed class14:40
anilvenkataDinaBelova, how to enable it to log all private functions?14:40
anilvenkataDinaBelova, do you mean I have to change neutron code i.e add  @trace decorators in neutron modules?14:41
DinaBelovaanilvenkata yes, because nobody from neutron or whatever other team is wishing to wrap all functions by default :) by default everyone agreed on tracing API, RPC, DB, but not everything14:42
DinaBelovaanilvenkata you can add required decorator (either @trace for just function or @trace_cls for the whole class) with trace_private=True passed as an agrument14:43
anilvenkataDinaBelova, adding decorator means changing module, right?14:44
DinaBelovaanilvenkata yes, it means14:45
anilvenkataDinaBelova, And it can't be done with changing only neutron config options?14:45
DinaBelovaanilvenkata nope, because if everything will be wrapped (even if not working by default) in case of ANY errors in neutron or whatever other project all trace will contain 95% of osprofiler tracing logs14:46
DinaBelovanobody is wishing to see them14:46
anilvenkataok14:47
anilvenkataDinaBelova, which config file to modify if I want to trace rpc calls and not api?14:49
DinaBelovaso of course core teams of openstack project have an agreement on some minimum default amount of enabled (and turned off by default) tracing points (api, rpc, db) and eveything else should be traced manually in case if there is a specific research14:49
dalvarezsups looks like we're having a simultaneuous conversation sorry DinaBelova  :)14:49
DinaBelovadalvarezs it's ok14:49
dalvarezsthat makes perfect sense... maybe wrapping around certain points when further profiling info works if depending on certain configuration flag14:50
DinaBelovaanilvenkata right now you can turn on separately only DB (trace_sqlalchemy=true in projects configs files) everything else is turned on automatically. the reason is that this will add a complexity to the trace and not projects have, for instance, RPC at all :) keystone does not have for instance14:51
*** hieulq_ has quit IRC14:51
DinaBelovaalso I can barely imagine a use case when you'd like to see only RPC without API callw between the projects. E.g. you're tracing server create and you're seeing only nova and neutron RPC calls without seeing what API calls were done?14:52
DinaBelovaalso if you're tracing one project and one request you'll see only one parent API call...14:52
anilvenkataDinaBelova, yes14:53
anilvenkataDinaBelova, In neutron case, any api, like port-create, network-create doesn't depend on agents or other openstack components14:53
anilvenkataDinaBelova, for example port-create creates entries in DB and notifies agent14:54
anilvenkataDinaBelova, if we trace port-create and check which functions are time consuming14:55
DinaBelovaanilvenkata that's true, moreover neutron has an issue that agents running on the compute nodes have no idea about API calls that came to the neutron API - that means that you won't see it in the tracing of API call14:55
DinaBelovathose agents are just trying to periodically check state on the compute node itself14:56
anilvenkataDinaBelova, yes14:56
DinaBelovawith no connections to what was asked from the neutron server14:56
DinaBelovaand that's was something we discussed with neutron team for a while ago14:56
DinaBelovaand no obvious solution was found14:57
anilvenkataDinaBelova, so for neutron API performance measurement and checking for bottleneck14:57
anilvenkataDinaBelova, do u thing existing OSProfiler will be sufficient?14:57
DinaBelovafor API performance you can use osprofiler as is - it should work ok, moreover you'll see nested calls to all neutron processes and DB calls timings14:58
DinaBelovathat means you'll see the most influencing parts14:59
DinaBelovaor at least would be able to locate a bottleneck14:59
anilvenkataDinaBelova, here we have only one process i.e neutron-server14:59
dalvarezsDinaBelova, and if we need more tracing info, we still have the ability to wrap around the points we really want to explore further, right?15:00
DinaBelovadalvarezs yes15:00
anilvenkataDinaBelova, but OSProfiler wont trace all the nested called functions by default15:01
anilvenkatadalvarezs, ^15:01
anilvenkataDinaBelova, we have to find and enable them through decorators, right?15:01
DinaBelovaanilvenkata api call itself is transfering a call further - to DB for instance... this is something that takes time...15:01
DinaBelovaanilvenkata if you want to trace all functions one by one yes..15:01
DinaBelovathe issue is that I don't understand what api functions to you want to trace in fact. every API request has separated function dedicated to go through this request and do further actions - e.g. go to DB and extract the data15:03
dalvarezsDinaBelova, and including that kind of support into osprofiler is beyond the scope and probably rejected by ores15:03
DinaBelovausually this is something that takes time15:03
dalvarezscores*15:03
DinaBelovadalvarezs osprofiler is just a tracing library, you can trace whatever you want :) the issues is that if you'd like to see all python functions traced one by one this is not going to be accepted by cores - as this will make all requests and all tracebacks too messy15:04
anilvenkataDinaBelova, can u kindly show which changes in https://review.openstack.org/#/c/273951/ done for enabling API trace15:04
DinaBelovaso if you want to wrap all python functions by @trace decorator this can be done, but only in the testing environment15:04
anilvenkataDinaBelova, agrre with you15:04
anilvenkataagree15:05
DinaBelovaanilvenkata sure15:05
dalvarezsDinaBelova, yes15:05
DinaBelovabasically https://review.openstack.org/#/c/273951/28/etc/api-paste.ini to include osprofiler to the pipeline, https://review.openstack.org/#/c/273951/28/neutron/common/profiler.py to add profiler helper, https://review.openstack.org/#/c/273951/28/neutron/pecan_wsgi/app.py to allow needed headers, https://review.openstack.org/#/c/273951/28/neutron/service.py to enable API point15:07
DinaBelovaall other places are either adding tracing to some of the RPC managers or DB or agent drivers (for neutron case we agreed those need to be traced as well)15:08
anilvenkataDinaBelova, thanks a lot Dina. Now I understood it better15:09
DinaBelovaanilvenkata u'r welcome :)15:09
dalvarezsDinaBelova, thanks indeed15:11
*** bvanhav_ has quit IRC15:27
*** ad_rien_1 has joined #openstack-performance15:34
*** ad_rien_ has quit IRC15:38
*** pcaruana has quit IRC15:58
*** anilvenkata has quit IRC15:59
openstackgerritDina Belova proposed openstack/performance-docs: Add new summit recaps part of documentation  https://review.openstack.org/39353817:25
*** jkilpatr has quit IRC17:42
*** bvanhav_ has joined #openstack-performance17:43
*** jkilpatr has joined #openstack-performance17:43
*** harlowja has quit IRC18:00
*** harlowja has joined #openstack-performance18:03
*** harlowja has quit IRC18:18
*** johnthetubaguy has quit IRC18:28
*** johnthetubaguy_ has joined #openstack-performance18:28
*** johnthetubaguy_ is now known as johnthetubaguy18:30
*** harlowja has joined #openstack-performance18:30
*** anilvenkata has joined #openstack-performance18:35
*** jkilpatr has quit IRC18:50
*** ad_rien_1 has quit IRC18:55
*** victorhe_ has joined #openstack-performance19:02
*** victorhe_ has quit IRC19:03
*** victorhe_ has joined #openstack-performance19:04
*** jkilpatr has joined #openstack-performance19:04
*** victorhe has quit IRC19:05
*** ad_rien_ has joined #openstack-performance19:20
*** ad_rien_ has quit IRC19:22
openstackgerritDina Belova proposed openstack/performance-docs: Add Newton summit recap  https://review.openstack.org/39391819:28
*** bvanhav_ has quit IRC19:39
*** rfolco has quit IRC20:00
*** victorhe_ has quit IRC20:02
*** victorhe has joined #openstack-performance20:17
*** jkilpatr has quit IRC20:25
*** victorhe has quit IRC20:33
*** jkilpatr has joined #openstack-performance20:46
*** victorhe has joined #openstack-performance20:48
*** ad_rien_ has joined #openstack-performance20:57
*** victorhe has quit IRC20:58
*** victorhe has joined #openstack-performance20:58
*** anilvenkata has quit IRC21:32
*** victorhe has quit IRC22:15

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!