16:00:03 #startmeeting ironic_bfv 16:00:04 o/ 16:00:08 Meeting started Thu Mar 30 16:00:03 2017 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:11 The meeting name has been set to 'ironic_bfv' 16:00:37 o/ 16:00:48 Good morning, afternoon, evening everyone! 16:00:57 Our agenda today has a few discussion items \o/ 16:01:09 #link https://wiki.openstack.org/wiki/Meetings/Ironic-BFV 16:01:21 #topic Announcements/Reminders 16:01:52 I have none at the moment, does anyone have anything they would like to make a note of today? 16:02:28 i have nothing 16:02:39 Okay then, moving on! 16:02:44 #topic Current Status 16:03:04 I see we have a number of notes in the etherpad today \o/ 16:03:14 #link https://etherpad.openstack.org/p/Ironic-BFV 16:04:22 Looks like the cinder interface has some feedback that might need to be addressed 16:05:04 And there is some ongoing discussion in https://review.openstack.org/#/c/366197/ 16:05:07 o/ 16:05:09 sorry I am late. 16:05:12 o/ joanna 16:05:40 No worries, we were just taking a minute to review the etherpad. 16:06:08 I'll update the interface patch 16:06:12 I updated the status on the etherpad for the cinder common code revision, there is feedback on it. 16:06:17 Awesome, Thank you joanna 16:06:44 mjturek: I see you've left some notes, can you give us a quick summary? 16:07:03 I'm wondering if we should handle this in attach, or rather fail and let the caller call detach 16:08:24 That might make more sense 16:09:13 Anyway, I guess mjturek is busy right now, so we can move on. 16:09:35 TheJulia I'm sorry - on a call will be on ASAP 16:09:35 or maybe call abort and do the cleanup in abort, se we return in somewhat clean state. I'll think about it :) 16:10:00 mjturek: no worries! 16:10:09 #topic Planning/Priorities 16:10:48 It appears that mjturek has been looking at devstack stuffs, and continues to do so. That is a relatively high priority for our velocity. 16:11:17 joanna: Any idea on timing for the interface revision? 16:11:51 ~3hours? 16:12:13 awesome 16:12:20 :) 16:12:45 My one ask is that everyone takes some time out before mid next week to review https://review.openstack.org/#/c/355625/ which is the cinder common code. 16:12:53 #link https://review.openstack.org/#/c/355625/ 16:13:29 Aside from that, I guess we're good to move into discussion, unless someone has questions relating to priority or planning? 16:14:14 i aggree the plan and have no question 16:14:22 Excellent 16:14:27 Moving on then.... 16:14:31 #topic Discussion 16:16:03 * mjturek is back 16:16:20 Today we have three items, the first is the question of the MAC address to IP lookup. This is raised from a question hshiina raised on, I believe the cinder common code since it doesn't support that presently, and I believe we need to address that in ironic since we can't in nova. hshiina I see you also mentioned the nova patch and possible solutions to the 16:16:20 original issue of MAC -> IP lookups? 16:17:15 TheJulia, yes 16:17:32 TheJulia: by cinder common code do you mean os_block? 16:17:40 or is that separate? 16:17:48 os-brick* 16:17:48 mjturek: the ironic cinder common code 16:17:52 oh! 16:17:56 sorry understood 16:18:01 mjturek: no worries 16:18:14 TheJulia, hshiina: the comments are in the driver patch 16:21:05 hshiina: Looking at the ironic nova driver comments, I would think the attach could only actually take place after the node the node has been spawned in ironic, or at least in process, which makes me think the best thing to do is still let ironic handle the attachments in it's workflow 16:22:16 Ahh, I also see the note about it might be difficult to just somehow skip it :\ 16:22:31 So we could possibly need the info in both places. :( 16:22:47 Well, that kind of renders that discussion pointless until we have more clarity. 16:23:20 I guess we should move on then? 16:23:34 TheJulia: I have a question about mac 16:23:38 TheJulia, yes. i will add some memo to etherpad later 16:23:59 TheJulia, about this issue 16:24:03 since spec says it's valid - what is the actual reason behind mac to ip conversion 16:25:08 if I define a mac to be part of a storage network, I don't know it's IP until I deploy. It would be a reasonable way to preserve the fact that it is valid in the hardware configuration. 16:25:21 hshiina: Awesome, thank you 16:26:13 joanna: does that answer your question? 16:26:48 Possibly the other context is that the connector intent was to be as generic as possible to provide storage as much connector information as possible. 16:26:58 TheJulia: yes. Why does spec include mac support? 16:27:51 I believe it is more-so you can define "this network card is always part of the storage fabric, lean towards using it" concept, but I honestly don't remember at this point. 16:28:52 thanks :)! 16:28:56 Moving on, the next item is... 16:28:59 Cinder storage interface should_write_image() logic and deployment skip logic addition 16:30:42 hshiina pointed out, i believe in the ipxe template patch, that the logic for that had not yet been proposed. I can likely do it fairly quickly in the next week or so. I just think it should be an additional patch on top of the ipxe template change. If there are no objections, I'll try and put that together before next thursday. 16:31:54 no objection, thanks 16:32:03 Awesome 16:32:44 In that case since, our last item is raised by hshiina, wondering if we should split apart the API patches. 16:33:21 From an ironic review standpoint, it is rather painful to get two independent API changes in in order since each one results in a micro version bump. 16:33:42 hshiina: Is your reasoning to split it just over review velocity? 16:34:46 TheJulia, yes. I have heard large patch is difficult to review in some other patches. 16:35:06 hshiina: what is the proposed split? Volume and VolumeConnector? 16:35:36 I think we should push it to the priority list for the next week, this can solve the issue of lack of reviews 16:35:39 joanna, VolumeConnector and VolumeTarget 16:36:17 I agree with joanna 16:36:39 seems doable 16:37:03 I volunteer as a reviewer :) will look at that later today or tomorrow 16:37:18 That way we get some of the later review/nitpicking out of the way, of course, the changes have functionally been up for a long time. It just seems like we should be able to review and agree if there is more work required in that patch. 16:37:48 A single api change will be much easier to land overall, so I don't think we should split them apart. 16:39:14 #action TheJulia will raise it in the ironic meeting on monday. 16:39:36 TheJulia, thanks 16:39:41 Anything else on this topic? 16:40:00 #undo 16:40:00 Removing item from minutes: #action TheJulia will raise it in the ironic meeting on monday. 16:40:30 #action TheJulia will raise the API patch in the ironic meeting on monday for reviews. 16:40:54 * TheJulia hears crickets :) 16:41:12 #topic Open Discussion 16:41:26 so I can give a summary of devstack investigation 16:41:39 mjturek: that would be awesome :) 16:42:27 basically I've been looking for anything in virtualbmc or the libvirt guests that we'd need to do differently. I don't forsee any changes there 16:42:31 just FYI: I looked at the sequence diagram shown by cinder team, that shows async communication (the one that caused the discussion an -1s on the interface patch). Nova uses the same client, which makes sync REST call, so everything is sync from our perspective 16:42:58 what I think it's going to come down to is just setting the configs for a boot from volume tempest test 16:43:14 I believe all the config changes are in the cinder common code patch? 16:43:47 mjturek: yes, the config will include additional fields 16:44:03 anyways, I also linked to the tempest test that nova does which we'll probably want to do 16:44:07 do we already have devstack with cinder plugin? 16:44:23 well ironic and cinder stack together fine 16:44:31 but I haven't tried with the patches 16:44:41 hshiina: it seems like you might've already though? 16:45:02 mjturek, i tried devstack with the patches. 16:45:14 cool, and nothing strange there? 16:45:34 mjturek, stack.sh succeeded 16:45:42 nice! 16:46:26 anyway, I want to try that myself this week and see if I can get devstack to be ready to go for something similar to that tempest test 16:46:28 hshiina: awesome :) 16:47:22 mjturek: I think we're just missing one vital piece to the puzzle, but I'll try to get that hammered out (the missing skip deployment check, which shouldn't be difficult to take care of for me in the next few days) 16:47:49 cool cool 16:48:23 Awesome, sounds like we're on a good path. Anything else to discuss or shall we all get ten minutes back? 16:48:53 i have nothing to discuss 16:49:04 good for now 16:49:55 i'm good 16:50:00 Awesome! Thank you everyone, and have a wonderful rest of the day! 16:50:23 thank you 16:50:33 thank you, TheJulia, hshiina, mjturek :) 16:50:37 #endmeeting