Tuesday, 2018-08-21

*** esberglu has joined #openstack-powervm01:24
*** esberglu has quit IRC01:29
*** esberglu has joined #openstack-powervm02:15
*** esberglu has quit IRC02:20
*** esberglu has joined #openstack-powervm02:40
*** esberglu has quit IRC02:45
*** esberglu has joined #openstack-powervm03:00
*** esberglu has quit IRC03:05
*** esberglu has joined #openstack-powervm03:10
*** esberglu has quit IRC03:15
*** esberglu has joined #openstack-powervm03:30
*** esberglu has quit IRC03:35
*** esberglu has joined #openstack-powervm04:30
*** esberglu has quit IRC04:34
*** esberglu has joined #openstack-powervm04:45
*** esberglu has quit IRC04:49
*** esberglu has joined #openstack-powervm05:30
*** esberglu has quit IRC05:35
*** esberglu has joined #openstack-powervm06:10
*** esberglu has quit IRC06:15
*** esberglu has joined #openstack-powervm06:30
*** esberglu has quit IRC06:35
*** esberglu has joined #openstack-powervm06:50
*** esberglu has quit IRC06:55
*** esberglu has joined #openstack-powervm07:10
*** esberglu has quit IRC07:15
*** esberglu has joined #openstack-powervm07:46
*** esberglu has quit IRC07:50
*** esberglu has joined #openstack-powervm08:40
*** esberglu has quit IRC08:44
*** esberglu has joined #openstack-powervm09:00
*** esberglu has quit IRC09:05
*** esberglu has joined #openstack-powervm09:20
*** esberglu has quit IRC09:25
*** esberglu has joined #openstack-powervm09:45
*** esberglu has quit IRC09:50
*** efried is now known as efried_goatin13:03
*** efried_goatin is now known as efried13:37
*** esberglu has joined #openstack-powervm13:59
efriedō/14:00
edmondsw#startmeeting PowerVM Driver Meeting14:01
openstackMeeting started Tue Aug 21 14:01:15 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)"14:01
openstackThe meeting name has been set to 'powervm_driver_meeting'14:01
edmondsw#link agenda: https://etherpad.openstack.org/p/powervm_driver_meeting_agenda14:01
edmondsw#topic In-Tree Driver14:02
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:02
*** mujahidali has joined #openstack-powervm14:02
esbergluo/14:03
edmondswI've been thinking about what we should attempt to do in-tree for Stein14:03
edmondswwe've talked about maybe doing some of the device passthrough work both IT and OOT in Stein, so that's one thing14:04
edmondswthe other obvious thing is the work that we didn't contain in Rocky for resize, migration, evacuation14:04
edmondswall the things that need multi-node CI14:04
edmondswanyone want to throw out other ideas?14:04
edmondswor comment on those?14:05
edmondswdon't everyone talk at once... ;)14:06
edmondswok, we don't have to hold the meeting on that... but think about it, and let me know14:06
efried.14:06
edmondswanything else to discuss for IT today?14:06
efriedAre there any prerequisites in-tree14:06
efriedfor device passthrough14:06
efriedto be implemented in-tree?14:06
efriedI'm not coming up with any offhand.14:07
edmondswnot that I know of14:07
efriedAnd in fact it may be easier to implement passthrough before we've implemented things like live migration and remote restart.14:07
edmondswat this point, the OOT driver is still the "full-feature" driver14:07
edmondswso anything we do IT we need to also do OOT14:07
edmondswso I don't know that it will make anything easier to do IT first14:08
edmondswwhen OOT would have to follow immediately in the same release14:08
edmondswunless it's a question of getting nova core eyes on it, which does have significant benefits14:08
edmondsw(not having to reimplement OOT to match IT if we have to make a lot of changes to satisfy them IT)14:09
edmondswbut let's say we do IT first... we need to do that with an eye on how we'll handle things like live migration and RR when we implement OOT14:10
edmondswand probably have those patches up in parallel14:10
edmondswefried thoughts?14:10
edmondswfeel like I'm typing to myself :)14:10
efriedI was thinking about doing them in parallel, yes.14:10
efriedEspecially if the in-tree work that kosamara is driving gets any traction.14:11
edmondswmakes sense to me14:11
efriedI want to be the first driver to do it.14:11
efriedor first-with-libvirt.14:11
edmondsw+1 to that14:11
edmondswalright, moving on14:12
edmondsw#topic Out-of-Tree Driver14:13
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:13
efriedotherwise, I don't have any particular agenda wrt working towards parity14:13
edmondswhttps://review.openstack.org/#/c/593529/ needs a 2nd +2 and +A14:13
edmondswhttps://review.openstack.org/#/c/592057/ already has 2 +2's but I'm happy leaving that open until gautpras gets back from vacation tomorrow14:14
edmondswI'd like to have his vote on that before merging14:14
edmondswmdrabe I've made some progress on stacking a multinode environment for you (for MSP testing)... and then screwed it up somehow... so still working on that14:15
edmondswthat covers the efforts I'm currently aware of IT... anything else?14:16
edmondswsorry... meant OOT14:16
edmondswI am keeping an eye on https://review.openstack.org/#/c/592520/ and will probably propose similar changes to our .gitignore files just to clean them up14:17
edmondsw#topic Device Passthrough14:18
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)"14:18
edmondswefried ^14:18
efriedOther than some more design discussion on kosamara's spec, nothing new to report since last week.14:18
edmondswalright, tx14:20
edmondsw#topic PowerVM CI14:20
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)"14:20
edmondswwe had some CI issues tracing back to the zuul merger nodes, but I believe that's resolved and things are working now14:21
edmondswmujahidali over to you14:21
mujahidaliesberglu: talked about getting help from tonyb for disk-image-builder.14:22
edmondswas part of the nodepool upgrade, yes14:23
edmondswwhich will be a prereq for multinode CI at this point14:23
edmondswmujahidali are you working on that in the staging environment?14:25
edmondswor should we make the change that esberglu has suggested for vSCSI in 6596 and try that in staging?14:25
edmondswI'd also like to try 6684 in staging14:25
mujahidaliyes14:25
mujahidaliI was looking into this https://github.com/openstack-infra/nodepool/blob/0.3.0/doc/source/configuration.rst14:26
mujahidalipointed by esberglu14:26
edmondswmujahidali ok if you are making progress on multinode, we can leave the staging environment tied up with that14:28
edmondswit's more important than the other 2 things I mentioned14:28
mujahidaliI wanted to try that as well in parallel but got stuck with py2-py3 work.14:29
edmondswsure14:29
edmondswanything else to discuss for CI today? esberglu mujahidali14:29
esbergluNothing from me14:30
mujahidaliwe are waiting for the devstack stable/rocky ??14:30
edmondswah, yes14:30
mujahidaliokay14:30
edmondswI've not gotten a reply from the swift guys14:30
edmondswand devstack is waiting for them14:30
edmondswbut I think we can afford to wait a couple days if need be14:31
mujahidalisure14:31
esbergluedmondsw: I had one comment on 668414:31
edmondswtx14:32
edmondsw#topic Open Discussion14:33
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:33
edmondswopening up the floor... whatchy'all got?14:33
mujahidaliI will be OOO on 23rd and 24th.14:33
edmondswmujahidali ack14:33
edmondswI will be out next Mon-Thurs14:33
edmondswso no meeting next week unless someone else wants to volunteer to run it14:34
edmondswalright, thanks everyone14:35
edmondsw#endmeeting14:35
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."14:35
openstackMeeting ended Tue Aug 21 14:35:52 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-08-21-14.01.html14:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-08-21-14.01.txt14:35
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-08-21-14.01.log.html14:35
efriededmondsw: It would be polite of me/us to +1 https://review.openstack.org/#/c/591898/ and https://review.openstack.org/#/c/594325/ at this point. Thoughts?15:55
efriedI can passive-aggressively +0 I suppose.15:57
edmondswefried looking15:58
edmondswI'm still not clear on what this has to do with PCI device allocation... can you explain that to me?15:59
edmondswdoes nova conflate a VF with a PCI device?15:59
efriedyes, they're the same thing, just with a different vif type.16:00
efriedin nova you have to create the vf, and then pass it through like it was any other PCI device (via whitelisting, etc.). Except it has a special vif type.16:00
efrieds/in nova you have to create the vf/if you want a SR-IOV VF in Nova, you have to create the VF by hand on the (linux) CLI/16:02
edmondswugh <shudder>16:05
edmondswefried commented in the review... +116:06
efriedokay, me too.16:06
efriedYeah, <shudder> everyone hates it, swhy we're trying to move to something else.16:07
openstackgerritMerged openstack/nova-powervm master: iSCSI: Clean up source VIOS on migration  https://review.openstack.org/59352916:20
*** mujahidali has quit IRC18:19
*** edmondsw_ has joined #openstack-powervm20:18
*** edmondsw has quit IRC20:19
*** edmondsw_ is now known as edmondsw20:19
openstackgerritMatthew Edmonds proposed openstack/nova-powervm master: Clean up .gitignore  https://review.openstack.org/59454620:34
tonybedmondsw, mujahidali: 'sup with DIB?23:20

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