19:00:13 #startmeeting Ironic 19:00:13 #chair devananda 19:00:13 Welcome everyone to the Ironic meeting. 19:00:13 Meeting started Mon Nov 17 19:00:13 2014 UTC and is due to finish in 60 minutes. The chair is NobodyCam. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:16 The meeting name has been set to 'ironic' 19:00:17 o/ 19:00:18 Current chairs: NobodyCam devananda 19:00:19 o/ 19:00:20 o/ 19:00:22 o/ 19:00:23 o/ 19:00:23 o/ 19:00:24 o/ 19:00:24 Of course the agenda can be found at: 19:00:25 #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting 19:00:25 o/ 19:00:25 o/ 19:00:27 o/ 19:00:30 o/ 19:00:34 wow big meeting today 19:00:41 hi 19:00:48 great to see everyone at the summit :) 19:00:57 #topic Greetings, roll-call and announcements 19:00:58 Roll-call: Who's here for the Ironic Meeting? 19:01:02 o/ 19:01:04 oh think we just did that one 19:01:09 o/ 19:01:11 o/ 19:01:24 announcements: 19:01:24 Devananda may be lurking, but I expect he's still traveling. 19:01:40 o/ 19:02:01 o/ 19:02:01 ok we chatted about a new format for the meetings, While its not official I was going to try and hold to the new format 19:02:21 \o 19:02:28 basicly more talk about specs/reviews and a little less status 19:03:07 all +1 here 19:03:13 sounds good 19:03:13 +1 19:03:15 +1 19:03:18 +1 19:03:19 I hope every one made it back with out any summit sickness 19:03:26 NobodyCam: should we do 5 minutes for updates since we don't have that stuff set up yet? (and it's been weeks) 19:03:37 jroll: yep comming up next 19:03:41 NobodyCam: You know better than to hope that; hah 19:03:45 :) 19:04:11 :) 19:04:41 ok lets jump in to the old format stuff: 19:04:45 #topic SubTeam: status report (deprecated) 19:04:45 In an effort to speed the meeting along and promote the new format lets have a 19:04:48 cattle call for status updates 19:04:51 #topic SubTeam: 19:04:53 IPA has updates 19:04:53 adam_g: testing 19:04:56 dtantsur: bugs 19:04:58 Ghe: oslo 19:05:01 jroll: IPA 19:05:03 Drivers: wanyen, linggao, lucas 19:05:03 Open: 97 (+9). 3 new, 26 in progress (+5), 0 critical, 10 high (+1) and 4 incomplete /end 19:05:06 (sorry of the large paste) 19:05:19 dtantsur: +9 :( 19:05:22 oh, sorry wrong copy-paste 19:05:23 Open: 100 (+12). 6 new (+3), 29 in progress (+8), 0 critical, 10 high (+1) and 3 incomplete (-1) 19:05:26 The agent_ssh tempest jobs are *passing* when using a prebuilt, binary agent (how they run for ironic). Please treat these jobs as voting now. 19:05:31 + 12 19:05:40 ieek that worse... can we go back to the other one :-p 19:05:45 working on design specs and currently under internalreview 19:06:01 I have https://review.openstack.org/#/c/134438/ up to have the agent_ssh-src job fixed, so IPA can then gate on tempest tests, at which point I'll start making the agent_ssh jobs voting as appropriate 19:06:02 I've been spending my AM looking into https://bugs.launchpad.net/openstack-ci/+bug/1393099 hoping to get some patches up to collect more debug info to get to the bottom of it 19:06:07 Launchpad bug 1393099 in openstack-ci "test_baremetal_server_ops fails with timeout waiting for provision_state to change" [Undecided,Incomplete] 19:06:17 JayF, w00t 19:06:21 wayen awesome 19:06:41 JayF, are we waiting like a week or so before making it voting? 19:06:43 #link https://review.openstack.org/#/c/134438 19:06:56 lucasagomes: the agent_ssh job (non-src) has already got quite a bit of good history of passing 19:07:03 agent_ssh jobs have been passing for a week or two on ironic changes 19:07:09 oslo: New libraries out of incubation are on its way: log, context, utils 19:07:09 adam_g: thats a odd one 19:07:10 lucasagomes: the agent_ssh-src job will run on IPA only, and it's a situation where if it passes once I wouldn't expect it to fail 19:07:12 oslo: syncing oslo blocked at: config (lucasagomes, solved) and new policy (romcheg) 19:07:18 adam_g: got a quick link to your ironic job stats? 19:07:30 #link http://no-carrier.net/~adam/openstack/ironic_gate_status.html 19:07:35 * JayF emphasizes to cores: Please do not approve any changes with tempest agent_ssh failing for a valid reason 19:07:37 thanks 19:07:41 GheRivero: Yup, I updated policy patch a few days ago 19:07:51 JayF, ack 19:07:52 JayF, jroll great! yeah we may want to have it voting soonish then 19:08:00 romcheg: I'm looking at it 19:08:01 probably it can be proposed already 19:08:03 agent_ssh is on adam's gate status thing 19:08:06 and lgtm 19:08:08 JayF: I've seen it fail with a rst file change 19:08:09 romcheg: thx for it 19:08:26 lucasagomes: NobodyCam: I am not going to make agent_ssh job voting until IPA itself can gate on it (what the -src tests are for) 19:08:34 lucasagomes: NobodyCam: So I hope we can flip that switch this week 19:08:53 JayF: :) 19:09:02 small announcement: ironic-discoverd is now on stackforge, more news coming next week, I hope https://github.com/stackforge/ironic-discoverd 19:09:10 \o/ 19:09:12 dtantsur: I have a question about that 19:09:13 nice :) 19:09:17 #link https://github.com/stackforge/ironic-discoverd 19:09:17 yay! 19:09:19 yes great work dtantsur :) 19:09:25 dtantsur: ironic-python-agent was put into openstack/ and was immediately made part of the baremetal program 19:09:28 dtantsur: wooo! 19:09:31 Nice :) 19:09:37 dtantsur: any reason we haven't taken that aggressive approach with discoverd? 19:09:57 JayF, we'll consider it later this cycle, that's what we agreed on with devananda 19:10:00 dtantsur: was looking under programs.yaml, and don't see any stackforge/ projects officially associated with a program 19:10:07 dtantsur: aha, wonderful then :D 19:10:18 JayF: we are going to start, is that not what came out of the summit? 19:10:50 NobodyCam: I was just asking if not doing all the things was an explict decision or a missed step 19:11:03 ahh :) 19:11:06 explicit decision is what dtantsur answered with which is fine by me 19:11:18 :) 19:11:42 just I remember from doing teeth-agent -> ironic-python-agent was something that not many folks knew all the steps up. Was going to offer help if needed P 19:11:44 :P 19:12:07 JayF, thanks, I'll ping you, if we'll be moving on :) 19:12:49 ok are there any thoughts on sending status info / updates to the ML before the meeting? and just have a small section where we can discuss any items of consern to folks? 19:13:00 small announcement: The liaison program has been extended to other projects: QA, Doc, API (lucasagomes), Stable, Vulnerability More info at: https://wiki.openstack.org/wiki/CrossProjectLiaisons 19:13:17 NobodyCam: I think we should do it; I think we should make the etherpad today, mail the list that it exists 19:13:26 #link https://wiki.openstack.org/wiki/CrossProjectLiaisons 19:13:31 appoint someone to send out current status report every friday/monday 19:13:46 #link https://etherpad.openstack.org/p/ironic-status-report 19:13:46 Has anyone laid claim to Vulnerability liason for Ironic? 19:13:48 is my proposal 19:13:57 NobodyCam: There are many subprojects. I prefer an etherpad than a mail report per status 19:14:19 jroll, +1 for the etherpad 19:14:21 JayF: I spoke to devananda about taking it on, he gave me some reading material, we didn't make it official 19:14:25 Aggreggate status to etherpad, email status to list periodically seems like a decent pattern 19:14:47 because *nobody* non-Ironic is going to view our etherpads, but our status reports are likely of interest to a wider audience 19:14:50 just my $0.02 19:14:58 yeah 19:14:59 +1 19:15:00 jroll: JayF: I'm good with etherpad. 19:15:24 (yet another etherpad) 19:15:26 lol 19:15:26 do we want to have a separate section for IPA or just put it under drivers 19:15:29 ? 19:15:45 jroll: you really fix in to both? 19:15:50 white not use existing whiteboard? 19:15:53 NobodyCam, jroll JayF we can even use the whiteboard no? 19:15:56 * mrda is waiting for the therpad to load 19:16:00 dtantsur, +1 19:16:03 could take up lots of space 19:16:06 I don't care either way 19:16:13 use whiteboard or ref from whiteboard 19:16:17 is the whiteboard/etherpad going to contain a history of status', or just the previous week's? 19:16:29 I don't what the whiteboard to get cluttered with history of status'. 19:16:30 ref from whiteboard +1 19:16:38 IMO, should contain just current status 19:16:43 current status gets emailed weekly 19:16:45 I tend to use the whiteboard for quick status stuff. 19:16:49 mailing list archive for old statuses 19:17:01 ++ 19:17:03 sounds good 19:17:08 ++ 19:17:14 +1 19:17:18 +1 19:17:19 if current status only, I'm ok with whiteboard ;) 19:17:25 +1 19:17:41 do we want a offical vote? 19:17:49 or hold off untill next week 19:17:59 vote on what? 19:18:06 sounds like it already passed by acclimation? 19:18:14 NobodyCam: let's do this, anyone disagree with this proposal? 19:18:15 * deva__ lurks from his phone 19:18:16 using ehterpad/whiteboard 19:18:18 yeah seems that we have agreed with it already 19:18:24 hey deva__ :) 19:18:28 ack. 19:18:37 NobodyCam: let's also email what we decide to the list for folks to disagree 19:18:56 (I can do that) 19:19:02 I don't think deciding on etherpad vs whiteboard requires a vote/email discussion? 19:19:03 jroll: you going to handle that? 19:19:04 yeah, we decided to use ML more 19:19:18 rloo: I mean the whole thing in general 19:19:25 rloo, just communicate so that someone can say nooooooooooooooo 19:19:43 while we're on the whiteboard topic, can we delete old gate issues please? 19:19:47 no to what? having status' sent in email once/week and not discussing much in meetings? 19:19:58 jroll: please do 19:20:17 jroll: I would say please lease anything less then a week old? 19:20:19 done 19:20:23 hehehe 19:20:27 I put an email up to discuss the meeting format, people can say no there 19:20:35 rloo, ^^^ 19:20:49 so we're talking about a vote to change the meeting format? 19:20:51 so far people only +1'ed 19:20:57 we also agreed in Paris to start having alternating meeting times, iirc 19:21:05 \o/ 19:21:09 deva__: thats next on my list 19:21:10 :) 19:21:16 #topic Post Summit Discussion 19:21:22 do we want to chat about splitting / alternating the meeting for those folks in 19:21:25 out lying time zones. 19:21:33 NobodyCam: oh, sorry :) 19:21:37 hehehehe 19:21:43 NobodyCam: did we have closure on what we just discussed? 19:22:29 rloo: I took it as whiteboard for current status, and jroll would be mailing the list for everything else 19:22:34 * NobodyCam *ducks* 19:22:43 ogod 19:22:43 :-p 19:22:54 I mean, I'm pretty good at copy/paste 19:22:56 and 'everything else' = = ? 19:23:11 am I the only one that seems confused? 19:23:19 meaning email the status report weekly 19:23:28 rloo: me too, I thought we were going with etherpad! 19:23:34 jroll: ah, ok thx. 19:23:39 rloo, no I'm a bit confused now... seems we are discussing the etherpad thing still 19:23:39 * NobodyCam backs up 19:23:47 ha ha 19:24:00 sigh 19:24:04 hehehe 19:24:12 I have since made the correct categories on the whiteboard and on https://etherpad.openstack.org/p/ironic-status-report 19:24:21 so whichever gets the first status update wins 19:24:49 so I left off with current status reports going on the whiteboard 19:24:58 I thought people wanted to use the whiteboard, not a different etherpad 19:25:01 ++ 19:25:03 that's fine with me 19:25:34 then each week a copy/paste email would capture the "history" in the mailling list 19:25:51 link to the whiteboard pls 19:25:52 have I missed the boat? 19:25:54 yes 19:25:59 wanyen: https://etherpad.openstack.org/p/IronicWhiteBoard 19:26:00 #link https://etherpad.openstack.org/p/IronicWhiteBoard 19:26:06 #link https://etherpad.openstack.org/p/IronicWhiteBoard 19:26:09 :) 19:26:10 tx 19:26:25 here's my understanding then: 19:26:37 people put status in whiteboard by XXX hours before weekly meeting 19:26:56 Someone sends email at/when weekly with status stuff and clears whiteboard status section 19:27:12 rloo: sounds good! 19:27:24 repeat weekly 19:27:33 agree 19:27:35 yeah 19:27:37 +1 19:27:39 jroll to send email about our new process wrt status 19:27:41 now to define XXX :) 19:27:43 yep 19:27:43 I say don't clear whiteboard section tbh 19:27:51 dtantsur: EOB friday? 19:27:52 if it were in it's own etherpad, this process could be automated... 19:28:05 I can also send the weekly mail 19:28:06 jroll, define EOB :) 19:28:14 what does EOB mean? 19:28:17 on my laptop now so i can actually say things 19:28:20 dtantsur: I'm in the last time zone to go EOB 19:28:22 End of Beer 19:28:23 so EOB for you 19:28:26 is fine 19:28:30 because that's before EOB for me 19:28:33 heh ok 19:28:35 at the summit we talked about locking the agenda 48 hours before the meeting, not sure thats valid for status 19:28:38 until we get a hawaiin 19:28:41 hawaiian? 19:28:59 NobodyCam: I think that's fine for status 19:29:01 yeah, locking bug report at Fri may make it incorrect on Mon 19:29:03 * Shrews volunteers to move to Hawaii... for the team 19:29:05 i'd prefer some time before the weekly meeting, since who knows if they will always be on mondays 19:29:15 then people can come up with questions/issues/etc based on that info 19:29:20 How about status report gets sent as soon as meeting is over 19:29:26 the point is to not talk about status on monday 19:29:30 so if there's anything sticky in the status, it can be brought up in the meeting 19:29:39 if not, the info is dissemenated after meeting 19:29:39 so it's irrelevant if there is inaccuracies in between 19:29:47 JayF: ++ 19:29:49 JayF, if report is made on Fri but sent on Mon, it's stale 19:30:01 it will be made immediately before sending 19:30:05 whenever we decide that is 19:30:08 for status I've actually say somethig like 4 four hours before the meeting to give folks time to look them over 19:30:16 status tracked in etherpad, we look at it around the meeting time and only discuss if something looks *wrong* 19:30:19 then send it after meeting 19:30:23 that sounds good to me 19:30:32 fine with me 19:30:34 then I +1 to forming it 4 hours in advance 19:30:38 yeah sounds reasonable 19:30:46 and email after meeting? 19:30:50 ++ 19:30:52 jroll, yes 19:30:52 ok 19:30:52 yeah 19:30:55 * jroll makes notes 19:31:18 (thnak you for taking notes on this jroll) 19:31:34 and whiteboard or non-whiteboard etherpad? (sorry, I have a very short-term memory) 19:31:45 whiteboard is fine 19:31:47 whiteboard +1 19:31:47 whiteboard IIRC 19:31:57 I'm ok with whiteboard 19:31:58 #agreed status reporting to move to an etherpad, updated before meeting. discuss only things which we disagree on. summary gets emailed after meeting 19:32:02 * lucasagomes have too many etherpads open already 19:32:20 lucasagomes: +++1 19:32:36 ok good to move on? 19:32:44 yes 19:32:45 +1 19:32:48 please 19:33:01 do we want to chat about splitting / alternating the meeting for those folks in 19:33:04 out lying time zones. 19:33:15 yes 19:33:29 I have a link: http://www.timeanddate.com/worldclock/meetingtime.html?iso=20141125&p1=5&p2=224&p3=78&p4=179&p5=367&p6=33 19:33:34 I think we should, the question is what is the other meeting time? 19:33:36 genius, mdra 19:33:44 has anyone looked for a free meeting slot? 19:33:47 (prepared beforehand :) 19:34:04 so, our chairs are both west coast US, usually 19:34:24 shall we make one very early and one very late for west coast folks? 19:34:32 where "very" is somewhat reasonable 19:34:39 i'm fine with lucas chairing an EU-timezone'd meeting, but that doesn't help mrda much 19:34:46 I think something only a few hours later would be fine 19:35:06 It would hurt our eastern european friends 19:35:10 mrda: oh, right. later is better for you, not earlier 19:35:14 is the current time up for grabs too? or are we looking to keep this one, add a second one? 19:35:25 rloo: add second one, alternate weeks 19:35:36 many other projects have adopted that as they grew 19:35:45 * jroll proposes 0000 and 1500 19:35:53 1900 is pretty late for europeans 19:35:55 this time doesn't seem to work for either EU (very well) or Australia (bad). 19:36:20 * lucasagomes is looking at the times 19:36:23 maybe s/1500/1700/, dunno 19:36:53 1500 better then 1700 for me personally :) 19:36:54 I can live with one week at 1900 (but in non-summer it's 0430) 19:36:54 jroll, +1 19:37:18 is anyone east coast US? 19:37:24 or central time? 19:37:31 east coast Canada ;) 19:37:41 remember, we'll still only have one meeting per week. so everyone is (probably) going to miss a meeting now and then 19:37:44 jroll: i'm east coast 19:37:49 Shrews: rloo: is 0000 too late for you? (7pm) 19:37:54 Alternate weeks, 2300 works fine is 2300 for Dublin and 0100 for Kiev 19:38:01 though 19:38:12 jroll: honestly, if 15 or 17:00 are proposed, i'd attend those 19:38:14 i'm happy attending a meeting once every two weeks 19:38:34 ok, then I stand by my proposal and brace for wet cats and other strange objects to be thrown 19:38:41 maybe let's put an email to ML to decide it 19:38:48 since it's going to affect folks that can't be in this meeting 19:38:49 we should have a time that makes folks happy outside of North America 19:38:52 1700 not that far from 1900 19:38:55 I think it's fairest to decide on the ML 19:39:05 lucasagomes: yes, we should do that regardless but need a couple good proposals first 19:39:13 actually, I'd rather not punt that to the ML - it's not a matter of making it perfect for everyone, cause that can't happen 19:39:17 I agree with lucas, but in the email maybe suggest some times just to get things heated up, err rolling 19:39:35 but lucasagomes is right, folks who might have a say may be sleeping now 19:39:44 The current 1900 is hard, but doable. 1700 is a killer :) 19:39:52 don't we have to consider what times are _available_ for the #-meeting channel(s)? 19:39:52 at least ask haomeng? 19:40:11 Shrews: yup. i was just getting that info 19:40:20 seems like we can have one US+AU meeting and one EU+Asia 19:40:23 it's not obviously listed, but it is available here: https://wiki.openstack.org/wiki/Meetings 19:40:23 Shrews, yeah also that, we should take a look at what is available for the openstack meetings 19:40:27 yes, we should ask haomeng 19:40:31 lucasagomes: are you planning on chairing the "OTHER" meeting? 19:40:37 NobodyCam, yup I can do that 19:40:44 there's three meeting rooms by now, I'd be surprised if many slots were full 19:40:46 (if folks agree with it ofc) 19:40:59 csn we ask the chair to get a consences for it and come back with a perposal 19:41:04 four, actually 19:41:06 4 meeting rooms 19:41:08 wow 19:41:24 hey, could always add a 5th room ;) 19:41:27 (sorry lucasagomes :-p) 19:41:31 NobodyCam, it's all good :) 19:41:56 I would like to see who is willing to participate in an alternate meeting 19:42:04 and make the best time for the majority 19:42:05 but I agree that the folks that care may not be at this meeting 19:42:30 I will ask one iLO driver teammember fromIndia to attend teh alternative meeting time 19:42:39 ++ to the idea we have to float this at the ML first, explicitly to catch people who can't/won't attend here 19:42:59 lucasagomes: can I give you a action item to see what time folks would like 19:43:02 besides haomeng, what other cores or ATCs are active outside of US/EU timezones? 19:43:13 NobodyCam, sure, I can put out an email about it 19:43:20 India 19:43:23 ah - wanyen, thanks! what is the UTF offset there? 19:43:29 * UTC 19:43:36 besides mrda too? 19:43:40 I don't know 19:43:44 15 17 sounds good for PRC 19:43:45 there's also some people in japan takada 19:43:48 and haomeng 19:43:50 yuiko? 19:43:54 rloo: mrda is here to represent himself :) 19:43:54 rloo, yeah 19:43:58 devananda: Hi, I'm in Japan 19:44:05 naohirot, is in japan too 19:44:11 oh yeah :) 19:44:14 naohirot: hi! thanks for speaking up :) 19:44:18 Japan, Australia and China line us nicely 19:44:19 (oh yeah, hi mrda) 19:44:21 lucasagomes: :-) 19:44:22 hi naohirot :) 19:44:34 india 19:45:23 http://www.timeanddate.com/worldclock/meetingtime.html?iso=20141125&p1=5&p2=224&p3=78&p4=179&p5=367&p6=33&p7=44&p8=248 19:45:24 there doesn't seem to be much 'daytime' overlap between dublin and eg beijing 19:45:27 I added mumbai and tokyo 19:45:46 rloo: agree 19:45:47 please add china also 19:46:08 isn't beijing in china? 19:46:10 that's why I think 1500-1700 and 0000-0200 are ok 19:46:38 UE/EU and US/Others, respectively 19:46:38 17:00 and 5:00 UTC 19:46:45 rloo, oh didn't see that. 19:46:57 lol just fyi less then 15 minutes left 19:46:57 devananda: who would chair 0500? 19:46:59 5 UTC is just the tail end of being attendable by crazy US west coast people (9PM for us) 19:47:11 oh, right, crazy people :) 19:47:23 but catches everyone else at good daytime hours 19:47:34 what is west coast time for 5:00 UTC? 19:47:38 9PM 19:47:50 that should works for Inida folks 19:47:52 17:00 UTC sounds nice 19:48:12 how does 17 utc work for Beijing/Tokyo? 19:48:18 dtantsur, +1 19:48:24 rloo: 1am/2am 19:48:35