Tuesday, 2018-03-13

*** edmondsw has joined #openstack-powervm03:18
*** edmondsw has quit IRC03:22
*** edmondsw has joined #openstack-powervm05:06
*** edmondsw has quit IRC05:10
openstackgerritOpenStack Proposal Bot proposed openstack/ceilometer-powervm master: Updated from global requirements  https://review.openstack.org/55230906:48
*** edmondsw has joined #openstack-powervm06:54
*** edmondsw has quit IRC06:59
openstackgerritShangXiao proposed openstack/nova-powervm master: Update the old links in docs  https://review.openstack.org/55237907:26
*** AlexeyAbashkin has joined #openstack-powervm07:50
*** edmondsw has joined #openstack-powervm08:42
*** edmondsw has quit IRC08:46
*** edmondsw has joined #openstack-powervm10:30
*** edmondsw has quit IRC10:35
*** edmondsw has joined #openstack-powervm11:45
*** apearson_ has joined #openstack-powervm12:52
edmondswtonyb did I read your comment about the meeting proposal correctly that there is a move *away* from using openstack-meeting channels?13:28
edmondswi.e. should I repropose for openstack-meeting-3 or just continue to have the meeting here like we have been?13:29
*** tblakes has joined #openstack-powervm13:30
edmondswtonyb I was trying to follow what it says in the project requirements about "moving to official OpenStack meeting channels once the project’s application is accepted"13:32
edmondswhttps://governance.openstack.org/tc/reference/new-projects-requirements.html13:32
*** esberglu has joined #openstack-powervm13:53
edmondsw#startmeeting PowerVM Driver Meeting14:00
openstackMeeting started Tue Mar 13 14:00:40 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)"14:00
openstackThe meeting name has been set to 'powervm_driver_meeting'14:00
edmondsw#topic In-Tree Driver14:01
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:01
esberglu\o14:01
edmondswefried?14:01
efriedSorry, chaos14:01
edmondswnp14:01
edmondswhttps://etherpad.openstack.org/p/powervm-in-tree-todos14:02
edmondswwanted to talk about what we're doing with the blurb at the top of that14:02
edmondswefried you probably have the best idea of what we should do there14:03
edmondswbut if you're still in chaos we can come back to that14:03
efriedSorry, guys, any way we can pick this up in 10 minutes?14:03
efriedotp and at the mercy of the other end14:03
edmondswfine with me14:03
esberglunp for me14:03
efriedI'm back, sorry about that.14:16
efriedWe're talking about the InstanceInfo thing?14:16
edmondswesberglu resuming14:16
esbergluack14:16
edmondswefried yeah... I don't think we have anything more to do there do we?14:16
efriedDid we flush those changes back to OOT?14:17
edmondswgood question14:17
edmondsw#action edmonds check whether we need InstanceInfo changes OOT14:17
edmondswI can move to the OOT todo list if need be14:17
edmondswas for Rocky...14:18
efriedLooks like we did.  So yeah, we can remove that item.14:18
edmondswefried great, tx14:18
efrieddef get_vm_info(adapter, instance):14:19
efried    """Get the InstanceInfo for an instance.14:19
efried    :param adapter: The pypowervm.adapter.Adapter for the PowerVM REST API.14:19
efried    :param instance: nova.objects.instance.Instance object14:19
efried    :returns: An InstanceInfo object.14:19
efried    """14:19
efried    pvm_uuid = get_pvm_uuid(instance)14:19
efried    pvm_state = get_vm_qp(adapter, pvm_uuid, 'PartitionState')14:19
efried    nova_state = _translate_vm_state(pvm_state)14:19
efried    return hardware.InstanceInfo(nova_state)14:19
edmondswI added a couple reviews to https://etherpad.openstack.org/p/rocky-nova-priorities-tracking14:19
edmondswincluding the spec for virt integration efforts in Rocky14:19
edmondswI'm hoping we can get that approved soon...14:19
esbergluI added network hotplug and snapshot as ready for subteam review there14:20
edmondswefried do you have a feel for how long I should wait before pinging melwitt?14:20
edmondswesberglu tx... I think that'll be a good place for us to keep track of things14:20
edmondswand have visibility in the larger nova team to what we're doing14:21
esbergluvSCSI is ready too, but I do want to get a stack with that and test again, make sure it still works14:21
edmondsw+114:21
efriedWe need to get subteam +1s first; then we can move 'em to broader review and start pestering people.  Which means I (at least) need to get on those reviews.14:21
efriedcause I think I'm behind on at least a couple.14:21
edmondswefried yep, that's why their only marked for subteam review except where you/I have already +1d14:21
edmondswthey're*14:22
edmondswgood call adding the comments on what each link is14:22
efried++14:23
edmondswI will try to take another look at the ones ready for subteam review again today14:23
edmondswesberglu update us on the others that are in-progress but not ready yet?14:23
esbergluThere are 2 more that I have underway, both related to localdisk14:24
esbergluhttps://review.openstack.org/#/c/549053/14:24
esbergluhttps://review.openstack.org/#/c/549300/14:24
esbergluThe first adds the DiskAdapter parent class, currently we just have the ssp adapter in tree14:24
edmondswwhy isn't 053 ready for subteam review?14:24
esbergluIt is14:25
edmondswok, so we can add that to the etherpad14:25
esbergluI just didn't add it yet in case snapshot changes will require rebasing / modifying14:25
esbergluI'll add it14:26
edmondswlooks like it is based on an older snapshot ps14:26
esbergluedmondsw: Yeah I was holding off on rebasing until you guys +114:26
edmondswworks for me14:26
edmondswI think the only other thing I had to mention IT is that esberglu and I cleaned up the TODO etherpad: https://etherpad.openstack.org/p/powervm-in-tree-todos14:27
edmondswI will add a link to the nova rocky etherpad... tx for pointing that out yesterday efried14:28
edmondswanything else for IT?14:28
esberglunope14:28
edmondsw#topic Out-of-Tree Driver14:29
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:29
edmondswnew etherpad for this: https://etherpad.openstack.org/p/powervm-oot-todos14:29
edmondswefried I added the volume id item we were discussing yesterday14:29
edmondswSRIOV max capacity merged, so I can remove that14:30
edmondswI spent some more time looking at the volume refactor yesterday14:30
edmondswgetting close there...14:30
edmondswI'd like to get reviews on that tied up this week, and see if we can get that tested and merged by end of the month14:31
edmondswefried your volume_id change proposal is pretty small, but we should talk about whether it makes sense to do that on top of the refactor rather than have to do it twice14:32
edmondswthoughts?14:32
edmondswImran said they can wait a couple weeks on the volume id change14:32
efriedAs you say, it's pretty small, the rebase wouldn't be hard, could do it either side.  Since Imran says we want this by end of month, we may want to do the volume ID first.14:32
efriedoh, if you want to think of it that way :)14:33
edmondswyeah, it is small, so I could go either way14:33
efriedWe need to get the pypowervm side merged and through g-r before it'll pass tests14:33
edmondswwas pretty set on it being after the refactor, but then realized how small it is :)14:33
efriedand core/REST needs more patches before it'll actually work.14:33
edmondswefried yep, I think the g-r change may be the bigger issue14:33
edmondswas far as how quickly we can get this to them14:33
efriedBut those don't really factor into which order we do the n-pvm changes14:34
edmondswand the core/REST changes, of course14:34
edmondswyep14:34
efriedSo - how close are we on The Big Refactor?14:34
edmondswpretty close14:34
efried(I of course should review that)14:34
edmondswdefinitely14:34
edmondswI am doing another pass through the changes, hope to finish that today14:35
edmondswdon't expect much more to shake out there14:35
edmondswI did notice something yesterday while digging through... we don't have live migration support for iSCSI14:35
edmondswso I added that to our TODO etherpad after talking to Gerald and confirming that PowerVC will need that14:35
edmondswanything else to talk about OOT?14:36
esbergluI have a couple easy reviews out14:36
esbergluhttps://review.openstack.org/#/c/548410/14:37
esbergluhttps://review.openstack.org/#/c/548412/14:37
esbergluIf efried could get a review on those14:37
esbergluAnd give your thoughts on14:37
esbergluhttps://review.openstack.org/#/c/548721/14:37
esbergluthat all I had14:38
edmondswlooks like someone has raised a docs fix: https://review.openstack.org/#/c/552379/14:39
edmondswI'll look at that after14:39
edmondsw#topic Device Passthrough14:40
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)"14:40
edmondswefried ?14:40
edmondswany updates from the PTG?14:40
efriedHeaping pile of blueprints/specs/patches from the PTG, plus the update_provider_tree stuff that's been sitting out there for a while.14:40
edmondswI spent some time thinking through use cases and such while you were out... we need to catch up and go over that when you have a few minutes14:41
efriedSome changes to UPT came out of the PTG; spec delta almost merged (https://review.openstack.org/#/c/552122/) but I need to write the code accordingly.  That's "first" on my agenda.14:41
efriedNo news on NRP in GET /a_c; I'll bug jaypipes about that soon.  But with those two pieces, we should be pretty free & clear to start proposing our own driver patches to implement UPT.14:42
edmondswI don't think we're going to have that borrowed system for too much longer, so you should probably try to get on that while we can14:42
efriedOnce we have that, we can do generic passthrough.  So edmondsw you have time to figure out the ux so we can walk that back to the code.14:43
edmondswfigure out what the card looks like as far as identifiers and such14:43
efriedOh, was that on me?  I thought you were on the hook for that.14:43
edmondswyes and yes14:43
edmondsw:)14:43
edmondswI figured out what it should look like14:44
edmondswI haven't gotten on the system to confirm that it actually looks like that... I thought you were doing that14:44
edmondswI can try to figure out how to do that14:44
efriedWasn't on my radar.  If you have room for it, that would be cool.  So the system has GPUs on it?14:44
edmondswyes14:45
edmondswthe really nice kind14:45
edmondswNicolas has it patched so it should work for us now14:45
efriedSo pvmctl sys list --xml maybe14:45
edmondswk14:45
edmondswefried get together this afternoon and go over things?14:46
efriedBut we still need to figure out the set of devices we'll support, and how we're going to represent it, and how we're going to discover.14:47
edmondswthat would be in the "go over things" discussion :)14:47
efriedYes, let's14:47
edmondswalright, enough on that for now I think14:47
efriedSend me a calendar notice, and then send me a message on IRC to let me know you've done that.  I'm only down to 283 unread messages in Notes.14:47
edmondswefried ack14:47
efried(432 and growing in my other client - dev ML)14:48
edmondsw#topic Open Discussion14:48
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:48
esbergluedmondsw: CI?14:48
edmondswoh, oops...14:48
edmondsw#topic PowerVM CI14:48
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)"14:48
edmondswesberglu, you're up14:48
esbergluCI has been pretty consistent lately14:48
esbergluEven with the updated post stack cleaner and https://review.openstack.org/#/c/540453/14:49
esbergluI'm still seeing that vopt issue on occaison on OOT runs14:49
esbergluI have some time cut out tomorrow to hop back into that14:49
efriedDid we try to reinstate the rename patch and see if that kills it?14:50
esbergluYeah the rename patch is being applied to all OOT runs14:50
edmondswI think that's the link above14:50
efriedOkay, so even with that, we're still hitting it?14:50
esbergluyep14:50
efriedoh, sorry, yeah.14:50
efriedSo hm, curiouser and curiouser.  Good luck with that.14:50
edmondswinteresting that we're still seeing it with that14:51
esbergluStill working the CI undercloud upgrade, decided to jump from ocata to queens instead of ocata to pike14:51
esbergluI have a working queens cloud, but the management services aren't playing nice with it14:52
esbergluBecause we are on old versions of those that are having some issues with the identity v3 api14:52
edmondswwhat?14:52
esbergluThe version of nodepool we are on doesn't work with the new identity api14:53
esbergluAnd needs to be upgraded as well14:53
edmondswthat gonna be a problem?14:53
esbergluedmondsw: It will also mean updating zuul and jenkins and adding a zookeeper service and maybe some other stuff14:53
edmondswmaybe that's a good thing... it'll be nice to be more current on everything14:53
edmondswmore work though14:54
esbergluedmondsw: I'm trying a queens deploy using identity v2 api for now14:54
esbergluJust to verify that queens works otherwise14:54
edmondswhuh... I thought v2 was removed in queens14:54
esbergluOh maybe, I thought I saw it in there, could have been looking at the wrong thing14:55
edmondswI wasn't very involved with keystone during queens, though, so I could have gotten that wrong14:56
esbergluBut yeah, still just trying to get something working there, I'll keep you posted on progress14:56
edmondswtx14:56
edmondswanything else?14:56
esbergluI'm starting to look forward into the multinode CI / OVS CI14:56
edmondsw+114:57
esbergluNothing to talk about there yet though14:57
edmondsw#topic Open Discussion14:58
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:58
edmondswI wanted to note a couple things with the PowerStackers group14:58
edmondswtonyb has proposed renaming to PowerVMStackers, making it PowerVM specific again like my original proposal14:58
edmondswhttps://review.openstack.org/#/c/55141314:59
edmondswI replied to that this morning14:59
edmondswI suspect it will get renamed, and I'm not sure I disagree with that14:59
efriedI'm writing up a concurring opinion atm15:00
edmondswhe also raised an objection on the meeting proposal: https://review.openstack.org/#/c/55213215:00
edmondswI replied to that as well seeking some clarification15:00
edmondswit sounded like he might be saying we should just meet in our channel because the official meeting channels are being deemphasized? but I'm not sure I got that right15:01
edmondswso we'll see where that goes15:01
edmondswanything else to discuss?15:01
esberglunope15:02
edmondsw#endmeeting15:02
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."15:02
openstackMeeting ended Tue Mar 13 15:02:46 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-03-13-14.00.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-03-13-14.00.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-03-13-14.00.log.html15:02
efriededmondsw: Posted (https://review.openstack.org/#/c/551413/)15:05
edmondswefried yep, tx15:07
edmondswI went ahead and bumped myself to +1 as well15:08
*** tjakobs has joined #openstack-powervm15:20
edmondswesberglu I didn't see multinode on the CI todo etherpad, so I added it15:22
esberglutx15:22
edmondswesberglu want to fix that typo on https://review.openstack.org/#/c/548721 or should I just merge it?15:48
esbergluedmondsw: I can fix it quick15:49
*** tblakes has quit IRC15:50
efriededmondsw: Feel free to fast-approve.  No need to wait for me to re+215:56
edmondswefried yep, I was planning to15:56
openstackgerritEric Berglund proposed openstack/nova-powervm master: Mock retry in test_remove_block_dev  https://review.openstack.org/54872116:01
openstackgerritMerged openstack/ceilometer-powervm master: Updated from global requirements  https://review.openstack.org/55230916:09
openstackgerritMerged openstack/nova-powervm master: Updated from global requirements  https://review.openstack.org/55236416:22
openstackgerritMerged openstack/nova-powervm master: Update taskflow instantiation  https://review.openstack.org/54841016:22
openstackgerritMerged openstack/nova-powervm master: Add missing tasks tests  https://review.openstack.org/54841216:22
openstackgerritMerged openstack/networking-powervm master: Updated from global requirements  https://review.openstack.org/55235516:22
*** AlexeyAbashkin has quit IRC17:34
openstackgerritEric Berglund proposed openstack/nova-powervm master: DNM: ci check  https://review.openstack.org/32831517:57
openstackgerritMerged openstack/nova-powervm master: Mock retry in test_remove_block_dev  https://review.openstack.org/54872118:20
*** AlexeyAbashkin has joined #openstack-powervm18:58
*** AlexeyAbashkin has quit IRC19:03
*** esberglu has quit IRC19:27
*** esberglu has joined #openstack-powervm19:37
openstackgerritEric Fried proposed openstack/nova-powervm master: Set volume ID as PV tag when mapping VSCSI volumes  https://review.openstack.org/55217220:18
openstackgerritEric Berglund proposed openstack/nova-powervm master: DNM: CI Check2  https://review.openstack.org/32831720:18
*** esberglu has quit IRC21:30
*** esberglu has joined #openstack-powervm21:33
*** AlexeyAbashkin has joined #openstack-powervm21:36
*** esberglu has quit IRC21:37
*** AlexeyAbashkin has quit IRC21:41
*** esberglu has joined #openstack-powervm22:02
tonybedmondsw: Yeah I didn't realise that old requirement still existised after the TC voted to allow meetings in project channels.  So yeah you can hold your meeting here or in a -meeting-{3,4} either is fine22:10
tonybthe latter is good if you want to highlight/ping people but that works best when there is TZ overlap22:10
edmondswtonyb sure... efried esberglu y'all have an opinion?22:11
edmondswI'll probably just abandon that and keep having it here for now unless someone speaks up22:11
efriedI thought there was some benefit to having it in a "real" channel.22:12
esbergluI'd prefer here but don't feel strongly either way22:12
tonybedmondsw: Rather than abanond it just chnage the channel to here22:12
tonybthat way you get listed on the ical/eavesdrop page22:12
edmondswtonyb ah, good call22:12
efriedThat ^22:12
edmondswwill do22:12
tonybefried: There certainly used to be and I disagree with the TC's move to encourage meetings in per project channels but at the same time I understand the motivation.  It's a shame they missed that old blurb22:13
tonybefried: I'll fix that today if it hasn't already been done by ttx ;P22:14
tonybedmondsw, efried I can do it for you and reference this log and then +W the change22:16
edmondswtonyb can do what?22:17
edmondswI just reproposed pointing to this channel as the meeting place22:17
tonybedmondsw: propose an alteration to you irc-meetings change setting the channel to here22:17
tonybedmondsw: Oh okay packest passing in the ether22:17
edmondsw:)22:17
tonybedmondsw: as long as tox likes it it'll merge in ~10mins22:18
edmondswtonyb great, tx22:18
tonybnp22:18
*** edmondsw has quit IRC22:21
*** apearson_ has quit IRC22:32
*** tjakobs has quit IRC22:45
*** AlexeyAbashkin has joined #openstack-powervm23:36
*** edmondsw has joined #openstack-powervm23:36
*** AlexeyAbashkin has quit IRC23:41
*** edmondsw has quit IRC23:41

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