16:01:00 #startmeeting ironic_bfv 16:01:01 Meeting started Thu Apr 27 16:01:00 2017 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:04 o/ 16:01:05 The meeting name has been set to 'ironic_bfv' 16:01:06 o/ 16:01:23 o/ 16:01:27 welcome back TheJulia 16:01:29 o/ 16:01:48 Thanks! 16:02:03 #link Our Agenda, as always https://wiki.openstack.org/wiki/Meetings/Ironic-BFV 16:02:23 #topic Announcements/Reminders 16:02:51 I'm back from vacation and two business trips \o/ 16:02:56 And somehow I'm still alive 16:03:11 Does anyone have anything to announce this week? 16:04:27 seems like a no :) 16:04:33 Yup 16:04:33 not sure if its an announce, but I'm hoping to help out here if I can 16:04:40 derekh: Welcome! 16:04:46 welcome! 16:05:00 Moving on! 16:05:02 thanks 16:05:05 #topic Current Status 16:05:22 I'm a little worried because I've not had time to digest the ether pad or check the review sets this morning. 16:05:45 #link https://etherpad.openstack.org/p/Ironic-BFV 16:06:15 Cinder driver - didn't get a ton done but I fixed a problem with failing docs tests this morning. I also introduced a patch in hopes of handling one of the TODOs there. I have it in discussion for later on 16:06:31 Awesome 16:06:39 I guess your the light gold color in the ether pad? 16:06:52 and orange 16:07:00 it seems to fade to gold after about a week :) 16:07:38 :) 16:09:18 Okay, looks like the ether pad is in decent shape, I just updated the notes on two of the revisions to be more up to date. Looks like https://review.openstack.org/#/c/406290 needs a rebase too 16:10:00 I guess that is it for status, there really is nothing else to cover it seems. 16:10:11 So if there are no objections, we can move on to discuss priorities 16:10:46 * TheJulia takes the silence as agreement to proceed 16:10:52 +1 16:10:57 #topic Planning/Priorities 16:13:09 Looks like hshiina found that there was some extra validation logic inside cinder that I didn't find when I dug through the code originally. Which seems kind of silly since it is asserting things that some drivers don't actually even use :( 16:13:18 But it is enforcing the contract as it were 16:13:35 good finds hshiina 16:14:14 So that seems like it is going to take some refactoring on our part, unless we just want to catch the error somehow and make it visible. I think he pointed this out in the validation checks on our side, so it makes sense to store the data and just double check on our end 16:15:24 The task at hand seems fairly clear actually, Anyone up for volunteering to tackle it? 16:15:53 TheJulia: is it just cinder driver changes? 16:16:24 to fix it I mean 16:16:37 Yes 16:17:03 I'll volunteer then, but I'm planning on just catching the errors (unless someone has a better option) 16:17:28 My brain needs to digest it a little more, to be honest 16:17:42 fair enough, we can discuss off meeting 16:17:43 I think catching the errors and returning them to the "operator" makes more sense 16:17:49 keeps ironic lighter weight 16:18:01 gotcha 16:18:19 That would be a topic my brain goes back and forth on though :) 16:18:55 #info mjturek to look at addressing hshiina's finds on the cinder driver with regards to required parameters for connections. 16:19:30 I'll try to rebase the storage interface calls wire-in before the next meeting. With the summit coming up, I have a few things on my plate so I'm not sure I'll get to it. 16:20:01 #info TheJulia to rebase the storage_interface wire-in change. 16:20:29 mjturek, TheJulia thanks. 16:20:53 I think that is good unless someone has plans or priorities to convey? 16:21:42 +1 for moving along 16:21:50 i agree that cinder driver is the priority 16:22:24 Moving along then! 16:22:46 #topic Discussion 16:23:27 So my first item was the TODO on line 271 here https://review.openstack.org/#/c/366197/39/ironic/drivers/modules/storage/cinder.py 16:24:26 TheJulia mentions that retrieving the target from volume_id is preferred 16:24:30 so I proposed this https://review.openstack.org/#/c/460250/ 16:24:38 #link https://review.openstack.org/#/c/366197/39/ironic/drivers/modules/storage/cinder.py#271 16:24:44 #link https://review.openstack.org/#/c/460250/ 16:25:15 #undo 16:25:15 Removing item from minutes: #link https://review.openstack.org/#/c/460250/ 16:25:19 #undo 16:25:20 Removing item from minutes: #link https://review.openstack.org/#/c/366197/39/ironic/drivers/modules/storage/cinder.py#271 16:26:08 Well, when did that stop working :( 16:26:10 #link https://review.openstack.org/#/c/366197/40/ironic/drivers/modules/storage/cinder.py 16:26:19 #link https://review.openstack.org/#/c/460250/ 16:26:30 not sure :( 16:27:24 Anyway, looking at it 16:28:35 Being able to query directly helps get rid of the loop on 270, which makes sense 16:29:29 cool, what about the fact that it returns a list of targets? The volume_id doesn't have a unique constraint so I figured it needs to be that way 16:29:58 I have no objection to adding the db api call and updating that code accordingly, or it gets rid of the loop on 269. Regardless, it becomes simpler and less looping 16:30:15 \o/ alright I'll rebase the driver on top of it and use it 16:30:23 Yeah, that I need to think about though 16:31:23 So as long as the volumes are limited to the node the task is executing on, I think it is okay 16:31:35 I mean targets, not volumes 16:31:48 if the targets returned are on different nodes, then that is problematic 16:31:48 if there's one where the node_uuid doesn't match, should it throw an exception? 16:32:14 okay I think that answers my question lol 16:32:18 heh 16:32:28 You could have multiple nodes connected to the same target though 16:32:42 hm 16:32:43 but they should have distinct records for each node in the targets 16:35:07 hmm, alright I think I'm confused then. I'll need to think that over 16:35:43 oh I think I get it 16:35:47 :) 16:36:11 anyway, probably a topic for the code review :) 16:36:32 Yeah, Anyway, I guess we're good for set discussion topics. Everyone ready to move along? 16:36:42 sure 16:37:21 yes 16:37:57 Excellent! 16:38:02 #topic Open Discussion 16:38:16 I have nothing else, other than I'm glad to be home :) 16:38:23 before I can help out on things I need to get myself familiar with whats going on, 16:38:23 if I get all the correct patches from the etherpad should I be able to boot a instance from a volume or is there more work yet to happen? 16:38:36 its always nice to be home ;-) 16:38:44 Once I am familiar it, I'm happy to take suggestions on how to help out 16:42:12 derekh, i guess we need more work. there is a wip patch in ehterpad 16:42:40 derekh: A little more work, mjturek was looking at getting things up and running in devstack. There is the tip patch that I posted to get feedback that needs to be finished 16:42:48 derekh: hshiina also detailed how to try out the patches with devstack. Take a look in the devstack section\ 16:42:55 Also, the nova changes, but hshiina and mjturek have been looking at that 16:44:37 I feel like someone else was seeking background/context for BFV earlier in the week that could also be helpful for you derekh, but I'm completely drawing a blank on who pinged me. 16:45:04 ok, I will take a look through the devstack section, to see how far I get, I'll ping should I hit any problems/questions, I only started setting up a env to try it out today so still feeling my way around 16:45:13 * TheJulia gets out ye olde jet lag sign and just holds it above her head 16:45:30 TheJulia: it was me, I mentioned in the virt sprint that I was hoping to help out 16:45:32 derekh: Awesome! 16:45:48 Oh, right! 16:46:02 I think I was walking into a datacenter during that conversation too :) 16:46:38 derekh: well, as with anything, we are just a ping away in #openstack-ironic :) 16:46:39 lol, anyways I can take a look at things and try them out, then I'll hopefully have something sensible to say next week 16:46:49 Excellent! 16:47:33 Out of curiosity, is anyone going to be in boston for the Summit? 16:47:45 not me 16:47:53 i'm not going 16:48:09 TheJulia: I'll be there :) 16:50:11 Awesome, I was just kind of curious since I'll be there as well. 16:50:47 Anyway, if we have nothing else to discuss, I say we call the meeting done, and get back to our various tasks for the day. 16:51:03 ttyl all 16:51:15 ttyl, thanks 16:51:28 thanks 16:52:25 Thank you everyone! 16:52:28 #endmeeting