Tuesday, 2018-06-26

*** edmondsw has quit IRC00:37
*** Vedanu has quit IRC01:05
*** AlexeyAbashkin has joined #openstack-powervm03:47
*** AlexeyAbashkin has quit IRC03:54
*** AlexeyAbashkin has joined #openstack-powervm03:54
*** AlexeyAbashkin has quit IRC04:04
*** openstackgerrit has quit IRC06:04
*** AlexeyAbashkin has joined #openstack-powervm06:13
*** Alexey_Abashkin has joined #openstack-powervm06:15
*** Alexey_Abashkin1 has joined #openstack-powervm06:16
*** AlexeyAbashkin has quit IRC06:18
*** Alexey_Abashkin1 is now known as AlexeyAbashkin06:18
*** Alexey_Abashkin has quit IRC06:19
*** AlexeyAbashkin has quit IRC07:05
*** AlexeyAbashkin has joined #openstack-powervm07:07
*** openstackgerrit has joined #openstack-powervm07:29
openstackgerritChhavi Agarwal proposed openstack/nova-powervm master: iSCSI volume detach after migration  https://review.openstack.org/57603407:29
*** edmondsw has joined #openstack-powervm12:58
*** gman-tx has joined #openstack-powervm13:11
*** esberglu has joined #openstack-powervm13:37
*** mujahidali has joined #openstack-powervm13:53
efriededmondsw: We doing this thing?14:02
edmondsw#startmeeting PowerVM Driver Meeting14:02
openstackMeeting started Tue Jun 26 14:02: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:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)"14:02
openstackThe meeting name has been set to 'powervm_driver_meeting'14:02
edmondswlink: https://etherpad.openstack.org/p/powervm_driver_meeting_agenda14:02
edmondswping gman-tx mdrabe mujahidali chhagarw14:02
edmondsw#topic In-Tree Driver14:03
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:03
edmondswlink: https://etherpad.openstack.org/p/powervm-in-tree-todos14:03
efriededmondsw: It would be neat to include TechM in these meetings once they're set up.14:04
edmondswefried agreed14:04
edmondswI don't know that we have a lot of IT work going on right now14:04
edmondswefried anything you want to talk about here?14:04
efriedWill defer to dev passthru topic.14:05
edmondsw#topic Out-of-Tree Driver14:05
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:05
edmondsw#link https://etherpad.openstack.org/p/powervm-oot-todos14:05
edmondswmdrabe any update on the MSP work?14:06
mdrabeHaven't started it yet14:06
edmondswI saw a new patch set from chhagarw but haven't looked yet14:07
edmondswesberglu has proposed some things porting changes back from the IT driver14:07
edmondswI think I still owe him a couple reviews there14:07
esbergluYep. They should be pretty easy reviews14:08
efriedI think I'm up to date on those.14:08
edmondswyeah, I looked at a couple on Friday I think14:08
edmondswmaybe all of them? I don't recall now14:08
esbergluEverything we needed to backport is either covered there or by a TODO on the etherpads14:08
edmondswanything else for OOT?14:09
edmondsw#topic Device Passthrough14:09
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)"14:09
edmondswefried ^14:09
efriedOkay, so Jay is back from his PTO (btw he left Verizon and is now working for yahoo) and I'm hoping he'll merge the last nrp-in-alloc-cands patch today.14:09
efriedor at least this week.14:10
efriedWhich will clear the way for us to implement our update_provider_tree with nested GPUs14:10
efriedWhich means edmondsw and I need to talk about what that's going to look like.14:10
efriedAnd probably write it down.14:10
efriedThough procedurally we want to avoid having to propose a blueprint to nova, because we're past spec freeze.  We maybe should have done that at the beginning of the cycle.14:11
edmondswdo it OOT first?14:12
edmondswand port IT for stein?14:12
efriedYeah, that's a good point.14:12
efriedAnyway, the first todo is to have that design discussion.  edmondsw, when are you available to do that?14:12
edmondswgood question :)14:13
edmondswI can probably find some time this afternoon if that works14:13
efriedDoes mdrabe need to be involved too?14:13
edmondswdoesn't have to be, but he might want to join us14:14
edmondswinvite him14:15
edmondswsounds like we're done there for now14:15
efriedOh, I figured you would do the calendar thing since you've got all the restrictions.14:15
edmondswefried ok :)14:15
efriedAnyway, beyond that I've still got some fup to do integrating new placement-isms into the scheduler - the newer generation handling stuff is exposing races (as it should) and I need to fix 'em.14:15
efriedand I owe cyborg some spec review.14:16
efriedThe more I look at cyborg the more involved I feel we're going to need to be to do our accelerator stuff.14:16
efriedLike, we're going to need to write os-acc plugins as soon as that's a thing.14:16
edmondswyes, I've wanted us involved from the start14:16
efriedhttps://review.openstack.org/#/c/577438/  <== review me14:17
edmondswI tried to push that when I first heard of it but nobody had bandwidth to get really involved there14:17
edmondswI'm glad you're getting more involved there14:17
efriedWell, we're only now getting to the point where the nova/cyborg interaction is being defined.14:17
efriedso it's not like we missed any boat or anything.14:17
edmondswright, I think we're fine14:18
efriedyup, just need to stay on top of it.14:18
edmondswanything else?14:18
efriedNot sure if there are others on the pvc team who want/need to become familiar in this space.14:18
efriednope, that's it from me.14:19
edmondswat this point I think it would be me and mdrabe, maybe madhavi as well14:19
*** chhagarw has joined #openstack-powervm14:19
edmondsw#topic PowerVM CI14:19
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)"14:19
edmondsw#link https://etherpad.openstack.org/p/powervm_ci_todos14:19
efriedas of yesterday, I think the CI was ill.  Is it back?  (I haven't looked yet today)14:20
edmondswPowerVM CI is failing for everything14:20
esbergluI looked at ci-watch yesterday, looks like it has been failing since it got back online14:20
esbergluFailing the test_show_update_rebuild_list_server test14:21
edmondswmujahidali have you looked at this?14:21
esbergluWhich was updated here https://github.com/openstack/tempest/commit/1fa4464404dd4400e1c0669dda29d696d3e5badb14:21
esbergluAnd here's the gerrit review https://review.openstack.org/#/c/526485/14:21
esbergluI haven't looked into why that test is failing, that should be enough to get mujahidali started14:21
edmondswesberglu tx14:22
esbergluWe can add it to the skip list temporarily if it isn't easy to debug14:22
edmondswI'll try to help take a look at that after the mtg14:22
edmondswesberglu there was an email question to you about moving the zuul merger instances to mujahidali14:23
edmondswplease look for that and reply when you can, should be quick14:24
esbergluedmondsw: I responded to the thread right before the meeting14:24
mujahidaliyeah, I looked into the failure, but didn't get much from the logs, thanks esberglu for the hlp14:24
edmondswoh, I see it now, sorry14:24
edmondswmujahidali when the CI is having issues like this, please ping me and/or efried so we know14:25
edmondswthat you've seen it14:25
edmondswand are working. And maybe we can help14:25
edmondswthe change that was blocking stable/pike vSCSI CI work merged (in neutron, if I remember correctly), so that should be unblocked when we can get back to it14:26
edmondswesberglu oh, yeah... ocata14:28
edmondswin devstack, for neutron14:28
edmondswmujahidali in last week's meeting we agreed that you would split out the pike and queens stuff so that we could get that merged14:29
edmondswand we would do ocata later14:29
edmondswbut if that has merged now, it may be easier to just do ocata here as well14:29
edmondswunless you hit more issues14:29
edmondswdoesn't look like anything has happened with 6596 since last week14:29
edmondswmujahidali please take a look at that once we get the CI working again14:30
mujahidaliwill try to close it asap14:30
edmondswesberglu do we have to use x86 for the zuul merger nodes, or could they be ppc64le?14:31
mujahidaliI have started looking into the multinode-setup as well , currently, trying out the steps mentioned by :esberglu on Staging environment.14:31
*** gman-tx has quit IRC14:32
esbergluedmondsw: They could be ppc64le14:33
esbergluI don't know of any reason they couldn't be I should say14:33
esbergluShould be fine as long as its still Ubuntu 16.04 I would think14:33
edmondswso mujahidali you might want to try setting those up in os4pcloud, where I think we can keep them from expiring14:34
edmondswnot sure it's worth the risk... but something to consider14:35
edmondswesberglu any other pros to having in jupiter?14:35
mujahidaliI will first deploy the ppc64 instances and will add them in host list and see if it's working then will revert to jupiter14:35
edmondswe.g. other things run there, so we're not susceptible to networking issues with os4pcloud today14:35
mujahidali*if ppc not working14:35
esberglumujahidali: Test it out on staging first14:36
edmondswanything else for CI?14:37
chhagarware there any open issues with nova-powervm CI14:37
edmondswchhagarw yes, the CI is totally busted right now14:37
edmondswwe're working on it14:37
edmondsw#topic Open Discussion14:38
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:38
edmondswwe got back the draft image of our PowerVMStackers mascot14:39
edmondswI emailed it around14:39
edmondsweveryone ok with it? The feedback I've heard so far has been positive14:39
esbergluedmondsw: I like it14:39
*** efried has quit IRC14:40
*** efried has joined #openstack-powervm14:40
edmondswefried and gman-tx also gave thumbs up14:40
edmondswand svenkat14:41
*** chhavi__ has joined #openstack-powervm14:41
edmondswunless I hear something negative shortly, I'll reply to Kendall and tell her it's good.14:41
edmondswthat's all I had... anything else?14:41
*** chhagarw has quit IRC14:41
edmondswchhavi__ did you want to give an update on iSCSI work?14:42
edmondswyou missed the OOT discussion where that would normally go14:43
edmondswguess not14:44
edmondswalright, thanks folks14:44
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."14:44
chhavi__yeah, on iSCSI we one change set, I am incorporating the reviews for the sme14:44
openstackMeeting ended Tue Jun 26 14:44:13 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-06-26-14.02.html14:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-06-26-14.02.txt14:44
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-06-26-14.02.log.html14:44
chhavi__edmondsw: apart from the one open review, we don't need any additional changes for iSCSI.14:45
edmondswgreat, tx14:45
chhavi__there is a CI failure for this14:45
edmondswchhavi__ we don't link IBM-internal stuff here14:46
edmondsware you saying that the nova-powervm change depends on a pypowervm change?14:46
chhavi__no they are independent14:48
chhavi__pasted the wrong link: I was mentioning about this review: https://review.openstack.org/#/c/576034/14:49
edmondswchhavi__ I'll try to review today14:50
*** gman-tx has joined #openstack-powervm14:57
*** AlexeyAbashkin has quit IRC15:01
*** gman-tx has quit IRC15:03
*** AlexeyAbashkin has joined #openstack-powervm18:25
edmondswefried what's the best way to have a commit go back to the n-1 patch set?18:35
efriededmondsw: We should ask the lawyers whether we can remove the stupid copyright dates from all our files.  Their provenance is indelibly and eternally discoverable via git, so the dates are at best redundant and at worst (and usually) wrong.18:35
edmondswefried good luck with that18:35
efriededmondsw: git review -d <change_number>,<ps_number>18:35
edmondswthat'll pull it down... then just git-review it?18:36
efriedI think they fixed the bug where you couldn't then just git review that back up.  But if not, make a trivial change and push it.18:36
*** chhavi__ has quit IRC18:37
*** mujahidali has quit IRC18:40
*** AlexeyAbashkin has quit IRC19:13
*** AlexeyAbashkin has joined #openstack-powervm19:13
*** AlexeyAbashkin has quit IRC19:14
efriedmdrabe: edmondsw: If we're not trying to identify which cards are what types, then how do we know what resource class to use when creating the inventory?  Answer: our yaml paragraph includes a section where they can identify the resource class; otherwise we default to CUSTOM_IOSLOT or similar.  Y'all cool with that?20:15
mdrabeefried: Yea that makes sense to me20:16
*** esberglu has quit IRC21:47
*** esberglu has joined #openstack-powervm21:56
*** esberglu has quit IRC22:01
*** edmondsw has quit IRC22:04
*** esberglu has joined #openstack-powervm22:05
*** esberglu has quit IRC22:05
*** edmondsw has joined #openstack-powervm22:07
*** edmondsw has quit IRC22:11
openstackgerritEric Berglund proposed openstack/nova-powervm master: Snapshot In-tree Backports  https://review.openstack.org/57663022:13
openstackgerritEric Berglund proposed openstack/nova-powervm master: DiskAdapter Parent Class In-tree Backports  https://review.openstack.org/57721222:13
openstackgerritEric Berglund proposed openstack/nova-powervm master: Localdisk In-tree Backports  https://review.openstack.org/57728722:13
openstackgerritEric Berglund proposed openstack/nova-powervm master: vSCSI In-tree Backports  https://review.openstack.org/57751522:13
efriedmdrabe: https://etherpad.openstack.org/p/powervm-device-passthrough22:14
mdrabenice thnx22:15
openstackgerritEric Berglund proposed openstack/nova-powervm master: DiskAdapter Parent Class In-tree Backports  https://review.openstack.org/57721222:27
openstackgerritEric Berglund proposed openstack/nova-powervm master: Localdisk In-tree Backports  https://review.openstack.org/57728722:27
openstackgerritEric Berglund proposed openstack/nova-powervm master: vSCSI In-tree Backports  https://review.openstack.org/57751522:27
openstackgerritEric Berglund proposed openstack/nova-powervm master: vSCSI In-tree Backports  https://review.openstack.org/57751522:32

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