Tuesday, 2016-08-23

*** hockeynut has quit IRC01:36
*** markvoelker has joined #openstack-performance01:44
*** markvoelker_ has joined #openstack-performance01:46
*** markvoelker has quit IRC01:50
*** rfolco has quit IRC02:18
*** markvoelker has joined #openstack-performance04:21
*** ilyashakhat has joined #openstack-performance04:22
*** markvoelker_ has quit IRC04:22
*** markvoelker has quit IRC04:28
*** markvoelker has joined #openstack-performance05:29
*** ilyashakhat has quit IRC05:31
*** markvoelker has quit IRC05:39
*** ilyashakhat has joined #openstack-performance05:40
*** ilyashakhat has quit IRC05:50
*** msimonin has joined #openstack-performance05:54
*** msimonin has quit IRC05:57
*** msimonin has joined #openstack-performance05:57
*** msimonin has quit IRC05:59
*** msimonin has joined #openstack-performance05:59
*** msimonin has quit IRC06:00
*** pcaruana has joined #openstack-performance06:14
*** markvoelker has joined #openstack-performance06:36
*** markvoelker has quit IRC06:42
*** f13o has quit IRC06:53
*** msimonin has joined #openstack-performance07:20
*** markvoelker has joined #openstack-performance07:38
*** markvoelker has quit IRC07:43
*** openstackgerrit has quit IRC08:03
*** openstackgerrit has joined #openstack-performance08:04
*** f13o has joined #openstack-performance08:07
*** dewanee has joined #openstack-performance08:25
*** f13o has quit IRC08:31
*** markvoelker has joined #openstack-performance08:39
*** markvoelker has quit IRC08:44
*** markvoelker has joined #openstack-performance09:40
*** markvoelker has quit IRC09:44
*** markvoelker has joined #openstack-performance11:09
*** bvanhav has joined #openstack-performance11:19
*** markvoelker has quit IRC11:20
*** rfolco has joined #openstack-performance11:47
*** eandersson_ has quit IRC13:47
*** eandersson has joined #openstack-performance13:56
*** pcaruana has quit IRC14:02
*** hieulq_ has joined #openstack-performance14:08
*** zz_dimtruck is now known as dimtruck14:17
*** pcaruana has joined #openstack-performance14:17
*** tinbar has joined #openstack-performance14:25
*** tinbar has quit IRC14:25
*** hieulq__ has joined #openstack-performance14:31
*** hieulq_ has quit IRC14:33
*** bwallis has quit IRC14:55
openstackgerritIlya Shakhat proposed openstack/performance-docs: Add Neutron ML2 OVS plugin performance test plan  https://review.openstack.org/35925514:56
*** hockeynut has joined #openstack-performance14:58
*** hieulq__ has quit IRC15:01
*** hieulq_ has joined #openstack-performance15:01
*** klindgren has quit IRC15:17
*** bwallis has joined #openstack-performance15:21
*** klindgren has joined #openstack-performance15:30
*** bwallis has quit IRC15:37
*** rohanion has joined #openstack-performance15:50
*** aignatev has joined #openstack-performance15:51
DinaBelovarohanion, aignatev o/15:56
DinaBelovaklindgren wow, you joined the channel right before the meeting :) does it mean you're going to attend?15:56
DinaBelova:)15:56
*** pcaruana has quit IRC15:56
klindgrenum15:57
klindgrenmore like I had to fix some stuff before I have to attend 2 meetings15:57
klindgrenat once15:57
*** ad_rien_ has joined #openstack-performance15:57
klindgren(this would be #3)15:58
DinaBelova:D heh, I know you're having the daily meetings at this time slot15:58
DinaBelovaI hoped to discuss new time slots this meeting15:58
ad_rien_15:30 sounds good on our side ;)15:58
ad_rien_(Hi all BTW)15:58
DinaBelovaklindgren and for you? is 15:30 UTC (8:30 PST better? as we usually have meeting for 30-45 mins)15:59
DinaBelovaad_rien_ o/15:59
ad_rien_o/15:59
DinaBelova#startmeeting Performance Team16:00
openstackMeeting started Tue Aug 23 16:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'performance_team'16:00
DinaBelovaI think we may start with organizational questions16:00
DinaBelovaas the new time for the meeting :)16:00
DinaBelova#topic New time for the meeting16:00
DinaBelovaso we have several options16:01
DinaBelova16:00 UTC (current time, really tough) vs 15:30 UTC vs 17:30 UTC vs 18:00 UTC16:01
*** AugieMena has joined #openstack-performance16:01
rook1200 EST isn't great.... :)16:02
rooko/16:02
DinaBelovarook indeed16:02
DinaBelovafrom what I heard from people 30 minutes earlier (15:30 UTC) seems to be the best option for now16:02
rohanionhey everyone :)16:02
DinaBelovarohanion o/16:03
*** rcherrueau has joined #openstack-performance16:03
DinaBelova15:30 UTC (11:30 EST, 8:30 PST) is something I've heard from AugieMena and ad_rien_ and other Inria folks at least16:03
ad_rien_for French Inria Guys 15:30  UTC is a good choice -  (17:30 can be a second one)16:03
rook+1 to 153016:04
DinaBelovarook ack16:04
DinaBelovaI want to grad confirmation from klindgren - if at least he'll be able to attend from GoDaddy side on more or less weekly basis it'll be cool16:04
DinaBelovaI know that for harlowja it'll be too early :D16:05
DinaBelovaglad -> grab **16:05
DinaBelovaalthough these two are having right now a daily meeting ^^, so let's wait for their response later16:05
DinaBelova#info preliminary agreed on moving the meeting 30 minutes earlier on Tuesdays, 15:30 UTC (11:30 EST, 8:30 PST)16:06
DinaBelovarohanion am I right that for Moscow it'll be convenient as well?16:06
DinaBelovarohanion it'll be 18:3016:07
rohanionyeah, no problem16:07
rohanion18:30 RTZ-216:07
DinaBelovaok, cool, I suspected this, but wanted to collect the information16:07
*** bwallis has joined #openstack-performance16:07
DinaBelovaok, so I'll send a final update via email thread16:07
DinaBelovaso let's jump to the current progress on test plans16:08
DinaBelova#topic Current progress on the planned tests16:08
DinaBelovafrom Mirantis side we (finally) were able to move forward with labs configuration16:08
DinaBelovaour 200 nodes lab is under intensive Neutron testing for now (dataplane tests with huge enough number of Neutron objects and VMs)16:09
*** pcaruana has joined #openstack-performance16:09
DinaBelovaand it looks like we finally were able to filter all non-working nodes from 500 nodes lab, so we'll have 400+ nodes Openstack cluster (installed by MOS)16:10
DinaBelovaso we'll run http://docs.openstack.org/developer/performance-docs/test_plans/control_plane/plan.html against it16:10
DinaBelovahopefully this will start tomorrow16:10
rookMOS ?16:10
DinaBelovaMirantis OpenStack (way of deploying)16:10
rookAh MOS != Fuel ?16:11
DinaBelovarook yep :D16:11
DinaBelovaMOS includes OpenStack packages with more fixes and backports16:11
msimoninFrom inria side we made some progress on the 1000 nodes test plan16:11
DinaBelovathan usual stable/* usually have16:11
DinaBelovabut deployment tool itself is Fuel, yes16:11
DinaBelovamsimonin cool!16:12
DinaBelovaplease share some details16:12
msimoninbut …16:12
msimonin:)16:12
DinaBelova:D16:12
msimoninwe still have some performance issue when scaling with 500+ computes16:12
DinaBelovamsimonin you use fake computes?16:12
msimoninfor the record we are using a kolla based deployment16:12
luzCo/16:12
DinaBelovaluzC o/16:12
msimoninDinaBelova: yes fake drivers16:12
rookmsimonin: what sort of scaling issues? Control plane?16:13
DinaBelovamsimonin ok, so kolla + fake driver16:13
DinaBelovawhat kind of issues?16:13
luzChello Dina16:13
msimoninactually, let me share a document that we are maintaining16:13
DinaBelovamsimonin it'll be cool16:13
msimonin#link https://pad.inria.fr/p/FK18ZSyjFyLPITfE16:13
DinaBelovamsimonin ok, I see " very slow apis when using 500 computes"16:14
msimoninapis + mariadb are behind the haproxy16:14
msimoninyep16:14
msimoninthat's the issue16:14
rookthe issue is haproxy?16:14
DinaBelovadoes it relate to all OpenStack REST APIs?16:14
msimoninrook: maybe haproxy, but we need more insight16:15
DinaBelovamsimonin I suspect some parameters of HAproxy may influence here indeed on the performance, I'll agree with rook here16:16
msimoninyes it's my feeling too16:16
msimonindo you have some experience with haproxy ?16:16
DinaBelovamsimonin not too big sadly16:16
rookmsimonin do you know at what # of computes you start seeing the problem?16:16
msimonin100 computes is ok, 500 isn't16:17
rookwell you go 5x :)16:17
msimoninsure :)16:17
DinaBelovamsimonin I can suggest you to ping alwex (Alex Shaposhnikov) and try to discuss this with him, he may have some ideas16:17
msimonincool, I'll do that16:17
rookmsimonin we have a monitoring solution to help track down what might be slowing down16:17
rookusing collectd/graphite/grafana16:18
rookmight provide insight into the slowness or the possible culprit.16:18
msimoninactually we are using cadvisor/influx/grafana16:18
msimoninbut it just keep track of basics metrics16:18
DinaBelova#info Mirantis: Neutron testing on 200 nodes in progress, 400 nodes cluster almost installed for baseline performance testing16:18
DinaBelova#info Inria facing issues with 1000 nodes emulation experiment: https://pad.inria.fr/p/FK18ZSyjFyLPITfE16:19
rookmsimonin: sure, we break out per-process16:19
DinaBelovamsimonin I think you may try the same method rook is talking about + let's ask alwex to help16:20
DinaBelova#action DinaBelova msimonin alwex find out what's slowing down OpenStack REST APIs in the Inria 1000 nodes experiment16:20
msimoninrook: do you have what metrics can help tracking the issue ?16:21
msimonindo you know*16:21
ad_rien_Since we built our deployment framework on top of Kolla, we get the ha-proxy by default…. DinaBelova do you think it can be possible to see how you are deploying the different containers on your side ?16:21
ad_rien_For us it is not so complex/time consuming to redeploy a set of containers on top of G5K16:22
DinaBelovaad_rien_ I think that's possible, let's anyway communicate this with Alex as he was originating the experiment16:22
rookmsimonin: since it seems to be based on the # of computes... we could look at the msging services (rabbit?), haproxy, and possibly the individual nova services. since each of the compute nodes will be checking in on a interval.16:22
DinaBelovaad_rien_ fyi now we're playing with k8s and fuel-ccp (containeraized control plane) to see if we can use it for the experiments and testing16:22
msimoninrook: ack, rabbit may be the issue as well indeed16:23
rookmsimonin: honestly, it wouldn't shock me.16:23
rookmsimonin: what errors are you seeing?16:23
DinaBelovaad_rien_ although I believe HAproxy is either not an issue at all or this can be fixed even without redeployment16:23
msimoninrook: WARNING nova.openstack.common.loopingcall [-] task <bound method DbDriver._report_state of <nova.servicegroup.drivers.db.DbDriver object at 0x7f454c8db710>> run outlasted interval16:24
msimoninin the nova-compute.lgo16:24
rookyeah - could be msging for sure.16:24
msimoninyes16:24
DinaBelovamsimonin so let's check this option as well16:25
* rook isn't familiar with your control-plane setup16:25
ad_rien_DinaBelova:  actually to be fair with your experiments, we should remove it…. ok let's see whether we can fix that point by discussing with Alex.16:25
DinaBelovaad_rien_ ack16:25
ad_rien_(to be faire, i.e. to provide fair comparisons)16:25
DinaBelovaad_rien_ msimonin I'll start separated email thread with Alex16:26
msimoninDinaBelova: ack16:26
ad_rien_DinaBelova:  ack thanks16:26
DinaBelovait looks like we may proceed for now16:26
rcherrueauDinaBelova: could you also put me in CC16:26
DinaBelovarcherrueau sure16:26
rcherrueauthanks16:26
DinaBelovaok, so let's jump to the OSprofiler16:26
DinaBelova#topic OSProfiler weekly update16:27
DinaBelovarohanion aignatev - the floor is yours16:27
aignatevneed review for https://review.openstack.org/#/c/340936/16:27
aignatevother than that I'm not currently working with osprofiler, so no updates16:27
rohanionok, will look at it today16:27
aignatevthanks!16:28
*** msimonin has quit IRC16:28
DinaBelovaaignatev I'll take a look as well, thanks16:28
aignatevthank you16:28
DinaBelovarohanion any updates from your side?16:28
rohanionyep, writing :)16:28
rohanionI'm working on enabling osprofiler in Fuel. basically I have to code a PoC that updates configuration and reloads the services.16:28
rohanionthis PoC will be turned into a Fuel plugin16:29
rohanionAlso I'm thinking about a set of profiling scenarios with single entry-point and results in table format.16:29
DinaBelovarohanion I believe you found out that's a bit overkill solution?16:29
DinaBelovaI mean fule plugin?16:29
DinaBelovafuel*16:29
rohanionyes, a little. but still it will be a good option to set all the needed variables in a nice UI16:30
DinaBelovaor you decided it's not too difficult to develop this profiling plugin?16:30
DinaBelovarohanion ack16:31
rohanionit will be tough but I think I'll handle that.16:31
rookbummer, will it be written to only work with Fuel?16:31
rooknot OOO?16:31
rohanionno updates regarding osprofiler itself16:31
rohanionrook, no16:31
rookno to only Fuel ?16:32
rohanionthe script will work with vanilla openstack16:32
rookah ha cool16:32
DinaBelovarook it's just way for us to deploy it automatically using fuel, but it workd with any OpenStack and is automated to be used with devtack16:32
rohanionthe plugin will just launch this script, sending all necessary parameters16:32
rookcool rohanion - have a link to this work16:32
*** AugieMena has quit IRC16:33
DinaBelovaok, rohanion is this all for now?16:33
rohanionI'll publish the changes as soon as I write the code :)16:33
rohanionyes, that's everything16:33
DinaBelovaok, cool16:33
DinaBelovaso we may jump to open discussion :)16:34
DinaBelova#topic Open Discussion16:34
DinaBelovaanything else to share?16:34
rcherrueauWe really want to contribute to the performance documentation16:35
DinaBelovarcherrueau you're really welcome :)16:35
rcherrueaudo you think it's possible16:35
DinaBelovarcherrueau of course :)16:35
DinaBelovathat's usual enough contribution process16:35
DinaBelovato the repository16:35
rcherrueaufor instance, do you think it's possible to add a specific subsection in the labs section with information about our grid?16:35
DinaBelova#link https://github.com/openstack/performance-docs16:35
DinaBelovarcherrueau for sure16:35
DinaBelovato have all info shared16:36
rcherrueaucool16:36
DinaBelovaand you'll mention this lab in the test plans/test results16:36
rcherrueaupleaze what is the process to do so16:36
DinaBelovarcherrueau you need to upload several commits16:36
DinaBelovacommit #1 - regarding the lab description16:36
DinaBelovalemme find an example16:37
rcherrueauyes thanks16:37
DinaBelovarcherrueau like this https://review.openstack.org/#/c/292835/16:37
DinaBelovabut regarding your lab16:37
ad_rien_ok DinaBelova I think we got the information we were looking for16:37
rcherrueauok thank you DinaBelova16:38
DinaBelovaand second one with your results, as you're going to use the same test plan as we did16:38
DinaBelovarcherrueau https://review.openstack.org/#/c/324806/ - test results part16:38
ad_rien_yes modulo the way we perform(ed) the experiments16:38
DinaBelovaad_rien_ indeed16:38
DinaBelovathe overall documentation is free form, the only rule is to set test plans regarding the template  https://github.com/openstack/performance-docs/blob/master/doc/source/test_plans/template.rst16:39
DinaBelovabut you're not going to propose your own test plan :)16:39
DinaBelovaso feel free to skip my last message :)16:39
ad_rien_ok we gonna give a look16:39
rcherrueauOK great, that's all for us.16:40
DinaBelovaad_rien_ sure, will take a look with great pleasure :)16:40
DinaBelovaanything else here? from my side I have nothing more to share16:40
ad_rien_not sure whether it will be done for the next week as right now we are focusing on kolla related issues but once we get relevant results we will commit them16:41
DinaBelovaad_rien_ ack, thanks for the update16:41
DinaBelovaok, it looks like we're done for now16:41
DinaBelovaplease wait the meeting time update email16:41
DinaBelovaI think we'll stop with 15:30 UTC16:42
DinaBelovathanks folks for coming and participation16:42
DinaBelovasee you16:42
DinaBelova#endmeeting16:42
openstackMeeting ended Tue Aug 23 16:42:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/performance_team/2016/performance_team.2016-08-23-16.00.html16:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/performance_team/2016/performance_team.2016-08-23-16.00.txt16:42
openstackLog:            http://eavesdrop.openstack.org/meetings/performance_team/2016/performance_team.2016-08-23-16.00.log.html16:42
*** rohanion has quit IRC16:47
*** aignatev has quit IRC16:52
*** Guest25180 is now known as med_17:06
*** med_ has joined #openstack-performance17:06
*** med_ is now known as medberry17:06
*** medberry is now known as med_17:06
*** ilyashakhat has joined #openstack-performance17:14
*** rcherrueau has quit IRC17:16
*** hieulq_ has quit IRC17:20
*** ilyashakhat has quit IRC17:21
*** ad_rien_ has quit IRC17:25
*** hockeynut has quit IRC17:33
*** bwallis has quit IRC17:36
*** ilyashakhat has joined #openstack-performance17:39
*** ilyashakhat has quit IRC17:40
*** ilyashakhat has joined #openstack-performance17:40
*** dimtruck is now known as zz_dimtruck17:59
*** zz_dimtruck is now known as dimtruck18:01
*** ilyashakhat has quit IRC18:07
*** hockeynut has joined #openstack-performance18:13
*** ilyashakhat has joined #openstack-performance18:36
*** ilyashakhat has quit IRC18:57
*** markvoelker has joined #openstack-performance18:58
*** markvoelker has quit IRC19:01
*** pcaruana has quit IRC19:20
*** hockeynut has quit IRC19:28
*** bvanhav has quit IRC19:31
*** ad_rien_ has joined #openstack-performance19:46
*** msimonin has joined #openstack-performance19:55
*** markvoelker has joined #openstack-performance19:57
*** ad_rien_ has quit IRC20:06
*** ilyashakhat has joined #openstack-performance20:07
*** hockeynut has joined #openstack-performance20:27
*** ad_rien_ has joined #openstack-performance20:38
*** markvoelker has quit IRC20:52
*** ilyashakhat has quit IRC20:53
*** rfolco has quit IRC21:01
*** dimtruck is now known as zz_dimtruck21:21
*** zz_dimtruck is now known as dimtruck21:23
*** hockeynut has quit IRC21:31
*** ad_rien_ has quit IRC21:49
*** AnarchyAo has joined #openstack-performance22:22
*** dimtruck is now known as zz_dimtruck22:30
*** msimonin has quit IRC22:53
*** eandersson_ has joined #openstack-performance23:40
*** eandersson has quit IRC23:43
*** AnarchyAo has quit IRC23:59

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