14:06:08 <andreykurilin> #startmeeting Rally
14:06:08 <openstack> Meeting started Mon Mar 14 14:06:08 2016 UTC and is due to finish in 60 minutes.  The chair is andreykurilin. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:06:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:06:12 <openstack> The meeting name has been set to 'rally'
14:06:17 <amaretskiy> o/
14:06:46 <andreykurilin> \o
14:08:14 <ikhudoshyn> 0/
14:08:56 <andreykurilin> redixin: ping
14:09:01 <redixin> sup
14:09:21 <andreykurilin> stpierre: ping
14:09:43 <boris-42> hi hi
14:09:51 <andreykurilin> boris-42: good morning:)
14:10:38 <andreykurilin> lets start from the news
14:10:55 <andreykurilin> today we release new version of Rally - 0.3.2
14:11:07 <andreykurilin> *we released
14:11:15 <boris-42> andreykurilin: great
14:11:58 <andreykurilin> lets schedule the next release date
14:12:12 <andreykurilin> what about 28.03 ?
14:12:18 <boris-42> andreykurilin: let's keep schedule
14:12:31 <andreykurilin> boris-42: 3/18 ?
14:12:38 <andreykurilin> in 4 days new release
14:12:42 <redixin> +1
14:12:45 <boris-42> andreykurilin: maybe we can just move to the mnday
14:12:53 <andreykurilin> ok, it would be nice
14:12:55 <boris-42> andreykurilin: and move all other
14:13:03 <andreykurilin> monday is much better than friday
14:13:04 <andreykurilin> lol
14:13:04 <andreykurilin> :)
14:13:14 <boris-42> andreykurilin: so add +3 days to google doc page
14:13:34 <andreykurilin> boris-42: done
14:13:38 <redixin> so next release will be at March 21?
14:13:41 <andreykurilin> yes
14:13:47 <redixin> good
14:14:10 <rvasilets> Hi
14:14:56 <andreykurilin> rvasilets: hi
14:15:06 <andreykurilin> it looks like we done with topic about releases
14:15:27 <andreykurilin> I don't have more topics:)
14:16:33 <amaretskiy> boris-42 has proposed recently to discuss design of new scenario class
14:18:12 <boris-42> amaretskiy: yep
14:18:24 <boris-42> andreykurilin: can you start topic?
14:18:31 <amaretskiy> sure
14:18:39 <andreykurilin> #topic design of new scenario class
14:18:56 <amaretskiy> the idea is having new scenario class
14:19:27 <amaretskiy> which will represent the scenario itself (in opposite to current implementation where the scenario is actually a method)
14:19:54 <boris-42> amaretskiy: yep so we will basically have interface for scenarios which will be actually just method "run" that should be implemented
14:20:24 <boris-42> amaretskiy: and all decorators will go to the class level as we have in all other plugin types
14:20:28 <amaretskiy> yes, and we should keep in mind that both scenario implementations should be working
14:20:42 <boris-42> this will allow us to remove some magic from framework
14:21:02 <boris-42> andn make it simpler
14:21:28 <amaretskiy> we can use class decorators, or we can just set properties explicitly
14:21:43 <amaretskiy> there are a lot of details to discuss
14:21:58 <boris-42> we won't need this https://github.com/openstack/rally/blob/master/rally/common/plugin/plugin.py#L96-L118
14:22:17 <boris-42> amaretskiy: nope we won't setup properties explicity
14:22:22 <boris-42> amaretskiy: it is mistake that we done many times
14:22:27 <amaretskiy> okay
14:22:33 <boris-42> amaretskiy: why you want to repeat it?
14:22:45 <amaretskiy> so, we will make a class decorator
14:22:58 <amaretskiy> boris-42, I'm just discussing :)
14:23:11 <boris-42> amaretskiy: we won't make class decorator
14:23:19 <boris-42> amaretskiy: we already have all decorators
14:23:25 <andreykurilin> +1
14:23:35 <boris-42> amaretskiy: we will just move them from function level to class level that is all
14:23:49 <boris-42> when we finish moving all benchmarks to top level
14:23:56 <boris-42> scenarios***
14:24:02 <boris-42> to class model**
14:24:08 <amaretskiy> this couls work
14:24:12 <amaretskiy> *could
14:24:17 <boris-42> we can remove old way of scenario description
14:24:29 <boris-42> so i think this will simplify overall everything
14:24:30 <boris-42> =)
14:24:51 <boris-42> btw it was impossible to achieve in backward compatible way until we implemented plugin base+)
14:24:56 <amaretskiy> okay, let's assume that we have a decision about scenario configuration
14:25:20 <boris-42> amaretskiy: I belive we need spec
14:25:28 <boris-42> amaretskiy: so I would suggest you to write it
14:25:31 <amaretskiy> the main question is scenario base class methods and properties
14:25:44 <boris-42> amaretskiy: ??
14:25:48 <amaretskiy> sure, this is obviously a spec and a blueprint as well
14:25:49 <boris-42> amaretskiy: I do not get it
14:26:10 <amaretskiy> methods like "run"
14:26:19 <boris-42> amaretskiy: there is only 1 method "run"
14:26:23 <amaretskiy> okay
14:26:25 <boris-42> amaretskiy: and 0 properties
14:26:35 <boris-42> amaretskiy: that should be implemented
14:26:56 <boris-42> amaretskiy: and a bit refactored Scenario.get method to include such plugins
14:27:04 <amaretskiy> maybe "cleanup" ?
14:27:21 <amaretskiy> to have scenario-based cleanup in separate method
14:29:35 <boris-42> amaretskiy: cleanup is context
14:29:35 <amaretskiy> scenario class should be inherited from https://github.com/openstack/rally/blob/master/rally/task/scenario.py#L95 right?
14:30:03 <boris-42> amaretskiy: yep everything is the same
14:30:37 <amaretskiy> about cleanup: https://github.com/openstack/rally/blob/master/rally/plugins/openstack/scenarios/nova/servers.py#L101
14:30:57 <boris-42> amaretskiy: please don't mess the stuff
14:31:01 <amaretskiy> okay
14:31:23 <amaretskiy> this task will have more than one work item, right?
14:31:28 <boris-42> amaretskiy: the goal is to do transition from method to classes that requires implemenetation of specific method
14:31:29 <amaretskiy> should we have a bp?
14:31:45 <boris-42> amaretskiy: yes because we are chaning >200 plugins
14:32:05 <amaretskiy> okay, so I will create a bp and a spec
14:32:10 <boris-42> amaretskiy: yep
14:32:16 <amaretskiy> any other ideas, comments?
14:33:02 <boris-42> amaretskiy: nothing from side I will wait for spec
14:33:17 <amaretskiy> okay
14:33:29 <boris-42> redixin: what is the status of boot_run_command?
14:33:54 <redixin> it is ready for review https://review.openstack.org/#/c/291686/
14:34:28 <boris-42> redixin: it even work?
14:34:40 <redixin> sure
14:34:46 <boris-42> redixin: great
14:34:50 <boris-42> redixin: I will take a look
14:35:01 <boris-42> redixin: btw I have task for you
14:35:21 <redixin> boris-42: here is some custom results http://r-ci.tk/stuff/heat-80-down-small.html#/VMTasks.runcommand_heat/output
14:35:35 <boris-42> redixin: can you create a directory in certification/
14:35:43 <boris-42> redixin: like openstack-dataplane
14:36:02 <boris-42> redixin: and create task with all files required to execute dataplane performance testing
14:36:35 <redixin> boris-42: sure
14:36:52 <boris-42> redixin: and we will need better CI for certification/* stuff
14:36:56 <boris-42> redixin: like a job
14:37:06 <boris-42> redixin: btw what is the status of ssl testing?
14:37:35 <redixin> I've finished only mos.80-ssl job
14:37:51 <redixin> dsvm-ssl will be done later
14:38:20 <amaretskiy> redixin, boris-42: I believe demo titles will be changed to something descriptive on this chart :)
14:38:28 <boris-42> redixin: do we run there keystone v3 or keystone v2?
14:38:42 <redixin> boris-42: v2
14:38:53 <boris-42> redixin: amaretskiy btw output looks great
14:39:03 <boris-42> redixin: is iit possible to have another job for kesytone v3/
14:39:08 <redixin> https://github.com/redixin/rci-config/blob/master/config.yaml#L745
14:39:10 <boris-42> redixin: I mean instead of 1 job 2
14:39:36 <redixin> one more job vs mos.80-ssl-keystone-v3?
14:39:48 <boris-42> redixin: yep evetyhing the same just v3
14:40:04 <redixin> okay
14:41:33 <andreykurilin> anything else to discuss?
14:41:36 <boris-42> redixin: great thanks
14:41:58 <boris-42> andreykurilin: so I will try to work on rally this week
14:42:00 <boris-42> amaretskiy: =)
14:42:08 <andreykurilin> boris-42: nice!
14:42:14 <andreykurilin> we have a lot of work for you
14:42:15 <andreykurilin> lol
14:42:16 <andreykurilin> :D
14:42:51 <rvasilets> )))
14:43:49 <andreykurilin> anything else?
14:44:00 <amaretskiy> nothing from my side
14:44:13 <rvasilets> nothing  from me
14:44:29 <andreykurilin> boris-42 ?
14:44:38 <boris-42> andreykurilin: seems like we can end meeting
14:44:49 <andreykurilin> thank you all
14:44:51 <andreykurilin> #endmeeting