16:59:30 #startmeeting Rally 16:59:31 Meeting started Tue Sep 2 16:59:30 2014 UTC and is due to finish in 60 minutes. The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:59:35 The meeting name has been set to 'rally' 16:59:58 olkonami andreykurilin_ marcoemorais RainbowBastion coolsvap hi guys 17:00:10 hi there 17:00:50 hi! 17:01:57 let's wait a bit for others 17:02:23 ok:) 17:02:25 hi! 17:03:40 msdubov oh hi there 17:04:36 harlowja hi there 17:04:51 boris-42 yo yo 17:04:51 sup dawg 17:05:08 okay i think we can start 17:05:44 hi 17:06:48 #topic @Validation refactoring 17:07:13 Okay yesterday we merged quite big patch 17:07:15 https://review.openstack.org/#/c/111989/7 17:07:26 that fixes tons of bugs & improves usability of validation 17:07:27 woot 17:07:45 #topic Benchmarking with already existing users 17:07:53 me and RainbowBastion are working on this topic 17:08:06 feature request is https://github.com/stackforge/rally/blob/master/doc/feature_request/LDAP_support.rst 17:08:11 and there are 2 patches on reviwe 17:08:40 https://review.openstack.org/#/c/117302/ 17:08:41 this and 17:08:46 https://review.openstack.org/#/c/116766/ 17:08:50 it's just first part 17:09:12 that will allow to extend deployments (to make them contain as well users) 17:09:39 after that we will need to rework a bit benchmark.engine and probably create (existing_users context) 17:09:45 and that's all 17:09:55 so we are quite close to this finishing this task 17:10:05 any questions? 17:10:48 I just need to fix up some the test_engine unit tests in order for it to pass Jenkins and it should be done on my end. 17:11:20 Shouldn't one of those patches be "needed" by the other? 17:11:50 msdubov not they are quite independent 17:12:03 boris-42 Okay just to make sure 17:12:04 RainbowBastion actually you'll need to do a bit more cleanup 17:12:40 boris-42 okay, we can discuss that after the meeting 17:12:50 RainbowBastion ya I'll left some comments 17:13:08 RainbowBastion actually it's very simple (you just don't need to initialize with users scenario runner) 17:13:29 RainbowBastion https://github.com/stackforge/rally/blob/master/rally/benchmark/runners/base.py#L157 17:13:35 RainbowBastion you don't need endpoints anybmore 17:14:20 okay let's move to next topic 17:14:46 #topic Refactoring ReadTheDocs 17:14:56 msdubov could you provide some details why and what we are going to do 17:15:41 First, we want to make the docs much simpler to get through for newcomers 17:15:43 rook here =) 17:15:58 To achieve that, we've analyzed what different groups of users might wish to see here 17:16:00 rook hi there 17:16:14 And also boris-42 and me had a discussion on how to organize the contents of these docs 17:16:24 msdubov could you share documents? 17:16:29 The core of these new docs will be a kind of tutorial though rally 17:16:35 boris-42 just a moment 17:17:42 Here is the description of different user groups and of what they expect to find in our docs https://docs.google.com/a/mirantis.com/document/d/18wmAZA5_qC1PuQsHOTDVBnVS9VSi0hAdjIJ9EI5-z58/edit 17:18:04 Below, you can find a high-level structure of the docs. 17:18:32 So, the "Install & Use" section will guide the user through Rally with a series of lessons on how to use it 17:18:43 They will get more complicated as the user reads further 17:19:00 And also these tutorials hopefully will be the basics for the upcoming videos 17:19:29 So I expect to have the first version to share and to discuss till the end of this week 17:19:50 Another point is that we'll remove all the stuff from our WIki 17:20:09 So ReadTheDocs will be the only centralized place to find all relevant infos 17:22:32 msdubov great 17:22:35 msdubov thanks for update 17:22:46 Does anybody want to help msdubov to provide better docs? 17:22:50 RainbowBastion ?^ 17:23:55 boris-42 Yeah, I'll work on it after I finish my prior refactoring 17:25:03 RainbowBastion, be sure to contact me at any time 17:26:18 msdubov RainbowBastion so actually you can collaborate on that google docs 17:26:29 msdubov I'll let you know when I finish up the refactoring. 17:26:34 great 17:26:39 okay let's move on next topic 17:26:40 Could I get a link to the Google docs? 17:26:55 RainbowBastion, https://docs.google.com/a/mirantis.com/document/d/18wmAZA5_qC1PuQsHOTDVBnVS9VSi0hAdjIJ9EI5-z58/edit 17:27:47 msdubov Thanks! 17:28:02 okay next topic 17:28:09 #topic Week of CLI improvments 17:28:28 The idea is that CLI should and can be better much better 17:28:48 *) Auto completion 17:29:25 *) rally info / rally deployment / rally task / rally validation 17:29:45 should show by default Information about this command 17:30:10 *) Any command with wrong or missing arguments should show more user friendly message 17:30:25 *) Some unification between commands are required 17:30:32 *) Writing missing tests 17:30:56 boris-42: do you mean cli functional tests? 17:31:16 rediskin I was talking about unit tests at that point 17:31:24 *) Writing functional tests for CLI 17:31:47 so and other stuff 17:31:56 RainbowBastion rediskin rook andreykurilin_ ^ 17:32:01 olkonami ^ 17:32:39 Gamekiller77 ping* 17:32:43 * boris-42 Gamekiller77 we are here 17:33:01 so any thoughts? 17:33:24 yes just got back from PTO so doing work stuff 17:33:29 while i haven't had many problems with the CLI with Rally - the one thing that bugs me is rally task results vs rally task detailed ... I feel like those are backwards, Results should be the pretty output, where detailed should be the JSON 17:33:51 just a nit pick 17:34:13 rook no any nit pick will be important next week 17:34:48 rook so I know Rally CLI is consumable (but It's far from that I can say nice CLI) 17:34:51 like "git" has 17:37:44 Okay any questions? 17:37:51 any thoughts? 17:38:07 boris-42, maybe we should create some document in google docs with all nits related to cli? 17:38:16 andreykurilin_ going to that 17:39:43 andreykurilin_ rook Gamekiller77 https://docs.google.com/a/mirantis.com/document/d/1iZa9V8C3Z09JTC3x2MGpBq-FEszwRmVCYoxCbN1zHgo/edit 17:39:49 RainbowBastion rediskin ^ 17:40:07 good) 17:40:20 trello? 17:40:25 rediskin what about trello? 17:40:34 rediskin we need to make document first 17:40:39 ok 17:40:39 rediskin like brainstorm 17:40:51 rediskin probably first day of next week 17:41:06 rediskin, it seems to me, we should use documents for discussion and than move tasks to trello 17:41:41 imo trello+irc much better 17:42:04 or whatever+irc 17:42:52 andreykurilin_ +1 17:43:00 rediskin first document and then trello 17:43:04 rediskin as a result 17:43:11 rediskin of brainstorm 17:44:47 #topic Generic cleanup 17:44:57 rediskin could you share some information about your work? 17:45:41 I still waiting on review and finishing tests https://review.openstack.org/#/c/116269/ 17:46:56 rediskin boris-42, i will have more free time for review after thursday 17:46:57 boris-42: ^ 17:47:04 rediskin soo 17:47:18 rediskin imho you should provide commit message 17:47:29 rediskin that describes what you've done 17:47:54 boris-42: ok 17:48:47 rediskin I'll try to understand your pach=) 17:48:53 #topic Plugins 17:49:03 olkonami what are you working on? 17:51:56 olkonami around? 17:54:46 hi, yes 17:55:08 I am fixing last comments now 17:56:09 olkonami, link 17:56:14 please) 17:56:40 https://review.openstack.org/#/c/103145/ 17:56:51 olkonami so now plugins are for everything? 17:56:56 olkonami not only scenarios ? 17:57:30 yes 17:57:39 olkonami okay I'll review that patch 17:57:48 okay it's quite close to the end of this meeting 17:58:02 so let's continue in rally chat if somebody has something to ask 17:58:06 #endmeeting