17:00:12 #startmeeting ironic 17:00:12 Meeting started Mon Nov 14 17:00:12 2016 UTC and is due to finish in 60 minutes. The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:14 o/ 17:00:15 o/ 17:00:16 The meeting name has been set to 'ironic' 17:00:19 o/ 17:00:22 o/ 17:00:24 as always, agenda: 17:00:24 o/ 17:00:25 o/ 17:00:26 o/ 17:00:28 o/ 17:00:32 o/ 17:00:36 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 17:00:39 let's jump in 17:00:48 #topic announcements and reminders 17:01:07 a reminder for people with features touching nova: nova spec freeze is thursday (nov 17) 17:01:10 o/ 17:01:18 o/ 17:01:30 not much of an announcement, but I saw good progress on lots of things last week 17:01:32 good work everyone \o/ 17:01:38 anyone else have a thing here? 17:01:56 o/ 17:01:58 ocata priorities were 'finalized' 17:02:04 PTG registration is open, not sure if that was covered last time 17:02:05 ah, yes 17:02:06 o/ 17:02:08 o/ 17:02:19 those are here: 17:02:21 #link http://specs.openstack.org/openstack/ironic-specs/priorities/ocata-priorities.html 17:02:29 and yes, PTG reg is open 17:02:39 #link https://www.eventbrite.com/e/project-teams-gathering-tickets-27549298694 17:02:42 oh, trello board for ocata priorities: https://trello.com/b/ROTxmGIc/ironic-ocata-priorities 17:02:51 #link https://trello.com/b/ROTxmGIc/ironic-ocata-priorities 17:03:00 we plan to be wed-fri for ironic meetup, though I suspect most people will leave friday afternoon 17:03:32 thanks rloo and mariojv 17:03:53 o/ 17:04:03 anything else? 17:04:30 #topic subteam status reports 17:04:37 these start around line 81 here: 17:04:42 #link https://etherpad.openstack.org/p/IronicWhiteBoard 17:05:09 woo for new pep8 passing 17:05:53 interface attach/detach spec/BP went through, we should get that code done early as it blocks nova portgroups code 17:06:19 so what's the order for portgroups & attach/detach code? 17:06:32 ironic portgroups, ironic attach/detach, nova attach/detach, nova portgroups? 17:06:40 yeah, sounds right 17:07:03 jroll: so we need to land the actual code in nova till feature freeze? Jan 23-27? 17:07:13 i see 'movement' wrt the nova spec for portgroups. does it look close to being approved this week? 17:07:14 BFV stuff looks ready for review 17:07:16 vdrok: yep 17:07:24 rloo: yes, I think it will be approved this week 17:07:36 rloo: it has a +2 now 17:07:43 jroll: sweet! 17:07:47 :) 17:08:33 jroll: that was fast :) 17:08:58 o/ 17:09:11 it's not on a subteam report, but I've made some progress on dropping ironic code from tempest - I think that will be ready to land this week as well 17:09:23 vdrok: yes, nova code has to land by feature freeze, R-4 like you said 17:09:40 yup, thanks 17:10:34 sambetts: wrt attach/detach -- you'll let us know this week when you've got the updated patches? 17:10:39 do "this week's priorities" look alright to folks? I updated it a bit (line 74) 17:11:04 rloo: yup will do :) Ironic side is nearly finished, just adding more tests 17:11:09 sambetts: thx 17:11:15 I'd like to get root device hints done and get it out of the way, same for notifications 17:11:21 lgtm 17:11:34 If people want to stick in links to the patches to review for the priorities, I wouldn't object :) 17:11:35 jroll: lgtm 17:11:39 jroll: root device hints docs should be fairly easy, not sure it is a priority? 17:11:41 I need to update the docs, will do it tomorrow (writting it down here) 17:11:43 jlvillal: yeah, I plan to add links 17:11:53 (for root device hints I mean) 17:12:03 Thanks 17:12:04 rloo: I worry it will get left behind if we don't just get it done now 17:12:18 rloo: it's also on trello left over from newton 17:12:21 jroll: it is close, lucasagomes just has to update i think. 17:12:24 yeah 17:12:27 jroll: ah, the real reason :) 17:12:36 keeping visibility will help us just get it over with :) 17:12:45 jroll: true 17:12:57 jroll: what about the security patch then? 17:13:11 rloo: security groups? 17:13:13 jroll: security groups :) 17:13:20 o/ 17:13:32 rloo: same idea, I guess, though I've been keeping a close eye on it 17:13:38 rloo: just couple of unittests missing there 17:13:54 right ^ almost done 17:14:12 sukhdev needed some help with it, once we work it out I'll plug it for review 17:14:23 ok, good. 17:14:57 cool, sounds like we have another week nice and full of work - anything else here? 17:15:20 i'm looking for a week that is not nice and not full of work :) 17:15:37 rloo: thanksgiving is next week, that'll only be about 60% full of work :P 17:15:47 JayF: phew. Saved! 17:15:52 * jroll hands rloo a vacation request form 17:15:55 :D 17:15:59 lol 17:16:00 lucky you! 17:16:05 next up 17:16:08 #topic Bringing MoltenIron into the Ironic governance 17:16:14 heyo 17:16:18 hi krtaylor, mjturek 17:16:40 does anyone need background on this or do we all remember the previous conversation(s)? 17:16:52 i thought we had decided to do it 17:16:52 so hamzy has projectized molteniron https://review.openstack.org/#/q/project:openstack/molteniron 17:17:15 * lucasagomes thinks he remembers it 17:17:17 https://launchpad.net/molteniron 17:17:18 rloo: ditto 17:17:22 rloo: well, we decided it fits in our new rules, now it's time to exercise those 17:17:23 :) 17:17:33 also not everyone was in that room 17:17:33 #link http://governance.openstack.org/reference/new-projects-requirements.html 17:17:38 the rules btw ^ 17:17:45 oh, i thought we exercised it at the time too, but yay, we get to vote on something? :) 17:17:52 and ironic's rules specifically 17:17:55 #link http://docs.openstack.org/developer/ironic/dev/governance.html 17:18:26 so one concern I pointed out to the molteniron folks last week was a bunch of self-approved patches 17:18:36 looks like they understand that's not okay and are already changing that 17:18:44 yep I've been making it a priority to review new changes 17:18:46 well 17:18:47 see the last few here 17:18:49 #link https://review.openstack.org/#/q/project:openstack/molteniron 17:18:52 ones that aren't mine 17:19:04 mjturek: :) 17:19:12 :) 17:19:32 so otherwise I think this looks like an ironic project, does anyone else disagree / have concerns? 17:19:50 (and should we formally vote or is lazy consensus enough?) 17:20:09 so is molteniron going to be tested in the gate? 17:20:25 I think formal voting sometimes takes less time than informal consensus, lol :). I agree with their inclusion though. 17:20:27 * TheJulia thinks lazy consensus/polling for disagreement works 17:20:43 rloo: depends what you mean, I guess, they already have unit tests and pep8 17:20:53 CI for a CI tool is an interesting paradox 17:20:55 rloo: I think use it , in the third party ci 17:21:05 *they use it 17:21:05 jroll: depends on what the new-project-requirements mean: http://governance.openstack.org/reference/new-projects-requirements.html 17:21:07 sambetts: lol 17:21:14 So will ironic-core be added to the project as core reviewers? 17:21:14 sambetts, hah indeed 17:21:14 rloo: right we have pep8 and unit tests 17:21:23 rloo: and pkvmci is using it 17:21:27 The project has core reviewers and adopts a test-driven gate in the OpenStack infrastructure for changes 17:21:45 rloo: yeah, pep8/unit tests is enough 17:21:51 mjturek: Off topic, but a coverage job would be nice (if not existing) and see what the percentage is for the unit tests. 17:21:54 jlvillal, yes, I think we agreed that all projects under the ironic umbrella will include the ironic-drivers group, right ? 17:21:55 ok, that is good enough for me 17:21:58 see also http://governance.openstack.org/reference/project-testing-interface.html 17:21:58 jlvillal: yes 17:22:01 Thanks 17:22:16 jlvillal: sounds fair to me. I'd be interested in that as well 17:22:24 mjturek: who are the core reviewers? 17:22:37 as of now it's myself, krtaylor, and hamzy 17:23:09 sounds good to me. mjturek, are you all at ibm? 17:23:10 I expect ironic-core to have core reviewer rights on any ironic project, btw 17:23:14 (which I may need to fix) 17:23:15 rloo: yes 17:23:20 we're open to others of course 17:23:31 but we'd like to get non-ibmers involved of course 17:23:36 +1 17:23:42 so i think this is fine. what happens in a year or so if only ibm is contributing? guess we can revisit it then if we feel like it 17:23:56 yeah, I think that should be a case-by-case thing 17:24:06 sounds reasonable 17:24:42 agreed 17:25:02 so lets vote cuz we so rarely do it. how many votes are needed anyway? 17:25:14 * rloo looks for fun in the smallest things 17:25:19 we have 11 cores 17:25:26 so 6 I guess? 17:25:35 * jroll doesn't think we have rules about consensus written down 17:26:19 #startvote should molteniron be in ironic governance? Yes, No 17:26:20 Begin voting on: should molteniron be in ironic governance? Valid vote options are Yes, No. 17:26:21 Vote using '#vote OPTION'. Only your last vote counts. 17:26:22 #vote yes 17:26:26 #vote yes 17:26:27 #vote yes 17:26:30 #vote yes 17:26:31 #vote yes 17:26:32 #vote yes 17:26:35 #vote yes 17:26:49 #vote yes 17:27:01 #vote yes 17:27:13 #vote yes 17:27:19 perfect time for UPS to come \o/ 17:27:25 * jroll waits another minute or two 17:27:36 jroll: that is the nature of the universe 17:27:57 looks like a yes though 17:28:04 \o/ 17:28:06 #endvote 17:28:07 Voted on "should molteniron be in ironic governance?" Results are 17:28:07 I think that is 9 cores. 17:28:08 Yes (10): TheJulia, lucasagomes, dtantsur, rloo, jlvillal, JayF, stendulker, vdrok, jroll, sambetts 17:28:13 mjturek, krtaylor btw, some refactoring on the tests files name and directory structure would be appreciated (to match ironic and other projects): https://github.com/openstack/molteniron/tree/master/molteniron/tests 17:28:26 lucasagomes, absolutely 17:28:28 mjturek: would you like to propose the governance repo change or shall I? 17:28:41 congrats mjturek, krtaylor, hamzy ! 17:29:11 mjturek: I have some changes to do there anyway, so I don't mind 17:29:21 jroll: that would be appreciated. thanks! 17:29:27 cool, no problem 17:29:31 thanks rloo! 17:29:35 ok what's next 17:29:39 #topic open discussion 17:29:50 karthiks had a thing, otherwise the floor is open 17:29:55 We have proposed a spec for retrieving NUMA node information during introspection 17:30:00 https://review.openstack.org/#/c/396147/ 17:30:00 Please give us feedback. 17:31:08 I also updated the spec on rolling upgrades 17:31:12 https://review.openstack.org/#/c/299245/ 17:31:20 sweet, thanks xek 17:31:29 I guess one more thing we should make sure we hit this week :) 17:31:36 #info Rolling upgrade spec updated: https://review.openstack.org/#/c/299245/ 17:31:44 karthiks, I'll take look as well 17:31:51 Thanks milan 17:32:07 karthiks, np 17:32:15 jroll: i was going to suggest next week - to look at some specs. i saw some in the subteam reports that might need some attention. 17:32:43 rloo: yeah, we should get all of the specs out of the way soon 17:32:54 before we bikeshed all the way into release day 17:33:06 jroll: yup. i figured we already had a lot on our plate this week 17:33:13 Would any folks be interested in a spec review jam? 17:33:24 indeed, but if folks need things to fill their free time, specs are good 17:33:57 JayF: it could help, maybe we all try to look at some priority specs, and if there seems to be contentious things, line them up for a jam 17:33:58 jroll: true -- i challenge anyone to have free time though, after going through this week's priorities! a beer on me! 17:34:09 :P 17:35:02 anything else or do we want 25 minutes back? 17:35:37 cool cool, thanks y'all :) 17:35:42 #endmeeting