17:04:35 #startmeeting Rally 17:04:36 Meeting started Tue Dec 3 17:04:35 2013 UTC and is due to finish in 60 minutes. The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:04:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:04:40 The meeting name has been set to 'rally' 17:04:52 hi all 17:05:11 am I alone ;) 17:05:12 ?) 17:05:20 alone in the room 17:05:24 yep 17:06:02 lol 17:06:20 wat 17:06:26 #topic Splitting Rally benchmark & deploy workflows 17:06:42 akscram could you share latest news ? 17:08:31 akscram ? 17:08:41 today we discussed benchmarking workloads as a complex tasks 17:08:51 akscram see topic pls 17:09:12 akscram splitting benchmark & deploy workflows 17:09:28 is it the #topic command, right? 17:10:08 afaik this work depends on resource-db-tracking, and patches are coming soon 17:10:46 akscram yep 17:10:57 Okay let's speed up this discussion 17:11:13 #topic splitting benchmark & deploy workflows 17:11:29 I think that only I am able to run this command 17:11:33 #topic splitting benchmark & deploy workflows 17:11:58 so, redixin is right 17:12:04 akscram so pls say in few words what we are going to do and links do bp and pathces 17:12:12 the splitting is blocked by the resource tracking 17:13:22 a patch introducing Resource model is still in progress 17:14:30 akscram okay to make in more clear I will try to explain 17:14:32 after that I want to create a patch with tracking resources in server providers 17:14:56 akscram we should merge this patch https://review.openstack.org/#/c/57455/ 17:15:24 but it is impossible until deploy part of Rally will track all allocated resources like allocated VMs 17:15:57 it is caused because before this patch, we made deploy-benchamrk-deploy_clenaup in one action and store all data in memory of process 17:16:14 and now deploy and deploy_cleanup are totally separated tasks 17:16:32 so we should store all allocated resources in DB instead of process memory 17:16:53 so I hope at this week we will finish all work around this stuff 17:17:10 #topic benchmark engine improvements 17:17:19 msdubov ping 17:17:25 boris-42 here 17:17:36 msdubov could you share improvements around benchmark engine 17:19:09 boris-42 So, 1) we have merged the patch which enabled Rally to run benchmark scenarios for a given period of time, say, 10 minutes. This is a significant improvement since earlier we were only able to launch scenarios for a restricted number of times, say, 5 times, and this change allows us to create more realistic load 17:19:40 2) We have also enabled admin openstack client support in benchmark scenarios which will allow us to write fully functional keystone benchmark scenarios 17:19:52 And there are several changes pending for review: 17:20:28 msdubov okay nice 17:20:35 1) Periodic launch of benchmark scenarios (another significant change, since earlier we were able to run scenarios only continuously, but now we will be able to run periodic tasks 17:20:45 2) I've repaired the init() mechanism 17:21:02 basically that's all for now 17:21:30 msdubov okay thnaks 17:21:45 #topic make Rally more community oriented 17:22:09 Ok, we have pretty good wiki page, roadmap and so on 17:22:34 But it is hard to understand what are our current goals, current roadmap, tasks in progress and free tasks 17:22:52 so we made Rally page on etherpad that will contain all interesting infromation 17:23:18 boris-42 Will we post weekly updates there? 17:23:26 link? 17:23:36 so here is the page https://etherpad.openstack.org/p/Rally_Main 17:23:55 msdubov no weekly updates we will publish on wiki page 17:24:13 msdubov but there will be link from this page to rally updates 17:24:21 boris-42 ok nice 17:24:59 boris-42 btw I think next week I'll start pushing old updates to the archive since there are already 3 of them, and the wiki page is pretty long already 17:25:15 msdubov I think that we could wait a bit 17:25:24 msdubov 5-6 news per page 17:25:31 boris-42 Ok 17:25:46 boden do you have some news to share with us 17:25:56 boden around cloud cleanup 17:26:21 boris-42 -- almost done with the cloud cleanup... I just finished up the UTs... all I have to do now is merge with the latest and then retest before submitting code review 17:27:30 boden are you executing to finish it today? 17:27:36 expecting * 17:28:11 boris-42 I would like to, but it depends if I run into issues from the resulting merge 17:28:33 boden ok nice, thank you 17:28:59 Okay I think that we could end todays meeting 17:29:01 boris-42... I will probably not take on any more work in near future as I will be out for awhile this month for vacation 17:29:12 boden eh sad.. 17:29:35 why sad? some snowboarding is fun =) 17:30:04 redixin yep=) 17:30:52 boden okay have a nice vacation-=) 17:30:52 boden have a nice time 17:30:58 #endmeeting 17:30:59 thank you 17:31:09 boden I hope you won't forget us after vacation=) 17:31:14 #endmeeting