13:00:11 #startmeeting hyper-v 13:00:12 Meeting started Wed Aug 31 13:00:11 2016 UTC and is due to finish in 60 minutes. The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:16 The meeting name has been set to 'hyper_v' 13:00:19 hello folks! 13:00:21 Hi 13:00:22 anyone here? 13:00:23 hello 13:00:32 Hi everyone 13:00:40 Hi claudiub: 13:01:05 cool, we can start 13:01:11 hi 13:01:29 #topic monasca patches 13:01:38 ehm, got no reviews on them. :/ 13:01:47 oh .... 13:02:02 roland was on vacation for some time, as far as i know 13:02:15 yes he was on vacation 13:02:20 let me check if he is back 13:03:47 anyways. did you guys try monasca on windows? 13:04:02 any feedback on it? 13:04:16 i could not.... finding it difficult with liberty controller 13:04:25 and mitaka monasca 13:04:35 i see. 13:04:44 sorry .... got it confused again 13:04:53 mitaka controller with newton monasca 13:05:25 what exactly isn't working? 13:06:44 getting all the 14 dependent patches 13:07:08 in right order and getting them compiled on windows 13:07:17 to generate the exe 13:07:27 for me to start the agent 13:07:55 however not spent too much time on it 13:08:06 i may have missed something basic 13:09:13 gerrit typically lists the patches in the correct order 13:09:39 for example, this is the base patch: https://review.openstack.org/#/c/317919/ 13:09:56 and on the right, you see from bottom to top the order of the patches. 13:11:02 just sent a mail to Roland 13:11:06 asking for review 13:11:17 hopefully we can get some review comments 13:11:39 yeah. but we do have to keep in mind that this week is the feature freeze. 13:12:08 oh ... 13:12:18 even for monasca ? 13:12:30 for every project 13:12:40 ok 13:13:14 here's the release schedule: https://releases.openstack.org/newton/schedule.html 13:13:41 next thing will be in sep 12, RC1. 13:14:35 anyways, I hope we can still get in some patches. 13:14:39 moving on. 13:14:47 #topic OVS vs networking-hyperv 13:15:00 soo, abalutoiu has been doing some experiments 13:15:12 mind sharing some of your results, abalutoiu? 13:15:18 sure 13:17:26 so, I've been running tests to find the maximum throughput through OVS vs networking-hyperv, tests show 3.65 Gbps VM to VM over a single VXLAN tunnel on a 10 Gb NIC, while with networking-hyperv the performance was 4.95 Gbps 13:18:11 there is also a new OVS under development, which was also tested, and the performance was 4.80 Gbps under the same conditions 13:18:11 Ovs dpdk will help improve that I would guess 13:19:34 the new OVS also includes conntrack support, that means the OVS native firewall can be used instead of the windows ACLs 13:20:28 Using native ovs firewall will expose a challenge of live migration 13:20:54 why? 13:21:19 Who will build the firewall rules on the target host... 13:21:28 Neutron will have to do. 13:22:28 yeah, neutron will have to do it. doesn't it already do this anyways? 13:22:29 Who would intimate Nova or neutron to create ports and ovs rules on the port 13:22:54 Cluster level live migration will be transparent to neutron and nova 13:23:22 Unless we invoke migration through Nova migrate utility 13:24:16 Am I missing any point that you are seeing 13:24:31 so, when you do a nova cold / live migration, nova will create the ovs ports on the destination in advance. 13:25:22 Sonu_: are you referring to MSCluster and Nova cluster driver ? 13:25:57 when you mentioned "Cluster level live migration" 13:26:06 even on a failover migration, the destination node will detect a new vm and create the ovs port. 13:26:39 the nova hyper-v cluster driver will detect a new vm and create its ovs port * 13:26:53 Live migrations triggered from ms cluster I refer to 13:27:20 VM ports must be created on br-int, who will do? 13:28:03 Who will notify Nova to do? Once a port is created, then neutron will bind rules 13:28:21 the nova hyper-v cluster driver does it. 13:28:33 the nova hyper-v cluster driver creates the port. 13:28:55 OK then I get what you are saying. 13:30:43 anyways, thanks abalutoiu for the tests results. :) 13:31:52 #topic Barcelona OpenStack Summit 13:32:38 sooo, there is only one windows specific presentation in Barcelona 13:33:02 One more item under ovs topic 13:33:10 #undo 13:33:11 Removing item from minutes: 13:33:29 I see ovs is certified for Windows 2k12 13:33:41 yep. and 2012 r2 as well 13:33:48 we announced it last week. :) 13:34:01 How can we consume the driver? 13:34:23 Should we build the driver ourselves, will the certification be valid 13:34:32 you mean OVS itself? 13:34:50 I mean the extension driver 13:35:00 you can download the installer from here: 13:35:10 # Windows OVS installer: https://cloudbase.it/openvswitch/ 13:35:36 Can we ship the extension driver alone as part of our package 13:36:31 We don't have MSI based installation mechanics 13:37:20 installing the MSI is simple, you can do so by just running: msiexec /i openvswitch-hyperv-2.5.0.msi /l*v log.txt 13:37:24 claudiub: we build our nova and neutron from our downstream branch 13:37:51 MSIs can be installed in unattended mode. 13:37:58 hence we dont use CloudBase MSI 13:39:57 Sonu_: honestly, I don't know how to answer that question. 13:40:27 as far as I know, OVS was certified with the installer in its entirety. 13:40:50 Yes and that's Microsoft's specification I think 13:40:57 yep 13:41:20 Once certified can we ship the extension driver with our installation 13:41:32 So, I'm not sure Microsoft certification can be claimed without the installer. 13:41:47 well, the installer is free anyways 13:41:53 May be I can start a email chain to discuss this. 13:42:00 sure. 13:42:07 Thanks 13:42:26 claudiub: thanks 13:42:31 np. :) 13:42:38 #topic Barcelona OpenStack Summit 13:42:42 we hope to use OVS soon 13:43:13 soo, there was only session that was accepted, out the many Windows / Hyper-V related sessions submitted 13:43:34 the session is called: "What's new for Windows in OpenStack Newton" 13:43:42 ok 13:44:10 soo, if you are going to attend the Summit, you might be interested in it. :) 13:44:15 claudiub: i check with Paul Murray. he is at the summit. we discussed about this last week 13:44:51 he is coming from our team 13:44:51 cool, speaking of which, are you guys going to attend? 13:44:54 to the summit 13:45:15 Sonu_: anybody from networking team attending the summit ? 13:45:44 I might be there 13:46:06 Sonu_: cool... nice 13:47:08 cool. :) Sonu_: just FYI, there is going to be a Winstackers work session as well. So, feel free to join us. :) 13:47:21 I will thanks. 13:47:41 #topic Open discussion 13:48:24 not much topics from my side 13:48:43 first of all, as you know, feature freeze is going to be this week. I already did release candidates for networking-hyperv and os-win. 13:49:05 and the final release will be done in the next 1-2 weeks. 13:49:27 up next would be release testing 13:49:53 ok 13:50:22 as we do every cycle, we run tempest for each and all supported Hyper-V versions, with all kinds of scenarios: networking-hyperv, ovs, etc. 13:50:32 also, python 2.7 and python3.4 13:50:37 so, this will take a while. 13:51:16 Sonu_: one question. migration from networking-hyperv to ovs 13:51:26 you had anything to discuss on that 13:51:36 we'll probably have to do some bug hunt for python 3.4, though. 13:52:51 anything else you guys want to discuss? 13:53:14 claudiub: my question to sonu 13:53:25 you want to discuss anything on that topic 13:53:38 networking-hyperv to ovs migration 13:53:55 we had a mail discussion few days back... not much since then 13:57:38 c64cosmin: welcome.... anywork happening on freerdp .. or is it on low priority 13:59:19 c64cosmin_: ^ 13:59:32 claudiub: roland has replied 13:59:37 you saw that ? 13:59:47 hey sagar_nikam, low priority for now 13:59:52 sorry 14:00:03 c64cosmin: sure no problem 14:00:23 sagar_nikam: yep. saw it now. replying. 14:00:29 c64cosmin: just checking 14:00:39 claudiub: thanks 14:00:53 anyways, Sonu seems to have disconnected. 14:01:01 and we've passed our time limit. 14:01:05 we have to end it here. :) 14:01:14 thanks folks for joining, see you next week! 14:01:20 thanks 14:01:25 #endmeeting