08:07:06 #startmeeting tripleo 08:07:07 Meeting started Wed Oct 1 08:07:06 2014 UTC and is due to finish in 60 minutes. The chair is marios. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:07:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:07:10 The meeting name has been set to 'tripleo' 08:07:13 marios: :-) 08:07:24 marios: thank you 08:07:26 so, as no one else seems to be willing, i can do the copy/paste 08:07:43 #topic agenda 08:07:43 * bugs 08:07:43 * reviews 08:07:43 * Projects needing releases 08:07:43 * CD Cloud status 08:07:45 * CI 08:07:48 * Tuskar 08:07:50 * Specs 08:07:53 * open discussion 08:08:00 https://wiki.openstack.org/wiki/Meetings/TripleO 08:08:39 #topic bugs 08:08:50 #link https://bugs.launchpad.net/tripleo/ 08:08:50 #link https://bugs.launchpad.net/diskimage-builder/ 08:08:50 #link https://bugs.launchpad.net/os-refresh-config 08:08:50 #link https://bugs.launchpad.net/os-apply-config 08:08:50 #link https://bugs.launchpad.net/os-collect-config 08:08:52 #link https://bugs.launchpad.net/os-cloud-config 08:08:55 #link https://bugs.launchpad.net/tuskar 08:08:57 #link https://bugs.launchpad.net/python-tuskarclient 08:09:23 4 criticals in tripleo 08:10:25 anyone have any updates or a fav bug they want to highlight here? 08:11:16 so this one +bug/1263294 was discussed last week too 08:11:31 was previously assigned to mkerrin, but apparently he can't work on it any longer 08:11:47 so it's up for grabs if someone has the time and inclination 08:13:00 OK. if there's nothing else here, we can move on... 08:13:22 #topic reviews 08:13:37 #info There's a new dashboard linked from https://wiki.openstack.org/wiki/TripleO#Review_team - look for "TripleO Inbox Dashboard" 08:13:40 #link http://russellbryant.net/openstack-stats/tripleo-openreviews.html 08:13:43 #link http://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt 08:13:46 #link http://russellbryant.net/openstack-stats/tripleo-reviewers-90.txt 08:14:17 Stats since the last revision without -1 or -2 : 08:14:24 Average wait time: 11 days, 18 hours, 48 minutes 1st quartile wait time: 0 days, 19 hours, 24 minutes Median wait time: 7 days, 16 hours, 32 minutes 3rd quartile wait time: 14 days, 21 hours, 6 minutes 08:14:38 oh that didn't work so well 08:14:52 so the one we usually point to is 08:14:54 3rd quartile wait time: 14 days, 21 hours, 6 minutes 08:15:07 for reference, last week it was 08:15:09 19:11:09 3rd quartile wait time: 12 days, 17 hours, 27 minutes 08:15:24 so a *bit* worse 08:16:32 anyone want to request reviews or other discussion here? 08:16:46 what happened to the 'auto -1' discussion on the mailing list? 08:16:47 * marios looks 08:17:03 wow what a terrific audience 08:17:09 :-) 08:17:50 ok am going to move on in a minute if there's nothing else here 08:17:56 +1 08:17:59 +1 08:18:05 last week we also looked at the queue growth on the botttom of the 30 day stats 08:18:10 i guess the obligatory 'cores please keep up your review obligations' 08:18:38 it say sthe queue is down 7 reviews over the last 30 days.. 08:18:45 which is the right direction.. 08:19:01 did i mention my internet being not great at the omment? 08:19:14 tchaypo: lifeless was going to file a bug about a miscount too, but I missed the meeting and don't follow exactly what that was 08:19:47 ah, i can try to talk to him about that later this week, if we're both around at the same time 08:20:07 tchaypo: for clarity, which one is the 'queue growth over the last 30 days' i can't immediately see it @ http://russellbryant.net/openstack-stats/tripleo-openreviews.html 08:20:31 it's on the bottom of the 30-day stats page 08:21:24 anyone have any ideas how to progress with the auto -1 - i haven't followed the discussion for a couple days 08:21:29 i think consensus was: 08:21:44 www.nemebean.com/reviewstats/tripleo-30.txt - Queue growth in the last 30 days: -7 (-0.2/day) 08:21:45 it is a good idea, but there is still discussion about 'auto' vs 'human' -1 08:21:52 tchaypo: thanks 08:22:12 #note Queue growth in the last 30 days: -7 (-0.2/day) 08:22:47 i think there's also discussion about whether -1 is useful or just stats-twiddling 08:23:02 tchaypo: right. 08:23:26 if we can find another way to increase visibility of active changes i think we'd get consensus around taht easier 08:23:33 last I heard it was to be a workflow -1 which gets it out of the core reviewer queue 08:23:49 that is useful beyond making stats more accurate 08:24:19 but not everyone can workflow -1 08:24:33 so, regardless of the discussion, how do we get something like this passed? apparently irc votes are not binding/useful (cos of timezones?). how do we put a proposal to vote then? 08:25:32 ok, really moving on if there is nothing else here ... 08:25:45 but i guess that's what we want - workflow-1 means a core has reviewd it and judged it not ready to land 08:26:18 tchaypo: sounds reasonable 08:26:49 sorry, my internet is really bad. 08:26:51 OK 08:26:56 tchaypo: thanks for your input mate 08:27:11 i guess we leave it until we have a new ptl and they can pick it up next week 08:27:20 we can't do anything here anyway 08:27:28 moving on 08:27:35 #topic Projects needing releases 08:27:50 all those wanting to do a release please form an orderly queue 08:28:06 * marios pokerface 08:28:09 hehe 08:28:19 I guess it's time I learn how to do it 08:28:32 lsmola: thanks! 08:28:40 lsmola: do you have the necessary permissions? 08:28:40 lsmola: Are you in the -ptl group on gerrit? 08:29:03 I *think* I can add you if you are not (anyone already in that group can) 08:29:06 StevenK: no idea :-) 08:29:23 #link https://wiki.openstack.org/wiki/TripleO/ReleaseManagement 08:29:57 OK. so here's what we'll do. If I can add lsmola to the tripleo-ptl group after this meeting, then he will do the release. 08:30:05 otherwise, i will do it, and lsmola can do it next week 08:30:22 #note lsmola to release all the things 08:30:43 marios: ok, I agree with any of those options :-) 08:30:48 thanks lsmola - it's pretty self explanatory but I am very willing to help if there are any issues 08:30:59 marios: ok 08:31:09 moving on... 08:31:20 #topic CD Cloud status 08:31:32 anyone around with an update here? 08:31:41 rh1 is ok 08:31:43 I ment to push up a patch to start using hp1 last week, had to rebuild and redploy testenv image again, with updated bash and 3G VM's, that done now and I'ge ran 35 CI tests using it (32 passed), so I'll submit the patch to infra today. 08:32:06 great. 08:32:40 moving on in a minute if theres nothing else 08:32:49 Hp2 is on a go-slow as I'm on holiday 08:33:16 OK thanks derekh and tchaypo 08:33:19 #topic CI 08:33:29 3 ci incidents causing test to fail since the last meeting, details here https://etherpad.openstack.org/p/tripleo-ci-breakages 08:34:11 I've also stared emailing a weekly report to the list so people know how things are going 08:34:12 #note derekh> 3 ci incidents causing test to fail since the last meeting details https://etherpad.openstack.org/p/tripleo-ci-breakages 08:34:21 #link https://etherpad.openstack.org/p/tripleo-ci-breakages 08:34:40 *started 08:35:27 thats all from me for CI 08:35:32 thanks derekh 08:35:44 moving on in if there's nothing else 08:36:16 * marios moves on in 08:36:20 #topic Tuskar 08:36:32 lotsa tuskar ppl about 08:36:41 Tuskar is finished ;) 08:36:45 \o/ 08:37:04 anything worth mentioning here? 08:37:22 OK 08:37:24 I don't think so - we have a demo video is anyone wants to see what Tuskar can do now 08:37:29 * d0ugal find the link 08:37:35 thanks dougshelley66 08:37:41 d0ugal even 08:37:51 #link https://www.youtube.com/watch?v=--WWdJXmf8o 08:38:02 thanks! 08:38:35 #topic Specs 08:38:38 ^ Useful for anyone not following Tuskar too close but wants to see the current state 08:39:38 anything someone wants to bring up 08:40:03 OK 08:40:05 moving on 08:40:19 #topic open discussion 08:40:51 so james polley has emailed the list about summit planning 08:40:56 lemme get a link 08:41:20 #link http://etherpad.openstack.org/p/kilo-tripleo-summit-topics 08:41:26 thanks! 08:41:42 Thanks for bringing it up :) 08:41:51 #link https://wiki.openstack.org/wiki/Summit/Planning 08:42:06 oh sorry, that one is probably not so useful 08:42:25 OK. anything else someone wants to bring up? 08:42:36 otherwise, we get an extra 15 mins for reviews \o/ 08:42:57 going 08:43:03 going 08:43:13 #endmeeting