17:00:02 #startmeeting ironic 17:00:03 Meeting started Mon Apr 17 17:00:02 2017 UTC and is due to finish in 60 minutes. The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:06 The meeting name has been set to 'ironic' 17:00:11 o/ 17:00:11 o/ 17:00:12 \o 17:00:12 anyone around? 17:00:13 o/ 17:00:16 o/ 17:00:18 o/ 17:00:22 o/ 17:00:22 o/ 17:00:23 o/ 17:00:39 o/ 17:00:46 \o/ 17:00:59 ok, let's roll 17:01:03 #topic announcements 17:01:10 apparently mitaka EOL is this week 17:01:32 o/ 17:01:34 o/ 17:01:42 o/ 17:01:45 looks like nothing to merge there, except a devstack patch 17:01:51 which isn't necessary at EOL 17:01:53 :D 17:01:57 any other announcements? 17:02:09 jroll: next week meetup 17:02:17 ah yes! 17:02:26 oh and I have an announcement I forgot 17:02:29 but first, meetup link 17:03:01 we're having a voip meetup april 25, details here: 17:03:04 #link http://lists.openstack.org/pipermail/openstack-dev/2017-April/115488.html 17:03:20 and then my thing 17:03:30 so uh, my employment situation is changing 17:03:39 I haven't decided on a new thing yet 17:03:51 may or may not end up working on ironic or openstack in general 17:04:05 but I'm job hunting for the next few weeks, so don't expect much from me here :( 17:04:23 I will be around IRC, though, happy to help out if anyone needs anything 17:04:26 Best of luck jroll. That sucks :( 17:04:44 life moves on, I'll be okay :) 17:04:59 anything else? 17:05:21 Best wishes jroll 17:05:30 <3 17:05:33 jroll: good luck, i have no doubt that you'll do something great. /me hopes you stay in openstack though, for selfish reasons :) 17:05:51 heh, thanks 17:05:54 #topic subteam status reports 17:06:07 * jroll moves on, condolences can be elsewhere :P 17:06:13 so these are here: 17:06:17 #link https://etherpad.openstack.org/p/IronicWhiteBoard 17:06:21 jroll: good luck! 17:06:25 starting at line 79 17:06:46 * jroll hasn't been working upstream for about 2 weeks so has no idea what is updated and what is not 17:06:52 oh, give me 5 minutes and i'll update the bugs stats... 17:07:06 * JayF == jroll re: job situation 17:07:17 rloo: wanna just update after the meeting before rama_y sends the report? 17:07:33 jroll: ah, yeah, will do that instead. 17:07:51 I see lots of april 10 updates 17:09:19 * jroll has no questions here, and isn't sure people are around to answer very many questions anyway 17:09:24 vsaienk0: i saw a WIP patch for changing grenade to only upgrade conductor, how is that going? 17:12:08 jroll: wrt xproject nova, we can delete that? 17:12:30 jroll: nova feature freeze was last week right? 17:12:31 rloo: done :P 17:12:36 I even looked for it and didn't see it 17:12:42 yeah, spec freeze, not feature 17:12:51 jroll: thx. right, sorry for starting a rumour :) 17:13:02 heh 17:13:28 anything else? 17:13:38 wrt SNMP, is someone looking into it? 17:13:43 gate broken 17:14:21 hmm, the fix has merged. is it still broken? https://review.openstack.org/#/c/456476/ 17:14:40 L301 for those that are following 17:15:09 I asked in channel a few minutes ago 17:15:35 http://status.openstack.org/openstack-health/#/?searchProject=ironic 17:15:41 looks like not everything failing right now 17:17:08 shall we move on? 17:17:21 ++ 17:17:35 #topic Deciding on priorities for the coming week 17:17:47 like I said, haven't been around much for 2 weeks, no clue what's going on 17:17:56 any problem with leaving these as-is? 17:18:06 it doesn't seem to matter, who is around to do any work? (ok, i'll be more positive tomorrow) 17:18:14 >.> 17:18:49 ok, let's leave it 17:18:53 #topic open discussion 17:18:56 anything else? 17:18:59 jroll: well, just need to update it a bit but i can do that. 17:19:07 rloo: okay cool, thanks 17:19:36 jroll, I have questions regarding resource provider/class & ironic 17:19:38 jroll: ok, updated to reflect this week's stuff 17:19:58 wanyen: sure, go ahead and ask 17:20:03 will ironic uses standard resource classes 17:20:30 not this cycle, no 17:20:39 that's in the specs that have been written about this 17:20:46 yes. what about queens? 17:20:54 I'm not sure, we haven't discussed it 17:21:04 I think long term, we would like to be able to use them 17:21:26 ok. My question is how inspection can populate teh discoveredinfo into resource classes? 17:21:53 we haven't discussed that, either. I think it will need to be a deployer-specific inspection rule 17:22:54 I am not very comforatble about Ironic ust use one single custom rsc class. I am not sure that's teh plan for queens. 17:23:10 it's per-node, not "a single custom rsc class" 17:23:18 you could set all your nodes to a separate resource class if you wanted. 17:23:38 so each node has one single custom rsc class? 17:23:44 wanyen: I'm not sure what you mean about the plan for queens - we don't have a specific plan for queens 17:23:46 yes... 17:23:52 have you read the specs about this? 17:24:29 yes, I have read a few specs about rsc class and make cutom rsc class for scheduling, etc 17:25:14 okay, those mention the resource class is per-node 17:25:26 I am hopng in Queens , ironic can use standard rsc class and inspection can populate the discovered info into standard rsc classes. 17:25:54 I hope so too - when those discussions arise, please contribute to them. you might even start this discussion :) 17:26:32 Yes. I would like to participate these discussion. 17:26:54 great! 17:27:00 anything else for open discussion? 17:27:19 It seems to me that we can do something in get_discovery(). 17:28:09 maybe, I don't know inspector enough to say how we would do it 17:28:11 get_discovery can return the correct standard rsc classes inventory to nova 17:28:47 please do send an email to the mailing list if you want to discuss the long term plans. nova team will need to discuss as well. 17:29:40 jroll, when will ironic discuss these topics: rsc provider, rsc classes, inspection,e tc? 17:30:07 wanyen: I can't predict the future. I don't know. probably when someone sends an email to the mailing list about it. 17:30:23 right now we've been focusing on pike 17:30:44 I meant get_inventory not get_discovery in the previous msg 17:30:47 queens planning will probably start shortly before the PTG 17:31:57 jroll, ok. The reason taht I am looking into these is because it has impact on oob inspection spec. 17:32:36 wanyen: sure 17:32:47 I left a comment on there with what I think the best way forward is 17:32:52 "The fastest way to get my +2 on this spec would be to just drop the non-boolean capabilities from this spec, though I've left comments on a few about moving them or making them boolean. :)" 17:33:22 I think we should have a larger discussion about the non-boolean capabilities and how they fit into the bigger picture 17:33:28 jroll, Nisha and myself would like to add more things to discover for inspections. Some of them are quantative proerties. 17:33:35 but I haven't had time to start that conversation 17:34:07 if you want to start that conversation, it needs to start on the mailing list 17:34:21 jroll, ok. 17:35:15 thanks 17:35:17 anything else? 17:36:02 jroll, the fundamental concern that I have is that I am not sure how inspection can populate custom rsc classes but I think it's easier to populate the standard rsc classes. 17:36:22 wanyen: sure. that isn't a concern I can address in this meeting. 17:36:41 wanyen: first we need to agree that ironic can or should use standard resource classes 17:36:47 i think we/you should take this offline now 17:36:52 yes, please 17:37:01 jroll, ok. so much for this discussion today. Thanks! 17:37:14 you're welcome 17:37:23 thanks for coming, y'all 17:37:25 #endmeeting