Tuesday, 2018-10-23

*** chhagarw has joined #openstack-powervm00:47
*** chhagarw has quit IRC00:51
*** chhagarw has joined #openstack-powervm03:58
*** mujahidali has joined #openstack-powervm13:52
*** mujahidali has quit IRC13:53
*** mujahidali has joined #openstack-powervm13:56
*** mujahidali has quit IRC13:56
*** mujahidali has joined #openstack-powervm14:00
*** edmondsw has joined #openstack-powervm14:00
edmondswI will be a few minutes late starting the meeting14:01
edmondsw#startmeeting PowerVM Driver Meeting14:08
openstackMeeting started Tue Oct 23 14:08:37 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.14:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:08
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)"14:08
openstackThe meeting name has been set to 'powervm_driver_meeting'14:08
edmondswefried: mdrabe: mujahidali: getting started14:09
edmondsw#link agenda https://etherpad.openstack.org/p/powervm_driver_meeting_agenda14:10
edmondsw#topic In-Tree Driver14:10
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:10
edmondswI've been working on a bug fix IT: https://review.openstack.org/#/c/610174/14:11
edmondswI think we're pretty close to merging that, and I will propose the same for OOT14:12
edmondswanything else to discuss IT?14:12
efriednot here14:13
edmondsw#topic Out-of-Tree Driver14:13
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:13
* efried saves for device passthrough topic14:13
efriednothing else from me14:13
edmondswceilometer-powervm tests were broken by a requirements change, but I think we have those working again now14:14
edmondswlast I checked there was still a commit pending to re-enable testing with ceilometer master in the gate instead of with ceilometer stable/rocky14:15
edmondswoh, good... looks like that finally merged: https://review.openstack.org/#/c/609823/14:15
efriedin what repo?14:15
edmondswI think we're still going to need to backport that to rocky14:16
edmondswwhich will enable testing with stable/rocky changes that haven't been tagged in a new ceilometer release yet14:16
edmondswI'll propose that today14:17
efriedwill need to be done manually.14:17
edmondswAnd then as mentioned above, I'll propose the bug fix I've been working on IT14:17
edmondswefried it certainly won't be a clean backport14:18
efriedIf you're on a roll, you could also do that pypowervm py37 thing that's been back-burnered for a while. py37 is heating up.14:18
edmondswefried I don't know that I'm on that much of a roll :)14:18
edmondswI still have that on my todo list, but I have no idea when I'll be able to get to it14:19
efriedbug 1785255  (<== /me checks whether we've got that bot in here)14:19
openstackbug 1785255 in pypowervm "py3.7 test failures" [Undecided,Confirmed] https://launchpad.net/bugs/178525514:19
edmondswas for py37, since you brought that up... I've been trying to follow all the ML posts and commenting on related commits as we determine which py3.x will be supported going forward, etc.14:19
edmondswthat brings up a whole bunch of issues for us14:20
edmondswa quick rundown from the top of my head:14:20
edmondsw1) Ubuntu 18.04 isn't supported on PowerVM, so the newest we can test with is py3514:20
efriedunless we install py37 on whatever ubuntu we do support??14:21
efriedit's not like py37 won't run on older ubuntus. It's just not what's shipped there.14:21
edmondswI don't know if that's possible. I've been tackling that more from the perspective of a) trying to get OpenStack to keep support for py35 and b) trying to get Ubuntu 18.04 supported on PowerVM at least for NovaLink14:21
edmondswbut yeah, should probably try to figure out what can be done to run py37 on Ubuntu 16.0414:22
efriedI've got it running on my victim rn14:22
efriedthat's where we were testing and debugging the pypowervm stuff, remember?14:23
edmondsw2) we're supposed to start testing py36 or py37 in both UT and CI14:23
edmondswefried true... did you pull it down from source or find a deb?14:23
efriedtrying to figure that out now. I may have pulled a tarball. It's not in dpkg14:23
edmondswI'll try to figure out if whatever deb(s) for py36 in Ubuntu 18.04 will work in Ubuntu 16.0414:24
edmondswthis transitions into CI discussion, so...14:25
edmondsw#topic PowerVM CI14:25
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)"14:25
edmondswWe merged a CI change yesterday to get local2remote working in py314:26
edmondswso that mujahidali can work on getting the CI to run as py3 instead of py214:26
edmondswmujahidali did you get a chance to try that again with the local2remote change?14:26
edmondsw(this would be py35 at this point, since it's an Ubuntu 16.04 image without additional py3.x releases added)14:27
mujahidaliI tried to redeploy the stage env(to pick :edmonds's changes) and I got the same error again.14:27
edmondswso slack me the env info again and I'll take a look14:27
edmondswwhat else do you have to report for the CI today?14:27
mujahidaliThere is some problem with the os4p cloud due to whcih zuul-mergers nodes are down hence, there is no job in the queue. I will look into it once os4p is back.14:27
edmondswah, yep, we're at the mercy of os4p now that we have the zuul mergers there14:28
efriededmondsw: Based on my browser history, I probably built 3.7 from source following https://serverfault.com/questions/918335/best-way-to-run-python-3-7-on-ubuntu-16-04-which-comes-with-python-3-514:28
edmondswI wonder if we should run other things there as well, or move the merger nodes where everything else is... so we're only at the mercy of one infrastructure instead of 214:29
edmondswefried ack thanks14:29
mujahidaliearlier all zuul-mergers were jupiter14:29
edmondswyeah, so it's not a new problem, just moved from jupiter to os4p14:30
edmondswnot an immediate concern... just thinking out loud14:30
mujahidaliOn multinode-front I installed zookeper and trying to figure out how it connects with nodepool(using this https://zuul-ci.org/docs/nodepool/configuration.html as ref I am able to connect zookeper with nodepool). Now I am getting error with diskimage-builder, there is some issue with nodepool py2 and py3.14:30
edmondswsounds like you're making progress, though. Good14:31
edmondswmujahidali anything else?14:32
mujahidalithat's it from me.14:32
edmondsw#topic Device Passthrough14:33
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)"14:33
edmondswefried ^14:33
efriedThere is general support for the idea of a generic provider config file, and a consensus that the design for that should be split out from the device passthrough spec(s). So I did that:14:33
efried#link Provider config YAML spec https://review.openstack.org/#/c/612497/14:33
efriedIt accomodates the device passthrough use case, plus a bunch of others.14:34
efriedToday is a spec review sprint for nova. Hoping this gets some attention.14:34
efriedThe idea is hopefully to get it close enough to baked that we can go and implement it at least OOT14:34
efriedit'll be a delta from what we've got proposed right now (and from what's in the merged spec)14:34
edmondswanything I should be concerned about in there?14:35
efriedwhat do you mean, concerned about?14:35
efriedYou should read it14:35
efriedbut no, there shouldn't be anything hugely worrisome.14:35
edmondswyep, I loaded the link and will try to read14:35
edmondswk good14:35
efriedThe subset that deals with device stuff is pretty much the same as what we had before.14:35
efriedyeah, even including how to identify via traits and how to add/remove traits.14:36
efriedbut this spec leaves out the (controversial) part about us autogenerating a bunch of traits based on things like PCI vendor ID and whatnot.14:37
efriedThat's the "split" aspect.14:37
efriedThat's all I have for the moment on passthrough.14:37
edmondswok, thanks14:38
edmondsw#topic Open Discussion14:38
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:38
edmondswthe floor is open...14:38
* efried dances14:38
* efried sits14:39
efriednothing here14:39
* edmondsw enjoyed that14:39
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."14:39
openstackMeeting ended Tue Oct 23 14:39:23 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-10-23-14.08.html14:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-10-23-14.08.txt14:39
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-10-23-14.08.log.html14:39
openstackgerritMatthew Edmonds proposed openstack/ceilometer-powervm stable/rocky: Don't use pypi releases for ceilomter  https://review.openstack.org/61272214:47
*** mujahidali has quit IRC14:58
*** irclogbot_4 has joined #openstack-powervm18:35
*** chhagarw has quit IRC18:57
*** openstackgerrit has quit IRC20:06

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!