17:02:33 <boris-42> #startmeeting Rally
17:02:34 <openstack> Meeting started Tue Apr 21 17:02:33 2015 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:38 <openstack> The meeting name has been set to 'rally'
17:02:43 <boris-42> andreykurilin: ping
17:02:45 <boris-42> msdubov_: ping
17:03:17 <serg_melikyan> boris-42: sorry :)
17:03:33 <serg_melikyan> It was funny - I was deadly sure that it is our meeting :)
17:03:44 <boris-42> serg_melikyan: =))
17:05:35 <msdubov_> boris-42:hi!
17:05:59 <oanufriev> hi, guys
17:06:09 <rook> hey
17:06:44 <boris-42> rook: hi there
17:07:14 <rook> hey hey!
17:07:57 <boris-42> So should we start?)
17:08:43 <meteorfox> yes
17:08:59 <andreykurilin__> hi all)
17:10:04 <boris-42> okay great=)
17:10:12 <boris-42> #topic Meeting changes
17:10:25 <boris-42> so we were asked not to move to our room *
17:10:32 <boris-42> and be in one of openstack-meeting rooms
17:11:22 <boris-42> so seems like it will be quite hard to chose some time for it
17:11:30 <boris-42> meteorfox: btw is it too early for you
17:11:42 <boris-42> if we move our meeting to 1-2 hours earlier?
17:12:43 <meteorfox> boris-42: well, so when there's daylight saving, it's at 12 pm, and without daylight saving is at 11 am
17:12:52 <boris-42> meteorfox: ah so it's quite ok
17:13:19 <meteorfox> boris-42: it's ok with me
17:13:25 <dmellado> I guess it'd be great for most Europe-based folks ;)
17:15:02 <boris-42> dmellado: yep
17:15:10 <boris-42> okay I will try to find proper time to do the things
17:16:15 <boris-42> okay
17:16:29 <boris-42> #topic 2 meetings / week
17:16:38 <boris-42> So we are going to have 2 meetings / week
17:17:04 <boris-42> One is related to release management and I would like to have it in #openstack-rally chat
17:17:17 <boris-42> another common (for discussion of everything)
17:17:28 <boris-42> we should keep in #openstack-meetings room
17:17:46 <msdubov_> boris-42 Let's do as you suggest
17:18:18 <boris-42> oK
17:18:28 <boris-42> #topic meeting Agenda
17:18:35 <boris-42> msdubov_: are you ready to manage this?
17:19:53 <boris-42> msdubov_: ??
17:20:11 <boris-42> so basically I think that we should do next things:
17:20:17 <boris-42> * create template for weekly agenda
17:20:26 <boris-42> * put all required info each week
17:20:37 <boris-42> * make rally meeting announce weekly
17:20:46 <boris-42> so not so much work
17:20:48 <msdubov_> boris-42: Do you mean 'common' meetings? Not release meetings?
17:21:01 <msdubov_> boris-42: Anyway I'm ready to take over this stuff
17:21:05 <boris-42> msdubov_: both
17:21:08 <msdubov_> boris-42: Ok
17:21:10 <redixin> is there an ird bot command like "add to meeting agenda"
17:21:17 <msdubov_> boris-42: So weekly announce in openstack-dev?
17:21:20 <redixin> we need simple way for adding items to agenda
17:21:57 <boris-42> redixin: wiki page
17:22:05 <boris-42> msdubov_: yep like other project does
17:22:15 <redixin> wiki page is not simple way =)
17:22:20 <boris-42> msdubov_: day before the meeting they put in mailing list Rally meeting reminder
17:22:25 <boris-42> msdubov_: with agenda
17:22:29 <boris-42> redixin: why?
17:23:15 <redixin> you want me to answer lol?
17:23:26 <boris-42> redixin: yep
17:23:31 <boris-42> redixin: I do not understand
17:23:39 <boris-42> redixin: why it's hard to change wiki page to add new points
17:23:56 <boris-42> redixin: it's takes just few seconds
17:24:22 <redixin> as you say
17:24:40 <msdubov_> boris-42: Why not a google doc?
17:24:47 <msdubov_> boris-42: We use google docs for everything
17:24:48 <redixin> lol
17:24:53 <boris-42> msdubov_: lol
17:24:57 <msdubov_> releases, roadmap, ...
17:25:40 <boris-42> msdubov_: so usually projects are using wiki pages
17:25:45 <boris-42> msdubov_: but we can use google docs
17:26:30 <boris-42> any ideas?
17:26:36 <boris-42> anybody read this thread?)
17:26:48 <dmellado> lol, yep ;)
17:27:08 <redixin> please dont
17:27:10 <dmellado> I wouldn't mind, just use the tool you're more comfortable with :)
17:27:22 <boris-42> redixin: so wiki or google docs?
17:27:27 <redixin> wiki
17:27:31 <dmellado> for the meetings we could even use an etherpad :D
17:27:40 <boris-42> okay wiki=)
17:27:52 <boris-42> i will creat inital version & template
17:28:08 <boris-42> #topic rally-coverage-job
17:28:18 <boris-42> Okay recently we made rally unit test coverage job voting
17:28:30 <boris-42> so now you can't merge patches without almot 100% unit test coverage
17:28:39 <boris-42> woot=)
17:29:02 <boris-42> #topic stackforge/rally -> openstack/rally
17:29:19 <boris-42> Okay we moved from stackforge to openstack finally!-)
17:29:20 <boris-42> woot
17:29:34 <boris-42> #topic Introducing rally-ci project
17:29:41 <boris-42> redixin: could you please say about it
17:29:51 <boris-42> because I believe people does not what it is
17:30:32 <redixin> rally-ci is daemon who listening gerrit stream and launching jobs
17:31:01 <redixin> it very handy if you limited in resources
17:31:38 <boris-42> here is the link: https://github.com/redixin/rally-ci
17:31:49 <redixin> rally-ci can run on localhost and start jobs in docker. it takes a few second from uploading patch to unittests results
17:32:38 <redixin> it is not on review.openstack.org yet
17:32:48 <redixin> https://review.openstack.org/#/c/166962/
17:32:57 <boris-42> redixin: I hope it should be soon https://review.openstack.org/#/c/166962/
17:33:34 <redixin> so thats it
17:33:44 <boris-42> redixin: you forgot the main part
17:33:59 <boris-42> redixin: that it simplifes running rally against every patch
17:34:02 <boris-42> redixin: on own hardware
17:34:40 <redixin> it simplifies running anything
17:34:44 <boris-42> okay
17:34:52 <boris-42> Any questions??
17:35:06 <boris-42> seems like no questions =)
17:35:39 <clarkb> I have a qusetion
17:35:50 <clarkb> does it run anything other than rally/tempest tests?
17:36:20 <redixin> clarkb, rally-ci?
17:36:23 <clarkb> yes
17:36:42 <redixin> currently it run rally vs devstack and MOS clouds, and also unit tests
17:36:51 <redixin> but it can run anything
17:37:14 <clarkb> also, was there a specific reason to not just use zuul which is also a daemon that listens to the gerrit even stream to launch jobs
17:37:54 <redixin> rally-ci is more flexible and less resources usage
17:38:15 <clarkb> can you expand on that? how is it more flexible? and zuul resource usage should be pretty low
17:39:09 <redixin> is it possible to not use openstack for test vm's?
17:39:13 <clarkb> yes
17:39:22 <clarkb> you can use any gearman worker
17:39:59 <boris-42> clarkb: so basically what we would like is to call rally for creating env and then run rally to test it
17:40:20 <redixin> so i should use complex setup with jenkins zuul gearman
17:40:23 <redixin> all this java stuff
17:40:41 <clarkb> http://cacti.openstack.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=23&page=3 is resource usage. The node has a lot of RAM due to a tmpfs that is no longer in use, we should probably trim that node down
17:40:49 <clarkb> redixin: you don't need any java stuff
17:40:52 <redixin> or use one simple daemon on python with plugins and one simple config file
17:41:01 <clarkb> redixin: thats exactly what zuul is
17:41:25 <clarkb> its a simpel daemon written in python with one config file (well two if you count the ini to point at a gerrit)
17:42:49 <redixin> zuul is not simple
17:42:52 <clarkb> boris-42: I am not sure what that means, but zuul runs rally many times per day for you already
17:42:57 <clarkb> boris-42: so I think zuul can run rally...
17:43:52 <boris-42> clarkb: okay I think we should investigate
17:43:56 <boris-42> clarkb: this during next week
17:44:11 <boris-42> clarkb: and continue discussion on next week
17:44:59 <boris-42> okay
17:45:07 <boris-42> #topic Free discussion
17:45:22 <boris-42> anything to discuss?
17:45:36 <clarkb> boris-42: redixin the feedback would be good. I think we see zuul as fitting this mold and if there are problems with it that can be addressed filing bugs and other feedback is valuable
17:46:21 <boris-42> clarkb: thank you for taking part in meeting
17:46:54 <boris-42> clarkb: we deff need to ensure that rally-ci is not the clone of zuul
17:47:04 <boris-42> clarkb: and if it is we need to migrate to zuul
17:47:07 <boris-42> if it is possible
17:47:21 <redixin> the only problem with zuul is too complex for configuration
17:49:41 <boris-42> okay if nothing to discuss let's finish meeting
17:49:51 <boris-42> #endmeeting