Tuesday, 2015-11-10

*** harshs has joined #openstack-performance00:13
*** harlowja has joined #openstack-performance00:20
*** wootehfoot has joined #openstack-performance00:21
*** wootehfoot has quit IRC00:21
*** wootehfoot has joined #openstack-performance00:22
*** wootehfoot has quit IRC00:26
*** wootehfoot has joined #openstack-performance00:26
*** arnoldje has joined #openstack-performance00:44
*** wootehfoot has quit IRC00:50
*** badari has quit IRC01:32
*** badari has joined #openstack-performance01:45
*** arnoldje has quit IRC01:48
*** badari has quit IRC02:12
*** badari has joined #openstack-performance02:19
*** badari has quit IRC02:25
*** arnoldje has joined #openstack-performance02:42
*** badari has joined #openstack-performance02:48
*** badari_ has joined #openstack-performance03:01
*** badari has quit IRC03:04
*** badari_ has quit IRC03:15
*** badari has joined #openstack-performance03:28
*** badari has quit IRC03:41
*** harshs has quit IRC04:01
*** manand has joined #openstack-performance04:32
*** manand has quit IRC05:22
*** harshs has joined #openstack-performance05:27
*** badari has joined #openstack-performance05:29
*** badari has quit IRC05:33
*** harshs has quit IRC05:43
*** harshs has joined #openstack-performance05:46
*** arnoldje has quit IRC06:11
DinaBelova#startmeeting Performance Team08:01
openstackMeeting started Tue Nov 10 08:01:05 2015 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
openstackThe meeting name has been set to 'performance_team'08:01
DinaBelova#topic test08:01
DinaBelova#topic test208:01
DinaBelova#endmeeting08:01
openstackMeeting ended Tue Nov 10 08:01:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-10-08.01.html08:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-10-08.01.txt08:01
openstackLog:            http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-10-08.01.log.html08:01
DinaBelovaokб умукнерштп ыууьы ещ цщкл щл Ж)08:02
DinaBelovawow :)08:02
DinaBelovaeverything seems to work ok :)08:02
kun_huangI thought I had missed this meeting when seeing the notification "meeting end log..." in my phone08:17
*** P has joined #openstack-performance08:30
*** P is now known as Guest530708:31
*** harshs has quit IRC09:34
DinaBelovakun_huang - please sorry for that :) I just got all changes related to OpenStack bots merged today morning, and wanted to make sure they work ok :)11:55
*** pwolsza has joined #openstack-performance12:16
*** pwolsza has left #openstack-performance12:20
*** patrykw has joined #openstack-performance12:23
*** wootehfoot has joined #openstack-performance13:31
*** wootehfoot has quit IRC13:43
*** dburnazyan has joined #openstack-performance13:50
*** ilyashakhat_mobi has joined #openstack-performance13:55
*** ilyashakhat_mobi has quit IRC14:06
*** gals has joined #openstack-performance14:11
*** arnoldje has joined #openstack-performance14:11
*** gals has quit IRC14:22
*** gals has joined #openstack-performance14:27
*** Guest5307 has quit IRC14:30
*** patrykw has quit IRC14:30
*** gals has quit IRC14:35
*** gals has joined #openstack-performance14:36
*** arnoldje has quit IRC14:45
*** regXboi has joined #openstack-performance14:46
*** badari has joined #openstack-performance14:52
*** listomin has joined #openstack-performance14:55
DinaBelovaheh, people are joining the channel :)14:57
*** deepika has joined #openstack-performance14:57
*** arnoldje has joined #openstack-performance14:59
DinaBelova#startmeeting Performance Team15:00
openstackMeeting started Tue Nov 10 15:00:00 2015 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
openstackThe meeting name has been set to 'performance_team'15:00
DinaBelovaHello everyone! o/15:00
DinaBelovawho's here? :)15:00
kun_huang+115:00
DinaBelovaharlowja - were you able to wake up? :)15:00
*** Kristian_ has joined #openstack-performance15:01
DinaBelovahope some other channel members are here as well :)15:01
badari+115:01
DinaBelovaregXboi, SpamapS - are you around as well?15:01
*** augiemena3 has joined #openstack-performance15:02
DinaBelovaok, let's wait for few more minutes15:02
Kristian_so not used to this type of meeting, more of an ATT Connect user, but #it works15:02
DinaBelova:D15:02
Kristian_#itworks15:02
DinaBelovawhile people are waking up - here is our agenda15:02
*** UK has joined #openstack-performance15:02
DinaBelova#link https://wiki.openstack.org/wiki/Meetings/Performance#Agenda_for_next_meeting15:02
*** UK is now known as Guest1161715:03
DinaBelovaI decided to start with something related to the passed summit15:03
DinaBelova#topic Summit follow-up15:03
DinaBelovaas you remember we had kick-off session in Tokyo15:03
DinaBelova#link https://etherpad.openstack.org/p/mitaka-cross-project-performance-team-kick-off15:03
regXboiregXboi is here15:03
DinaBelovayay!15:03
DinaBelovaI see one moment in the etherpad that seems interesting to me and not covered during the summit session.15:04
DinaBelova#info What's good for performance test (time to do $thing) vs scale test (behavior of doing $thing in parallel)15:04
* regXboi is also over in the neutron drivers meeting so running between two rooms15:04
DinaBelovaat Mirantis we use Rally for this purpose with different coefficients.15:04
DinaBelovayeah, that's sad...15:04
DinaBelovaregXboi - hope you were able to go through the etherpad?15:04
regXboiunfortunately ... no15:04
regXboi:(15:04
DinaBelovaheh :)15:05
regXboior at least - not yet15:05
DinaBelovaok, i'll kindly ask you to do that in some nearest future :)15:05
*** patrykw has joined #openstack-performance15:05
regXboithere is an RFE over in the neutron drivers meeting that I want to reflect up to oslo because I think it has impact to this effort15:05
patrykwhi all patrick@intel15:05
DinaBelovacool, thank you for visiting it15:05
*** jeffcb has joined #openstack-performance15:05
DinaBelovapatrykw o/15:05
regXboiok, did a quick scan :)15:06
DinaBelovaso quick description of what happened on summit and what feedback was collected15:06
DinaBelovathe main input from different community people on the summit for this team was to start with common methodologies, tool sets, ways to compare different deployments, etc. and eventually work on recommendations for projects, writing up testing methodologies and best deployment practices, and share results of the testing.15:06
DinaBelovaso we had many people, many tools, lots scenarios, etc.15:06
DinaBelovaand I decided to start with basic standardisation15:07
DinaBelovalike "what tools to name as the canonical ones?"15:07
DinaBelovaetc.15:07
regXboiI guess I'd ask "what do people mean by performance?" as that word means different things to different people15:07
DinaBelovayes, that's true15:08
kun_huangregXboi: agreed...15:08
regXboi(sorry for the meta question)15:08
DinaBelovaat mirantis we use to measure two things during the performance testing15:08
DinaBelovacontrol plane performance (operations over OpenStack resources)15:08
kun_huangperf = benchmark, tracing, tuning and so on15:08
kun_huangthere're a lots of tools on for different purposes15:09
regXboiDinaBelova: ok, so what do you mean by "control plane performance?"15:09
badariDinaBelova: Control plane performance without any data plane load at all?15:09
DinaBelovalike what time it'll take to boot Vm, assign floating IP, etc. in different load15:09
kun_huangrally is good at benchmark of API level15:09
DinaBelovaand data plane separately :)15:09
Kristian_we use Rally now and modify some of the out of the box .json scenarios according to our architecture :)15:09
DinaBelovakun_huang I'll agree15:09
DinaBelovacool :)15:09
Kristian_mainly because its Free and we are saving on test tool licensing.  but it is a flexible, great too;l15:10
regXboiwell, I'll say I take a slightly different view of control plane performance15:10
augiemena3we use Rally as well and make modifications as well for our use15:10
DinaBelovaand for data plane we use Shaker  https://github.com/openstack/shaker (Functionality is being moved from Shaker to Rally)15:10
Kristian_we are looking at jmeter next for load/VM testing as well15:10
DinaBelovaregXboi - please share the idea15:10
Kristian_@DinaBelova good news!15:10
andreykurilinhi all:)15:10
regXboiI tend to look *very closely* at execution time of operations in the agents/API/etc15:10
kun_huangKristian_:  is there some good points on jmeter other than rally?15:10
regXboibecause at it's core - the messaging RPC is just a queuing system15:11
regXboier queueing15:11
DinaBelovawell, it looks like I need to change topic and return back to something else in open discussion15:11
DinaBelova#topic Rally as a control plane benchmarking tool agreement15:11
patrykwin our team we have different approach, we are simulating LOB applications on cloud and "simulating real" (strange :)) workload by gatling15:11
augiemena3I do think it's important to categorize the performance tools:  benchmarks, benchmark harnesses, workloads, profiling/tracing, monitoring, etc15:11
Kristian_@regXboi we are looking at it for virtual machine testing, something Rally does not yet do15:12
kun_huangaugiemena3: +115:12
patrykwapplications do not stressing the resources on max15:12
Kristian_we need something open-source based and easier to learn, community supported as well15:12
DinaBelovaaugiemena3 +115:12
regXboiok, so Rally is very good at supplying API load, which lets you stress the API and the input to the RPC15:12
DinaBelovaKristian_ - it's going to support that type of testing in future15:12
patrykwplus during the test checking with rally how the API is working15:12
DinaBelovaKristian_ - workloads testing15:13
DinaBelovaandreykurilin - am I right?15:13
regXboibut AFAICT, OpenStack lacks the ability to report on execution time in the agents15:13
kun_huangregXboi: if you just need execution time on agent and rpc level, there would be a lot of tools15:13
regXboiand note: I'm not just saying "profiling"15:13
andreykurilinDinaBelova: yes15:13
*** rohanion has joined #openstack-performance15:13
rohanionhi everyone15:13
kun_huangregXboi: I think boris' osprofiler is design for that15:13
DinaBelovaok, so we can assume Rally is good for the API testing15:13
Kristian_@DinaBelova that's right, workload as well as VM characteristics measurements we are looking at.  we need to develop SLAs in the integrated cloud , and that is difficult to do w/o a standard set of measurement15:14
patrykw+115:14
andreykurilinDinaBelova: kun_huang is also core of rally, so he can answer to all rally related question too :)15:14
DinaBelovafor profiling and tracing we can eventually use osprofiler15:14
kun_huangregXboi: but I just read his writings without real test15:14
regXboikun_huang: it's possible, but it has to be something built into the system and turned off and on with configuration15:14
regXboiDinaBelova: please note what I just said :)15:14
DinaBelovaand eventually rally will support dataplane as well15:14
DinaBelovayep, sorry :)15:14
kun_huangregXboi: haha, have you tried systemtap/ftrace?15:14
*** amaretskiy1 has joined #openstack-performance15:14
DinaBelovaregXboi - that's true, although if it will be deeply integrated with openstack projects - why not in fact?15:15
*** oanufriev has joined #openstack-performance15:15
regXboiDinaBelova: because I'm trying to get to the point where I can do continuous test for performance15:15
regXboiand I think that means the tools have to be there and turned on/off via a simple config switch15:16
kun_huangregXboi: "continuous test for performance" +1 for this good point15:16
regXboier sorry ... tools was a bit of a misnomer15:16
DinaBelovaregXboi - so you want like one place to have this swithed on/off15:16
regXboiDinaBelova: so let me give you an example: https://etherpad.openstack.org/p/hyper-scale15:17
regXboiright now to do that, I'm having to decorate files manually to get increasing levels of execution time data15:17
DinaBelovalooking15:17
regXboiand anything manual doesn't work15:17
DinaBelovayeah, that's true..15:17
DinaBelovawell, it's one more moment to define15:18
regXboiso whatever we use for execution time data has to be built in and has to be easily turned on and off so that we don't pollute logs15:18
regXboionce you *have* that15:18
regXboithen we get into the whole statistical tool discussion15:18
DinaBelovaalthough it more related to the tracing and profiling15:18
DinaBelovaif we are talking about API benchmarking Rally is pretty good here15:18
DinaBelovaI suppose we all can agree hee15:18
DinaBelovahere*15:18
regXboias I said, the RPC is essentially a queueing system15:19
regXboiRally drives the arrival rate15:19
DinaBelovayes, so we need to extend it with other tools, but I suppose we still need it15:19
regXboibut something needs to document the processing time so that you know what's causing you problems if the RPC starts to break15:19
DinaBelovaagree15:19
regXbois/if/when/15:19
DinaBelova:d15:19
DinaBelova:D15:19
DinaBelovayes, that's true15:19
regXboiso... I agree that Rally is great for the front end :)15:20
patrykwtesting data plane with Rally ?? really ?15:20
DinaBelovaand we need something else for deeper analysis15:20
DinaBelovapatrykw - eventually :)15:20
*** harlowja_at_home has joined #openstack-performance15:20
DinaBelovawe have rally contributor here :)15:20
harlowja_at_homeDinaBelova, i made it!15:20
harlowja_at_homebetter late than never :-P15:20
DinaBelovaharlowja_at_home o/15:20
harlowja_at_home:)15:20
harlowja_at_homeonly half zombine15:20
DinaBelovapatrykw - andreykurilin is Rally core15:20
Kristian_question: does Rally log all API objects it creates/destroys (i believe it does) and does it have a separate log report, similar to the reports that it comes pre-packaged with?15:20
kun_huangregXboi: https://github.com/openstack/scalpels/blob/master/scripts/rbt-trace.py at least, this script could be used RPC tracing15:20
* regXboi looks15:21
DinaBelovaKristian_ - yep, it logs, yes it has separated log report for everything it does15:21
regXboikun_hunag: I'm looking to go deeper15:21
regXboithat will tell me about the RabbitMQ, which is certainly useful15:21
andreykurilinDinaBelova: we have a lot of rally contributors here: kun_huang, oanufrief15:21
DinaBelovakun_huang - thanks for the link, I'll need to go through it further15:22
Kristian_@DinaBelova thank you!  looking for a runtime type of report15:22
DinaBelovaandreykurilin - yep, sure15:22
andreykurilin:)15:22
regXboibut I'm looking to root cause the delays in processing to get them fixed in the code that serves the RPC15:22
*** patrykw_ has joined #openstack-performance15:22
kun_huangregXboi: I use dtrace to catch python function call time...15:22
regXboikun_huang: automagically?15:23
kun_huangbut that is not implemented in Ubuntu15:23
DinaBelovaso I think we can assume the following: we have Rally now for front-end API testing, it will be able to do dataplane with its help in future, and we need something else to catch what's going on deeper while request processing15:23
Kristian_@kun_huang does it provide stress against RabbitMQ?15:23
kun_huangregXboi: script only, I'm working on my prototype15:23
andreykurilinDinaBelova: +115:23
DinaBelovain fact it's not only RPC, it's various drivers work, it's DB performance, etc15:23
kun_huangKristian_: that rbt-trace.py, don't; it is just rpc log15:23
DinaBelovaso it looks like it'll be some number of additional tools15:24
andreykurilinosprofiler can be really useful for profiling/tracing stuff, but it need more contribution:(15:24
Kristian_i see. because that is something also we are looking for, as a stressful/load component against RPC queues and RabbitMQ15:24
kun_huangandreykurilin: yep, it is15:24
*** patrykw has quit IRC15:24
DinaBelovakun_huang, Kristian_, regXboi - would you agree with the points I mentioned?15:24
kun_huangandreykurilin: about osprofiler, I think boris need bring more and good demo for users15:24
kun_huangDinaBelova: I agree with Rally is a good openstack benchmark framwork15:25
* harlowja_at_home will try to work on osprofiler stuff soon, will do some tweaks to it maybe later this week...15:25
* DinaBelova as well15:25
andreykurilinkun_huang: the main problem of osprofiler is a cores of other projects, since osprofiler needs integration with them15:25
andreykurilinharlowja_at_home: nice15:25
regXboiDinaBelova: I would summarize as a profiler that is built into all OpenStack projects (likely via oslo)15:25
Kristian_yes, we need some community tools that do back-end stress to the VMs and databases w/ a front-end manager15:25
regXboiand if osprofiler fits the bill, sure15:26
kun_huangandreykurilin: I think we should educate them, there fantastic tracing tool has to built into native codes15:26
DinaBelovaregXboi - agreed15:26
harlowja_at_homeandreykurilin, yes that, we need to make a joint effort to fix what cores have complained about and figure out why its not integrated yet...15:26
kun_huangs/there/every15:26
DinaBelovaok, let me write something with >agreed< tag15:26
regXboiis osprofiler part of oslo?15:26
harlowja_at_homekun_huang, +1 education, and working through the issues they have with it...15:26
regXboiif not, it should be15:26
kun_huangregXboi: nope15:26
harlowja_at_homeregXboi, not yet15:26
regXboier it *must* be15:26
regXboiok, that's #115:26
patrykw_ku_huang: from the perspecive of end user, which using VM, the numbers from Rally is what he wanted to see ??, or he just want to have information how well the VM is working and plus if infrastructure is fine15:26
andreykurilinharlowja_at_home: as far as I remember, they were against check `if profiler == None`, since it can produce performance issues :D15:27
harlowja_at_homeandreykurilin, yes, we have to bust that kind of dumb stuff15:27
harlowja_at_homebut in a politically nice way, ha15:27
kun_huangpatrykw_: I think you are looking for a "vm workload benchmark framework"15:27
DinaBelova#agreed Rally is good benchmarking solution that we want to use widely for OpenStack API benchmarking and dataplane testing in future. Although we need something else for profiling that is built into all OpenStack projects15:27
kun_huangpatrykw_: I'm not sure ;(15:27
augiemena3@DinaBelova +115:28
patrykw_kun_huang: what we want to benchmark ?? only APIs or something more ??15:28
andreykurilinkun_huang, patrykw_: we have serie of patches for "vm workload", but they need more reviewers15:28
andreykurilin*we = Rally15:28
patrykw_:)15:28
kun_huangpatrykw_: both API level benchmark and vm workload benchmark15:28
regXboiDinaBelova, can we go further and say the profiling has to be controlled via config as well as by decoration?15:28
DinaBelovaregXboi - I'll agree here15:28
regXboiI mean, I'd like to have decoration for one offs :)15:29
regXboibut CT says config (unless somebody can find a better solution)15:29
DinaBelovawe need single opportunity to switch this possibility on/off15:29
patrykw_andreykurilin: it is fine to use Rally to test API, we are doing this same but vm workload is something else15:29
DinaBelovapatrykw_ - this is just new commits and new Rally functinality15:29
DinaBelovathat's in progress now :)15:30
andreykurilinpatrykw_: What is the difference?)15:30
kun_huangpatrykw_:  yes it is...15:30
harlowja_at_homeregXboi, as for oslo, let's work on that, and chat with dims and such, i'd like to capture a list of why it isn't integrated into say nova, keystone... and attempt to resolve those (either by dispelling myths or fixing code) before osprofiler ---> oslo though....15:30
Kristian_@DinaBelova - we also need a way to isolate troublesome VMs from a test, that it picks up from statistics during runtime by IP/name/node identification15:30
regXboipatrykw_: I suspect that we need to come up with a common vm workload to handle that stressing15:30
DinaBelovaharlowja_at_home +115:30
regXboiharlowja_at_home: well, that's a bit of a chicken and egg problem15:30
DinaBelovaKristian_ - I suppose eventually it's possible, although not sure how to do that right now15:31
patrykw_DinaBelova: want to see that :) currently we are using mix of PKB + gatling to achieve some level of workload15:31
regXboiI'd like to have that conversation begin with "this is going into oslo, and you really need to integrate to support CT, so what can we do to help with that"15:31
DinaBelovapatrykw_ brrr...15:31
kun_huangI think today's meeting is one hour open discussion ;)15:31
DinaBelovayep, it'll be very cool to have everything in one box15:31
andreykurilinkun_huang: :D15:31
Kristian_@DinaBelova as long as we can get requirement in for future development in Rally or a back-end version of Rally early, i'm fine w/ that answer15:31
Kristian_:)15:31
DinaBelovakun_huang, andreykurilin - do you have links to the workloads patches?15:32
andreykurilinregXboi: there was a spec of moving osprofiler to oslo namespace15:32
DinaBelovakun_huang - well, yes15:32
andreykurilinDinaBelova: one moment please15:32
DinaBelovaI was too stupid to create an agenda15:32
harlowja_at_homeregXboi, sure, i think some of the issues that will be captured aren't 'it isn't in oslo so i won't integrate it'15:32
regXboiandreykurilin: is there a #link?15:32
DinaBelovaandreykurilin sure15:32
kun_huang#link https://review.openstack.org/#/q/status:open+project:openstack/rally+branch:master+topic:bp/vm-workloads-framework,n,z15:32
DinaBelovakun_huang thank you sir15:32
andreykurilin:)15:32
regXboiharlowja_at_home: yes I don't want to be blocked by that quote :)15:32
harlowja_at_homeregXboi, we can resolve that quote if it happens rather quickly imho...15:33
Kristian_@DinaBelova you were asking about other tools, we are using jmeter and looking at traffic engineering with SmartBits iTest / Hyperscale solution for scale test15:33
harlowja_at_homebut saying something like 'shutup u crazy person, it will go into oslo once we resolve the other issues'15:33
harlowja_at_home^ not exactly like that , ha15:33
Kristian_we don't have a PoC in place yet15:33
andreykurilinregXboi: https://review.openstack.org/#/c/103825/15:33
DinaBelovaKristian_ - a-ha, thank you sir15:33
regXboiharlowja_at_home: yes, that isn't political (rotflmao)15:33
harlowja_at_home:)15:33
andreykurilinregXboi: as you can see there were a lot of + for osprofiler:)15:33
regXboiandreykurilin: on my list to read and comment on today15:34
regXboiand thx :)15:34
kun_huangandreykurilin: I'm 100% sure that osprofiler will be a good solution15:34
patrykw_i was working on other cloud solutions and main think always was how much load (instances) I can put without issues, issues to the resources, and issues to the management plane15:34
DinaBelovaso let's write something in OSprofiler topic to have beautiful notes15:34
regXboiDinaBelova: I assume we want to put of the "statistical" discussion for another day?15:34
DinaBelova#topic Taking part in the OSprofiler initiative15:34
kun_huanggoogle's dapper and twitter's zikpin examples15:34
DinaBelovaregXboi - I suppose yes15:34
regXboier off15:34
andreykurilinbtw, everyone saw the rexample of osprofiler reports? http://boris-42.github.io/ngk.html15:35
regXboiDinaBelova: I'm good with thta :)15:35
* regXboi looking15:35
patrykw_will the rally tell us: hold done, you are going to far ?? :)15:35
DinaBelovaso it looks like during Mitaka there will be some activity on making osprofiler workable enough for all projects15:35
DinaBelovaharlowja_at_home, me and Boris at least will try to do that15:35
andreykurilinDinaBelova: don't forget about me:)15:36
DinaBelovaand if this solution will be fully ok to be used for tracing, I believe it'll become an oslo standard15:36
andreykurilinI'll try to help too15:36
regXboidoes osprofiler only do db and rpc or can it go to specific python functions?15:36
DinaBelovaandreykurilin sorry sir :)15:36
kun_huangregXboi: yep15:36
regXboikun_hunag: yep == ???15:36
harlowja_at_homeregXboi, == yes15:36
andreykurilin:)15:36
regXboino, I asked an A or B - > yes doesn't answer15:36
kun_huangregXboi: osprofiles covers db level things15:36
regXboiok, and RPC15:37
Kristian_will chk out osprofiler, thx for the tool tip @andreykurilin15:37
kun_huangregXboi: in document, it covers too...15:37
regXboibut *does it cover specific functions in the agent code*15:37
kun_huangregXboi: no it doesn't15:37
harlowja_at_homeif u make it do so :)15:37
DinaBelovaharlowja_at_home ++15:37
regXboiok... *that's* a problem15:37
regXboithat means osprofiler doesn't in its current form go deep enough15:37
harlowja_at_homeit doesn't integrate with pdb to automatically do all the things15:38
DinaBelovaI thing it can be developed after making current unctioanlity workable15:38
harlowja_at_homeits not magic ;)15:38
kun_huangregXboi: that's the reason I am using systemtap15:38
DinaBelovaregXboi - right now - yes15:38
DinaBelovabut if we want unified way of tracing, we need to work on this...15:38
andreykurilinregXboi: I suppose osprofiler can be a base for good profiling tool, but it need some work on it15:38
DinaBelovaregXboi - otherwise everyone will be using something they use to have and the results won't be comparable at all15:39
regXboiall - I'm not saying we shouldn't improve it, I'm just working to understand what it would need for this15:39
andreykurilin:)15:39
regXboior I should say what I think it would need for this15:39
DinaBelovaand that's something I want to avoid15:39
DinaBelovasure15:39
DinaBelovaregXboi - I'm very glad to collect your feedback, it's very useful :)15:39
regXboiand believe me, I'll make these comments on that commit :)15:40
regXboibecause what I see, I *mostly* like15:40
DinaBelova:D15:40
regXboibut it needs some more pieces to make it sing15:40
regXboianother question - are we sold on Ceilometer only for reporting?  what about simple logs?15:40
DinaBelovaok, so it looks like we have solid opinion here - OSprofiler may become one day the tracing / deeper analysis tool, but it requires some work to be done15:41
andreykurilinregXboi: it supports text files15:41
regXboiandreykurilin: ok, I missed that on the quick scan15:41
andreykurilinalso, there is a spec for multi backend - https://github.com/openstack/osprofiler/blob/master/doc/specs/in-progress/multi_backend_support.rst15:41
DinaBelovaregXboi - one of the boris-42 concerns was to make more collector backends, but simple text was available afair15:41
andreykurilin#link http://lists.openstack.org/pipermail/openstack-dev/2015-November/078845.html15:42
DinaBelova#link https://github.com/openstack/osprofiler/blob/master/doc/specs/in-progress/multi_backend_support.rst15:42
andreykurilinthe latest thread related to osprofiler15:42
DinaBelovand all specs that need to be covered at least are placed there as well15:42
regXboiandreykurilin: yes I saw that :)15:42
DinaBelovaok, so it looks like we're done with osprofiler15:43
DinaBelovaany more notes about it?15:43
DinaBelovaok15:43
DinaBelova#topic Data plane testing tools15:43
andreykurilinrally!15:43
andreykurilin:D15:43
DinaBelovaok, so later rally will support it15:43
DinaBelova;)15:43
andreykurilin;(15:43
DinaBelovaKristian_ is using jmeter and looking at traffic engineering with SmartBits iTest / Hyperscale solution for scale test15:43
DinaBelovafor some of the bits15:44
DinaBelovaMirantis uses shaker right now15:44
badariDinaBelova: we are looking at using "cbtool" currently15:44
kun_huangI know vmtp/kloudbuster15:44
DinaBelova#link https://github.com/openstack/shaker15:44
DinaBelovaok, so it looks like until we'll have nice Rally solution it'll be a complete mess here :)15:44
regXboiSo, here is where I think it may make sense to come up with a standard image that can be bundled with OpenStack?15:44
DinaBelovaregXboi - that will be very logical I believe15:45
Kristian_@DinaBelova can u explain to me in a nutshell what shaker does?  is it L2/L3 stress tool?15:45
patrykw_regXboi :)15:45
DinaBelovaKristian_ - in short, yes15:45
regXboiDinaBelova: I thought I saw somebody suggest that earlier in the thread (or get most of the way there)15:45
Kristian_just heard of it so will read the docs shortly :)15:45
kun_huanghaha15:45
DinaBelovaKristian_ - currently it's only about networking15:46
DinaBelovaand no need to make it wider due to the current Rally changes15:46
DinaBelovaregXboi - can you find a thred please?15:46
Kristian_so shaker only touches/focuses on neutron component?15:46
regXboiDinaBelova: it was in this meeting... let me go back and look15:46
DinaBelovaregXboi, oh, I missedit :)15:46
DinaBelovaKristian_ - yes, that's true :)15:47
regXboiIt was patrykw_ that got most of the way there: http://eavesdrop.openstack.org/irclogs/%23openstack-performance/%23openstack-performance.2015-11-10.log.html#t2015-11-10T15:29:3515:48
DinaBelovaa-ha, thank you sir15:48
DinaBelova#link http://eavesdrop.openstack.org/irclogs/%23openstack-performance/%23openstack-performance.2015-11-10.log.html#t2015-11-10T15:29:3515:48
patrykw_yep, for data plane we are using Gatling + PKB15:48
DinaBelovaok, so it looks like we need to enforce standard image creation/assumption15:49
DinaBelovaand then try to understand if we can compare at least somehow currently gathered data15:49
regXboiif the image has what is needed for stressing of the various components, that makes sense15:49
patrykw_as data source mediawiki + magentoshop15:49
DinaBelovapatrykw_ - interesting, thank you sir15:50
DinaBelovapatrykw_ - do you have this data somewhere published?15:50
augiemena3Badari:  yes, https://github.com/ibmcb/cbtool15:50
DinaBelovapatrykw_ - or is it private info?15:50
patrykw_DinaBelova: not yet, currently gathering multinoda data with top bin CPUs15:51
patrykw_"multinode"15:51
DinaBelovapatrykw_ - will you be able to share the results once they'll be collected? I mean, it's interesting experience15:51
DinaBelovaand personally I would love to take a look on the results15:51
kun_huangokay guys, this meeting is close to end; I'm working on my prototype, scalpels, which is debugfs system with systemtap/ftrace support, if you're interested in this, welcome to #openstack-scalpels15:52
DinaBelova#topic Open Discussion15:52
patrykw_DinaBelova: probably yes, and probably the automated scripts15:52
DinaBelovapatrykw_ - thank you sir15:53
DinaBelovakun_huang - thanks, will join15:53
DinaBelovaI would ask everyone here who uses rally to prepare and send to this channel scenarios you use to run15:53
regXboiwhere did the hour go :)15:54
DinaBelovaregXboi :D15:54
DinaBelova#action everyone who uses Rally - please share the scenarios you're running15:54
patrykw_DinaBelova: +1 good point15:54
DinaBelovaI think we can try to unify the scenarios list15:54
regXboiDinaBelova: can we start an etherpad for that?15:55
DinaBelovaI think we can use etherpads or whatever for this purpose15:55
kun_huangusing rally to run complex load to openstack15:55
DinaBelovahttps://etherpad.openstack.org/p/rally_scenarios_list15:55
regXboiDinaBelova: thx15:55
Kristian_@DinaBelova - if you need inputs on what can be put into "out-of-the-box" scenarios for testing i can do that collectively here @AT^T15:55
DinaBelovaI've quickly copy-passed the scenarios names, but I'll add their configs somewhere too15:55
DinaBelovaKristian_ - this will be perfect!!!!15:56
Kristian_for Rally testing in particular15:56
DinaBelovaKristian_ - thank you sir15:56
Kristian_yw :)15:56
DinaBelova#action Kristian_  - have internal att session to collect feedback on what can be added to out-of-box- rally15:57
DinaBelovaok, so it looks like we're running out of time15:57
DinaBelovaany specific points to cover?15:57
regXboiother than another channel or two to watch? no :)15:57
DinaBelova;D15:57
Kristian_@DinaBelova and group - will do15:57
kun_huangDinaBelova: we need a focus next time15:57
regXboiyep, time to post an agenda :)15:58
DinaBelovakun_huang - that's true15:58
kun_huangon benchmark topic, or tracing, or people's need15:58
Kristian_agenda would be nice, agreed15:58
kun_huangit helps us to find more details15:58
DinaBelovaplease feel free to clear https://wiki.openstack.org/wiki/Meetings/Performance#Agenda_for_next_meeting and fill with your items15:58
DinaBelova:)15:58
Kristian_context would be good too.  performance testing means different things to different engineers/techies :P15:59
*** rohanion has left #openstack-performance15:59
DinaBelovaok, thanks everyone, and let's have a bit clearer meeting next tim :)15:59
DinaBelova#endmeeting15:59
patrykw_http15:59
openstackMeeting ended Tue Nov 10 15:59:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-10-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-10-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/performance_team/2015/performance_team.2015-11-10-15.00.log.html15:59
*** Kristian_ has quit IRC15:59
DinaBelovaI've cleared agenda for the next meeting16:00
DinaBelovaplease feel free to fill it16:00
*** jeffcb has quit IRC16:00
*** bapalm has joined #openstack-performance16:02
*** augiemena3 has quit IRC16:04
*** listomin has quit IRC16:09
*** mdorman has joined #openstack-performance16:24
*** patrykw_ has quit IRC16:33
*** harlowja_at_home has quit IRC16:42
*** wootehfoot has joined #openstack-performance16:57
*** wootehfoot has quit IRC17:00
SpamapSDinaBelova: sorry I could not join the meeting. 0800 Pacific is basically never going to be free for me (taking kids to school.. :-P  )17:03
SpamapSso I can join whe daylight savings time happens again and it is 090017:04
SpamapSWill try to find a more-eastern colleague to represent me. ;)17:04
*** amaretskiy1 has quit IRC17:11
*** badari has quit IRC17:29
DinaBelovaSpamapS, np :)17:40
DinaBelovathanks for letting know :)17:40
*** manand has joined #openstack-performance17:53
*** harshs has joined #openstack-performance18:23
*** wootehfoot has joined #openstack-performance18:27
*** ilyashakhat_mobi has joined #openstack-performance18:35
*** Guest11617 has quit IRC18:44
*** gals has quit IRC19:20
*** wootehfoot has quit IRC19:39
*** wootehfoot has joined #openstack-performance19:56
*** deepika has quit IRC20:04
*** badari has joined #openstack-performance20:26
*** ilyashakhat_mobi has quit IRC20:30
*** wootehfoot has left #openstack-performance20:34
regXboiDinaBelova: we need to get that osprofiler oslo-spec resubmitted for Mitaka - who should take that action item?20:51
*** rvasilets___ has joined #openstack-performance21:48
*** boris-42 has joined #openstack-performance22:30
*** regXboi has quit IRC22:33
*** harshs has quit IRC22:52
notmorganDinaBelova: ooh meeting is 080023:40
notmorgan?23:40
notmorgandoh23:40
*** arnoldje has quit IRC23:40
*** manand has quit IRC23:49
*** mdorman has quit IRC23:50

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