*** k0da has quit IRC | 00:37 | |
*** k0da has joined #openstack-powervm | 06:24 | |
*** AlexeyAbashkin has joined #openstack-powervm | 07:22 | |
*** k0da has quit IRC | 09:05 | |
*** k0da has joined #openstack-powervm | 10:49 | |
openstackgerrit | Chhavi Agarwal proposed openstack/nova-powervm master: iSCSI volume detach with no UDID https://review.openstack.org/576034 | 11:46 |
---|---|---|
*** edmondsw has joined #openstack-powervm | 12:06 | |
openstackgerrit | Chhavi Agarwal proposed openstack/nova-powervm master: iSCSI volume detach with no UDID https://review.openstack.org/576034 | 13:11 |
*** esberglu has joined #openstack-powervm | 13:32 | |
*** chhagarw has joined #openstack-powervm | 13:47 | |
openstackgerrit | Chhavi Agarwal proposed openstack/nova-powervm master: iSCSI volume detach with no UDID https://review.openstack.org/576034 | 14:02 |
*** mujahidali has joined #openstack-powervm | 14:02 | |
edmondsw | #startmeeting PowerVM Driver Meeting | 14:06 |
openstack | Meeting started Tue Jul 17 14:06:24 2018 UTC and is due to finish in 60 minutes. The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:06 |
chhagarw | edmondsw: while testing the iscsi changes on devstack, there were some issue could | 14:06 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:06 |
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)" | 14:06 | |
openstack | The meeting name has been set to 'powervm_driver_meeting' | 14:06 |
edmondsw | #link https://etherpad.openstack.org/p/powervm_driver_meeting_agenda | 14:06 |
edmondsw | ping efried gman-tx mdrabe mujahidali chhagarw | 14:07 |
esberglu | o/ | 14:07 |
edmondsw | getting started a bit late... I got too caught up in reviewing the device passthrough spec | 14:07 |
efried | ō/ | 14:07 |
efried | heh, good news | 14:07 |
edmondsw | I'm sure efried will mind that :) | 14:07 |
edmondsw | #topic In-Tree Driver | 14:07 |
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)" | 14:07 | |
edmondsw | #link https://etherpad.openstack.org/p/powervm-in-tree-todos | 14:08 |
edmondsw | I don't know of anything to discuss here... anyone else? | 14:08 |
edmondsw | I don't believe we've made any more progress on the TODOs there | 14:09 |
edmondsw | everything on hold as we focus on other priorities | 14:09 |
edmondsw | #topic Out-of-Tree Driver | 14:09 |
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)" | 14:09 | |
edmondsw | #link https://etherpad.openstack.org/p/powervm-oot-todos | 14:09 |
edmondsw | chhagarw I saw that you posted a new patch set for your iSCSI work... is that based on something you found with devstack? | 14:10 |
edmondsw | I think you were starting to say that right as I started this meeting | 14:10 |
edmondsw | in which case... good example of why we wanted devstack testing, and thank you for doing that | 14:10 |
chhagarw | yeah, while testing with devstack there are couple of issues found | 14:11 |
chhagarw | i am re-verifying on pvc now, will keep u posted | 14:11 |
edmondsw | as an aside on that... I am trying to spend spare cycles here and there improving our example devstack local.conf files in nova-powervm based on things I've been learning from chhagarw's environment and the CI | 14:11 |
edmondsw | chhagarw I think the last patch set I saw still had pep8 errors, so make sure you iron those out | 14:12 |
chhagarw | yeah i am updating | 14:12 |
edmondsw | I had a conversation with mdrabe about the MSP work. I hope he's getting to that here soon | 14:12 |
edmondsw | mdrabe any comments there? | 14:13 |
mdrabe | edmondsw: I'll be syncing the conf options, but the migration object in pvc will remain the same | 14:13 |
edmondsw | we can talk about pvc in other forums | 14:14 |
edmondsw | I added a section in our TODO etherpad about docs | 14:15 |
edmondsw | basically, readthedocs builds are failing since stephenfin's changes | 14:15 |
edmondsw | efried I also figured out how to register in readthedocs to be notified when a docs build fails... thought you might be interested to do the same | 14:16 |
efried | edmondsw: I would rather get us into docs.o.o. Is that possible? | 14:16 |
edmondsw | I believe so, and it's on the TODO list | 14:17 |
edmondsw | in fact, I think that may be the only way to solve the current build issues, short of reverting some of what stephenfin did | 14:17 |
edmondsw | which I'd rather not do | 14:17 |
edmondsw | that will probably be the next thing I try | 14:18 |
edmondsw | that == moving to docs.o.o | 14:18 |
edmondsw | while we're talking about docs builds... I also noticed that one of our stable docs builds is broken, and all of our EOL tagged docs builds are broken | 14:18 |
edmondsw | lower priority, but also need to be fixed | 14:19 |
edmondsw | I hope we can also move them to docs.o.o but I'm not sure on that | 14:19 |
chhagarw | edmondsw: I want the updated code to reviewed once for the LPM change perspective | 14:19 |
efried | docs.o.o is latest only, I thought. | 14:19 |
edmondsw | efried no, it has older stuff too | 14:19 |
edmondsw | chhagarw I'll try to look later today | 14:20 |
edmondsw | anything else to discuss OOT? | 14:21 |
edmondsw | #topic Device Passthrough | 14:21 |
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)" | 14:21 | |
edmondsw | Eric has a couple things up for review: | 14:21 |
edmondsw | #link https://review.openstack.org/#/c/579359 | 14:22 |
edmondsw | #link https://review.openstack.org/#/c/579289 | 14:22 |
edmondsw | efried I've started commenting on both in parallel | 14:22 |
edmondsw | efried what do you want to add here? | 14:22 |
edmondsw | (i.e. I'm done talking, take it away) | 14:23 |
efried | Reshaper work is proceeding apace. Once that winds down, I'll probably be looking in nova (resource tracker and report client) to make sure nrp support is really there; as well as working through more of that series ^ | 14:23 |
efried | mdrabe: We're counting on you to be our second core reviewer for this series, in case you didn't have enough to do. | 14:24 |
edmondsw | mdrabe I know you have other things to focus on atm... probably let me get my comments up today first, and then look at it | 14:25 |
mdrabe | sounds good | 14:25 |
edmondsw | efried anything else? | 14:26 |
efried | no | 14:26 |
chhagarw | mdrabe: if u can have a look https://review.openstack.org/#/c/576034/ want you to check if this change does not impact NPIV lpm | 14:26 |
edmondsw | #topic PowerVM CI | 14:27 |
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)" | 14:27 | |
edmondsw | #link https://etherpad.openstack.org/p/powervm_ci_todos | 14:27 |
edmondsw | we've been having some CI stability issues that mujahidali is working | 14:27 |
mdrabe | chhagarw: will do | 14:28 |
edmondsw | I've helped some there, as has esberglu | 14:28 |
esberglu | Here's what I think is going on with CI. The underlying systems are a mess. Filesystems are full, vios issues, etc. | 14:28 |
edmondsw | yes | 14:28 |
esberglu | Everything else is just a symptom of that | 14:28 |
edmondsw | agreed | 14:28 |
edmondsw | question is how best to fix it | 14:28 |
mujahidali | I looked into the the neo-21 and found that pvmctl was not working so restarted the neo followed by | 14:28 |
mujahidali | pvm-core | 14:28 |
mujahidali | pvm-res | 14:28 |
mujahidali | and after that pvmctl worked for neo-21 | 14:28 |
mujahidali | I have cleared the other neo sytems as suggested by esberglu but still no luck, so, I decided to manually clear the ports. But it seems after cleaning them manually they are not coming back to active state | 14:29 |
esberglu | The ports are just going to keep failing to delete until the underlying issues are resolved | 14:29 |
esberglu | Are the /boot/ directories still full on some of the systems? | 14:30 |
mujahidali | managemnt nodes and most of the neo have only 30% filled /bbot/ directory | 14:31 |
mujahidali | */boot/ | 14:31 |
mujahidali | esberglu: do we need to again re deploy the CI after the cleanup and neo restart ? | 14:32 |
esberglu | Have you been restarting neos? If you restart them you need to redeploy them | 14:32 |
esberglu | And yes if they are broken because of full filesystems they need to be redeployed | 14:33 |
edmondsw | esberglu is it possible to redeploy a single neo, or do they all have to be redeployed as a group? | 14:33 |
mujahidali | so, redploying the cloud_nodes or only management_nodes will do the work ? | 14:33 |
esberglu | You should deploy the compute_nodes and the management_nodes | 14:34 |
mujahidali | okay | 14:34 |
esberglu | You can redeploy single nodes using the --limit command, I've given mujahidali instructions on that before, but let me know if you need help with that | 14:35 |
esberglu | At this point it's probably better to redeploy all of them though | 14:35 |
mujahidali | sure | 14:35 |
edmondsw | mujahidali have we fixed the VIOS issues? | 14:36 |
edmondsw | and you said "most" of the neos have only 30% filled in /boot... what about the others? | 14:36 |
mujahidali | for neo-26 and neo-30 ?? | 14:36 |
edmondsw | yes | 14:36 |
openstackgerrit | Eric Fried proposed openstack/networking-powervm master: Match neutron's version of hacking, flake8 ignores https://review.openstack.org/582686 | 14:36 |
openstackgerrit | Eric Fried proposed openstack/networking-powervm master: Use tox 3.1.1 and basepython fix https://review.openstack.org/582404 | 14:36 |
edmondsw | I want to address as much as we can before you redeploy to increase our chances of that fixing things | 14:36 |
mujahidali | I am not getting what exactly gone wrong with neo-26 and 30 | 14:37 |
edmondsw | ok, let's try to look at that together after this meeting, before you redeploy | 14:38 |
mujahidali | they(neo-26 and 30) are having sufficient /boot/ space as well | 14:38 |
mujahidali | edmondsw: sure | 14:38 |
edmondsw | anything else to discuss here? | 14:38 |
esberglu | Yeah I have some stuff | 14:39 |
esberglu | mujahidali: Have you created all of the zuul merger nodes? | 14:39 |
esberglu | So that I can stop maintaining mine soon? | 14:39 |
mujahidali | I want to try them with today's deployment for prod | 14:40 |
mujahidali | so let me deploy the prod with the new zuul mergers and if all went right then you can free yours | 14:41 |
esberglu | mujahidali: Please propose a patch with the changes | 14:42 |
mujahidali | sure | 14:42 |
esberglu | mujahidali: edmondsw: What's the status on vSCSI CI for stable branches? I think last I heard ocata was still broken there. I gave some suggestions | 14:43 |
esberglu | Is it still broken with those? | 14:43 |
esberglu | Is it worth moving forward with vSCSI stable CI for pike and queens only and skipping ocata for now? | 14:43 |
edmondsw | I thought we were going to split that commit into 1) pike and newer 2) ocata so that we could go ahead and merge #1 | 14:43 |
edmondsw | but I haven't seen that done yet | 14:44 |
mujahidali | I am able to stack it now with changes esberglu suggested | 14:44 |
edmondsw | yay! | 14:44 |
mujahidali | but there are 3 tempest failure | 14:44 |
edmondsw | mujahidali ping me the details after the meeting | 14:45 |
edmondsw | and we can work through that | 14:45 |
edmondsw | after we work through the other thing | 14:45 |
mujahidali | okay | 14:45 |
esberglu | edmondsw: mujahidali: There were a bunch of additional neo systems that we had slated for the CI pool. Did those ever get set up? | 14:46 |
mujahidali | no | 14:46 |
edmondsw | because we've been focused on other things, or is there another reason? | 14:47 |
mujahidali | we were hitting CI breaking very frequently so, didn't get a chance to a look at it. | 14:47 |
edmondsw | I think that's understandable... keeping the CI running takes priority | 14:48 |
esberglu | Last thing on my list was multinode CI. Any questions for me there mujahidali? I'm guessing not much work has happened there either with the CI stability issues | 14:49 |
mujahidali | I redeployed the staging CI using the changes suggested by esberglu for multinode | 14:49 |
edmondsw | and? | 14:51 |
mujahidali | the jenkins job failed. can I paste the log link here | 14:52 |
edmondsw | no, that's another thing we can talk about in slack | 14:52 |
mujahidali | sure | 14:52 |
edmondsw | I think that's it for CI? | 14:52 |
esberglu | All for me | 14:53 |
edmondsw | #topic Open Discussion | 14:53 |
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)" | 14:53 | |
mujahidali | I will be OOO next monday. | 14:54 |
edmondsw | I meant to bring this up when we were talking about OOT, but efried has fixed our specs so they build now. Thanks efried | 14:54 |
edmondsw | mujahidali got it, tx | 14:54 |
edmondsw | #endmeeting | 14:55 |
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack." | 14:55 | |
openstack | Meeting ended Tue Jul 17 14:55:18 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:55 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-07-17-14.06.html | 14:55 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-07-17-14.06.txt | 14:55 |
openstack | Log: http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-07-17-14.06.log.html | 14:55 |
*** k0da has quit IRC | 15:35 | |
*** esberglu has quit IRC | 16:28 | |
*** k0da has joined #openstack-powervm | 16:54 | |
*** esberglu has joined #openstack-powervm | 16:57 | |
*** esberglu has quit IRC | 16:58 | |
*** esberglu has joined #openstack-powervm | 16:58 | |
*** AlexeyAbashkin has quit IRC | 16:59 | |
*** chhagarw has quit IRC | 17:09 | |
*** mujahidali has quit IRC | 17:10 | |
*** chhagarw has joined #openstack-powervm | 17:29 | |
*** k0da has quit IRC | 17:37 | |
*** chhagarw has quit IRC | 17:45 | |
mdrabe | efried: Is it possible to make a nova-powervm change depend on a nova change? | 18:21 |
efried | mdrabe: Depends-On works for zuul but not for CI, IIRC. esberglu? | 18:22 |
esberglu | Yeah | 18:43 |
edmondsw | i.e., use Depends-On to keep things from merging in the wrong order, but we'll need to recheck the CI after the nova change merges | 18:46 |
*** k0da has joined #openstack-powervm | 19:01 | |
*** efried has quit IRC | 19:14 | |
*** efried has joined #openstack-powervm | 19:14 | |
edmondsw | efried posted comments on https://review.openstack.org/#/c/579359 | 20:05 |
edmondsw | I need to learn to insert "I" when I prefix something with an irc nick... | 20:06 |
edmondsw | or add ":" or something | 20:06 |
efried | edmondsw: My client adds : automatically. Yours doesn't? | 20:09 |
edmondsw | nope | 20:09 |
*** AlexeyAbashkin has joined #openstack-powervm | 20:22 | |
*** AlexeyAbashkin has quit IRC | 20:54 | |
efried | edmondsw: Got a sec to talk about allow/deny logic? | 21:14 |
edmondsw | efried fire away | 21:14 |
efried | edmondsw: | 21:15 |
efried | I thought we talked about making it an error if the same device was identified more than once in a file. But a) I don't see myself having written that down anywhere :( and b) it would be convenient to support generalized allow=true paragraphs overridden by more specific allow=false paragraphs. However, c) speccing that all out gets pretty complicated. What's simpler is to say that, if you want to allow only X devices ou | 21:15 |
efried | way, you just have to specify those X devices in individual paragraphs. Whereupon we don't need 'allow' at all, because you always allow devices that are mentioned and deny ones that aren't. | 21:15 |
edmondsw | that's probably good enough for the first pass, anyway | 21:17 |
edmondsw | and enhance later if needed? | 21:17 |
efried | edmondsw: If we did want to support the whole "set logic" thing, the rules would have to look something like: | 21:19 |
efried | - You can't have a device represented by more than one allow=true paragraph. That's an error. Because we wouldn't know which to use for resource_class, traits, etc. The yaml syntax, at least as we've designed it thus far, gives us the paragraphs in unpredictable order (it's a dict). | 21:19 |
efried | - You *can* have a device represented by more than one allow=false paragraph. | 21:19 |
efried | - We process allow=true paragraphs first, then process allow=false paragraphs and remove any devices we find (however many times we find 'em). | 21:19 |
efried | My concern is that that's kind of a complex semantic to try to document for the operator, and also to test. | 21:20 |
efried | So - I can make that a "stretch goal" and/or "future" if you're satisfied with that first thing I said. | 21:20 |
edmondsw | efried yeah, I'm ok with that being either stretch or future. | 21:22 |
efried | ack | 21:22 |
edmondsw | efried I think you spelled it out there pretty well, so I'm not sure it's too complicated to document... but it's not MVP either | 21:23 |
*** edmondsw has quit IRC | 21:36 | |
*** esberglu has left #openstack-powervm | 21:38 | |
*** esberglu has joined #openstack-powervm | 21:38 | |
*** esberglu has quit IRC | 21:38 | |
*** edmondsw_ has joined #openstack-powervm | 21:45 | |
*** edmondsw_ has quit IRC | 21:49 | |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: Spec: Device Passthrough https://review.openstack.org/579359 | 22:00 |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: Spec: Device Passthrough https://review.openstack.org/579359 | 22:30 |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: Passthrough whitelist schema and loading https://review.openstack.org/579289 | 22:39 |
*** k0da has quit IRC | 23:18 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!