| *** efried_off is now known as efried | 13:05 | |
| efried | edmondsw: I've got to take a kid to the dentist this morning, will miss the meeting. | 13:30 |
|---|---|---|
| efried | Sorry for the short notice. | 13:30 |
| efried | I'm in solo parentis for a couple of days, and it's been pretty heinous | 13:30 |
| efried | One thing if it was just life-as-normal, but we chose days where multiple people have multiple special events. And right after getting back from a trip. | 13:31 |
| edmondsw | efried sounds fun! no worries here. Take care of the fam | 13:31 |
| *** efried is now known as efried_afak | 13:32 | |
| *** efried_afak is now known as efried_afk | 13:32 | |
| *** efried_afk is now known as efried | 13:47 | |
| efried | edmondsw: Hah, the dentist called right as I was about to leave and gave me an out. So I'll be in the mtg. | 13:47 |
| edmondsw | :) | 13:48 |
| *** mujahidali has joined #openstack-powervm | 13:52 | |
| edmondsw | #startmeeting PowerVM Driver Meeting | 14:00 |
| openstack | Meeting started Tue Sep 18 14:00:48 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| *** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)" | 14:00 | |
| openstack | The meeting name has been set to 'powervm_driver_meeting' | 14:00 |
| edmondsw | #link agenda: https://etherpad.openstack.org/p/powervm_driver_meeting_agenda | 14:00 |
| edmondsw | efried mujahidali y'all here? | 14:01 |
| mujahidali | ^ | 14:02 |
| efried | ō/ | 14:02 |
| edmondsw | #topic In-Tree Driver | 14:02 |
| *** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)" | 14:02 | |
| edmondsw | I haven't had any time to look at this in a while, and probably won't for a while | 14:02 |
| edmondsw | efried anything we should discuss here, particularly anything from the PTG? | 14:02 |
| efried | um | 14:03 |
| efried | no, I don't think so. | 14:03 |
| edmondsw | cool | 14:03 |
| edmondsw | moving on | 14:03 |
| edmondsw | #topic Out-of-Tree Driver | 14:03 |
| *** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)" | 14:03 | |
| edmondsw | I've got a WIP patch up to update our devstack examples: https://review.openstack.org/#/c/601628/ | 14:04 |
| edmondsw | still working on some things there, but the SEA changes work | 14:04 |
| edmondsw | it's an ongoing, as-able type of thing | 14:04 |
| edmondsw | mdrabe has also been working on secure boot: https://review.openstack.org/#/c/595877/ | 14:06 |
| edmondsw | there was a bug in pypowervm 1.1.17 so we had to release 1.1.18 for this to work properly | 14:06 |
| *** mdrabe has joined #openstack-powervm | 14:06 | |
| edmondsw | I believe the patch has been updated to use 1.1.18 now, but last I checked that wasn't in u-c yet so it wouldn't work | 14:06 |
| edmondsw | #action edmondsw check on u-c for pypowervm | 14:07 |
| edmondsw | anything else to discuss for OOT? | 14:07 |
| edmondsw | mdrabe how are things looking for you to test MSP support, time-wise? | 14:08 |
| mdrabe | I can spare a moment | 14:09 |
| mdrabe | Do we have a multinode env? | 14:09 |
| edmondsw | I have one devstack aio up that you could use, but not a 2nd compute to go with it | 14:09 |
| edmondsw | rather, I have a second system partly setup, but not devstacked | 14:09 |
| edmondsw | I am tied up in other things atm, but if you're available to work on that I could give you a devstack local.conf that I think should work and you could try it / play with that to get things working | 14:10 |
| efried | I can lend my machine if you need a second. | 14:11 |
| mdrabe | Maybe, that'll take me some time. Got some other stuff to get to first | 14:11 |
| edmondsw | thanks, but it'll need to be the 2nd that I already identified, so they share an SSP | 14:11 |
| edmondsw | rather, I already set it up to use the same SSP | 14:11 |
| efried | ight | 14:11 |
| edmondsw | mdrabe ok, let me know when you can get to it | 14:12 |
| edmondsw | #topic Device Passthrough | 14:12 |
| *** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)" | 14:12 | |
| edmondsw | efried ^ | 14:12 |
| * efried totally unprepared to report on anything | 14:12 | |
| efried | Sean Mooney and I are going to work through some of the yaml file format ideas | 14:13 |
| efried | Rahul is going to start working on a PoC based on what we've got at the moment. | 14:13 |
| efried | Cyborg just might have a spawn-only solution in Stein. | 14:14 |
| efried | well, a flavor vehicle, so technically I suppose you could hot attach with resize. | 14:14 |
| efried | not sure if that's going to be a supported path. | 14:14 |
| efried | closing on nrp is top priority | 14:15 |
| efried | That's about all I've got for now, until I get my head organized again. Hopefully more coherent next week. | 14:15 |
| efried | Any questions? | 14:15 |
| edmondsw | much discussion at the PTG about this stuff? | 14:15 |
| efried | yes, from several angles. | 14:16 |
| efried | Mainly cyborg | 14:16 |
| efried | Let me summarize what that's going to look like for phase 1 | 14:16 |
| efried | cyborg API/CLI to create a "device profile" | 14:16 |
| efried | Stuff a reference to that profile into the flavor | 14:16 |
| efried | boot with the flavor | 14:16 |
| edmondsw | is that device profile anything like what we've designed to put in our yaml? | 14:17 |
| efried | compute communicates with cyborg to turn that reference into an object to pass to virt. Virt does the attach. | 14:17 |
| efried | It's analogous to a neutron port. | 14:17 |
| efried | So you create it with e.g. a resource class and traits, and it's just hanging out there in the world. | 14:18 |
| efried | Then you boot with it and there's a point where it gets "bound" - only then does it become part of an instance+host. | 14:18 |
| efried | And then the bound thingy is what gets passed to the virt driver, which does the attach. | 14:18 |
| efried | As for the yaml file, we agreed we were going to try to make it a common format that could be read by cyborg and/or nova. | 14:20 |
| edmondsw | I assume "boot with it" = "cyborg programming an FPGA" | 14:20 |
| efried | no | 14:20 |
| efried | phase 1 I believe we're just talking about non-programmable device passthrough. | 14:21 |
| efried | I mean nova boot --flavor X | 14:21 |
| efried | where flavor X contains a reference to the device profile thingy (VAR - Virtual Accelerator Reference - I believe) | 14:21 |
| edmondsw | then I have no idea what this means: "Then you boot with it and there's a point where it gets "bound" - only then does it become part of an instance+host." | 14:22 |
| edmondsw | if it's not programming, then the thing exists on the host before any of this process has started, nothing is creating it | 14:22 |
| efried | openstack var create --resource-class GPU --traits CUSTOM_FOO CUSTOM_BAR | 14:24 |
| efried | ==> $var_uuid | 14:24 |
| efried | openstack flavor update --flavor X --extra-specs hw:cyborg:var:$var_uuid | 14:24 |
| efried | nova boot --flavor X | 14:24 |
| efried | or are you talking about inventorying and discovery? | 14:24 |
| efried | actually maybe s/var_uuid/profile_name/ -- I don't think these are one-time-use gizmos, I think they're more like flavors themselves. So the "binding" step actually picks a specific device on the host. | 14:25 |
| efried | now I can't remember | 14:25 |
| efried | But Sundar is going to put up a spec. | 14:25 |
| edmondsw | I'll wait and read the spec | 14:25 |
| edmondsw | ping me when it's up? | 14:26 |
| efried | https://etherpad.openstack.org/p/stein-ptg.cyborg-nova-new | 14:26 |
| edmondsw | lot there | 14:27 |
| edmondsw | is this being actively looked at, or are comments there a waste of time? | 14:27 |
| edmondsw | s'why I prefer commenting in reviews | 14:27 |
| edmondsw | plus they have more structure so easier to make sense of them | 14:27 |
| efried | I don't know if Sundar is still consuming that to construct his spec. | 14:29 |
| efried | In any case, yeah, I'll let you know when I see that spec come through. | 14:29 |
| edmondsw | tx | 14:29 |
| efried | But in the meantime, if you have questions/comments, I may be able to answer them | 14:29 |
| efried | because they may have already been discussed | 14:29 |
| efried | we had several hours to get to this point. | 14:30 |
| edmondsw | I wasn't able to follow what you meant above, so... | 14:30 |
| efried | above where? | 14:30 |
| edmondsw | a lot of it | 14:30 |
| edmondsw | looking at the etherpad helped me understand 'bound | 14:31 |
| efried | guess it helps to be familiar with the neutron flow | 14:31 |
| edmondsw | I'll see if I can figure out the rest later if i get some time | 14:31 |
| efried | which I *barely* am. | 14:31 |
| edmondsw | might, but I don't think that's my issue here | 14:32 |
| edmondsw | anyway, moving on | 14:32 |
| efried | k, well, let me know if you want to discuss further. | 14:32 |
| efried | yeah | 14:32 |
| edmondsw | #topic PowerVM CI | 14:32 |
| *** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)" | 14:32 | |
| edmondsw | mujahidali how are things? | 14:32 |
| edmondsw | yesterday you had identified a couple nodes that were always timing out.. that fixed? | 14:33 |
| mujahidali | Jobs running on Neo24 and ne08 are taking too long to complete and eventually failing after timeout and neo 6 was having some problem with pvmctl so restarted neo6 and redeployed neo,6,8,24. | 14:33 |
| mujahidali | CI run looks better now. | 14:33 |
| edmondsw | great, tx | 14:33 |
| edmondsw | that it? | 14:35 |
| mujahidali | I have tried installing nodepool,zuul and jenkins on my test env but things are a little complicated | 14:35 |
| edmondsw | that sounds like an understatement :) | 14:35 |
| mujahidali | nodepool and zuul are not launching | 14:35 |
| edmondsw | did you also install zookeeper? | 14:35 |
| mujahidali | no | 14:35 |
| edmondsw | I remember esberglu saying that would be needed with the newer versions | 14:36 |
| mujahidali | okay | 14:36 |
| mujahidali | I first want to try it on dev env then stage and then prod. | 14:36 |
| edmondsw | you have a dev env other than the staging env? | 14:37 |
| edmondsw | if so, great | 14:37 |
| mujahidali | I am just using vms | 14:37 |
| mujahidali | to look how installation and config is working. | 14:37 |
| edmondsw | k | 14:37 |
| edmondsw | sure | 14:37 |
| mujahidali | we had a discussion for the blacklist and whitelist for the 700 test case with :efried | 14:38 |
| mujahidali | I am not able to conclude from that discussion. | 14:39 |
| edmondsw | I think we table that for the time being | 14:39 |
| mujahidali | okay | 14:39 |
| edmondsw | anything else? | 14:39 |
| mujahidali | that's it from me. | 14:39 |
| edmondsw | thanks | 14:40 |
| mujahidali | :) | 14:40 |
| edmondsw | #topic Open Discussion | 14:40 |
| *** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)" | 14:40 | |
| edmondsw | nothing from me here | 14:41 |
| edmondsw | anyone else? | 14:41 |
| mujahidali | no | 14:41 |
| edmondsw | alright, thanks everyone | 14:42 |
| edmondsw | #endmeeting | 14:42 |
| *** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack." | 14:42 | |
| openstack | Meeting ended Tue Sep 18 14:42:05 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:42 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-09-18-14.00.html | 14:42 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-09-18-14.00.txt | 14:42 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-09-18-14.00.log.html | 14:42 |
| *** mujahidali has quit IRC | 14:46 | |
| edmondsw | mdrabe looks like u-c has pypowervm 1.1.18 in it now, so we should be good on https://review.openstack.org/#/c/595877 once you address the RR thing | 14:48 |
| mdrabe | edmondsw: There shouldn't be any additional changes for RR | 14:50 |
| edmondsw | see the comment I made in the review | 14:50 |
| edmondsw | mdrabe it's the same thing we were talking about the other day | 14:50 |
| mdrabe | Oh you want to block it in the driver? | 14:51 |
| edmondsw | where else? | 14:51 |
| mdrabe | For pvc we do it in the scheduler | 14:51 |
| edmondsw | I don't think that's an option for community, since we don't have any powervm logic in the scheduler there | 14:52 |
| mdrabe | Mm okay, I can make the change to block it in the driver for nova-powervm, it'll be a functional difference between pvc. I guess that's okay | 14:53 |
| edmondsw | would just mean pulling out the last section of lines you added in vm.py, right? | 14:54 |
| mdrabe | I think there'd need to be an explicit exception raised in the driver | 14:55 |
| edmondsw | mdrabe should raise an exception anyway... you just thinking the default exception might not have enough info to understand why it failed? | 14:58 |
| edmondsw | if that's the case, then we'd have an issue with the non-RR failure case even without this update... and similarly for other capabilities. So I hope the default exception is good enough | 14:59 |
| mdrabe | Yea we can count on that I suppose | 15:00 |
| mdrabe | I'll remove those lines in vm.py, the evacuate would go through but the spawn would fail on the hypervisor | 15:00 |
| edmondsw | and then nova would roll it back, right? | 15:01 |
| mdrabe | I don't think there's evacuation rollback | 15:02 |
| edmondsw | if it leaves the VM on a host that can't support it, how will we move it to a host that does support it? | 15:02 |
| edmondsw | maybe cold migration | 15:03 |
| mdrabe | Or well, I believe the nova-powervm driver will clean up the LPAR/adapters from the failed deploy | 15:03 |
| mdrabe | If the exception that gets raised triggers a rebuild, then the scheduler will choose a different host to deploy to | 15:03 |
| edmondsw | better test and see what happens | 15:04 |
| edmondsw | so we know we're not getting things stuck | 15:04 |
| mdrabe | Stuck how? | 15:04 |
| mdrabe | You should still be able to trigger an evacuate to a different host | 15:04 |
| mdrabe | The question of rollback just doesn't really apply to evacuation I don't think | 15:05 |
| edmondsw | I thought you were saying that the LPAR would be gone from the original host we RR'ed from | 15:05 |
| mdrabe | No | 15:05 |
| edmondsw | ok, then we're probably fine | 15:05 |
| edmondsw | just try another RR to a different host | 15:05 |
| mdrabe | Yep | 15:05 |
| *** openstackgerrit has joined #openstack-powervm | 15:08 | |
| openstackgerrit | Matt Rabe proposed openstack/nova-powervm master: Support secure_boot extra_spec in _format_flavor https://review.openstack.org/595877 | 15:08 |
| *** efried has quit IRC | 20:44 | |
| *** efried has joined #openstack-powervm | 20:44 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!