12:59:49 #startmeeting hyper-v 12:59:50 Meeting started Wed Aug 24 12:59:49 2016 UTC and is due to finish in 60 minutes. The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:59:52 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:59:54 The meeting name has been set to 'hyper_v' 13:00:10 helloo 13:00:15 waiting for people to join 13:02:14 hello all 13:02:55 Hi All 13:03:07 helloo. :) 13:03:16 sagar_nikam: anyone else joining us? 13:03:48 claudiub: i think no.. we can start 13:03:53 yeay 13:04:17 #topic OpenvSwitch certification status 13:04:32 soo, about this, there are 2 good news, and one bad news. 13:04:44 one of the good news is that there is no bad news. :) 13:04:54 the other good news is that it is done. 13:05:31 #link Windows Server Catalog entry for OpenvSwitch: https://www.windowsservercatalog.com/item.aspx?idItem=18117a8c-c7bf-f20c-9185-3a53117b9875&bCatID=1638 13:05:55 you mean microsoft certification for OVS is done ? 13:06:00 yep 13:06:05 wow !!!!! 13:06:08 thats great 13:06:13 yep. :) 13:06:19 thank you all from cloudbase for getting it done 13:06:26 no problem. :) 13:06:59 ok, next topic. 13:07:30 #topic designate patch status 13:07:37 merged. 13:08:03 #link Microsoft DNS Server backend support in designate: https://review.openstack.org/#/c/332703/ 13:08:09 looks like ... today it is good news day !!!! 13:08:25 :D 13:08:35 for now. :D 13:08:43 hey guys 13:09:06 #topic Hyper-V OVS VIF plug driver 13:09:28 #link Windows support for OovsPlugin in os-vif: https://review.openstack.org/#/c/344433/ 13:09:31 this has a +2 13:09:34 yeay 13:09:55 the patch on nova though has a -2. naaay. 13:10:21 so, I'll have to reach an agreeable solution with danpb for this. 13:10:42 might have to make another patch to os-vif. 13:10:57 ok 13:11:07 next topic 13:11:12 can it make it to O ? 13:11:21 i hope it can still make it in N. 13:11:21 os-vif changes 13:11:27 i mean nova changes 13:11:34 ok... thats good 13:11:48 we have until next week, i think to get it merged. 13:12:07 as next week it is going to be feature freeze 13:12:19 ok 13:12:32 next topic 13:12:54 #topic monasca patches status 13:13:33 I've sent an email with logs, config files, metrics definitions and samples collected from my Windows Server 2012 R2 node. 13:13:55 might have to write a couple more unit tests. 13:14:09 but IMO, it is mergeable. 13:14:49 monasca doesn't have any tempest test that validates the agent 13:15:09 monasca doesn't have any tempest test that validates the agent's functionality or its collected metrics, so I guess that makes them hesitant when accepting code. 13:15:58 didn't get much review though.. 13:16:42 well, the monasca meeting is in 2 hours. going to sneak in there and push a little. 13:17:44 anyways, next topic 13:17:58 #topic Barcelona OpenStack Summit 13:18:34 claudiub: let me try to check with monasca core team 13:18:36 soo, most of us are going to be there. There is also going to be a Winstackers work session as well. 13:18:39 i will reach out to them 13:19:08 sagar_nikam: from your team, who is going to go to the Barcelona Summit? 13:19:29 i think sonu: 13:19:34 let me ask 13:19:41 that is from india team 13:19:53 i think paul murray will be there 13:21:08 cool. this is just an fyi, you folks welcome to join the work session. :) 13:22:04 #topic Hyper-V Cluster spec 13:22:27 claudiub: i will let sonu know about it 13:22:29 well. it didn't get any reviews yet. 13:23:07 :( 13:24:30 sagar_nikam: do you think you can try to get some help on this? 13:24:56 we could use some help in getting it approved. :) 13:25:13 the BP ? 13:25:17 yeo 13:25:19 yep 13:25:30 otherwise the nova-core is just going to ignore it 13:25:31 ok let me try 13:25:31 link please ? 13:25:32 ok let me try 13:25:33 link please ? 13:25:49 #link Hyper-V Cluster spec: https://review.openstack.org/#/c/350559/ 13:26:04 thanks. i will try 13:26:10 cool. thanks! 13:26:20 #topic open discussion 13:26:31 well, that all the news from me. 13:26:44 anything else that needs to be discussed? 13:29:27 claudiub: i did a clone on monasca-agent 13:29:36 newton 13:29:45 cool. did it work? 13:30:04 initial thoughts ... it looks a bit complex to backport your patches to Mitaka 13:30:14 i tried only today 13:30:19 so will try again 13:30:23 yeah, that's what i said. 13:30:33 that's why i suggested trying the newton monasca-agent branch 13:30:45 ok ... one more idea 13:30:53 what if i take newton branch 13:30:59 and then your patches 13:31:07 and try to connect to my mitaka controller ? 13:31:10 will it work 13:31:14 yeah, that's what i was suggesting. 13:31:20 nova will work.. not sure monasca will work 13:31:30 ah .... i missed that point 13:31:36 ok ... will try tomorrow 13:31:45 not sure either, but it doesn't hurt to try. :) 13:31:58 have you tested with devstack ? 13:32:16 yeah 13:32:27 ok ... 13:32:34 let me try first with my setup 13:32:37 that;s how i got it working, and how i tested it. :) 13:32:44 else i will try with devstack 13:33:06 if all the 14 patches merge... are we done with monasa for hyperv ? 13:33:17 you've seen my mail to the monasca folks, right? i've included a link with config files, logs, and so on. 13:33:38 yes ... saw that 13:33:41 nice... 13:33:59 sagar_nikam: yeah, if you use all the checkers i've mentioned in the email 13:34:08 good 13:34:15 cpu, disk, host_alive, hyperv, iis, memory, network, process, wmi_check 13:34:23 what is the plan on monasca-log ? 13:34:46 i haven't tried any other checkers, but roland said that those are good enough, as they are the most used 13:35:12 i didn't try monasca-log yet. 13:35:38 are you planning ? 13:36:01 is that required as part of monasca support for hyperv ? 13:36:22 i'll give it a shot, if time allows it 13:36:39 but it's optional, IMO. 13:36:45 ok 13:37:12 if we can get the monasca-agent patches in, I'd be happy with the result for this cycle. :) 13:37:24 i will try to get it reviewed 13:38:23 now moving on... what's new coming in O 13:38:29 not just nova 13:38:35 other components as well 13:38:39 for hyperv 13:39:02 we're thinking about it, and building a list. we'll have to propose blueprints and specs for most of them. 13:39:16 ok 13:40:10 for now, merge the stuff that didn't get in this cycle: nova: vNUMA support, setting instance boot order, boot from ISO, set disk / volume QOS, UEFI secure boot, shielded VMs. i might be missing a few one. 13:40:17 the code is up for those already. 13:40:26 ok 13:40:33 that is a big list 13:40:40 as for other things: we're going to take a look at SRIOV, PCI device passthrough. 13:40:53 ok 13:41:11 freezer support will be in O as well. 13:41:18 ok 13:41:25 it isn't done yet. 13:41:28 magnum ? 13:42:02 magnum works as long as kubernetes / docker swarm / mezos works on windows. 13:42:16 ok 13:42:28 so, that's not tied to any openstack release cycle. 13:42:56 i think manila support is already there 13:43:26 other than that, we're going to add objects to os-win, which will make it more user-friendly and easier to understand and work with. plus, it will improve the instance spawn times. 13:43:30 sagar_nikam: yep. 13:44:02 claudiub: what change in os-win to speed instance spawn ? 13:44:08 currently, we're working on adding a Windows / Hyper-V CI for the oslo libraries, so we know that they won't break us in the future. :) 13:45:21 sagar_nikam: so, as you know, the time needed to spawn an instance on hyper-v was greatly reduced thanks to os-win and pymi. Last time we tested it, the spawn time was close to the libvirt times. We can reduce it even more. :) 13:45:39 that is intresting 13:45:55 i agree that os-win and pymi improved the perf drastically 13:46:07 the thing is, currently the hyper-v nova driver queries for the vm object for every operation: update_vm, attach_disk, attach_nic, power_on, and so on. 13:46:11 just curious to know what more is planned 13:47:08 ok got it 13:47:14 so, if we don't query the vm object every single time, the time improves. WMI queries can take a lot of time, and that's why we reduced and optimised them. 13:48:11 anyways. 13:48:34 python3 support is still a must. 13:48:53 nova still requires a lot of changes for that. 13:49:55 anyways, if there are any other features we should consider, let us know. :) 13:50:23 livirt driver 13:50:32 is adding lot of support for NFV usecases 13:50:50 may be we can try some of those as BPs for hyperv 13:51:18 well, the vNUMA is used for the NFV usecases, as well as sriov and pci passthrough. 13:51:31 agree 13:52:31 you guys have some nfv usecases / environment for it? once we're done, it would be cool to see how the performance on hyper-v compares to kvm. 13:52:58 yes... i think 13:53:14 let me check with scale team 13:53:30 i will get back on it 13:53:39 atleast the usecase tried for libvirt 13:53:45 in scale tests 13:54:07 not sure if we can get access to that setup... will try 13:54:14 cool, let me know when you find out. :) 13:54:55 anything else you'd like to discuss? 13:55:16 i think if we can achieve the perf on par with libvirt 13:55:25 for NFV usescases 13:55:31 then it would be amazinf 13:55:36 amazing 13:55:51 especially with windows nano 13:56:02 i think it will be a good fit for NFV 13:56:05 yep. :) that would be great. :D 13:56:08 what is your opinion 13:56:18 windows nano for NFV ? 13:56:53 NFV is a big usecase ..especially for libvirt 13:56:57 hm, don't really know. I haven't tried nano yet. 13:57:06 ok 13:57:12 we are almost done with time 13:57:18 thanks for the 2 good news 13:57:35 hopefully next few weeks we will have the 3rd good news on monasca 13:57:35 no problem. :) 13:57:46 agree to that. :) 13:57:53 i am done 13:58:02 anything from your end ? 13:58:05 well then, we can end the meeting here. :) 13:58:14 sure thanks !!! 13:58:29 bye folks, thanks for joining. see you next week! 13:58:32 #endmeeting