17:08:29 <boris-42> #startmeeting Rally
17:08:30 <openstack> Meeting started Tue Jul  1 17:08:29 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:08:30 <oanufriev> hi
17:08:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:08:33 <openstack> The meeting name has been set to 'rally'
17:08:36 <boris-42> olkonami
17:08:37 <boris-42> hi
17:08:40 <boris-42> rediskin
17:08:43 <olkonami> hi
17:08:46 <rediskin> hi
17:10:17 <boris-42> Okay let's just start discusssion
17:10:23 <boris-42> #topic stress runner
17:10:28 <boris-42> olkonami pls go on
17:11:10 <olkonami> I'll send new patchset with fixed comments in a few minutes
17:11:51 <boris-42> olkonami anything to discuss?
17:12:13 <olkonami> yes, my questions from rally chat
17:12:28 <olkonami> I think it's better to specify "max_failure_rate" in percents. It will be more clear and it is done so in sla patch. Are you agree? Also about this parameter name, it is better to indicate that it is associated with a stop and that it is different from sla "max_failure_percent". May be something like "stop_failure_percent", what do you think?
17:14:21 <boris-42> olkonami stop_on_failure_percent
17:14:56 <boris-42> olkonami probably )
17:15:24 <boris-42> olkonami btw
17:15:34 <boris-42> olkonami ah no
17:16:04 <boris-42> olkonami so how user will setup?
17:16:09 <boris-42> olkonami 0.10 ?
17:16:13 <boris-42> olkonami or "10"
17:16:19 <boris-42> olkonami or "10%" ?
17:16:34 <olkonami> I think 10
17:16:42 <olkonami> will be more clear
17:17:08 <boris-42> olkonami I don't have strong opinion on that
17:17:14 <boris-42> olkonami so I'll be ok with both
17:17:33 <olkonami> that it is percents shold be specified in parameter name
17:17:48 <olkonami> or what do you mean?
17:17:49 <boris-42> olkonami ok
17:18:02 <boris-42> olkonami hm no I am ok with 10
17:18:19 <boris-42> olkonami and stop_on_failure_precent: x
17:18:53 <boris-42> Okay so let's move
17:18:58 <boris-42> #topic RPS runner
17:19:03 <boris-42> oanufriev hey there
17:19:09 <boris-42> oanufriev any update?
17:19:11 <oanufriev> yo!
17:19:21 <rediskin> \o
17:19:41 <oanufriev> i sent the patch for review and got -1.
17:20:02 <oanufriev> have a question about one comment
17:20:17 <oanufriev> https://review.openstack.org/#/c/102363/6/rally/benchmark/runners/rps.py,cm
17:20:28 <oanufriev> here it is - the second-one
17:21:40 <oanufriev> should i reuse implementation from glance?
17:22:16 <boris-42> oanufriev ?
17:22:37 <boris-42> oanufriev what implementation?
17:23:17 <oanufriev> implementation of rate limitting of requests
17:23:24 <boris-42> oanufriev I am not sure
17:23:33 <boris-42> oanufriev actually I am sure that we shouldn't use this
17:23:43 <boris-42> oanufriev we don't need speed limit
17:24:01 <oanufriev> ok. got it
17:24:19 <boris-42> oanufriev olkonami I will try to find time to review your patches
17:24:31 <boris-42> oanufriev olkonami sorry currently I am quite busy with osprofiler
17:24:36 <boris-42> #topic SLA
17:24:43 <boris-42> rediskin so is it finish finally?
17:25:12 <rediskin> boris-42: this patch got +2, so i think it quite ready
17:25:19 <rediskin> https://review.openstack.org/#/c/98158/
17:25:21 <boris-42> rediskin okay I'll take a look
17:25:27 <boris-42> rediskin what about functional tests ?
17:25:33 <boris-42> #topic func tests
17:25:36 <rediskin> but there is a lots of criteria to be added
17:26:08 <boris-42> rediskin for example?
17:26:46 <rediskin> only two criteria done, and i believe it is not enough
17:27:03 <rediskin> people will want more criterio =)
17:27:04 <boris-42> rediskin any examples?
17:27:17 <rediskin> maximum time per specific atomic action
17:27:33 <boris-42> rediskin ouh ok
17:27:35 <boris-42> rediskin yep
17:27:45 <boris-42> rediskin zoo okay we will work on that
17:27:59 <boris-42> rediskin so what about function tests in rally-cli job?
17:28:27 <rediskin> it finally works
17:28:46 <boris-42> rediskin so we can result script that made k4no
17:28:52 <rediskin> you can see results in comments for this patch https://review.openstack.org/#/c/102899/
17:28:52 <boris-42> rediskin to display results btw
17:29:02 <rediskin> job called check-rally-dsvm-cli
17:29:19 <boris-42> rediskin where is HTML??
17:29:24 <boris-42> =)
17:29:38 <rediskin> no html yet
17:30:08 <boris-42> rediskin so you can rest from tempest in future
17:30:11 <rediskin> i focused around helper methods for tests
17:30:15 <rediskin> and tests itself
17:30:19 <boris-42> rediskin okay I will review it
17:35:23 <boris-42> #topic open discussion
17:35:31 <boris-42> so do we have anything to discssu?
17:35:36 <boris-42> discuss? )
17:36:50 <boris-42> so seems like we can end it=)
17:36:53 <boris-42> woohoo=)
17:40:42 <rediskin> oh
17:40:55 <rediskin> https://review.openstack.org/#/c/103706/
17:41:56 <rediskin> -3k lines =)
17:52:11 <boris-42> #endmeeting