13:01:24 #startmeeting hyper-v 13:01:26 Meeting started Wed Mar 2 13:01:24 2016 UTC and is due to finish in 60 minutes. The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:30 The meeting name has been set to 'hyper_v' 13:01:44 morning everybody! 13:01:49 Hi 13:01:55 Hi 13:01:58 Hi 13:02:30 sagar_nikam: anybody else on HP side? 13:02:32 hi 13:03:51 sagar_nikam: you had some questions for FreeRDP, would you like to start with that? 13:03:56 hi... back again 13:04:07 yes alexpilotti: 13:04:14 should we discuss that 13:04:16 now ? 13:04:24 #topic #FreeRDP-WebConnect 13:04:27 yes 13:04:29 :) 13:04:47 in nova.conf, we specify the FreeRDP IP 13:04:57 the url 13:05:09 and that IP is sent by nova, which horizon uses to connect to RDP Console 13:05:18 am i right ? 13:05:31 yes, exactly like libvirt does with novnc 13:05:40 ok 13:05:58 now let us assume that freerdp is installed on the HyperV host where nova compute runs 13:06:01 it's very much the same, we wanted to keep the same identical experience 13:06:19 and we have multiple networks in the environment 13:06:27 o/ 13:06:41 tenant users access the horizon on "USER-NET" 13:06:47 the user network 13:06:48 Hi guys 13:07:14 and compute to controller commication is on a network "MGMT-NET" 13:07:25 in this case how will FreeRDP work 13:07:49 we dont want to have "USER-NET" configured on HyerV host due to security reasons 13:08:10 so when horizon requests for the console 13:08:19 how will it work ? 13:08:32 the you have two options: 1) a proxy, 2) putting freerdp-webconnect on a different host 13:08:53 how do you do it today for novnc on the libirt case? 13:09:14 need to check 13:09:32 have not used novnc yet on libvirt 13:09:38 for sometime now 13:09:46 your deployment will be mostly mixed, e.g. KVM + hyper-v? 13:09:54 yes 13:09:58 kvm_hyperv 13:10:04 kmv + hyperv 13:10:41 then I'd recommend a unified design, so that you dont need different architectural choices for novnc and freerdp 13:11:04 ok 13:11:31 need to check on novnc, as of now dont have much details 13:11:50 will check and get back if i need more clarity on FreeRDP 13:12:19 most of the hyperv deployments 13:12:29 what is the recommended approach ? 13:12:37 sagar_nikam_: sounds good, let us know! 13:12:41 having FreeRDP on compute or on a different machine 13:13:07 as we already discussed, it depends on your design, hyperconverged or not plus security implications 13:13:25 ok 13:13:57 exposing a service on a compute node directly to the user network is not a great idea, but a reverse proxy can fix that 13:14:12 agree 13:14:30 on the other side, putting freerdp on a separate cluster of nodes requires additional complexity 13:14:32 hence i was thinking of a separate machine for FreeRDP 13:14:45 how do you scale horizon today? 13:14:51 i was thinking of having 3 machines 13:15:04 all in a NLB cluster 13:15:15 and then give that cluster IP in nova.conf 13:15:32 in that way all freerdp requests will go to NLB cluster IP 13:15:32 one of the options could even be to put freerdp on the horizon nodes 13:15:40 and it gets load balanced 13:15:58 putting freerdp on horizon nodes is a good idea 13:16:09 only issue, no debian for it is availanle 13:16:16 we only have windows MSI 13:16:43 we dont have support for debian atm, but it can be added, of course 13:16:43 if a deb was available, we would have used it 13:17:03 that would be great.... if it happens 13:17:17 we will use it, as and when it is available 13:17:29 do you any plans for it ? 13:18:40 it's on the pipeline, but with a very low priority 13:18:48 ok 13:19:03 let us know when it is available 13:19:22 we can use it, test and let you know how it works 13:19:33 sure! 13:19:36 tx 13:19:39 thanks 13:19:54 do you have any other questions on freerdp? 13:19:57 in the meanwhile i will check on how novnc works in our case 13:20:13 else use another VM 13:20:13 i am done on FreeRDP 13:20:20 sonu: you have anythuing ? 13:20:54 looks like sonu and vinod are not in the meeting 13:21:05 alexpilotti: we can move to next topic 13:21:32 #topic Hyper-V clustering 13:21:40 patches are pretty much ready 13:21:58 ok 13:22:01 we're going to start backporting to compute-hyperv pretty soon 13:22:18 backporting ? 13:22:27 to liberty ? 13:22:35 or just merging in mitaka 13:22:35 so if you guys want to backport on your Liberty branch, times are pretty much ripe 13:23:12 you mean cluster driver has been backported in liberty already ? 13:23:14 i think alexpilotti meant to say "include"it in compute-hyperv, mitaka 13:23:14 adding to compute-hyperv, not backporting, wrong verb in this case 13:23:19 in compute-hyperv ? 13:23:28 yeah of course 13:23:29 ok 13:23:49 as usual, patches are available upstream in Nova, for eventual merging 13:23:50 so it will be merged in compute-hyperv mitaka branch 13:24:03 and in the meantime we add in compute-hyperv 13:24:11 ok 13:24:13 yes, like everything else 13:24:30 hopefully one day our nephews will see those patches merged in Nova 13:24:36 :) 13:24:41 as mentioned in last IRC, we are still on liberty, we can test it when we move t Mitaka 13:25:04 do you have any deadline for Mitaka? 13:25:15 however if you decide to backport to liberty, kmb: has setup a cluster today 13:25:27 we can start from next week 13:25:37 not sure of Mitaka 13:25:44 i think couple of months 13:26:05 in our case backporting would still mean compute-hyperv (kilo, liberty) 13:26:19 we dont backport to Nova, as we don't use it 13:26:38 yes, we can try picking from the compute-hyperv n libety 13:27:30 we'll let you know of course if / when we will backport that patchset 13:27:37 sure 13:27:40 that depends a lot on customer demand 13:27:51 my team mate kmb: has setup the cluster today 13:27:51 ok, moving on 13:27:58 sure 13:28:17 unless there are other questions on this topic of course 13:28:32 no questiosn from my end 13:28:57 cool 13:29:05 #topic networking 13:29:21 claudiub: anything to add on recent improvements? 13:29:53 nope. just adding os-win in networking-hyperv. making sure things work properly. 13:30:15 hyper-v ci says (s)he's happy for now. 13:31:15 that's all from me, if anyone else has anything else to add on this topic, go ahead 13:32:06 k, next topic? :) 13:32:20 sagar_nikam_: are you still doing perf testing? 13:32:40 i was speaking to sonu: yesterday 13:32:43 on this topic 13:32:44 claudiub: all utils in networking-hyperv are in os-win, correct? 13:32:54 alexpilotti: yep. 13:33:00 i think it is being planned again after few weeks 13:33:07 but sure of the plan 13:33:17 so sagar_nikam_ on our end networking-hyperv is ready for mitaka 13:33:32 it all depends on getting a slot for perf testing 13:33:39 if you guys have anything else in mind we'd be happy to address that 13:34:13 i think sonu has some question on ovs2.6 in the last meeting 13:34:34 ok, I dont see him online today 13:34:43 yes 13:34:47 but is he done w it? 13:34:52 both he and vinod seem to be away 13:35:06 lets chat on this topic again next week 13:35:14 ok sure, we can move on I think then 13:35:20 yes 13:35:31 #topic mitaka release 13:35:46 we're going to wrap up as soon as M3 is out 13:36:24 ok 13:36:38 and dedicate as usual the period between that and release to do tons of integration testing 13:36:55 in all possible supported configurations 13:37:32 for both the Nova hyper-v anc Cinder SMB scenarios 13:37:44 ok 13:37:54 which also includes testing on Python3 13:38:21 are we done with pyMI ? all things merged ? 13:38:32 any patches pending ? 13:39:12 Pymy reached 1.0.0, signed release 13:39:24 ok 13:39:25 and it has been included in OpenStack's global-requirements 13:39:37 that's good 13:40:02 no pending issues 13:40:12 ok 13:40:27 we're going to add some more MI API coverage, but that's not needed for Nova, etc 13:40:41 ok 13:41:12 #topic Shielded VMs 13:42:06 things are getting ready there as well, but we might wait some time before releasing to ensure that the Hyper-V API are stable 13:42:20 since this is based on 2016 prerelease 13:42:40 ok 13:42:56 just wanted to mention it here, to keep the community up to date 13:43:04 ok that was my last topic 13:43:12 #topic open discussion 13:43:30 anything that anybody would like to add before wrapping up? 13:44:01 nothing as of now from my end 13:44:35 ok, thanks everybody for joining today's meeting! 13:44:42 #endmeeting