17:10:05 #startmeeting rally 17:10:06 Meeting started Tue Oct 14 17:10:05 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:10:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:10:10 The meeting name has been set to 'rally' 17:10:11 boris-42: Error: Can't start another meeting, one is in progress. Use #endmeeting first. 17:10:16 andreykurilin_ hi 17:10:18 rediskin hi 17:10:20 msdubov hi 17:10:20 Hi 17:11:09 hi 17:11:10 ) 17:11:11 hi 17:13:35 hi 17:13:57 amaretskiy rediskin msdubov andreykurilin_ hi guys 17:14:02 so 17:14:19 #topic new design of rally report 17:14:26 amaretskiy could you share a bit info 17:14:31 amaretskiy about your work 17:14:54 I've completely reworked HTML report 17:15:48 now we have report with responsive layout (bootstrap framework) and powered by AngularJS 17:15:58 menus, tabs, etc... 17:16:10 and I'm continuing this work... 17:16:27 amaretskiy share some link for new people 17:17:09 http://logs.openstack.org/19/125119/14/gate/gate-rally-dsvm-rally/1a2e582/rally-plot/results.html.gz 17:17:33 amaretskiy ya looks really nice 17:17:42 thanks :) 17:18:03 cool 17:18:03 our operators will like it rmk mux ^ =) 17:18:27 amaretskiy so okay let's move to next topic 17:18:41 #topic future plans for rally task report 17:18:44 amaretskiy so 17:18:52 amaretskiy what you are going to add to it as next steps ? 17:19:22 very cool 17:19:40 I'm planning to add tabs for scenario output data (if any) and for raised exceptions (if any) 17:20:07 plus a lot of small changes 17:20:21 rmk this is just first step=) 17:21:57 amaretskiy what about putting description on graphs and benchmarks 17:22:09 amaretskiy like now it's not clear what actually and how we are benchmarking 17:22:15 yes, that is a topic of next patch 17:22:23 amaretskiy so you are going to use doc strings? 17:22:34 amaretskiy basically we will need to put them to rally results 17:22:44 yes, scenario docstrings will be displayed 17:23:15 amaretskiy so maybe something like "info" tab? 17:23:33 so you can read description about what was actually run? 17:24:10 maybe rename "config" into "info" and include description 17:24:46 I guess we can put both description and scenario config in the same tab 17:25:16 or just put the description behind the tabs 17:26:22 scenario docstring should be saved in the database 17:27:05 amaretskiy ya 17:27:10 amaretskiy together with taskrestuls 17:27:15 yes 17:27:17 amaretskiy let me help you with this part 17:27:25 amaretskiy cause I am refactoring that part currently 17:28:04 okay let's move to next stuff 17:28:09 #rally task info updates 17:28:17 msdubov please provide some updates 17:31:59 msdubov around?) 17:32:35 boris-42 yep 17:33:05 msdubov_ so 17:33:25 msdubov_ do you have something to say about rally task info command? 17:33:47 rally info now supports typos handling 17:34:12 e.g. you type "ExistingServer" and it suggests "ExistingServers" 17:34:27 also "Nova"->"NovaServers" 17:34:44 So it also works as a kind of autocompletion me 17:34:50 chanism 17:35:09 nownI'm concerned with covering Rally with docstrings 17:35:29 msdubov_ hm wait a bit 17:35:30 and also simplifying the rally info syntax quite a bit 17:35:34 msdubov_ what about LIST command ? 17:35:47 msdubov_ as well when I type rally info find NovaServers 17:35:56 msdubov_ it doesn't display methods from it 17:36:04 msdubov_ so it's hard to use for now 17:36:14 boris-42 i know 17:36:23 msdubov_ maybe we should concentrate on functionality ? and then on docstirngs? 17:36:31 it is partially implemented in one of my commits on review 17:36:40 boris-42 agree 17:36:56 msdubov_ what about having command "rally info" 17:37:02 msdubov_ without list/query 17:37:17 msdubov_ just make it like bash-competition and version commands? 17:37:20 that's syntax simplification I mentioned above 17:37:48 I also want to make it like you describe 17:41:36 msdubov_ where? 17:41:36 msdubov_ ah see 17:41:36 msdubov_ okay when you are expecting to finish it? 17:41:38 msdubov_ ? 17:41:40 okay moving to next topic 17:41:41 #topic changes in Rally CI 17:42:21 gate-rally-dsvm-cli - is going to be voting + in gates 17:42:27 as it works quite stable 17:42:50 https://review.openstack.org/#/c/128246/ 17:42:53 here is patch 17:43:00 We added as well new job 17:43:22 called gate-rally-tox-self 17:43:30 This job will be used to run Dummy scenarios 17:43:40 and test actually Rally 17:43:48 so there won't be devstack cloud 17:44:10 and we will use Dummy scenarios so we will be able to test a lot of for 25 mintues 17:44:10 boris-42 Certainly this week, sorry for missing your message! 17:44:22 msdubov_ ok 17:44:33 msdubov_ then I will wait with first release 17:44:41 so we are going to test everything 17:44:45 1) All runners 17:44:56 2) Exceptions in any place of scenarios 17:44:59 3) Timeouts 17:45:06 4) Exceptions in context 17:45:20 5) Maybe even new cleanup mechanism 17:45:32 6) Test it at large scale like 200k iterations 17:45:43 7) Test it at high load 500rps 17:45:47 boris-42, Rally will be used for testing Rally? http://i0.kym-cdn.com/photos/images/original/000/531/557/a88.jpg 17:45:48 and so on 17:45:57 :) 17:46:01 andreykurilin_ ggg 17:46:08 andreykurilin_ actually it is not rally for rally 17:46:20 andreykurilin_ we are just running special task that test it=) 17:46:59 so this will be actually nice improvement in our functional testing stuff 17:47:09 okay let's move to next topic 17:47:18 #topic Cleanup refactoring 17:47:20 boris-42, thanks for the clarification 17:47:34 I am finishing work on patch that rewrites from scratch cleanups 17:47:42 and makes them much better and safe 17:47:46 1) retries 17:47:50 2) speed limitation 17:48:00 3) simple way to add new resources to cleanup 17:48:19 4) better & unfired logging of failures 17:48:28 so much much better then we have now 17:48:39 so we will cover almost everything 17:48:57 from this #link https://github.com/stackforge/rally/blob/master/doc/feature_request/production_ready_cleanup.rst 17:49:12 everything except Disaster cleanup 17:49:16 that will be some of future steps 17:49:41 Any questions about this? 17:50:19 when you want to finish this task?) 17:50:23 boris-42 ^ 17:50:53 seems like no questions =) 17:50:53 #topic free discussions 17:50:53 andreykurilin_ I hope tonight =) 17:50:54 andreykurilin_ docstrings & code are mostly done 17:50:56 andreykurilin_ I need to write unit tests 17:53:52 boris-42, I updated the spec to openstack-qa today:) 17:54:03 andreykurilin_ that's grate 17:54:07 mtreinish ^ 17:54:11 dkranz 17:54:19 sorry guys for big delay in that stuff 17:54:30 a slight delay)) 17:54:39 sorry 17:54:39 andreykurilin_ I will try to review it tomrrorw 17:54:47 thx 17:55:08 boris-42, now I have enough time for it 17:55:23 andreykurilin_ I hope you'll have enough time to implement it as well 17:55:32 andreykurilin_ so we will be able to move from rally tempest.conf gerenation 17:55:52 boris-42, yeap 17:56:25 andreykurilin_ nice 17:56:32 boris-42, what about our first release? 17:56:38 oh 17:56:41 #topic release 17:56:53 I am going to start cutting release every two weeks 17:57:19 so our first release should be 0.0.1 during this week 17:57:38 andreykurilin_ actually I would like to finish cleanup stuff + get merged msdubov patch 17:57:47 andreykurilin_ before cutting it 17:58:08 yeah, our first release should be stable enough :) 17:58:30 and contain a lot of useful stuff 17:59:08 I agreed with you, lets wait for newest cleanup and msdubov patch 17:59:24 okay we need to finish this meeting 17:59:29 #endmeeting