15:00:06 #startmeeting ironic 15:00:07 Meeting started Mon Jun 3 15:00:06 2019 UTC and is due to finish in 60 minutes. The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:10 The meeting name has been set to 'ironic' 15:00:14 Good morning everyone! 15:00:22 o/ 15:00:23 \o 15:00:26 o/ 15:00:27 o/ 15:00:28 It is time for our weekly meeting of irony! 15:00:31 o/ 15:00:37 Our agenda can be found on the wiki. 15:00:39 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 15:00:44 o/ 15:00:50 #topic Announcements/Reminders 15:01:09 o/ 15:01:11 #info Shanghai Open Infra Summit CFP closes on July 2nd 15:01:13 o/ 15:01:54 #info The Ironic train priorities document merged! \o/ 15:01:55 #link https://specs.openstack.org/openstack/ironic-specs/priorities/train-priorities.html 15:02:06 o/ 15:02:13 Does anyone have anything they would like to announce or remind us of? 15:02:49 Good morning. My name is Rodney Brown from Lenovo DCG. I will be joining the discussion over the next few weeks to see how I might be able to contribute. 15:02:58 \o 15:03:00 rodneyHugh: Welcome! 15:03:08 \o 15:03:48 o/ 15:04:07 Well, sounds like there are no other announcements or reminders this week! 15:04:08 Onward! 15:04:20 TheJulia: rodneyHugh is working with my group from Lenovo. :-) 15:04:20 o/ 15:04:29 rodneyHugh: Thanks for joining. 15:04:39 jungleboyj: awesome! 15:04:46 Thank you. 15:04:50 \o/ 15:05:08 welcome, rodneyHugh 15:05:25 All action items seem resolved with Chris Hodge following up and core reviewers reviewed the train priorites, so we can skip ahead then. 15:05:42 #topic Subteam Status Reports 15:05:48 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:06:00 I re-shuffled the reports based upon the train priorities 15:06:09 Starting at line 207 15:07:27 As we discussed, some of our items are more general themes to allow for ideas to evolve. Seems like the faster deployment topic is getting some discussion 15:08:22 etingof: resolved dupliation 15:08:59 arne_wiebalck: I suggest removing old notes from the software RAID section 15:09:11 +1 15:09:24 thanks for all the reviews, btw 15:09:42 I'll try to get round to this again during the next days 15:09:43 So for the record, smartnic stuff is follow-up in neutron. I'm going to put a note for us to add a reno for us to indicate that the functionality should work if properly setup. 15:10:08 how about the indicators feature? how much is it of interest? 15:10:44 nice to have for sure 15:10:58 I think it is interest, we've had some operators of recent express lots of interest, so I'll definitely review it 15:11:16 do we have the code up (updated to match the spec)? 15:11:29 coming this week I think 15:12:16 Regarding v6, I've been trying to focus on getting us a v6 native CI job going. The traffic seems to be disappearing somewhere into the router ether. If anyone wants to help me with that, I would love another set of eyes. 15:12:53 Sadly, MOST devstack seems to be missing lots of "only use v6 knobs too" so it is going to take a litle time before everything is v6 15:13:27 Anything else for subteam updates? 15:14:06 I added Node retirement... @ L269ish. 15:14:17 since that was in the train priorities 15:14:22 rloo: Thanks! 15:14:26 rloo: thx 15:15:02 Are we good to proceed to priorities for the week? 15:15:25 line 290 15:15:31 is that the same as line 336? 15:16:14 rloo: different 15:16:53 TheJulia: thx. 15:16:56 290 is power only 15:17:32 so 290 is subset of 336? (do we need 336 then?) 15:17:58 Lets keep 336 on our radar for now 15:18:33 rloo: seems so, yes. maybe a door opener :) 15:18:52 arne_wiebalck: heh. whatever works for you all :) 15:19:44 So onward to priorities for the week? 15:19:55 o/ 15:20:00 \o mjturek 15:20:05 onward! 15:20:09 TheJulia: ++ 15:20:22 #topic Priorities for the coming week 15:20:29 #link https://etherpad.openstack.org/p/IronicWhiteBoard 15:20:33 Line 123 15:20:40 * TheJulia removes the completed items 15:22:13 Okay, that looks like what is outstanding. Are there any items anyone would like to add to the list this week? 15:25:53 I'e added a couple things from inspector, two stable changes which shouldn't be a big deal 15:26:01 Is there anything else or are we happy with the list? 15:26:18 * dtantsur removed duplicates 15:26:30 I think this is good 15:26:52 I think it's ok 15:27:10 Shall we proceed onward? 15:27:10 TheJulia: qq about https://review.opendev.org/#/c/629060/ since it is in the list. do we want more people to ack or should we merge? 15:27:11 patch 629060 - ironic - Add a high level vision reflection document - 3 patch sets 15:27:43 Well, considering the window I just looked at was only one core reviewer, I suspect we can just approve it 15:27:48 to merge that is 15:28:09 done 15:28:15 \o/ 15:28:29 Moving to Discussions 15:28:40 #topic Discussion 15:29:47 I have two items, and this first one is largely a raise awareness item to see if anyone is willing to go hunt down depreation noties in our test runs and submit patches for some of the various things that are deprecated. In our current state, we have deprecation notices warning us that we will break on python 3.8. 15:30:31 TheJulia: I would gladly do that 15:31:00 rpittau: thanks! FYI python 3.8 (alpha) is in Fedora. 15:31:09 rpittau: thanks! 15:31:10 dtantsur: yep :) 15:31:19 anything for Python 3.x :P 15:31:26 If anyone else is interested, please feel free to jump in, and we can keep a list of patches on an etherpad. 15:31:33 Next item! 15:31:42 Meeting times! :( 15:32:26 We've had an uptick in people in Aisa/Pacific timezones that would like to attend a meeting and be more involved with the community. Steve Baker and Jacob Andrews have both expressed interest in being more involved. 15:32:42 Jacob created a doodle for us to hopefully visualize overlaps 15:32:44 #link https://doodle.com/poll/bv9a4qyqy44wiq92 15:33:12 I feel like the only truly viable option is to alternate week to week. Are there any thoughts? 15:33:28 * jroll wonders if rloo saw the wednesday options or is busy on wednesdays 15:33:41 i found the doodle confusing. was it to find a time on m/t/w only? 15:33:49 if we have enough people for the other time - we can alternate 15:33:55 last time we did alternate meetings, we didn't get very much activity in the US-nighttime meeting, but that was ages ago 15:34:00 i thought it was to find a time of the day. not the actual day. what happened to thurs then? 15:34:01 It was to find a overlaping time window over the course of two days that would generally work 15:34:43 i am fine with alternate or whatever. my recollection is that we had alternating but we cancelled because there weren't enough cores to have any quorum in one of the meetings. 15:35:10 And those meetings were silent most times 15:35:41 is there one time that can accommodate most folks? vs 2 alternate times? 15:35:41 But we've diversified, so I think it would be good. I can propose a time to the folks more focused on the other side of the planet, and we can go from there 15:37:33 I'd rather find 2 times that are convenient each for many people, rather than one time that is inconvenient for everyone 15:37:55 ++ 15:38:05 ++ 15:38:08 agreed 15:38:10 * rloo agrees, why would we want one time that is inconvenient for everyone. best is one time that is convenient for everyone :) 15:38:41 heh 15:38:42 so we're agreeing on a time now. the day of the week is going to be decided later? 15:38:59 i mean, we're agreeing to find times that work for people. not the actual days yet? 15:39:01 I think decide later, we have insufficent information to make that determination ath teh moment 15:39:37 Is the doodle still open? 15:39:41 yes 15:39:52 I would like to see more people respond to the poll, looks like only 2-3 apac people in there now (not sure where harald is) 15:39:55 maybe we should change the doodle to only give choices for 24 hours then. or maybe i was the only one that was confused. 15:40:22 I just saw this. I'll vote too :) 15:40:36 are people planning to attend the inconvenient week? 15:40:59 presumably PTL would be expected to, is TheJulia ok with that? 15:41:00 i see 4 from apac? (where is apac? :D) 15:41:13 mgoddard: it depends on the inconvenient time. (for me anyway). 15:41:21 there is probably inconvenient as in 10pm and inconvenient as in 3am 15:41:26 fwiw, i'm totally fine not attending all the meetings. 15:41:28 jroll: I'm in Central Europe timezone. :) 15:41:31 rloo: Asia-Pacific :) 15:41:49 rpittau: that includes india, right? 15:42:03 rloo: yes 15:42:04 nobody should be having meetings in the middle of the night, PTL included 15:42:04 I will do my best, I'm actually in a decent timezone for it... at least for the next few weeks :) 15:42:13 mgoddard: ++ 15:42:21 mgoddard: i agree. 15:43:06 i don't expect anyone to attend a meeting if it is outside their normal working hours. if you/we can't communicate in other ways, then shame on us. 15:43:10 hjensas: ok, so 2 in apac on the poll so far :) 15:43:16 how about a biweekly ML-based 'meeting'? 15:43:18 rloo: ++ 15:43:37 something async that is timezone neutral 15:43:47 That is... tempting 15:44:04 How does everyone feel about doing that? 15:44:15 Maybe we should try it for one week 15:45:08 encouraging discussion might take a bit of practice, but it should be quite inclusive 15:45:08 Ilya Etingof proposed openstack/ironic master: Add Redfish Virtual Media support https://review.opendev.org/638453 15:45:17 and visible 15:45:23 what does that look like? feels like a status update that generates discussion 15:45:35 something like that 15:45:38 jroll: I'm kind of thinking the same 15:45:46 or an agenda with explicit questions to be raised 15:45:51 or resolved 15:46:24 ++ 15:46:27 I like the sound of it 15:46:56 we can try it. i think we aren't very responsive to email discussions. 15:47:00 #agreed Ironic will try to run a meeting next week entirely on the mailing list. Wish us luck ;) 15:47:04 'we' meaning more than 1-2 people. 15:47:16 rloo: that is the worry - ML is easy to ignore 15:47:34 It is worth a try! 15:47:45 Anyway, are we ready to move on? 15:47:57 * kaifeng wonders how would we define the ML meeting is ended? 15:47:58 so what did we decide? 15:48:03 but then IRC meetings are sufficiently slow to be distracted from, unlike emails 15:48:06 async meeting + two different times for sync meetings? 15:48:13 kaifeng: when people stop replying? :) 15:48:30 I was thinking keep the current meeting time? 15:48:49 mgoddard: no, that isn't fair to the ones that are asking for a diff meeting time. 15:48:54 I guess emails would have more latency 15:49:11 mgoddard: I agree. 15:49:21 emails should encourage us to convey more complete thoughts. There would be no rush to fit thoughts into an hour 15:49:26 well let's keep the current time/date plus one different, no ? 15:49:30 rloo: it's an improvement on the current status though 15:49:43 mgoddard: well, put yourself in the other folks' shoes. 15:50:08 mgoddard: we might as well just pick some other time (via the poll, what is the most voted time) and use that time, + this async one. 15:50:22 rloo: sure, I'm just worried we'll end up with two meetings where TheJulia is the only common attendee 15:50:33 That is a distinct possibility 15:50:39 and that isn't fair on TheJulia 15:50:53 mgoddard: oh, i agree. that goes to the 2-diff time thing. but we need to look at that first, to see if that is what will happen. if so, then no way. 15:50:54 Hence why I'm thinking we should try fully async and see if that works for a week 15:51:28 async ML meetings + infrequent video calls? 15:51:38 well, the folks that cannot make this meeting have no voice wrt the fully async. so perhaps the first thing, before we go to async? or maybe go to async anyway, is to solicit their feedback. 15:51:53 that's a fair point 15:52:05 I was thinking exactly that 15:52:24 we have this poll. the very least we can do is use it to pick another time (if there is one) that most people voted for. assuming we stick with one time. 15:52:25 "We're going to try something, lets see if it helps, let us know what you think!" 15:52:33 ++ 15:52:38 rloo: ++ 15:52:59 rloo: ++ 15:53:20 ++ 15:53:21 i'm not saying the async thing is a bad idea. i just want to kind of stand up for the ones that asked for alternate meeting time :) 15:53:21 Looking at the doodle, Apac->India response times don't overlap very well :( 15:53:40 Well, lets reach out to them and broaden the discussion 15:53:44 so india is not in apac? 15:54:10 I kind of see it as its own zone, tbh 15:54:15 rloo: It is, also Sri Lanka 15:54:22 kaifeng: not to pick on you but will you vote? :) 15:55:20 rloo, sure I will take vote, but I think there is no much difference with current time :( 15:55:21 * rloo thinks we should take this offline now. an async email thread to continue discussion. would be good to see how much discussion occurs there... 15:55:23 technically APAC includes India, but eh.... 15:56:05 if we want to try the async meeting, then we need to be better at email discussions...? 15:56:08 I'll send an email to the mailing list 15:56:16 Indeed 15:56:26 thanks TheJulia 15:57:11 Merged openstack/ironic master: Add a high level vision reflection document https://review.opendev.org/629060 15:57:32 Is there anything else for us to discuss today? 15:57:37 #topic Open Discussion 15:58:16 * TheJulia pages for crickets 15:58:29 2mins left.. 15:59:07 I believe there's something to discuss about the bandit tests, but I guess we can postpone ? 15:59:24 post-meeting works 15:59:28 ++ 15:59:35 And with that, thanks everyone! 15:59:43 thanks! 15:59:46 Thank you \o 15:59:48 thx TheJulia 15:59:52 thank you TheJulia 15:59:55 #endmeeting