13:00:31 <claudiub> #startmeeting hyper-v
13:00:32 <openstack> Meeting started Wed Oct  5 13:00:31 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:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:36 <openstack> The meeting name has been set to 'hyper_v'
13:00:47 <claudiub> hellou
13:01:02 <claudiub> gonna wait a bit for people to join
13:01:50 <sagar_nikam> Hi
13:02:39 <claudiub> hello :)
13:02:57 <claudiub> sagar_nikam: anyone else joining?
13:03:49 <atuvenie> hi all
13:03:54 <claudiub> hello :)
13:03:56 <sagar_nikam> no
13:04:00 <sagar_nikam> we can start
13:04:17 <claudiub> cool
13:04:30 <claudiub> #topic nova patches
13:04:56 <claudiub> sooo, just fyi, we already merged 2 blueprints in ocata in nova
13:05:05 <sagar_nikam> nice !!!
13:05:07 <sagar_nikam> which ones ?
13:05:20 <claudiub> those are the Hyper-V UEFI one, and the storage QoS one.
13:05:27 <claudiub> #link Hyper-V storage QoS support patch: https://review.openstack.org/#/c/175479/
13:05:36 <claudiub> #link Hyper-V UEFI Secure Boot https://review.openstack.org/#/c/209581/
13:05:55 <claudiub> there have been a couple of python3 related patches that merged too
13:06:06 <lpetrut> hey guys
13:06:10 <sagar_nikam> any progress on FC ?
13:06:15 <sagar_nikam> in ocata
13:06:15 <claudiub> and I can say that nova-compute on Hyper-V works well with python 3
13:06:41 <sagar_nikam> any perf improvement after moving to python 3
13:06:41 <sagar_nikam> ?
13:07:06 <claudiub> the os-brick in nova patch is still pending.
13:07:21 <claudiub> #link os-brick in nova patch: https://review.openstack.org/#/c/273504/
13:07:33 <claudiub> the blueprint is approved, and it got some core review on it
13:07:38 <claudiub> soo, yeah
13:08:02 <sagar_nikam> ok
13:08:15 <claudiub> also, for the Hyper-V OVS vif driver, the blueprint is approved, and the patch no longer has a -2. still waiting reviews
13:08:39 <claudiub> as for the python 3 performance impact: we didn't do rally tests against it yet
13:08:52 <claudiub> but python 3 is typically slower than python 2.7
13:09:17 <lpetrut> on the other hand, WS 2016 seems to bring some considerable performance improvements
13:09:37 <sagar_nikam> lpetrut: that is irrespective of python 3 ?
13:09:45 <lpetrut> yep
13:09:48 <claudiub> yeah, so it can potentially balance it out. :)
13:10:50 <claudiub> as for blueprints, we still have the shielded vms spec up for review.
13:10:59 <claudiub> didn't get much attention
13:11:18 <sagar_nikam> ok
13:11:28 <claudiub> questions?
13:11:35 <sagar_nikam> no
13:11:41 <sagar_nikam> not much as of now
13:11:53 <claudiub> moving on
13:11:58 <claudiub> #topic PyMI release
13:12:07 <claudiub> soo, PyMI 1.0.4 was released.
13:12:15 <claudiub> #topic PyMI release: https://pypi.python.org/pypi/PyMI
13:12:23 <claudiub> feel free to grab it
13:12:37 <claudiub> as mentioned in the previous meetings, it boasts better performance. :)
13:13:12 <sagar_nikam> ok.. we will check it
13:13:57 <claudiub> #topic monasca status
13:14:08 <claudiub> ehm, I have to rebase pretty much everything again :)
13:14:24 <claudiub> also got some comments. will have to check them out.
13:14:58 <sagar_nikam> why ? the last time they were almost fine and just wanted some documentation
13:15:21 <claudiub> don't know if I've mentioned this previously, but I've also sent a patch adding documentaion
13:16:06 <claudiub> yeah, will have to check the comments. it probably won't be anyting big anyways
13:16:10 <sagar_nikam> the last time we discussed this... you attended a meeting with monasca team and they were fine with the code except docs
13:16:23 <claudiub> yep
13:17:13 <sagar_nikam> so new code comments again ?
13:17:25 <claudiub> yep. anyways, will sort it as soon as i can
13:17:44 <sagar_nikam> ok
13:17:54 <sagar_nikam> thanks
13:17:58 <claudiub> np :)
13:18:41 <claudiub> #topic open discussion
13:19:08 <claudiub> hm, so there are a couple of things that I want to mention here
13:20:01 <claudiub> first of all, on your hyper-v compute nodes, you should change the neutron_hyperv_agent.conf's firewall_driver to hyperv.neutron.security_groups_driver.HyperVSecurityGroupsDriver
13:20:57 <claudiub> starting with ocata, the old value will no longer work
13:21:09 <sagar_nikam> ok ...
13:21:21 <sagar_nikam> so this is for ocata only ?
13:22:18 <claudiub> #info The neutron_hyperv_agent.conf firewall_driver config value must be changed to hyperv.neutron.security_groups_driver.HyperVSecurityGroupsDriver when upgrading to Ocata
13:22:41 <claudiub> the old value has been deprecated since mitaka
13:22:51 <claudiub> still works, but in ocata it won't work anymore
13:23:03 <claudiub> for more info, see patch:
13:23:11 <sagar_nikam> ok got it. will mention it to sonu
13:23:20 <claudiub> # Removes remaining Hyper-V plugin in neutron: https://review.openstack.org/#/c/378299/1
13:23:27 <claudiub> #link Removes remaining Hyper-V plugin in neutron: https://review.openstack.org/#/c/378299/1
13:23:45 <claudiub> the docs have been updated as well.
13:24:59 <claudiub> secondly, there has been a bug affecting python 3 on hyper-v, on python-swiftclient, which has been fixed and merged
13:25:08 <claudiub> #link https://bugs.launchpad.net/python-swiftclient/+bug/1628107
13:25:09 <openstack> Launchpad bug 1628107 in python-swiftclient "Futures package should not be installed for python 3" [Undecided,Fix released] - Assigned to Claudiu Belu (cbelu)
13:26:04 <claudiub> basically, python-swiftclient was installing the futures library in python3, and it shouldn't have, as, ironically, futures is not python 3 compatible
13:26:13 <claudiub> python 3 comes with a native futures library anyways
13:26:26 <sagar_nikam> why is this affecting hyperv ? nova's requirements.txt has it and hence it gets installed on nova compute for hyperv ?
13:27:11 <claudiub> it does, but if you check the requirement, it says that it will only be installed on python 2.6 or python 2.7
13:28:10 <claudiub> futures>=3.0;python_version=='2.7' or python_version=='2.6' # BSD
13:28:29 <claudiub> that line basically means that futures>=3.0 will be installed if the python version is 2.7 or 2.6
13:28:58 <sagar_nikam> ok
13:30:15 <claudiub> also, currently working on solving some of the tests that are failing on the ci
13:30:39 <claudiub> seems i'll have to send a patch up, most probably oslo.messaging
13:31:06 <claudiub> anyways, that's about it from me
13:31:15 <claudiub> sagar_nikam: any news from your side?
13:31:19 <sagar_nikam> one point from me
13:31:31 <sagar_nikam> i am planning to start off on kubernetus
13:31:39 <sagar_nikam> how is it going ?
13:31:46 <sagar_nikam> anything that i can try
13:32:05 <claudiub> atuvenie: hi
13:32:24 <atuvenie> heya, what are your plans there sagar?
13:32:58 <atuvenie> the aprenda folks have a WIP pull request that is on the K8 repo
13:33:14 <atuvenie> I'm helping in the review process with that
13:33:26 <sagar_nikam> first of all.... kubernetus is new to me
13:33:43 <sagar_nikam> i will start some initial learning and trying out basic things
13:33:56 <sagar_nikam> and then if something is ready for windows, i can try that
13:34:01 <sagar_nikam> and provide you feedback
13:34:02 <atuvenie> on the other side, I'm still playing with OVN to setup a overlay network like k8 needs, but it's kinda slow
13:34:56 <sagar_nikam> so as of now, basic k8s tests with windows also not a good option ?
13:35:25 <sagar_nikam> i am starting on k8s may be in a week or 10 days.. and will try for few weeks
13:35:32 <sagar_nikam> and then i can try with windows
13:35:33 <atuvenie> well, you can use the pull request that is currently under review
13:35:55 <sagar_nikam> so may be a month from now, i can try k8s for windows
13:35:59 <atuvenie> using that, I can create pods but networking is still a issue for me
13:36:04 <sagar_nikam> any docs available
13:36:10 <sagar_nikam> on how to use it ?
13:36:44 <sagar_nikam> and containers are windows containers ?
13:38:06 <atuvenie> containers are indeed windows containers
13:38:13 <atuvenie> have not tried with hyper-v containers
13:38:17 <sagar_nikam> ok
13:38:28 <sagar_nikam> so let me try k8s on linux first
13:38:36 <sagar_nikam> just basic hands on
13:38:41 <sagar_nikam> to get familar
13:38:54 <sagar_nikam> and then may be i will reach out to you to try on windows
13:39:06 <sagar_nikam> is that fine ?
13:39:32 <atuvenie> sure
13:39:52 <sagar_nikam> ok thanks
13:40:17 <sagar_nikam> next question
13:40:36 <sagar_nikam> claudiub: any plans on monasca-log ?
13:40:55 <claudiub> sagar_nikam: didn't look at it yet
13:41:08 <sagar_nikam> ok
13:41:13 <sagar_nikam> is that planned ?
13:41:27 <sagar_nikam> did the monasca team mention anything sbout it
13:41:31 <sagar_nikam> about it
13:41:48 <claudiub> no they haven't. it is a bit low on my priority list, to be honest
13:42:33 <claudiub> my main concern is nova and work on it. when I don't have anything to do there, and i have some free time, I can take a look
13:42:53 <claudiub> sagar_nikam: any news from the testing lab?
13:43:00 <sagar_nikam> ok sure got it
13:43:11 <sagar_nikam> no... getting slot has been difficult
13:43:28 <sagar_nikam> may be pushed by some more time
13:43:38 <claudiub> ack
13:43:38 <sagar_nikam> will let you know as and when we start it
13:43:58 <sagar_nikam> we plan to test it on mitaka
13:44:20 <claudiub> sounds good
13:44:27 <sagar_nikam> i was told by sonu that some neutron-agent code may not scale
13:44:32 <sagar_nikam> we are not sure though
13:44:57 <sagar_nikam> the last time, sonu's team picked some code from mitaka and put it in liberty
13:45:04 <sagar_nikam> and found sclability issues
13:45:11 <sagar_nikam> we reverted it back to liberty
13:45:24 <sagar_nikam> and we achieved good performance
13:45:31 <sagar_nikam> may be it just a backport issue
13:45:35 <sagar_nikam> cant confirm
13:45:40 <claudiub> there shouldn't have been any performance regressions from liberty to mitaka
13:46:02 <claudiub> from our tests, mitaka was performing significantly better than liberty
13:46:19 <sagar_nikam> i think we would have taken only some pieces of code
13:46:20 <claudiub> we presented those results a few months ago
13:46:35 <sagar_nikam> we will try with full mitaka
13:46:44 <sagar_nikam> rather than just some code backported
13:47:21 <claudiub> ok
13:47:31 <claudiub> well, that's about it from me
13:47:42 <claudiub> any other questions from you, sagar_nikam?
13:47:56 <sagar_nikam> no not as of now
13:48:23 <claudiub> well then, we can end the meeting soon. :)
13:48:23 <sagar_nikam> how is the summit plans going ?
13:48:50 <claudiub> well, we're currently working on demo's and other cool booth setups
13:49:16 <claudiub> hopefully it will be an enjoyable summit. :)
13:49:30 <claudiub> because after this, the summits won't be the same
13:49:37 <claudiub> as the summit will split into 2
13:49:41 <sagar_nikam> why ?
13:49:50 <sagar_nikam> oh ... what is that
13:49:53 <sagar_nikam> dont know about it
13:49:55 <claudiub> into the general public / marketplace summit, and the design summit
13:50:02 <sagar_nikam> ok
13:50:12 <claudiub> which will be in 2 separate locations, in 2 separate dates
13:50:17 <claudiub> i don't really know the reason
13:50:47 <sagar_nikam> ok
13:51:03 <sagar_nikam> i am done with all topics... thanks
13:51:11 <claudiub> well then, thanks folks for joining, see you next week!
13:51:33 <claudiub> #endmeeting