17:00:00 #startmeeting ironic 17:00:01 Meeting started Mon Feb 13 17:00:00 2017 UTC and is due to finish in 60 minutes. The chair is dtantsur. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:02 O? 17:00:02 o/ 17:00:03 o/ 17:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:04 o/ 17:00:04 o/' 17:00:05 o/ 17:00:05 o/ 17:00:05 The meeting name has been set to 'ironic' 17:00:07 o/ 17:00:09 o/ 17:00:10 o/ 17:00:12 * jroll raises a cup 17:00:27 o/ 17:00:28 hi everyone! welcome to the ironic weekly meeting! 17:00:29 \o 17:00:30 o/ 17:00:30 o/ 17:00:34 o/ 17:00:36 congrats on your first meeting dtantsur 17:00:36 o/ 17:00:37 o/ 17:00:39 o/ 17:00:41 our agenda is where it usually is: 17:00:46 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 17:00:50 +1 congrats 17:00:55 thanks all :) 17:00:58 hello, dtantsur :) congrats 17:01:13 #topic Announcements / Reminders 17:01:22 o/ 17:01:33 first, as you've noticed already, you'll see my leading this meeting much more often now :) 17:01:34 dtantsur: Congratulations! 17:01:39 +1 17:01:40 * jroll dances 17:01:50 dtantsur: the first more many :) 17:01:51 huge thanks to jroll for EVERYTHING 17:01:57 +1! 17:01:58 s/more/of/ 17:02:01 ++ 17:02:02 YES 17:02:07 Absolutely! 17:02:11 \o/ jroll !! 17:02:12 who's jroll? :) 17:02:14 psh, y'all did all the work, I just turned the steering wheel. thanks to YOU 17:02:17 dtantsur: congrats :) 17:02:22 also many thanks to JayF and TheJulia for running for the PTL this time 17:02:40 It's an anagram of rloo with a 'j' 17:02:40 ++ thx for making it harder for me to decide :) 17:02:45 haha 17:02:45 Thanks for winning to save us from the stack of work the PTL has to do ;) 17:02:51 :) 17:02:55 JayF: ++ 17:02:56 jlvillal: jrool? 17:03:03 Close enough ;) 17:03:06 :) 17:03:07 mariojv: ja rule 17:03:19 lol 17:03:22 :) 17:03:25 now, to more sad things: 17:03:27 jlvillal: :) 17:03:40 we have to release? :( 17:03:42 we need to release today or tomorrow, and get stable/ocata for the final 3 projects: ironic, inspector and IPA 17:03:47 o/ 17:03:48 or even 17:03:52 #info we need to release today or tomorrow, and get stable/ocata for the final 3 projects: ironic, inspector and IPA\ 17:03:56 ++ 17:04:07 * rloo wonders why that is sad 17:04:09 Bifrost also needs to be released, I think our last change should be going through CI now 17:04:18 just waiting on this for ironic, afaik: 17:04:19 TheJulia, good point, totally forgot about it 17:04:20 #link https://review.openstack.org/#/c/431188/ 17:04:20 ironic-ui? 17:04:25 ironic-ui is done 17:04:36 jroll: will review that 17:04:38 dtantsur: btw, I'm still pretending I'm PTL for ocata things 17:04:40 :) 17:04:49 jroll, pretend well please ;) 17:05:01 heh 17:05:02 Isn't that how it's supposed to work anyway? PTLs are assigned per project+release set 17:05:04 e.g. I'm leaving it up to you to propose the final releases 17:05:12 JayF: eh, kinda, not really 17:05:14 dtantsur: yeah, will do 17:05:29 jroll, I think we have reno clean up proposed against all three I* 17:05:32 then we can release 17:05:45 dtantsur: awesome, thanks 17:05:57 next, 17:06:05 #info The first in history PTG starts next week 17:06:06 o/ 17:06:41 I'm looking for volunteers to try reserve a place for get-together one evening 17:06:49 probably someone knowing the place :) 17:07:00 Do we have anyone on the project in or familiar with the Atlanta area? 17:07:03 o/ 17:07:12 lucasagomes + Yelp = Success :) 17:07:25 I lived in the atlanta area for about six months, so semi-familiar 17:07:25 * dtantsur approves lucasagomes :D 17:07:32 * JayF nominates TheJulia 17:07:34 jlvillal, I wish :-P 17:07:34 what night would this be? wednesday or thursday maybe? 17:07:41 But, I have no idea what is around the conference center 17:07:54 mariojv, we probably need a doodle 17:07:54 fwiw, milan offered to organize the get together. 17:08:04 mariojv, would be good to have a vote 17:08:06 rloo, that's why he's not here ;) 17:08:16 TheJulia, so, could you please figure this out? 17:08:28 dtantsur: even better :) it's in the ptg etherpad, i didn't make it up (this time) :) 17:08:28 dtantsur: sure! 17:08:37 * jroll votes wed/thurs, refuses to plan it (sorry) 17:08:41 o/ 17:08:41 #action TheJulia to try organizing a get-together on the PTG 17:08:45 thanks! 17:08:45 TheJulia: thank you! 17:08:53 thanks TheJulia! 17:09:01 any other announcements? 17:09:05 can someone paste the ptg etherpad? 17:09:07 if i recall, it isn't hard to take the subway in atlanta... 17:09:08 I'm also generally curious how many folks will be at the PTG Mon/Tues 17:09:09 * jroll asks ATL friends what might be good 17:09:15 for the cross-project sessions 17:09:15 davidlenwell, we'll get to it soon 17:09:23 davidlenwell, but it's https://etherpad.openstack.org/p/ironic-pike-ptg 17:09:25 davidlenwell, https://etherpad.openstack.org/p/ironic-pike-ptg 17:09:29 I got last minute travel approval ..so I'll actually be there. 17:09:39 JayF, I arrive on Sun 17:09:42 JayF, I will arrive on tuesday 17:09:49 * JayF arrives Sunday 17:09:56 * jroll sun-fri 17:10:00 * davidlenwell arrives sunday too 17:10:04 and milan 17:10:05 * vdrok same 17:10:07 Suggest we post on etherpad. 17:10:12 good idea 17:10:22 ++ 17:10:35 #topic Review subteam status reports (capped at ten minutes) 17:10:42 #link https://etherpad.openstack.org/p/IronicWhiteBoard 17:10:55 starts with line 90 17:11:33 dtantsur: bugs go down, more features than bugs now :) or is it :( 17:11:38 TheJulia: made a doodle, feel free to use a different one (or i can give you the admin link for this): http://doodle.com/poll/urmpt82pax77vmuz 17:11:42 As a note relating to subteam stuff: once ocata is cut, Rescue is sitting waiting reviews. I'd love if we could get it in early in Pike so we can land nova support as well. 17:11:56 rloo, still more than 200, too many IMO 17:12:00 mariojv: Awesome 17:12:07 dtantsur: +1 17:12:26 * dtantsur wants to schedule something like regular bug triage meeting/mini-midcycles 17:12:47 vdrok: are you OK if I delete the 'Some bugs vdrok thinks'... from etherpad? 17:13:09 rloo: sure 17:13:16 #action Review rescue patches once Pike is open 17:13:22 I guess we won't do more anyway 17:13:26 in this cycle 17:13:38 someone added the 'misbehaving -- provision-state thing. was it something proposed for ocata? 17:14:03 rloo, this was found by me, I thought it's an easy win 17:14:15 dtantsur: oh, i just deleted it. it was in the client from the looks of it. 17:14:16 mat128, did you have a chance to take a look at yolanda's deploy steps spec? 17:14:23 rloo, it probably is, ignore it 17:14:41 vdrok: for portgroups support, is there still more docs needed? 17:14:50 dtantsur: not yet, I'll put it on today's todolist 17:15:07 rloo: I don;t think so, maybe we should move those to install guide at some point tho 17:15:15 along with multitenancy docs 17:15:18 jlvillal and vdrok: good news about grenade & multitenant 17:15:33 rloo: was it vsaienk0 ? :) 17:15:45 rloo: And vsaienk0 for patching networking-generic-switch the correct way. 17:15:45 vdrok: we should discuss; i think maybe admin guide, but not sure. 17:15:48 Unlike my hack :) 17:16:02 * rpioso added attendance section to bottom of Pike PTG etherpad 17:16:03 vdrok: oh, sorry, you might be right. vsaienk0, good work on grenade and multitenant! 17:16:15 rloo thanks :) 17:16:23 vdrok: deleting the 'documentatoin' part of portgroups. it just needs tempest test, rigth? 17:16:40 rloo: right 17:16:56 thanks rpioso 17:17:02 sorry for not updating that :( 17:17:07 TheJulia: Monday today is 2/13 (wrt boot-from-volume) 17:18:00 rloo: indeed :) 17:18:06 wrt driver comp. jroll, dtantsur. someone added a comment saying it was done for ocata except for docs? 17:18:13 rloo, it was me 17:18:27 dtantsur: what about CI? can we consider than separate/follow up? 17:18:30 notice: 2 minutes to review the statuses 17:18:36 rloo, we have a non-voting job with ipmi hw type 17:18:49 line #135 17:18:56 dtantsur: and are there plans for more? (based on irc discussion earlier) 17:19:04 and in pike we'll add more HW types 17:19:09 jroll++ 17:19:10 and figure out how to deprecate classic 17:19:17 we need cooperation with vendors on it 17:19:26 right 17:20:13 done reviewing statuses? 17:20:18 wrt soft power off etc. that last bullet about treating separately. 17:20:29 is that separate treatment being tracked? 17:20:35 rloo, nope, just my proposal 17:20:45 as it's not really part of "getting soft power/NMI in" 17:20:54 just a consequence of our design decisions 17:21:07 for context: rloo is talking about patches exposing supported_power_states in API 17:21:09 dtantsur: it is part of the spec. i dont' care if we treat it separately or not, just so it isn't forgotten. 17:21:31 the patches are up anyway, yeah. I think we can rename this section, if we think the other bits are done 17:21:39 dtantsur: so can i delete that subteam then? or is doc still outstanding too? 17:21:39 that patch looks fine, just won't make it this release 17:22:03 rloo, I don't quite remember, sorry 17:22:29 we're 2 minutes past 10 minutes cap. ready to move on or do we need a few more minutes? 17:22:40 dtantsur: ok, will leave it there until someone (ptl?) decides later. 17:22:54 rloo, I think we rebuild these subteams on the PTG anyway 17:23:00 dtantsur: this week's priorities? 17:23:01 depending on what we call priorities? 17:23:11 ah, yeah 17:23:25 imo, release ocata and review all the ptg specs/proposals/etc 17:23:28 specs in general 17:23:34 imo, take the week off :) 17:23:38 bug triage, RFEs, etc 17:23:43 * jroll saving time off for after ptg :P 17:24:04 or maybe 'please test ocata' ? 17:24:09 o/ 17:24:14 or maybe 'prepare for ptg' ? 17:24:32 sure 17:24:40 I think we all know generally what to do for this week :P 17:25:33 are there other release notes/things to review to get releases done? 17:25:41 there are moar release notes, yeah 17:25:59 dtantsur: maybe put down in priorities 17:26:22 done 17:26:25 release notes are coming out of the woodwork now :) 17:26:27 now looks good to me 17:26:33 ++ 17:26:41 any objections/additions? 17:26:41 agree 17:27:02 ok, let's move to the biggest fun we may have today 17:27:04 #topic PTG planning 17:27:12 #link https://etherpad.openstack.org/p/ironic-pike-ptg 17:27:19 uh oh 17:27:23 is an etherpad with a lot (> 30) of topic ideas 17:28:00 note that folks suggested (and I agree with that) to not have a formal schedule, but rather a flow of topics 17:28:31 the "Summary of the proposed topics" section is the list of these topics, roughly grouped and roughly prioritized 17:28:42 So the three days will be "organized" more like a mid-cycle than the traditional design summit? 17:28:56 this was the idea, yeah 17:28:57 yeah, that's how I imagined it 17:29:13 unless folks have other ideas? 17:29:20 now, seems like at least some projects still plan formal slots, but I was not impressed how it worked previously.. 17:29:20 Awesome. So it's also possilbe we'll have simultaneous stuff then, like a mid-cycle? Two groups with different interests talking about different things? 17:29:22 that are better :) 17:29:36 JayF, it is, and we'll plan such things as we go 17:29:43 * JayF mainly wondering if theres *one list* or if it's just "stuff to talk about" 17:29:58 JayF, I don't quite see the difference 17:30:30 In a world where you can break out smaller groups, I'm just not sure there's as much of a need to prune the list 17:30:46 Is where I'm going with that :) 17:31:11 JayF: I agree with that, not every topic will apply to everyone 17:31:18 the breakout sessions at the midcycle of 2015 were pretty effective imho 17:31:19 well, I only suggest pruning right now, if there are items that people think should not be there at all 17:31:35 with a couple larger group sessions on high priority and contentious topics 17:31:42 I'm pretty sure many of the things, especially from the second half, can be done in parallel 17:31:55 I think pruning will be easier in person, "does anyone actually want to talk about x?" 17:32:01 jroll++ 17:32:18 jroll, I agree 17:32:21 do folks want to decide *anything at all* right now, or just as we go? 17:32:25 FYI nova plans to talk about placement/scheduling things wed afternoon, some of that will be ironic related. I'll be heading over to their room for that, other folks are welcome 17:32:55 * TheJulia makes mental note of that 17:33:11 * dtantsur makes physical note of that 17:33:19 * rloo interested in nova wed aft 17:33:28 * TheJulia updates calendar 17:33:40 * rloo votes to have JayF in charge wed aft 17:33:48 wasn't there a Kolla/Ironic session also? 17:33:50 wait, what? 17:33:53 * krtaylor searches... 17:33:55 ha ha 17:33:55 haha 17:33:55 * JayF didn't do it 17:33:59 krtaylor, not that I'm aware of 17:34:14 there was an email about kolla & ironic i think? 17:34:15 there's a kolla topic about ironic 17:34:19 but not a meetup sort of thing 17:34:25 ok, thx 17:34:35 there's nothing for the ironic team to do, afaik, they just want to deploy the thing 17:34:56 they've come into channel with strange questions/issues in the past 17:35:06 might be wise for one of us to pop in if we can 17:35:12 to prevent spread of FUD or general misunderstanding 17:35:29 I plan on attending most of Kolla Mon/Tues 17:35:35 * jroll touches his nose 17:35:39 * dtantsur too 17:35:40 I'll be happy to report 17:35:54 here's kolla's etherpad: https://etherpad.openstack.org/p/kolla-ptg-pike 17:35:58 ctrl-f ironic returns nothing 17:36:00 I remember questions around how to deploy project atomic, because it uses OSTree so we couldn't use partition images for that (it requires some more complex root= kernel cmdline) 17:36:11 JayF, so ++ 17:36:16 krtaylor: I'll be around all week, so feel free to ping me and I can jump into one of their sessions if needed 17:36:30 TheJulia, cool, will do 17:36:51 thanks krtaylor, TheJulia 17:36:57 yeah, I expect lots of "can come to please" in irc channels next week :) 17:37:24 hehheh 17:37:24 jroll: That could be awesome, or get old very quickly :) 17:37:30 :D 17:37:41 * dtantsur moves attendance higher in the etherpad 17:37:42 TheJulia: I think/hope it works well 17:37:53 would be neat if we got a couple large screens displaying an irc live stream 17:38:10 TheJulia: I think it'll be similar to e.g. nova/ironic shared midcycles, where we could yell between them 17:38:54 is there a dedicated IRC channel for the PTG? 17:39:25 I think they discussed it, but not sure 17:39:34 It appears that there might be one 17:39:35 #openstack-ptg 17:39:36 oh, by the way, what's the scheduled time for all the things to happen? 9am-5pm? 17:39:41 17:39:28 -- | Topic for #openstack-ptg is "Discussion of the Project Teams Gathering and for use during the PTG for on-site announcements" 17:39:56 ^^^ 17:40:21 #link http://doodle.com/poll/urmpt82pax77vmuz#table is the poll for a team get-together 17:40:40 dtantsur: I was just going to mention that :) 17:40:48 #info IRC channel openstack-ptg will be used for coordination during the PTG 17:41:11 If people could fill that out today/first thing tomorrow, that will help me out figuring how many people and time windows 17:41:26 TheJulia, wanna send out a email? 17:41:30 Sure 17:41:38 or are we going to keep it private for folks who don't skip meetings? :) 17:42:00 wow, that's err a big poll... 17:42:05 * jlvillal is sad he won't be there :( 17:42:06 anyway, anything else here? schedule suggestions, logistics, etc? 17:42:09 jlvillal, :( 17:42:15 jlvillal, :-/ 17:42:26 oh, when filling in the attendance, please also state your hotel/rough location 17:42:27 But rloo will be! :) 17:42:31 jlvillal: :-( 17:42:51 jlvillal: :-( to that too! 17:43:12 moving on? 17:43:14 dtantsur: "attendance" - on the poll or elsewhere? 17:43:21 jroll: it's in the pike ptf 17:43:30 *etherpad, line 81 17:43:33 jroll, etherpad 17:43:37 right 17:43:37 oh right in the middle, heh 17:43:57 TheJulia: when you send out email, perhaps also mention the Attendance thingy in the ptg etherpad too 17:44:23 ++ 17:44:39 * rloo wonder why dtantsur wants to know where we're staying 17:44:48 hehehe 17:44:52 :) 17:44:59 dtantsur: any word on logo? 17:45:07 * rloo sorry she asked that 17:45:11 rloo, I haven't heard anything 17:45:12 oh yeah, need to loop back on that 17:45:22 it's probably still on jroll's plate 17:45:39 I completely forgot about it 17:45:43 because I really don't care 17:45:46 I sent the email about adding horns to make the bear more metal, but I suppose nobody likes that idea 17:45:47 ++ 17:45:49 rloo: will do 17:45:50 was hoping she'd answer lucas' questions 17:46:10 dtantsur: I'll bump one of the threads this week and include you 17:46:15 jroll, thanks! 17:46:15 today or tomorrow 17:46:17 jroll: ++ but no peep 17:46:35 I will be bringing my cache of Pixie Boots stickers to the PTG 17:46:36 anything else here? 17:46:40 so snag me if you don't have one yet :) 17:46:46 jroll, yeah me too, but seems the ML thread is now dead :-/ 17:46:47 JayF++ though I still have a few 17:46:48 JayF: +1 17:47:21 #topic RFE review 17:47:32 I have a few prepared 17:47:47 #link https://bugs.launchpad.net/ironic/+bug/1662446 Add should_bind_property to NetworkInterface 17:47:47 Launchpad bug 1662446 in Ironic "[RFE] Add should_bind_property to NetworkInterface" [Wishlist,In progress] - Assigned to Vasyl Saienko (vsaienko) 17:48:01 +1 from me :) 17:48:03 dtantsur: you can't have any prepared w/o noting them in the agenda. 17:48:12 dtantsur: but we'll make an exception for you today :) 17:48:14 rloo, sorry :) 17:48:14 well, you can 17:48:19 it's just annoying :P 17:48:35 jroll: esp since we're supposed to mention them the thurs before or something like that and we never do! 17:48:41 * vdrok was getting ready to get back to beer 17:48:51 whatever, I can skip it 17:49:04 i'm +1 to the part that adds binding:host_id 17:49:07 rloo: meh 17:49:11 i think "do some things" should be more specific, though 17:49:12 dtantsur: go ahead it's cool 17:49:18 JayF ++ 17:49:24 jroll: so we should remove that note about thurs etc :) 17:49:49 context: currently we do thinks like "if node.network_interface == 'neutron': # some logic" 17:50:07 rloo: idk, people should try to be respectful, but if nobody reads anyway, meh. 17:50:23 I'd prefer we move these to explicit flags/properties on task.driver.network instead 17:50:26 i'm good with this, except i would like more details about the new property. described in the bug. 17:50:31 well 17:50:40 why shouldn't those things be abstracted to the driver 17:50:53 jroll: i try to read the morning of, to prepare :) 17:50:56 instead of https://github.com/openstack/ironic/blob/b9a792af9f90dcaa33896a82a4183ad403155591/ironic/common/neutron.py#L198 17:51:08 we should have node.driver.network.set_bind_host_id() 17:51:26 or this, yes 17:51:40 maybe even get_port_body then? 17:51:56 to be completely abstract 17:52:14 sure, something like that, I don't think we need an RFE for this tbh 17:52:20 another example: https://github.com/openstack/ironic/blob/b9a792af9f90dcaa33896a82a4183ad403155591/ironic/common/neutron.py#L407 17:52:25 consider this a bug: if node.network_interface != 'flat': 17:52:27 and go fix it 17:52:34 we shouldn't ever need to write that 17:52:56 ok, objections to converting this to a bug? 17:52:59 jroll: unless the solution is a change to an API, then we do need an RFE 17:53:08 i think 17:53:15 rloo: a REST API, imo 17:53:18 well, it does change the driver interface, right? 17:53:22 any API 17:53:23 an interface api, idk 17:53:27 any api imho, otherwise agreed 17:53:37 oh 17:53:51 I thought we did specs for API changes (even if I thought it was REST API only) 17:53:54 * jroll muahaha 17:54:52 anyway, yeah, I'm fine with this rfe, I'm also fine with a new method 17:55:28 hmm, I'd remove the @abstractproperty as it's going to break the backward compatibility. otherwise looks fine 17:55:41 ah yeah 17:55:41 it depends on the 'places' where that kind of code is being used. (i mean, whether it is a property or a method) 17:56:00 rloo, currently it's just a static flag 17:56:09 but I was mostly objections to "abstract" bit 17:56:35 dtantsur: no abstract if it breaks backwards compat. 17:56:49 yep 17:57:23 so, rfe-approved with removal of "abstract"? 17:57:51 sounds good to me 17:58:00 dtantsur: not quite. i still want to know what it will be set to 17:58:09 dtantsur: i mean, default value in the base class is what? 17:58:27 and it should say that it is a flag... 17:58:39 * rloo tired of descriptions being incomplete. makes it harder to review later. 17:58:48 yeah, makes sense 17:58:58 rloo, mind summing it up in a comment? 17:59:07 dtantsur: i can do after the meeting 17:59:10 thanks! 17:59:11 One minute 17:59:16 right 17:59:24 any other extremely quick comments? :) 17:59:37 dtantsur: good 1st meeting :D 17:59:37 * TheJulia hears crickets 17:59:38 o/ 17:59:41 \o/ 17:59:41 thanks! 17:59:42 Thank you dtantsur 17:59:43 o/ 17:59:44 o/ 17:59:45 thanks dtantsur 17:59:48 o/ 17:59:49 \o 17:59:51 o/ 17:59:56 \o 17:59:56 thx 17:59:57 o/ 18:00:00 #endmeeting