Tuesday, 2018-08-14

*** openstackgerrit has quit IRC01:06
*** esberglu has quit IRC02:43
*** esberglu has joined #openstack-powervm02:45
*** esberglu has quit IRC02:50
*** esberglu has joined #openstack-powervm02:56
*** esberglu has quit IRC03:00
*** esberglu has joined #openstack-powervm03:06
*** esberglu has quit IRC03:10
*** esberglu has joined #openstack-powervm03:16
*** esberglu has quit IRC03:24
*** esberglu has joined #openstack-powervm03:35
*** esberglu has quit IRC03:40
*** esberglu has joined #openstack-powervm03:45
*** esberglu has quit IRC03:50
*** esberglu has joined #openstack-powervm03:55
*** esberglu has quit IRC03:59
*** esberglu has joined #openstack-powervm04:26
*** esberglu has quit IRC04:30
*** esberglu has joined #openstack-powervm04:36
*** esberglu has quit IRC04:40
*** esberglu has joined #openstack-powervm04:46
*** esberglu has quit IRC04:50
*** esberglu has joined #openstack-powervm04:56
*** esberglu has quit IRC05:01
*** esberglu has joined #openstack-powervm05:06
*** esberglu has quit IRC05:10
*** esberglu has joined #openstack-powervm05:26
*** esberglu has quit IRC05:30
*** esberglu has joined #openstack-powervm05:35
*** esberglu has quit IRC05:40
*** esberglu has joined #openstack-powervm05:45
*** esberglu has quit IRC05:50
*** esberglu has joined #openstack-powervm06:00
*** esberglu has quit IRC06:05
*** esberglu has joined #openstack-powervm07:32
*** esberglu has quit IRC07:37
*** openstackstatus has quit IRC08:12
*** esberglu has joined #openstack-powervm08:54
*** esberglu has quit IRC08:58
*** esberglu has joined #openstack-powervm09:25
*** esberglu has quit IRC09:29
*** openstackstatus has joined #openstack-powervm09:41
*** ChanServ sets mode: +v openstackstatus09:41
*** esberglu has joined #openstack-powervm09:55
*** esberglu has quit IRC10:00
*** antxon has quit IRC10:07
*** esberglu has joined #openstack-powervm10:25
*** esberglu has quit IRC10:30
*** esberglu has joined #openstack-powervm12:38
*** esberglu has quit IRC12:43
*** esberglu has joined #openstack-powervm13:08
*** esberglu has quit IRC13:13
*** mujahidali has joined #openstack-powervm13:20
*** esberglu has joined #openstack-powervm13:44
*** gman-tx has joined #openstack-powervm13:56
edmondsw#startmeeting PowerVM Driver Meeting14:02
openstackMeeting started Tue Aug 14 14:02:59 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
openstackThe meeting name has been set to 'powervm_driver_meeting'14:03
edmondsw#link agenda: https://etherpad.openstack.org/p/powervm_driver_meeting_agenda14:03
edmondswefried mujahidali mdrabe gman-tx ^14:04
edmondsw#topic In-Tree Driver14:04
edmondswnothing new here for Rocky14:05
efriedI'm going to propose update_provider_tree probably this week, hopefully today.14:06
edmondswah, true14:06
efriedoh, but not for rocky.14:06
edmondswyou are going to do that both IT and OOT, right?14:06
edmondswright, it would just be Stein14:06
efriedI don't see us doing anything more for rocky at this point.14:07
efriedunless we find actual bugs14:07
edmondswin the coming weeks we'll need to start talking about what else we do in Stein, but I'm not sure we're ready to dig into that today14:07
edmondswyep, I think we're done with Rocky14:07
edmondsw#topic Out-of-Tree Driver14:07
edmondswas efried mentioned, will be update_provider_tree changes coming soon here14:08
gman-txwhat do we mean by soon?14:08
efriedthis week / today14:08
edmondswsee above... "hopefully today"14:08
gman-txgot it14:08
efriedThis will be a backward-compatible update_provider_tree, btw.14:09
efriedWhich will then be extended later for dev passthrough work (coming up in a later topic in this meeting)14:09
edmondswyep, there is nova code that has been doing x for us, and we're just reproducing x in our code as the first step, and then we'll start tweaking it14:10
edmondswmdrabe I'm still trying to get a multinode devstack working for you in my spare minutes here and there14:11
edmondswif this is blocking you and you want to try to work on it yourself, let me know and I can get you access to the systems.14:11
edmondswotherwise, hopefully I can get that done this week14:12
edmondswlearning a lot about devstack14:12
edmondsw(especially networking)14:12
edmondswon a brighter note, I got the readthedocs builds working for nova-powervm and networking-powervm14:13
edmondswand we branched stable/rocky and tagged rc1 for all the *-powervm projects and14:13
edmondswhave updated stable/rocky's .gitreview and tox.ini to point to rocky14:14
edmondswanything else for OOT discussion?14:14
efriedI've been keeping an eye on the req project, still hasn't forked.14:15
edmondswyeah, it'll probably be a couple weeks14:15
edmondswtx for looking out14:15
edmondswgman-tx all the storage work that I'm aware of your team doing has been merged at this point... anything else coming?14:15
gman-txthat should be it14:16
edmondsw#topic Device Passthrough14:16
edmondswefried over to you14:16
efriedokay, patch series is up through the driver work.14:17
efried#link device passthrough nova-powervm series https://review.openstack.org/#/q/status:open+project:openstack/nova-powervm+branch:master+topic:bp/device-passthrough14:18
efriedThe WIP needs test, but it passes our CI, which means a) the update_provider_tree bits for the compute RP are backward compatible; and b) we (probably) properly no-op the child providers when no inventory.yaml is specified.14:18
efriedThe spec is getting attention and has some good (post-merge) commentary on it14:21
efriedpursuant to which I believe I'm actually going to post a fup patch to edit accordingly, and it will impact the design.14:21
edmondswnova or nova-powervm spec?14:21
efried#link merged nova-powervm device passthrough spec https://review.openstack.org/#/c/579359/1014:22
efriedMeanwhile, kosamara has published a corresponding spec in nova that is libvirt-focused.14:22
edmondswhey, look at that... non-powervm folks commenting on our spec, I like it14:22
efried#link proposed nova spec for PCI-via-placement https://review.openstack.org/#/c/591037/14:23
efriedI have, ahem, reviewed it with some suggestions.14:23
efriedTL;DR, what I'd like to see is for that spec to a) define more clearly the split of responsibilities between the virt driver and the rest of nova; and b) include both powervm and libvirt, so we can be more sure that split is being done appropriately.14:24
efriedThere is a possible future where we land generic device passthrough in the powervm driver *in tree* in Stein.14:24
edmondswthat'd be nice14:25
gman-txyea it would14:25
edmondswI think we're about to the point where it makes sense to be doing co-development IT and OOT14:25
edmondswand this would be the perfect topic on which to do that14:26
efriedDon't hatchet your counts before they chicken, but it's a possibility.14:26
edmondswyep, understood14:26
efriedThe plan for this week is14:27
efried- Split https://review.openstack.org/589668 into a) generic backward-compatible compute-node-only update_provider_tree outside (but as a prereq) of the dev passthrough series; and b) add device passthrough to (a) within the series14:28
efried- Mirror ^ (a) in tree14:28
efried- Propose a spec update14:28
efried- Keep shepherding the nova spec14:28
edmondswsounds good14:29
edmondsw#topic PowerVM CI14:29
edmondswmujahidali you're up14:29
mujahidaliCI looks good after the outage and redeployment.14:30
mujahidaliWe are able to stack successfully for multinode setup on stage env(thanks to :esberglu) but there are 3 tempest failures.14:31
edmondsware you looking at those? Let me know if you need help14:32
mujahidaliyeah, I need help.14:32
mujahidaliand fo the vscsi stable ocata also, there are 3 tempest failures.14:32
edmondswok, ping me details after the meeting14:34
edmondswmujahidali have you started working to add rocky to the CI?14:34
mujahidalinot yet.14:34
esberglumujahidali: Sounds like the zuul merger issues are resolved. Most of those are 1 time setup steps for new servers14:35
edmondswshouldn't be too difficult... but I'd like it done sooner rather than later14:35
edmondswmaybe something you can work on tomorrow?14:35
edmondsw(I mean the rocky CI)14:35
esbergluHowever, the steps should be automated in the playbooks so that we don't hit the same issues if we ever use new merger severs14:36
esbergluOr, at a minimum, the steps should be documented14:36
mujahidaliI wanted to give it a try today, but I already deployed the CI with multinode change, so most probably will do it on thursday(tomorrow is holiday).14:36
esberglumujahidali: You shouldn't need to do a full redeploy to test the stable/rocky zuul changes14:37
mujahidaliesberglu: thanks for the help for resolving the zuul_merger issues.14:38
esbergluYou can just edit /etc/zuul/layout/layout.yaml14:38
esbergluAnd then restart the zuul service14:38
edmondswesberglu it looked like you enabled stable/queens CI runs without trying on staging first? The commit included updates to both staging and production yaml in one commit14:38
edmondswor maybe you tried manually?14:39
edmondswwhat do you suggest?14:39
esbergluedmondsw: I'm sure I went through manual runs for the new local.conf files14:39
esbergluFor the zuul layout.yaml I probably didn't even test them tbh14:40
esbergluI would test the new local.confs. Then make sure I'm on the zuul layout review14:41
edmondswpretty straightforward14:41
edmondswok, anything else for CI?14:42
esberglumujahidali: Do you have time to take this patch over?14:42
mujahidaliesberglu: apart from changing the /etc/zuul/layout/layout.yaml I think I need to redeploy the cloud_nodes and zuul_mergers.14:42
edmondswmujahidali if zuul mergers are working now, why redeploy?14:44
esberglumujahidali: To start running changes on stable/rocky, you just have to make the change to the zuul layout.yaml file and restart the zuul service14:44
esbergluNo redeploy is necessary14:44
mujahidali:esberglu will take it https://review.openstack.org/#/c/565239/, but will need a little bit help as well.14:44
edmondswmujahidali but first need to make the powervm-ci changes to add local.conf for rocky14:44
esbergluThe new local.conf files *should* just work. Unless something has gone into rocky that is breaking since they branched14:45
esbergluJust copy the master local.conf files14:46
edmondswesberglu yep, should be simple14:46
edmondswand I'd like that done quickly so that if we need to make any changes on rocky, i.e. a bug fix, it will be tested by CI14:46
edmondswso that should take precedence over multinode, vscsi, etc.14:47
mujahidaliI think it should be completed by end of this week.14:48
edmondswlet's shoot for Thursday if we can14:48
edmondswif you can get things ready for review Thursday, I will try to review quickly14:49
edmondswesberglu I'm hoping you could also review quickly14:49
edmondswalright, moving on14:50
edmondsw#topic Open Discussion14:50
edmondswanything else to discuss?14:50
mujahidaliI will be OOO from 22nd to 24th.14:50
esbergluedmondsw: Yeah I can review quickly, just ping me when they are ready14:50
efriedPTG and summit?14:51
efriedNegotiations for the former have commenced. Anything to report?14:51
edmondswI expect efried gman-tx and myself to be attending the PTG but haven't received final word14:51
edmondswsummit discussions aren't as far along14:52
edmondswprobably similar14:52
efriedUpdate on dev passthrough topic: sean-k-mooney is proposing an alternative schema14:52
efried#link etherpad to brainstorm device passthrough schema https://etherpad.openstack.org/p/generic-device-schema14:52
edmondswwill look14:53
efriedno hurry, imagine it'll go on for a bit, just thought I'd bring it up.14:55
edmondswsounds like that's it for today14:56
edmondswthanks everyone14:56
openstackMeeting ended Tue Aug 14 14:56:17 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-08-14-14.02.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-08-14-14.02.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-08-14-14.02.log.html14:56
efriededmondsw: Knee-jerk reaction to Sean's proposal is I don't like it, but a lot of that may just because it's not mine. Would like your opinion.15:18
edmondswyep, will try to look in a bit15:24
efriedgman-tx, edmondsw: Do we have use for this? https://review.openstack.org/#/c/580336/2/specs/rocky/approved/support-deleting-data-volume-when-destroying-instance.rst16:43
efriedI'm guessing pvc handles this on top; but might be nice if we could use community code for that and eliminate the debt.16:44
edmondswefried I think that might help us, yes. I sent a question to finken16:48
efriedcool. My work here is done.16:48
edmondswwould need to be proposed for stein, not rocky :)16:50
efriededmondsw: On your radar to propose that tweak to the goofy gc test in pypowervm, right?17:22
edmondswefried yes but behind some other things17:22
efriedokay, just making sure it wasn't on *my* radar :P17:23
edmondswefried I got this from finken:17:23
edmondsw"Hmm, may actually make things worse, as it would be one more way that volumes could get accidentally deleted, which would be the worst thing that can happen.  The only benefit would be that it could potentially make our current logic slightly more streamlined, but we already have what we have in place, so that's not that interesting."17:23
efriededmondsw: Roger that. Does pvc allow/support the user making changes to VMs through nova, bypassing pvc?17:24
efriedcause that would be the only way this would be able to impact you negatively.17:25
efried...assuming you otherwise ignored it.17:25
edmondswyes, we support users calling OpenStack APIs17:25
efriedI see.17:25
efriedWell, I leave it in y'all's capable hands.17:25
edmondswI'm not too worried about negative impact here... if a user calls an API, that's on them17:26
*** gman-tx has quit IRC17:28
*** mujahidali has quit IRC17:48
*** esberglu has quit IRC20:32
*** openstackgerrit has joined #openstack-powervm21:51
openstackgerritEric Fried proposed openstack/nova-powervm master: Inventory whitelist schema and loading  https://review.openstack.org/57928921:51
openstackgerritEric Fried proposed openstack/nova-powervm master: Filter IOSlots per inventory config yaml  https://review.openstack.org/58930621:51
openstackgerritEric Fried proposed openstack/nova-powervm master: Placement-isms for inventory items  https://review.openstack.org/58930721:51
openstackgerritEric Fried proposed openstack/nova-powervm master: WIP: update_provider_tree with device exposure  https://review.openstack.org/58966821:51
openstackgerritEric Fried proposed openstack/nova-powervm master: PowerVM: update_provider_tree() (compatible)  https://review.openstack.org/59185721:51
efriededmondsw: ^21:51
*** esberglu has joined #openstack-powervm21:56
esbergluedmondsw: See my email, I think I figured out the vSCSI CI issue21:57
edmondswesberglu awesome tx21:57

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