16:00:33 #startmeeting ironic_bfv 16:00:33 Meeting started Thu Jun 1 16:00:33 2017 UTC and is due to finish in 60 minutes. The chair is mjturek. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:37 The meeting name has been set to 'ironic_bfv' 16:00:44 o/ 16:00:51 Hey everyone, welcome to the Ironic-BFV weekly meeting 16:01:11 As always our agenda is here 16:01:14 o/ 16:01:14 #link https://wiki.openstack.org/wiki/Meetings/Ironic-BFV 16:01:51 #topic Announcements/Reminders 16:02:13 So it looks like our agenda this week hasn't been updated. Sorry about that 16:02:19 just wanted to ask :) 16:02:29 :) 16:02:47 Does anyone have anything they'd like to announce? 16:03:05 well, we're approaching Pike-2 16:03:21 which does not affect us directly, but is a sign that we should speed up :) 16:03:46 agreed, we do have a patch on the nova side that we might need to focus on 16:04:06 yep 16:04:19 and it's blocked on ironicclient change, which is blocked on API 16:04:28 oh right 16:05:09 alright, let's move on to planning. Any objections? 16:05:20 not from me 16:05:42 #topic Planning/Priorities 16:06:10 Looks like we still need to push on the next two patches in the chain. Not sure we need to adjust 16:06:28 personally I'm going to try to focus more on reviews 16:06:50 does anyone have any input here? 16:07:37 also, I'm still looking into moving out the storage operations. Read through vdrok's spec which is pretty straight forward, but still need to talk to him 16:07:56 *moving the storage operations out of the driver level to the conductor that is 16:08:13 yeah 16:08:17 Thats to address the comments in the first patch? 16:08:41 derekh: correct though there might be some other operations further down the chain I need to check 16:08:51 ok 16:09:13 TheJulia's patch to skip deployment comes to mind 16:09:52 i added the patch to the chain 16:09:58 it got non-wip 16:10:22 hshiina: looking 16:10:33 is there any piece of work that needs doing that isn't already being worked on? /me has a better handle on how everything is glued together now 16:11:11 derekh: Tempest tests have fallen to the backburner if you'd like to take a look there 16:11:36 mjturek: can do, 16:11:39 cool 16:11:46 #info derekh to look into tempest tests 16:11:55 i posted a few patches for devstack 16:11:56 thanks!! 16:12:10 hshiina: I'm not finding the other patch you mentioned, can you link? 16:12:30 hshiina: I've tried out the devstack stuff and successfully booted from volumes 16:12:46 mjturek, https://review.openstack.org/#/c/466333/ 16:12:50 w00t 16:13:02 I also stumbled accross the workaround patch, might be worth mentioning it in the etherpad 16:13:03 derekh: that's awesome! 16:13:47 hshiina: I was actually trying this out the other day but didn't get it to stack properly. 16:13:55 this one https://review.openstack.org/#/c/441944/ 16:14:35 maybe we should continue this in discussion 16:14:43 any objections for moving on to that? 16:15:16 cool 16:15:21 #topic Discussion 16:15:51 derekh: hshiina: have you tried stacking with the devstack patches recently? 16:16:15 wondering if we need to rebase of if it's something on my end 16:17:06 mjturek: my working devtest is from yesterday I think 16:17:17 hmm what distro derekh? 16:17:45 mjturek: fedora 16:17:53 ahhh okay, I'll give that a shot 16:17:57 F25 16:18:02 thx 16:18:17 hshiina: Thanks for the devstack patch, it looks great! 16:18:33 mjturek, you're welcome 16:19:32 my colleagues also started working for tempest 16:19:40 they will give some output 16:20:01 hshiina: do you have their nick on hand so derekh can reach out to them? 16:20:29 Hi that is me 16:20:31 mjturek: phuongnh and tiendc 16:20:45 cool hi phuongnh and tiendc 16:21:07 tiendc: hi, if there is anything you want me to help out on please ask (or test or however I can help) 16:21:22 #info phuongnh and tiendc are looking into tempest tests as well. 16:21:24 Thanks. Sure. 16:22:01 hshiina: I was wondering if you could elaborate on your comment here 16:22:05 #link https://review.openstack.org/#/c/454243/ 16:22:22 specifically Line 394 16:23:04 when does this happen in a normal deployment? 16:23:24 https://review.openstack.org/#/c/454243/3/ironic/drivers/modules/agent.py@394 16:24:01 usually pxe is set up in boot.prepare_ramdisk and boot.prepare_instance 16:24:14 yes, sure 16:24:18 ahhh understood 16:24:28 which we obviously skip in BFV 16:25:27 actually.. nvm I'm not sure of that 16:26:58 anyway - thanks for shedding some light there 16:27:03 does anyone else have anything? 16:27:39 alright moving on! 16:27:46 #topic Open Discussion 16:28:00 anything else people would like to discuss? 16:28:31 I' 16:28:44 ll give it 2 minutes 16:28:51 otherwise we can end early 16:29:43 Hi I want to ask about CI gate. Do we need to add a new CI gate for bfv? 16:29:55 that's a good question 16:30:05 if you mean a CI job, yes 16:30:07 I am learning about that 16:30:31 #info tempest tests will require seperate CI job 16:31:01 What is not tested cannot be considered working :) 16:31:01 Ah, thanks 16:32:15 alright do we have anything else to discuss? 16:32:32 tiendc: I've done this before, I'f you want I'll propose one tomorrow 16:33:12 Thanks derekh 16:33:35 #info derekh to propose CI job 16:33:36 Yes please do 16:33:51 tiendc: ok, I'll let you know when its up and you can see if its what your expecting 16:33:54 I can help with project-config, if needed. I spent quite some time there.. 16:34:17 :) 16:35:27 dtantsur: I'll take a first stab at something and point you at it 16:37:13 alright so conversation seems to be slowing down 16:37:31 cool 16:37:46 so thanks for joining everyone! ttyl 16:37:52 thank you 16:37:54 ty 16:37:58 thanks 16:37:59 #endmeeting