14:02:34 #startmeeting Rally 14:02:35 Meeting started Mon Apr 11 14:02:34 2016 UTC and is due to finish in 60 minutes. The chair is andreykurilin__. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:38 The meeting name has been set to 'rally' 14:03:45 o/ 14:04:23 hi there 14:04:47 amaretskiy rvasilets : ping 14:04:51 hi 14:05:01 looks like our agenda is empty 14:05:05 yeah 14:05:17 and there is no a lot of attendies 14:05:29 but we have something to discuss 14:05:35 so we'll be quick )) 14:05:36 at least one topic:) 14:05:42 amaretskiy 14:06:21 let's talk about term "workload" which appears in two different meanings 14:06:29 so this becomes confusing 14:06:35 ok 14:06:51 i got some input on that 14:07:01 #topic Term "workload" 14:07:21 'cos I kinda was close to birth of the term 14:07:26 1st occurrence is plugins directory https://github.com/openstack/rally/tree/master/rally/plugins/workload 14:08:00 2nd is a new name of scenario in our new task format https://github.com/openstack/rally/blob/master/doc/specs/in-progress/new_rally_input_task_format.rst 14:08:19 amaretskiy: let me clarify on that ^^ 14:08:20 this is really confusing 14:08:43 in our new task format, we will call scenario "workload" 14:08:50 nope)) 14:08:59 we won't 14:09:09 task/subtasks/workloads 14:09:14 yep 14:09:17 here is the structure^ 14:09:23 but it's not a scenario) 14:09:29 butrecently we have a dir in plugins 14:09:33 named "workloads" 14:09:52 workload 14:10:35 this dir is for plugins related to VM load scripts 14:10:44 I propose to rename this dir 14:11:04 find new term, like vmload, vmperf, etc..... 14:11:21 something that differ from "workload" 14:11:28 any ideas? 14:11:47 vmworkload 14:11:57 +1 14:12:02 looks good 14:12:09 so it differs from Rally workload 14:12:12 but too long :) 14:12:30 r we gonna to use it often? 14:12:40 shakers :) 14:12:54 ? 14:12:54 cos it's long but more or less self-explaning 14:13:22 shaker will get deprecatred earlier or later imo 14:14:01 just rename workload->shaker :) 14:14:11 why shaker? 14:14:25 boris-42 gonna love it)) 14:14:50 just remember about project that does something similar 14:14:50 he's a big cocktail enthusiast 14:15:21 https://github.com/openstack/shaker 14:15:40 it's only one project, I believe our stuff is multy-purpose) 14:15:44 amaretskiy: as far as I understand shaker is only about network workloads 14:16:16 I propose just name for the dir 14:16:31 okay, any other ideas, start voting? 14:17:39 +1 for vmworkload ) 14:19:36 maybe create google form and get opinions from most team members? 14:19:55 start mail thread.. 14:20:08 Hi 14:20:10 announce preliminary meeting 14:20:21 than actual meeting)) 14:20:41 maybe we'll just go with voting right now? )) 14:20:47 hi rvasilets 14:20:48 ikhudoshyn: i think we need opinion from redixin and boris-42 14:21:05 amaretskiy: that's true 14:21:38 but if we're looking for the voice of the two, google form seems a bit redundant for me)) 14:21:50 why just don't ask them? 14:22:04 amaretskiy: -1 for google form:) 14:22:08 (yep I noticed that they both are absent today))) 14:22:10 how to collect votes/ another ideas? 14:22:47 amaretskiy: try starting with tellyng your own vote)) 14:23:04 rvasilets: join us) 14:23:06 idea to create the patch with propose) 14:23:19 I would vote for vmload, vmperf, shaker (all get +) 14:23:42 vmworkload - good but too long 14:23:57 so by far +2 for vmworkload, +1 for vmload, +1 vmperf, +1 shaker)) 14:23:57 crossload 14:24:19 rvasilets: pls elaborate 14:24:28 vmio ? 14:24:33 -1 for shaker and vmperf 14:24:41 is it really 'cross' 14:24:52 is it really only for 'io' 14:24:53 +1 for vmload and crossload 14:25:30 the idea with crossload is similar as in crosstraining term 14:25:34 so we got +2 for vmworkload and +2 for vmload 14:25:38 andreykurilin__: your vote..... ? 14:25:50 what we have to do is just ask redixin and boris-42 14:26:20 andreykurilin__: was for vmworkload 14:26:27 :) 14:26:52 chris also is absent 14:26:55 amareskiy: please, start a mailing thread about this new entity 14:27:11 it would be good tohave his vote too 14:27:15 ["sarcasm"] ? 14:27:21 andreykurilin__: ok, let it be mail list 14:27:25 andreykurilin__: ^^ 14:27:32 ikhudoshyn: no 14:27:37 let it be, let it be...(song) 14:27:38 ok 14:27:55 letter 'b', letter 'b'... (song) 14:27:59 it would be nice if community will know everything about our new stuff 14:29:36 agreed, let the mail-thread begins.. 14:29:44 ok, so there is one more topic 14:29:44 anything else to discuss? 14:30:05 it relates to this previous one 14:30:34 #topic Rally glossary 14:30:37 #link https://review.openstack.org/#/c/266389/ 14:30:50 we should start working on our glossary as soon as possible 14:31:03 ok 14:31:08 i will look at it 14:31:09 andreykurilin__: I will submit a patch set soon 14:31:37 rvasilets: it doesn't include a lot of terms yet 14:32:35 ikhudoshyn: since you are familiar with new rally task format, please add some terms there 14:32:49 not really constructive, but usually Glossary is put closer to the end of TOC 14:32:57 andreykurilin__: will do 14:33:15 and our native speaker chris also welcome there=) 14:33:24 andreykurilin__: ikhudoshyn: I will add terms in new patch, but need to discuss their definitions 14:33:38 ok 14:33:55 thanks 14:34:06 that is all from my side 14:34:11 anything else to discuss? 14:34:35 nothing from me) 14:34:58 ok 14:35:05 #endmeeting