17:00:00 #startmeeting ironic 17:00:01 Meeting started Mon Feb 8 17:00:00 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:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:05 The meeting name has been set to 'ironic' 17:00:06 o/ 17:00:07 o/ 17:00:08 o/ 17:00:08 hey everyone :) 17:00:11 o/ 17:00:11 hi there 17:00:15 o/ 17:00:16 o/ 17:00:17 as always, the agenda is here: 17:00:21 o/ 17:00:22 o/ 17:00:22 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 17:00:37 o/ 17:00:49 o/ 17:01:03 #topic announcements and reminders 17:01:15 o/ 17:01:25 #info midcycle is next week! if you haven't yet, please rsvp here and add any topics you wish to discuss https://etherpad.openstack.org/p/ironic-mitaka-midcycle 17:01:27 #link https://etherpad.openstack.org/p/ironic-mitaka-midcycle 17:01:41 o/ 17:01:44 o/ 17:01:46 #info ironic meeting for february 15 will be cancelled due to midcycle 17:02:16 jroll: why cancel the meeting? 17:02:26 I'm still evaluating a/v systems, I'd like to come back to that in open discussion 17:02:28 o/ 17:02:37 rloo: any point to having it if we're having three days worth of meetings? 17:02:44 I'd rather not 17:03:05 jroll: i wasn't going to attend the meeting, but it seems separate. 17:03:22 we typically cancel the midcycle week's meeting, idk 17:03:39 we can have one if folks want to, I'd prefer not to 17:03:56 jroll: i'm fine with cancelling. just askin in case others aren't. i think we typically cancel cuz the midcycle IS happening that day. 17:03:57 I will be on PTO on Monday 17:04:21 jroll: continue on, there are no nays. sorry about that. 17:04:28 no worries 17:04:30 does anyone have other reminders or announcements? 17:05:39 #topic subteam status reports 17:05:53 as always, these are on the whiteboard: 17:05:56 #link https://etherpad.openstack.org/p/IronicWhiteBoard 17:06:02 beginning at line 173 17:06:13 I'll give folks a few moments to review/update 17:07:23 dtantsur: 19 high bugs? that seems like a lot. Maybe we should deal with those in midcycle 17:07:48 rloo, yeah, though we have some high bugs that are not easy to solve 17:07:55 o/ 17:07:58 we also have way too many assigned/in progress bugs 17:08:06 IDK where in subteam status it'd best fit; but TinyIPA merged 17:08:17 I don't have time to check whether people are actually working on them 17:08:21 JayF, \o/ 17:08:24 \o/ 17:08:25 JayF: under testing I think. 17:08:26 JayF: Yay 17:08:32 whoop! 17:08:32 JayF: and yeah, yay! 17:08:40 :) nice 17:09:08 dtantsur: too many meaning no patches or patches waiting to be reviewed or ? 17:09:21 JayF: yay! 17:09:48 rloo, I didn't check it, just my gut feeling that 116 in progress bugs is too much 17:09:58 +1 dtantsur 17:10:04 dtantsur: ahh. didn't we have some sort of rule that if assigned/progress with no patch after x time, we unassign? 17:10:08 it might be due to the gate problems we've experienced though. needs investigation 17:10:19 dtantsur: maybe something to do in midcycle? 17:10:22 rloo, we do have such rule, which I usually manually enforce ;) 17:10:35 dtantsur: I know that there are some people who assign bugs to themselves and then I don't see progress on them. I'm talking about people who don't attend this meeting. 17:10:44 JayF, sambetts w00ts for tinyipa 17:11:04 rloo: added to the midcycle list 17:11:10 jlvillal: I suspect we're all guilty of that. 17:11:38 rloo, we do forget a bug or two usually (I definitely do), but some people assign dozens to themselves 17:11:48 and often disappear 17:12:04 dtantsur: ok, we need a bug scrub or something. let's add to midcycle. 17:12:11 ++ bug scrub 17:12:12 rloo: yes. It can happen. 17:12:28 also, I wonder if other teams have any automation around unassigning inactive bugs 17:13:03 that would be a good thing to check/have 17:13:03 Also on bug scrub, I don't think we should be too shy about unassigning bugs if no progress and we can't contact them. 17:13:11 jlvillal: ++ 17:13:13 <[1]cdearborn> o/ 17:14:06 lucasagomes: I posted a question on the dracclient gov review 17:14:31 wrt tinyipa; it merged so it is being used in gate? 17:14:33 devananda, thanks will take a look 17:14:33 whoever added "updates to docs.o.o" and "effectiveness of setting priorities" to the midcycle etherpad, could you please add your name? :) 17:15:00 rloo: still waiting on https://review.openstack.org/#/c/269684/ 17:15:05 sambetts: apparently that needs an update 17:15:18 jroll: thx 17:15:24 :( more rebase 17:16:34 dtantsur: thx for the ipa + inspector test 17:16:43 :) 17:16:57 +1 17:17:03 anything else in this section? 17:17:26 #topic breaking change in dhcp_factory.DHCPFactory.update_dhcp(). How to handle it? 17:17:30 #link https://review.openstack.org/#/c/206245/53/ironic/common/dhcp_factory.py 17:17:32 rloo: this is you 17:17:43 jroll: so that was merged last week I think. 17:17:58 jroll: and there is a change to the update_dhcp() method 17:18:14 jroll: which isn't backwards compatible with any out-of-tree implementations. 17:18:40 jroll: should we have allowed that change? is it OK and we 'just' need a reno about it? not sure what to do about it besides not bring it up:) 17:18:43 we don't explicitly guarantee stability of that interface the way we do with the driver API 17:18:54 rloo: right, I believe we discussed this in the ironic/neutron meeting and agreed that it was okay, and we should reno/email about it 17:18:57 because what deva saisd 17:18:59 I think we should send an email to ML with a headsup for people saying that we may break their out of free dhcp plugin code 17:18:59 said* 17:19:24 devananda, jroll yeah, but if we can avoid we may should 17:19:32 like we could have another method to update the vifs for portgroups 17:19:39 update_dhcp_portgroup() or something like that 17:19:42 lucasagomes: right, this was fairly unavoidable without getting insane 17:19:48 Do we know of anyone with an out of tree dhcp provider? I'd be curious what it'd be plugging into. 17:19:49 iirc 17:19:55 JayF: someone was working on an isc one 17:19:56 jroll, devananda, lucasagomes: ok, that's fine with me. The reno can be added in a subsequent patch. 17:20:01 any volunteer to email? 17:20:04 I can email 17:20:08 jroll, hmm I mean, if you have 1 method for ports and another for portgroups 17:20:12 thx jroll 17:20:14 lucasagomes: I didn't see any reasonable way to not make this change, fwiw 17:20:16 JayF, I suspect ionutbalutoiu might 17:20:18 that would be avoided, casue the base class would be noop for portgroup 17:20:41 and plugins can implement that portgroup dhcp update method within them 17:21:33 devananda, yeah fair enough, plus we don't guarantee the backward compat as you mentioned 17:22:27 ok, my item has been addressed. that was fast! (thx.) 17:22:44 example: https://github.com/ionutbalutoiu/ironic/commit/30e68fb5cb40d7ca45f33c0dca10d97ef674653b 17:22:57 can't quickly figure out if it was affected 17:23:30 dtantsur, apparently not because he's not using the "vifs" option from update_dhcp_opts 17:23:37 which is the dict that has changed 17:23:49 s/option/param 17:24:05 right, good 17:24:25 I'll email regardless 17:24:31 ++ 17:24:37 jroll, +1 17:25:22 anything else on this topic? 17:26:01 #agreed jroll to email about the breakage 17:26:03 #topic open discussion 17:26:11 so, one thing I want to bring up here 17:26:41 infra folks have very heavily recommended that we use their asterisk VOIP system, rather than a proprietary system 17:26:49 with two concerns about proprietary video systems: 17:27:00 1) it will exclude folks that will not use non-free software 17:27:17 2) it will exclude folks with low internet bandwidth 17:27:31 iirc bluejeans allows to call-in via a phone 17:27:57 right, so does vidyo, but that may incur phone charges for international folks no? 17:28:00 jroll: did you see my link to this the other day? https://free.gotomeeting.com/ 17:28:04 they suggested using etherpad along with it 17:28:12 jroll: how much bandwidth does the Asterisk system require? 17:28:17 what if we need to share a screen? 17:28:21 sambetts: no, but that has the same issues and also "up to three people" 17:28:30 mgould: it's a SIP system; whatever that takes 17:28:41 jroll: have you decided whether we will use video or screen sharing at all? 17:28:43 jroll, dunno, depending on whether they have free local numbers 17:28:48 jroll: its not limited if someone signs up for a 30 day free trail 17:28:55 devananda: this is what we're talking about right now 17:28:58 no billing info required 17:29:03 sambetts: meh, we have two video systems that will work already 17:29:09 ok :) 17:29:17 so my larger question is 17:29:35 * lucasagomes likes the concerns raised and agrees with them 17:29:44 do we absolutely require video and/or screen sharing, at the risk of excluding some folks? or will voice + etherpad + irc suffice? 17:29:49 I would think VOIP using Asterisk should use in the kilobits per second. Maybe less than 256 kilobits per second. Audio is fairly low bandwidth. From what I recall. 17:30:11 sambetts: free trial doesn't solve either of those concerns, fwiw 17:30:15 jlvillal: yep, 64k voice is considered somewhat high quality 17:30:47 is 'everyone' at the midcycle going to want to do something all together? if folks break up into groups to do their own thing, then they can do video/share screens then? 17:30:54 I feel pretty strongly that we should not use a system which is limited in # of people, or requires such high bandwidth / low latency that it excludes any geographic regions 17:31:05 for the primary channel, at least 17:31:06 bluejeans seems to have a lot of local numbers https://www.intercallonline.com/listNumbersByCode.action?confCode=7220882266 17:31:22 * jlvillal adds clean home-office to TODO list :) 17:31:29 devananda: ++ 17:31:30 rloo: the problem even with breaking off into groups that do video is that will, potentially, exclude certain folks 17:31:49 devananda: true, maybe up to the group to decide? 17:32:03 how much screen sharing might be needed? 17:32:05 rloo, yeah that sounds fair, assuming we will break into groups 17:32:09 rloo: afaik, all of the video conference things are size limited. what happens when someone wants to join the group, but can't becaues of that? 17:32:15 I've also noticed during our midcycles that breaking into groups to do a thing usually results in 90% of attendees listening anyway 17:32:18 in past mid-cycles, did people need to look at screens? more like whiteboards? 17:32:36 devananda: vidyo and blue jeans are not size limited to the best of my knowledge 17:32:45 well, let's try with voice only for this midcycle and see how it goes. 17:32:59 hundred(s) of participants 17:33:00 devananda: I've personally seen >100 people on vidyo, fwiw 17:33:04 neat 17:33:10 I thought # of presenters was limited on those 17:33:29 at least 9 seems possible with bluejeans 17:33:33 # of videos may be limited, but it chooses which to display based on who is making noise 17:33:55 anyway, I feel like we should at least try voice + etherpad 17:34:01 IMO, white board + voice + etherpad for notes would be fine. as much as I like to see everyone 17:34:05 i counted 24 folks max, that have signed up on the etherpad for the midcycle. 17:34:11 jroll: do we have a decent option for shared whiteboard (besides etherpad) ? 17:34:17 if we feel that it's terrible we can move to vidyo for the next day 17:34:28 devananda: unsure, there are certainly web things out there 17:34:35 * dtantsur is the only non-native here right now, so he's in minority apparently 17:34:44 jroll, devananda: for drawing diagrams and the like? 17:34:47 dtantsur: what is a non-native? 17:34:48 mgould: yes 17:34:55 rloo, ... english speaker 17:34:57 cool 17:35:00 * mgould likes diagrams 17:35:06 dtantsur: lucasagomes is here too :) 17:35:12 devananda, jroll ++ we can try, if there's a topic that we really need video we maybe can figure out a way too 17:35:18 he lives in ireland, so he does not count :D 17:35:21 bluejeans or the other one mentioned 17:35:27 dtantsur: yeah, I feel your concerns but I'm not sure it's worth potentially excluding people 17:35:27 dtantsur, I'm non native 17:35:28 dtantsur: we have many contributors from east asia. timezones usually prevent them from joining this meeting regularly ... 17:35:44 lucasagomes: yeah, I need to test but I can spin up a room on my end in 60 seconds apparently 17:35:57 maybe I'm being idealistic, but I hope some of them will make the midcycle 17:36:19 jroll, nice, me and dtantsur can do something for bluejeans if needed on our end as well 17:36:28 devananda: I see some people from asia in the etherpad already :) 17:36:31 devananda, according to the etherpad they will 17:36:34 awesome 17:36:36 devananda: it’s unfortunate that they can’t join the regular meetings 17:36:44 mgould: I know :( 17:36:51 mgould: tis :/ 17:37:02 mgould: fwiw, we tried alternating meeting times last year, but found that it hurt the project velocity overall more to split 17:37:05 hmm, I can only hope they will find phone working for them.. 17:37:17 yeah, makes sense 17:37:39 devananda, mgould: besides the fact that it seemed like half the time or more, not many folks showed up and sometimes no core. 17:37:43 dtantsur: I hope so too :/ 17:37:51 rloo: right 17:37:57 * jlvillal is technically a non-native English speaker. At least he has been told that he only knew Spanish until age three 17:38:25 jlvillal, I'm not sure it's a good comparison to be honest 17:38:35 jlvillal, :-) are you still able to speak it? 17:38:44 true! and no :( 17:38:46 dtantsur: I think that's where asterisk will work better -- it's lower bandwidth, should work better than a video call for folks outside of major us/eu metropolitan areas 17:39:08 so did we decide? 17:39:18 +1 for me, I think we should try 17:39:19 devananda, I'm not talking about bandwidth, I'm talking about people not understanding what is going on at all 17:39:24 dtantsur: ahh 17:39:33 devananda: fwiw, I've heard it's easier for non-native speakers to communicate when facial expressions, body language, etc can be conveyed 17:39:35 dtantsur: well - not like video is going to help in that case either 17:39:36 if not we already have a plan B 17:40:03 just FYI: for a non-native speaker lips movements and face expressions give a lot of hints. and understanding who is speaking helps adjust to an accent faster. 17:40:24 jroll: one on one, definitely ... but I can't imagine trying to do that with 20 people 17:40:38 dtantsur, TIL 17:40:38 but maybe it's only me, I've also been very bad at listening :D 17:40:40 dtantsur: fair 17:40:44 It can be difficult for speakers of other languages to understand native English speakers if they are speaking fast. 17:40:45 devananda: I'm hoping we don't have 20 people talking at once :D 17:40:52 yeah, but we can also fallback to IRC if someone do not understand something 17:41:02 jroll: heh 17:41:12 yeah, so let's try VOIP+etherpad+irc to start. I'll verify that I can use external participants easily if needed. and I'll include both in my email about these details :) 17:41:23 in that case we should make clear at the start of the meetings that “I can’t hear you, can we fall back to IRC” is an option 17:41:33 or people will be too embarrassed to ask 17:41:36 jroll: Please provide info for how to connect to the VOIP, if you haven't already :) 17:41:42 jlvillal: yeah, I will be 17:41:45 mgould, people will be to embarrassed anyway 17:41:56 dtantsur: true 17:42:00 accessibility is hard :-( 17:42:04 dtantsur, heh ++ 17:42:09 dtantsur: point made. reflecting on my time studying other languages and you're correct -- it hasn't worked for me virtually in the past, but f2f, absolutely true 17:42:13 too embarassed to say they can't hear? or to say they can hear but don't understand? 17:42:23 rloo, the latter 17:42:42 dtantsur: got it. we don't have any deaf folks I hope. 17:43:00 I can't guarantee it, but hopefully not 17:43:38 As someone with hearing problems, I kinda hate non-video get-togethers too (difficult to understand what's being said), but I likely won't participate in the mid-cycle so I shouldn't get a vote :) 17:44:23 JayF, right, but would having a video chat help you with that? 17:44:26 or it would be the same? 17:44:31 Yes, it helps significantly 17:44:40 to the level where I almost always try to avoid audio-only meetings 17:44:54 best quality online voice "meetings" I've ever had with folks was years ago, using teamspeak, where everyone wore head sets 17:44:54 so the crazy computer nerd in me wants to actually run both and have my system pipe audio between the two. would take some work but is doable 17:45:01 I see 17:45:15 I may test that out actually 17:45:25 devananda, ++ I used it to play counter strike in the past 17:45:48 jroll: so folks with good connections can use video, and folks without can use audio? 17:45:53 so let's say: we'll definitely have VOIP, we may have video at the same time, we may have video on standby 17:45:54 mgould: yeah 17:46:18 shouldn't be too hard to set up using jack, I'm just scared I'll break my audio altogether :D 17:47:02 jroll: that would be awesome 17:47:09 if it works, I mean :) 17:47:13 heh 17:47:32 breaking audio altogether is not abnormal on my linux system anyway, so I'll give it a shot :) 17:47:54 if video for speakers helps non-native english speakers // folks with hearing difficulties, then yea, i'm all for us having that _in addition_ to the open source audio only channel 17:47:55 so yeah, I'll send an email with details by wednesday at the latest 17:48:03 nod, agree 17:48:25 devananda: by saying as much, you agree to help me test this out :D 17:48:30 jroll: sure thing 17:48:32 jroll: good luck! 17:48:57 alright, I think we're in agreement here 17:49:02 anything else folks want to chat about? 17:49:07 guys, I'd like your +/-1 on HA for Inspector spec https://review.openstack.org/#/c/253675/ warning: it's a bit longer reading ;) 17:49:29 mkovacik: how much has it changed in the last couple of weeks? 17:49:43 oh, yeah, anyone knowing about HA could help us a lot by looking at it 17:49:44 mgould, almost no change 17:50:00 dtantsur, ++ 17:50:11 mkovacik: you're not kidding about it being long :) 17:50:20 mgould, that's no change I remember making ;) 17:50:29 devananda, you didn't see how impressive the paper version of this spec looks :D 17:50:30 devananda, yeah 17:50:37 dtantsur: paper?! 17:50:43 how quaint :) 17:51:11 mkovacik: I'll try to give it a quick read today 17:51:17 devananda, we used to have some f2f reviews with dtantsur in the office over a cup of tea over the spec 17:51:19 devananda, yeah, we had an old-school spec review some time ago with a printed spec :) 17:51:23 could you tldr; one thing, though, before I start 17:51:34 devananda, sure 17:51:35 mkovacik, dtantsur hah that's awesome! 17:51:51 you guys should try s/tea/beer too :-) 17:52:29 lucasagomes, we can involve you and your (home) office, too :D beers on me ;) 17:52:29 is this proposing active/passive or active/active availability -- and in either case, why is inspection a critical enough service in the data center to require HA? 17:52:36 (not that I think it's not -- but I'd like to understand your reasoning) 17:52:40 mkovacik, wfm 17:53:03 I didn't see an answer to either of those in a skim of the problem description 17:53:31 devananda, it's active--active spec, the reasoning behind is we're a single point of failure atm 17:53:32 (ok, two questions) 17:53:54 mkovacik: yes, inspector has SPoF, but what other systems depend on it? 17:54:05 I think this discussion can be easily moved to the channel, as we have only 7 minutes left here 17:54:12 dtantsur: sure thing 17:54:30 dtantsur, devananda right 17:54:39 devananda, within Tripleo, there are use cases where we want to have inspector on the overcloud too (baremetal to tenant case) 17:54:43 so inspector needs to scale up 17:55:16 lucasagomes: ahh, gotcha 17:55:36 happy to discuss more in channel :) 17:56:04 devananda, dtantsur, lucasagomes I'll be relocating home, please bare with me, back in ~2hours 17:56:55 anything else or can I close this one out? :) 17:57:51 alright, thanks for a great meeting everyone :D 17:57:53 nothing here 17:57:55 #endmeeting