16:01:25 #startmeeting: ironic_neutron 16:01:26 Meeting started Mon Aug 8 16:01:25 2016 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:29 The meeting name has been set to '__ironic_neutron' 16:01:31 o/ 16:01:50 #topic: Agenda 16:01:52 o/ 16:01:55 o/ 16:01:57 #link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_August_8.2C_2016 16:02:41 feel free to add to the agenda, if you like to bring up anything additional 16:02:51 #topic: Annoncements 16:03:23 All patches for Ironic-neutron integration for phase-1 are now merged 16:03:33 congratulation to the team 16:04:05 finally we have ironic, nova, and neutron patches - all in 16:04:22 thanks to jroll for pushing the last nova patch last week 16:04:30 \o 16:04:42 * jroll apologizes for being late 16:05:00 jroll : no worries - you are just in time 16:05:19 Any other announcements? 16:05:24 o/ 16:05:50 #topic: Update on testing 16:06:14 I have been testing all of the new merged code for last couple of weeks 16:06:27 most of it works just fine, with the exception of one issue 16:06:54 I filed the bug for the issue that I discovered - 16:06:58 see here - https://bugs.launchpad.net/ironic/+bug/1610389 16:06:58 Launchpad bug 1610389 in Ironic "IPA fails to pull image after reboot" [Undecided,New] 16:07:09 that almost certainly isn't related to this work 16:07:34 jroll : probably - but, can't tell 16:07:51 well, it isn't a networking issue, I can tell that much :) 16:08:18 If I reboot the controller then IPA fails to get image because of tmpurl issue 16:08:22 jroll : right 16:09:03 on the surface it seems that devstack sets the tmpurl which gets messed up over the reboot (i.e. not persistent) 16:09:24 well, no, ironic generates the tempurl 16:09:29 However, I tried to look through the devstack code and could not find anywhere tmpurl set 16:09:33 I'm wondering if it's being cached or something 16:09:42 but regardless, I think we can take that out of this meeting :) 16:09:59 right 16:10:14 Wanted to see if any of you folks have seen this? 16:10:36 or may have any clue where to look 16:11:04 Other than this, everything is looking great!!! 16:12:04 that is the update from on the testing of new code 16:12:24 now on to the older agenda 16:13:07 jroll : when is the FF for ironic for Newton? 16:13:38 Sukhdev: we don't have a hard feature freeze, but we try to stop merging risky/large features a few weeks before cycle end 16:14:14 so, sometime in early October/late sept.. 16:14:49 #topic: Work items for Newton 16:14:56 no 16:15:04 final releases are Sep 26-30 16:15:25 so Sep 12-16 at the latest, possibly a week or two earlier 16:15:50 oh - so we have appx a month to get the code ready 16:16:14 we have three items that I am tracking for Newton 16:16:52 Port groups, inspector, and security groups 16:17:14 right 16:17:19 I think inspector is the most important 16:17:42 sambets is working on it - I have not seen him for past few weeks 16:18:08 he's been around 16:18:50 I will ping him on ironic channel to see if he has any update 16:19:12 join #heat 16:19:37 xenogear_ : did not understand that 16:19:53 that was a typo 16:20:19 :-) 16:21:43 mjturek1 had posted a patch for port groups - https://review.openstack.org/#/c/347549 16:22:06 #link: https://review.openstack.org/#/c/347549 16:22:16 Sukhdev: just to be clear it's just breaking out the classes from https://review.openstack.org/#/c/332177/ 16:22:34 (which I'm fixing the failing tests on right now) 16:22:40 mjturek1 : right - that is what I meant 16:22:46 :) 16:23:44 I am still caught up with the testing - probably will be busy for another week or so 16:24:00 after that I plan on jumping on to the security group implementation 16:25:06 Sukhdev: please do start the SG thing soon, there isn't a lot of time this cycle and it isn't on our priority list 16:25:55 jroll: yes, it is on my list of things to do - just the bug which mentioned earlier chewed up a lot of my time 16:26:03 and it has become a blocker for me 16:26:45 Sukhdev: okay, just a warning because we're already starting to pick what will and will not make it 16:28:06 jroll : right probably will get to it next week - 16:28:44 ok, thanks 16:28:44 Anything else? 16:29:33 If anybody can help with the bug I mentioned earlier, please give me a shout - 16:30:14 With this, we have covered the main agenda items - 16:30:29 I have listed all the details (patches, etc) on the wiki - feel free to check it out 16:30:46 #topic Open Discussion 16:30:58 Sukhdev: just curious, the issue you mentioned last week (where you had to specify the driver in the node create I believe). Was that solved? 16:31:39 mjturek1 : As long as I specify the driver information at the time of create, everything works just fine 16:31:58 So, I changed the script - 16:31:59 is that intended behavior though? Should update be available? 16:32:26 there's only certain states in which you can update the network_interface field, and iirc Sukhdev's node was not in that set of states 16:32:28 I could not tell if it is a bug or change in behaviour 16:32:51 jroll: got it, makes sense 16:33:55 right - I assumed it to be a change in behavior --- which is different from earlier version 16:34:35 in the past you could create a node without much details and then update to specify details about driver 16:34:41 with new code, that is changed 16:35:37 Once node is created correctly, all works just fine - 16:35:52 cool :) 16:35:58 So, if you have some older scripts, you might see this 16:36:43 yeah 16:37:00 and I think it's safe to assume deployers don't have older scripts for this yet :) 16:37:15 lol true :) 16:37:25 right 16:38:20 things are looking really good - very predictable 16:38:44 awesome, I'm excited to release this 16:38:57 my goal is tomorrow, might be wednesday given our gate breakages though 16:39:01 6.1.0 16:40:33 jroll : so 6.1.0 is official Ironic release ? 16:40:47 something equivalent to N2? 16:40:47 Sukhdev: it will be this week, yes 16:40:52 and likely 7.0.0 at end of cycle 16:40:55 and for stable/newton 16:41:06 perfect - 16:41:40 Once it is out, I will switch to this - to keep my test setup predictable 16:42:14 Anything else? 16:42:54 I guess we are done 16:43:04 Thanks everybody 16:43:23 thanks Sukhdev :) 16:43:39 bye 16:43:46 #endmeeting