15:58:41 #startmeeting hyper-v 15:58:41 Meeting started Tue Dec 11 15:58:41 2012 UTC. The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:58:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:58:44 The meeting name has been set to 'hyper_v' 15:58:53 hmm, my clock is 2 min off 15:59:04 pnavarro: how's it going 15:59:30 going to wait a couple more minutes for everyone to join 15:59:33 Hi primeministerp ! 15:59:47 pnavarro: how's it going 16:00:00 pnavarro: any progress on the cinder commands not responding 16:00:02 i'm doing well, and you? 16:00:14 pnavarro: a bit tired, we got a dog this weekend 16:00:26 a dog ! oufff 16:00:38 a new baby 16:00:40 pnavarro: and I'm coming off a lot of hours last week w/ the cloudbase team 16:00:56 pnavarro: yes, lucy the daschund 16:01:24 pnavarro: so I saw that alex is going to create an installer for the cinder bits 16:01:32 about cinder, I couldn't take a look this evening 16:01:38 pnavarro: ok 16:01:57 pnavarro: do we at least know if it's a bug? 16:02:47 well, It looks like a bug, but I'm not sure 16:04:05 no alex yet 16:04:45 pnavarro: i just pinged tavi 16:04:57 pnavarro: we made some progress last week 16:05:07 we refactored all the puppet bits I started 16:05:20 ociuhandu: tavi! 16:05:30 hello all 16:05:31 ociuhandu: is alex going to join as well 16:05:52 yes, he'll be joining in a couple of minutes 16:07:30 hi guys 16:07:39 hi alexpilotti 16:07:43 sorry for being late! 16:08:10 hey no worries 16:08:15 so 16:08:21 i guess we'll offically begin 16:08:21 my Colloquy was disconnected, can u plz tell me what's teh current topic? :-) 16:08:31 #topic cinder 16:08:37 cool 16:08:40 pnavarro: and i were discussing the bug 16:08:52 alexpilotti: from the email 16:08:53 what bug? :-) 16:09:02 alexpilotti: i wanted to confirm it's fit's a bug or not 16:09:20 alexpilotti: the non functioning cinder commands 16:09:30 * primeministerp looks at the email 16:09:45 alexpilotti: that you found 16:09:59 sure 16:10:22 it was a question. How to remove a cinder-volume service 16:10:26 the case is simple: 16:10:28 alexpilotti: removing existing volumes 16:10:29 you run devstack 16:10:57 alexpilotti: is it definately a bug? 16:11:03 ok, I'm missing something :-) 16:11:10 alexpilotti: the email you sent 16:11:22 the email I sent today? 16:11:27 On the controller I didn't find a way to remove an existing cinder-volume service except editing the db. 16:11:29 yes 16:11:42 yep 16:11:48 so the case is simple: 16:11:53 you have e.g. devstack 16:12:00 i just want clarity on what the problem is 16:12:02 you stop the cinder-volume service 16:12:22 you add cinder-volume running on Windows Storage 16:12:43 on the controller you'll still see both services 16:12:54 so if you run: cinder volume create 1 16:12:54 ahh gotcha 16:13:03 it will try to use either one 16:13:07 it will try to create on the wrong vol server 16:13:09 i get it 16:13:10 now 16:13:17 i thought it was on the target end 16:13:23 something in pnavarro bits 16:13:30 that wasn't functioning 16:13:30 no, nothing on our side 16:13:33 o 16:13:35 great 16:13:41 pnavarro: you're off the hook 16:13:42 ;) 16:13:49 thanks 16:13:52 haha 16:13:54 pnavarro: do you have any clue? I'm going to ask the cinder guys otherwise 16:14:00 alexpilotti: any timeline on the installer? 16:14:04 lol 16:14:14 alexpilotti:sorry 16:14:14 sorry alex, no idea what's the problem... 16:14:19 ah yep. I'm going to release the installer today 16:14:26 alexpilotti: awesome 16:14:32 for cinder-volume only, that's what we need 16:14:33 pnavarro: no problem on our end 16:14:50 pnavarro: just didn't automatically remove the linux service 16:14:52 IMO we can leave out cinder-api and cinder-scheduler 16:14:56 pnavarro: if i understand correctly 16:15:01 alexpilotti: why? 16:15:36 because I had some issues on running them with the latest Grizzly bits on Windows 16:15:49 alexpilotti: *nod* 16:16:15 and because those services run usually on a controller, not on each volume node 16:16:33 let's say that "cinder-volume" is for Cinder what "nova-compute" is for Nova 16:16:42 i get it 16:16:53 thx 16:16:55 ok 16:17:01 guess we'll move on 16:17:04 of course we want to have all the rest on WIndows as well ;-) 16:17:13 sure 16:17:13 ;) 16:17:21 #topic quantum 16:17:27 ahem 16:17:33 ? 16:17:36 next topic? :-) 16:17:42 quantum? 16:17:52 was there something i missed? 16:18:04 kidding, due to the CI stuff I was not able to do more than looking at pnavarro's bits 16:18:13 pnavarro: do you have anything new? 16:18:30 alexpilotti: i was asking mostly for pnavarro's input 16:18:35 pnavarro: you're on the hook again 16:18:38 ;) 16:18:45 lol 16:18:49 alexpilotti: agent is running ok, i'm still testing agent- plugin communication 16:19:09 pnavarro: great! 16:19:13 pnavarro: great 16:19:24 so, I'd appreciate any help 16:19:40 pnavarro: this week, I swear, I'm working on it :-) 16:19:50 perfect 16:19:50 and alexpilotti you'll start work again shortly 16:20:15 alexpilotti: will we be able to account for the nvgre bits 16:20:22 pnavarro: on the agent side, what hyper-V specific features did you test already? 16:20:51 sorry guys, i have to run now, will ba back in about 45 minutes 16:21:03 primeministerp: i'll ping you when i get back 16:21:03 ociuhandu: ok, let's touch base re: ci 16:21:09 ociuhandu: great 16:21:15 I tested ports updates 16:21:22 bye all & yalk to you later 16:22:28 pnavarro: nice 16:22:30 pnavarro: this time, we should think about a FakePlugin since we don't have the rush 16:22:36 alexpilotti: yeah 16:23:09 alexpilotti: and by fake plugin? 16:23:20 for my ignorance 16:23:24 please 16:23:34 same as the wmi test interface 16:23:43 but for quantum only? 16:23:52 basically a class that emulates the wmi calls, by creating an asbtarction layer on them 16:24:06 gotcha 16:24:07 so in the code, instead of calling WMI we call this new layer 16:24:28 which can be replaced by a fake one during tests 16:24:40 we have to do the same for Nova and Cinder of course 16:24:46 alexpilotti the wmi library creator gave you some hint about that? 16:25:27 pnavarro: nope :-( 16:25:27 pnavarro: but if we wrap all the calls we are fine 16:25:49 alexpilotti: aren't you wrapping them 2x then? 16:25:50 pnavarro: this IMO will not reach the level of coverage we had with the dynamic mocks, but it's ok 16:26:13 primeministerp: yes, no comment 16:26:18 hahaha 16:26:27 indeed we are not really wrapping them twice 16:26:43 there while be a lower level fine grained layer 16:26:48 *nod* 16:26:49 hehe 16:26:51 and a high level (the driver itself) 16:27:02 fair enough 16:27:25 the point is that we should test the low level one as well… that's the funny part 16:27:27 alexpilotti: maybe we can leverage the new relationship w/ tom for assistance 16:27:39 w/ getting you information 16:27:47 resources 16:28:04 unfortunately the way in which WMI is done is the problem 16:28:26 the amazing flexibility it provides becomes a huge PINTA for testing 16:28:53 *nod* 16:29:02 we definately don't have it easy 16:29:08 yeah, we can't use mocks library 16:29:20 so why not specifically 16:29:32 the nature of having to test the network itself? 16:30:23 setting up the tests will be relatively easy, as we can take the OVS ones as a reference 16:30:56 pnavarro: is your repo updated? 16:31:02 yeah 16:31:23 alexpilotti: I've added the binary 16:31:37 pnavarro: this it the latest plugin? https://github.com/pnavarro/quantum/tree/master/quantum/plugins/windowsvswitch 16:31:45 yes 16:31:51 #link https://github.com/pnavarro/quantum/tree/master/quantum/plugins/windowsvswitch 16:32:03 If you don't like the name, we can change it 16:32:34 pnavarro: name doesn't bother me 16:32:49 pnavarro: I'd go with hypervswitch, but that's a detail :-) 16:32:55 oki doki 16:32:59 pnavarro: he's a bit right there 16:33:15 alexpilotti: ... and your the purist 16:33:20 ;) 16:33:26 ok 16:33:29 should we move on? 16:33:35 to ci talk? 16:33:47 pnavarro: I'm loking at the utils.py, good work! 16:34:11 thanks alexpilotti ! 16:34:30 #topic CI 16:34:43 alexpilotti: this will be quick 16:34:52 since i'll have to catch up w/ tavi later 16:34:54 lol 16:35:12 but I figure we'll coordinate 16:35:18 then 16:35:25 sure, ociuhandu will be back in ca 1hr 16:35:26 i'm assuming you guys haven't picked up yet 16:35:33 i'll read the logs later, I have to go 16:35:36 from where we left off 16:35:40 pnavarro: thanks for everything 16:35:51 ciao ! 16:35:52 I resumed the work this afternoon (aka 2 hours ago) 16:36:18 alexpilotti: on the scripting? 16:36:22 pnavarro: hasta luego! 16:36:46 primeministerp: yep, I'm polishing up the scripts for the controller 16:36:54 alexpilotti: ok 16:37:10 alexpilotti: i figured out why my post script wasn't running out of the preseed 16:37:19 alexpilotti: fixed and going test 16:37:24 cool 16:37:28 also hoping to resume work on the windows unatted bit 16:37:28 s 16:37:42 next couple of days are going to be tough for me 16:37:45 due to meetings 16:37:47 primeministerp: BTW VPN works fine also from this side of the "pond" :-) 16:37:48 and now the move 16:37:52 alexpilotti: great 16:38:03 alexpilotti: i resurected my asa at home 16:38:12 I'm going to put a static tunnel up for me 16:38:16 now that I have to move 16:38:18 my office 16:38:48 also ordered sound protective bluetooth headset for working in the dc 16:39:07 anyway 16:39:23 o 16:39:27 mordred: ping 16:39:43 mordred: whats the best way for us to start the process of integration our hyper-v work 16:40:02 alexpilotti: i was thinking we can start adding the bits we've created 16:40:21 alexpilotti: that way we don't dump a whole lot on top 16:40:36 alexpilotti: and can increment at a minimum the working parts 16:40:45 alexpilotti: any thoughts 16:40:59 alexpilotti: also then we'd be working out of git 16:41:45 well mordred might be busy i'll try to follow up w/ him later 16:42:47 primeministerp: Since finishing the "layer 1" stuff is almost done, can we set up a meeting wit mordred this or next week? 16:42:47 ok 16:43:00 alexpilotti: that's my thoughts 16:43:05 alexpilotti: i'll work on that 16:43:06 cool 16:43:19 alexpilotti: and let's plan on having a skype when tavi gets back 16:43:25 just to touch base 16:43:33 coo, I'll be here as well 16:43:38 ok great 16:43:47 i've got to head in into the office 16:43:52 so i'll be offline for a while 16:43:59 ok closing the meeting 16:44:03 #endmeeting