16:02:31 #startmeeting hyper-v 16:02:32 Meeting started Tue May 7 16:02:31 2013 UTC. The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:35 The meeting name has been set to 'hyper_v' 16:02:51 so let's begin 16:03:27 I guess a good place to start is next steps post summit 16:03:37 where we currently are in that process 16:03:53 what is priority after the design session 16:04:33 alexpilotti: would you like to start? 16:04:47 sure 16:04:51 kpavel_: hi there 16:05:14 alexpilotti: or is there something else we should address prior? 16:05:28 quite a lot coming for Havana 16:05:50 let's start at the top priority 16:05:55 wmiv2 16:05:56 we got a lot of requests about how to handle clustering to begin with 16:06:32 most Windows workloads are based on the assumption that the HA is handled by the OS 16:06:33 from a "hyper-v cluster" as a compute node perspective 16:06:58 we need to support a Hyper-V windows cluster as a compute node 16:07:20 we can use an approach similar to what vsphere took 16:07:39 but use the hyper-v/cluster api's as the access point 16:07:47 to that functionality 16:07:56 yep 16:08:03 just to confirm 16:08:20 teh idea is that the cluster is seen as a single compute node 16:08:45 but Nova will be able to get data about each individual host 16:08:48 and the best part is hyper-v clustering features ship w/ the free hyper-v server 16:08:53 yep 16:09:08 the only thing is that we'll need a DC 16:09:25 we already do need one for live migration 16:09:36 in order to have a 100% free solution 16:09:47 then samba4 16:09:52 we can try to see how Samba4 works 16:09:54 yep :-) 16:10:08 I tried w a beta a few months ago 16:10:17 I have some people to reach out to if we have issues 16:10:20 and I had issues with Kerberos delegation 16:10:23 from the samba side of the things 16:10:37 that'd be great 16:10:51 on the API perspective 16:10:57 well on the samba perspective 16:11:04 and on the api perspective 16:11:07 Windows has some higher level Powershell API 16:11:10 and i can dig internally to see 16:11:26 sorry, I was starting a new sentence :-) 16:11:26 what is available for the cluster api interfaces 16:11:43 so we have Powershell and COM low level interfaces 16:11:44 and documentation 16:11:59 MS is suggesting Powershell, but it's a useless overhead for us 16:12:08 so I'd go with COM 16:12:18 depending on the level of PINTA, to say so :-) 16:12:29 * primeministerp silently agrees 16:12:55 we don't need additional overhead 16:12:55 We still have to target this one, but Havana-2 is a good target IMO 16:13:14 BTW Havana-1 is behind the corner (ca 1 month) 16:13:21 wtf 16:13:34 well, next month is June :-) 16:13:54 yes it is 16:13:57 let me see if I find the deadline scheduling 16:14:08 so I expect Havana-2 in July 16:14:15 and Havana-3 in August 16:14:34 lst year we started working end July / begin August 16:14:42 in time for Folsom-3 16:14:54 so it makes sense (unfortunately)! :-) 16:15:25 I'm not sure but i thought I heard something about releases shifting dates slightly 16:15:30 but I coudld be wrong 16:15:35 anyway 16:15:41 so 16:15:57 #link https://wiki.openstack.org/wiki/Havana_Release_Schedule 16:15:59 here it is 16:16:01 thx 16:16:15 even worse, May 30th 16:16:24 heh 16:16:36 but the good news is that the final one is after the summer ;-) 16:16:59 which means that the Gods decided not to **** up our summer this time :-D 16:17:23 alexpilotti: and we're not trying to get code resurrected ;) 16:17:35 so moving on 16:17:35 lol ;-) 16:17:39 ok 16:17:40 past cluster 16:17:41 V2 16:17:45 WMI 16:17:47 yes 16:17:51 that's the big one 16:18:13 the Grizzly refactoring gives us a great start 16:18:23 all the code is well layered 16:18:47 meaning that we have to add the V2 "utils" classes 16:19:05 and a factory that will allocate the right one based on the OS 16:19:17 alexpilotti: to deal w/ backward compatibality 16:19:18 V1 on 2008R2 (legacy, soon unsupported) 16:19:27 and V2 for 2012 and above 16:20:05 the testing will be way easier, as all the rest of the code will be untouched 16:20:15 *nod* 16:20:19 anyway it'll still be a long work 16:20:33 that blocks the next step (VHDX stupport) 16:20:41 alexpilotti: we need to followup on win-next 16:20:51 cool 16:20:59 alexpilotti: we'll i 16:21:11 I'd schedule WMIV2 for Havana-1 16:21:21 in order to unlock the rest 16:21:31 alexpilotti: sounds good to me 16:21:39 Questions or should we go on? 16:21:55 sounds good 16:21:59 move on 16:22:08 +1 16:22:33 alexpilotti: quantum 16:22:58 NVGRE ! NVGRE ! 16:23:16 There's something more than NVGRE coming ;-) 16:23:30 but we have to wait a few days to get a final confirmation 16:23:32 let's just say we're finalizing details 16:23:59 NVGRE is still in the list, but priority would be shifted quite a bit down to say so 16:24:10 yes 16:24:33 on QUantum we need anyway the Agent support in our plugin 16:24:49 so let's hold till next week on that discussion so we can confirm/deny 16:24:57 I mean, the new Agent API. I was trying to sneak them in for G3 16:25:07 but Quantum was frozen already 16:25:09 alexpilotti: H3 16:25:14 G3 16:25:17 o 16:25:19 in march 16:25:20 gotcha 16:25:24 so the work is mostly done 16:25:37 I just need to retarget the patchset 16:25:54 there are a gazillion BP on Quantum 16:26:09 one of them is related to merge all the agents in one 16:26:12 i would imagine 16:26:17 *the plugins, sorry 16:26:40 most plugins are very similar: OVS, LinuxBridge, Hyper-V, etc 16:26:51 so a refactoring makes definitely sense 16:27:45 and from release perspective? 16:27:59 on refactor work 16:28:40 I suggest to postpone the Quantum discussion to the next meeting, hopefully we'll have more details to disclose 16:28:40 what do you think primeministerp? 16:28:51 alexpilotti: yes 16:29:32 alexpilotti: quantum/networking discussion until we get appropriate confirmation 16:29:41 er postpone 16:30:09 are you including the VHDX work in the WMIV2 migration? 16:30:41 sure 16:30:44 ok 16:30:45 ops, no :-) 16:30:52 I didn't think it was 16:30:55 wmi v2 first 16:31:00 WMIV2 "unlocks" the VHDX badge :-) 16:31:01 vhdx after that is complete 16:31:02 yes 16:31:09 +200 mana 16:31:13 for hyper-v 16:31:14 ;) 16:31:33 so right after we are done with V2 VHDX support is fairly fast to achieve 16:31:57 so H2 is definitely a good target 16:32:01 good 16:32:16 fibre channel support? 16:32:19 next? 16:32:22 sure 16:32:31 if i can have san and hba's 16:32:40 FC dependes largely on HP's lab stuff 16:32:45 cool 16:32:55 so I have both in my lab already 16:32:57 as soon as we have a lab set up we can start developing 16:32:58 I just need to connect 16:33:03 it together 16:33:18 I can see if i can cobble it so we have something 16:33:22 to start 16:33:25 if interested 16:33:25 it's gonna be a bigger PINTA compared with iSCSI 16:33:32 i would imagine 16:33:36 pnavarro: anything to add on FC? 16:34:28 well 16:34:47 priority over that work would possibly be AD/Keystone work 16:35:54 ? 16:35:59 sorry that was a question 16:37:39 alexpilotti: we'll continue then 16:37:49 alexpilotti: think people are nodding off 16:37:51 ;) 16:38:05 oki, sorry about that 16:38:08 :-) 16:38:09 np 16:38:22 so take aways 16:38:22 AD / keystone sure 16:38:31 let's focus on the H1 16:38:33 milestones 16:38:33 I'd like to hear Cern opinion 16:38:40 luis_fdez: ping 16:39:38 it's late over there 16:39:52 let's finish up, then 16:39:55 alexpilotti: ^ 16:39:55 oki, let's move on 16:40:07 alexpilotti: so that's a good start 16:40:16 We're going to set up the BPs 16:40:21 yes 16:40:25 there's quite a lot of work as usual 16:40:41 as usual 16:40:41 ah, there's that annoying bug on cinder-volume to fix 16:40:50 pnavarro: ^ 16:40:54 the eventlet stuff 16:41:03 I got a guy writing me about that 16:41:11 can you cc me on the thread 16:41:20 if possible 16:41:37 pnavarro: would you like to sync about it and also talk about the Havana stuff that you'd like to work on? 16:44:22 ok, no ping from pnavarro :-) 16:44:29 sorry al 16:44:31 alex 16:44:35 I was on phone 16:44:36 np :-) 16:44:53 pnavarro: ^^ 16:45:42 so, about cinder, yes, there are some fixes to do 16:46:03 and the tests should be refactored to follow the other projects 16:46:15 pnavarro: +1 16:46:57 is there any specific area you'd like to work on for Havana? 16:47:00 I'd like to add the missing features copy image to volume, volume to image 16:47:06 cool 16:47:38 ociuhandu told me that image to volume works already 16:47:50 as far as I remember 16:47:59 mmm 16:48:05 but I have to recheck this 16:48:12 in the driver there are NotImplement 16:48:35 I can help in nova gaps, for example, ephemeral 16:48:53 cool, that's great 16:49:16 alexpilotti: have to check that, was a bit ago and have to go through the things to refresh the short memory buffer 16:49:22 the list of new features / BPs we started here is still uncomplete 16:49:54 ociuhandu: could be that it was simply related to the Linux driver on devstack? 16:49:58 Fibre channel would be cool too 16:50:28 ociuhandu: and not to the WIndows one and my braincells just mixed them up? 16:50:40 pnavarro: cool! 16:51:05 since we are running late my 2c are on continuing the list of BPs next week 16:51:31 as we still have quite a lot of stuff in the list from the design summit 16:52:01 and from what we discussed today there's definitely enough to work for a while :-) 16:52:15 sounds good 16:52:15 but if you guys prefer we can go on now 16:52:28 alexpilotti: we have a meeting in a few mintues 16:52:30 er minutes 16:52:36 that we should just get over 16:52:38 yep 16:52:41 perfect 16:52:48 then let's continue this discussion next week 16:52:52 cool 16:53:53 ok 16:53:56 closing meeting 16:54:00 thanks everyone 16:54:04 #endmeeting