17:01:08 #startmeeting Rally 17:01:08 Meeting started Tue Mar 18 17:01:08 2014 UTC and is due to finish in 60 minutes. The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:11 The meeting name has been set to 'rally' 17:01:37 marcoemorais hughsaunders stannie meeting 17:03:28 yes boris-42 17:03:47 hi 17:04:17 stannie hey there=) 17:04:20 msdubov ping 17:04:27 penguinRaider ping 17:04:31 boris-42, pong 17:04:33 marcoemorais ping 17:05:38 boris-42 hi 17:07:57 so let start 17:08:01 our meeting stuff 17:08:55 #topic Benchmarking future steps 17:09:15 So stannie you are improving perfromance of generic cleanup? 17:09:33 pong 17:09:52 yes boris-42 I am going to work on CleanupContext 17:09:56 haven't started yet 17:10:50 the task is to add a special decorator for CleanupContext that will increase the performance by having a a generic cleanup 17:11:41 e.g @cleanup(["service1", "service2"]) will only run cleanup for service1 and 2 17:11:45 service1 can be nova 17:11:54 yep yep 17:11:54 service2 e.g cinder etc 17:12:05 stannie btw Kun will work on another improvment 17:12:15 ok so he is depending on my patch ? 17:12:19 nope 17:12:23 ok 17:12:30 but he will improve as well generic clenaup 17:12:38 to cleanup only users that we actually used 17:13:04 e.g. if we have 10k users but run tests only 1k times (we don't need to cleanup all 10k users) 17:13:16 boris-42 Have you started the work on the StressRunner? 17:13:25 msdubov nope I didn't.. 17:13:39 boris-42 Ok I'll take it then if you're not against 17:13:47 msdubov okay 17:14:01 stannie hmm so I think that everybody agrees with that stuff? 17:14:27 stannie with having decorator that cleans only specified services?) 17:14:42 less cleaning, less waiting 17:14:47 hughsaunders yep 17:14:55 msdubov btw yes I am against 17:15:02 msdubov don't touch stress test 17:15:15 boris-42 why& 17:15:16 msdubov until you finish your patch with refactoring of utils 17:15:18 why? 17:15:22 boris-42 sure 17:15:32 msdubov or let Kun make it.. 17:15:39 msdubov or finish it by self.. 17:16:26 boris-42 I suppose we'll continue the work with Kun on the processing utils after we merge https://review.openstack.org/#/c/79970/ 17:16:54 msdubov it is not related... 17:17:11 msdubov to your work at all 17:17:24 msdubov so pls concentrate on first patch with utils 17:17:30 msdubov cause it blocks everything 17:17:43 msdubov "stress" runner doesn't block anything 17:18:09 boris-42 ok 17:19:32 hughsaunders are you working on passing context to scenario?) 17:19:42 boris-42: yep, but slowly 17:19:54 needs big rebase 17:20:14 hughsaunders hmm I didn't touch that part too much?) 17:22:25 so okay let move 17:22:29 let's move 17:22:39 So I am going to finish work (by the end of this wekk) 17:22:41 week* 17:22:59 and build ContextManger that will handle what context to run and what context are required by benchmark 17:23:15 this will finish work on BenchmarkStuff 17:23:31 So I will concentrate on other parts of projects 17:23:38 E.g. tempest & deploy stuff 17:23:54 And thoughts about benchmarking in VMs 17:24:19 hughsaunders msdubov stannie btw does anybody have any questions?) 17:24:29 I mean seems like it's clear what and why we are doing=) 17:24:55 seems clear to me 17:24:57 seems like Rally team works even without meetings =( 17:25:05 or probably I should be happy=) 17:25:19 # Tempest stuff 17:25:24 Yep, there is actually the guiding doc 17:25:28 so it's clear 17:25:28 #topic Tempest stuff 17:25:48 1. We should improve config generation (to make it works in any case0 17:26:10 I think that somebody should start playing with it… and catching all mistakes in configs 17:26:51 2. We should create benchmark scenario that will run tempest scenario 17:27:02 Seems like this work is quite close to be finished 17:27:22 we will use "verification" stuff to make proper configuration for tempest 17:27:34 and we will have TempestContext 17:27:54 that will "activate" virtualenv with all stuff from tepest and run tempest unit test 17:28:06 and in cleanup it will "deactivate" 17:28:26 So seems like it's clear here as well hughsaunders penguinRaider stannie msdubov ? 17:29:00 point 1. : Is it clear who will handle this "catching mistakes" stuff? 17:29:15 really lots of work as we discussed it today 17:29:27 msdubov probably you?) 17:29:52 boris-42 Certainly not this week then... 17:30:01 msdubov it's okay 17:30:02 msdubov, boris-42 I can do that maybe ? 17:30:09 penguinRaider yep sure 17:30:10 boris-42 Actually my thought was that this should be done by 2-3 people 17:30:17 so we could do it together 17:30:32 actually Olga is already working on this stuff 17:30:37 but she need help 17:30:51 cause task takes a lot of time and it's quite big 17:31:16 just to note, i am ready for some kind of work 17:31:25 amaretskiy okay nice 17:31:40 amaretskiy penguinRaider let's speak today and coordinate this work with Olga 17:31:48 tomorrow* 17:31:51 ok 17:32:18 sure 17:33:01 # Deploy stuff 17:33:07 #topic Deploy stuff 17:33:19 hughsaunders penguinRaider amaretskiy msdubov guys we should help rediskin 17:33:34 to finish at least multi host engine 17:33:50 boris-42 Do you mean code reviews? 17:33:56 or other kind of help? 17:34:02 msdubov code reviews and testing patches 17:34:26 hard to do code review without testing patches in case of rediskin =) 17:34:39 yep, I removed -1 today, but need to retest 17:34:54 msdubov lol 17:35:33 #topic Free discussion 17:36:05 msdubov hughsaunders penguinRaider amaretskiy does anybody have any questions about Rally/RoadMap/any stuff... 17:36:06 ? 17:36:23 i don't 17:36:28 boris-42, hughsaunders msdubov I need help regarding my application for gsoc 17:36:35 penguinRaider: what needs doing? 17:36:46 I need a unifying theme for the proposal 17:36:48 penguinRaider yep you should share with them 17:36:52 do you have any proposed changes for the output of the tasks? 17:37:05 tzabal hi! 17:37:08 tzabal ?) 17:37:11 hi tzabal :-) 17:37:19 hello :) 17:37:31 tzabal out of task you mean CLI or Graphics?) 17:37:47 penguinRaider: is your proposal available somewhere to read? 17:38:07 hughsaunders, yeah I made a rough first draft will share with you 17:38:09 i was thinking about putting the average, min, max results that we have in CLI, in the report of plot2htm 17:38:57 is there a way to dump the actual openstack calls rally is making ? 17:39:24 mwagner_lap all calls? 17:39:34 mwagner_lap all API calls you mean?) 17:39:50 mwagner_lap actually if you run it with -d you will get all calls.. 17:39:59 ok cool 17:40:18 mwagner_lap it will be just debug mode (and all http request will be shown with all details) 17:40:36 tzabal so that is the work that started msdubov 17:40:48 tzabal but he didn't finished yet first patch 17:41:09 tzabal after he finish work you may share this task with Kun 17:41:20 msdubov ^ pls help with organizing work on this 17:41:23 boris-42 ok 17:41:35 mwagner_lap so actually I have one idea 17:41:46 boris-42 ok 17:41:46 just one :) 17:41:48 mwagner_lap to collect more data form our benchmarking stuff 17:41:50 mwagner_lap =) 17:41:55 mwagner_lap one for you=) 17:41:59 mwagner_lap at this second=) 17:42:08 boris-42 do you have any proposed change for the plot2html stuff? 17:42:18 tzabal nope 17:42:24 * mwagner_lap waits anxiously 17:42:26 tzabal btw I have idea what you may do 17:42:35 tzabal until you are waiting for msdubov 17:43:01 tzabal draw histogram (with possibility on Y and duration on X) 17:43:05 tzabal interested ? 17:43:11 boris-42 yeap 17:43:22 tzabal okay I will share with details after meeting 17:43:26 mwagner_lap so 17:43:39 mwagner_lap actually as you see we are doing active pooling of resource 17:43:51 mwagner_lap e.g. checking status of VM until it becomes "Acitve" 17:43:54 mwagner_lap yep? 17:44:51 boris-42, actually trying to figure out how to do that now 17:45:02 mwagner_lap it's already done.. 17:45:10 tryting to figure out how you bypass the instance database 17:45:30 mwagner_lap not sure that understand queiston=) 17:45:41 mwagner_lap First step send request to create VM 17:45:56 mwagner_lap second step in while do get_vm_by_uuid 17:46:14 mwagner_lap if it is Active stop while, if it is in Error state raise Exception 17:47:06 as I mentioned earlier this morning, if i run the "boot" task, vms get created and are left running but they dont show up via nova list and they are not in the instance database 17:47:26 which doesn't delete them from the db 17:47:50 they show up in a ps -ef | grep qemu on the hypervisor but in virsh list --all 17:48:13 so procs are running but no record of them from the openstack or libvirt perspective 17:49:24 mwagner_lap so seems like you didn't get my response 17:49:49 mwagner_lap the reason why you didn't see them is that you try to list admin's VMs 17:49:58 mwagner_lap and Rally creates VMs from temporary users 17:52:55 boris-42, i did get that but shouldn't all the vms show up in the "systems" instance table ? 17:53:24 mwagner_lap "systems"? 17:53:34 from an openstack pov there should be an accounting of the resources used 17:53:35 mwagner_lap they should be showed in "instances" table 17:54:10 they are not showing up in mine, but they are running on the hypervisor 17:56:48 mwagner_lap hmm strange 17:56:58 mwagner_lap they should be all in DB 17:57:10 mwagner_lap and if you are looking in Horizon 17:57:27 mwagner_lap they should be listed in "instances" 17:57:30 horizon does not show them and 'virsh list' doesn't list them either 17:57:33 mwagner_lap at admin page 17:57:38 virsh list on the hypervisor 17:57:56 mwagner_lap okay lets disccuss this in rally chat 17:57:59 bogdando, right not even with the admin page 17:58:04 ok 17:58:08 #endmeeting