19:03:32 #startmeeting tripleo 19:03:33 Meeting started Tue Jan 13 19:03:32 2015 UTC and is due to finish in 60 minutes. The chair is SpamapS. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:03:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:03:36 The meeting name has been set to 'tripleo' 19:03:51 #link https://wiki.openstack.org/wiki/Meetings/TripleO 19:04:03 #topic agenda 19:04:25 o/ 19:04:34 o/ 19:04:35 Normally I paste the agenda blindly, but I want everyone to take a moment to confirm we need all these and that there aren't other agenda items we need. So I'll mention each one and pause for comments. 19:04:40 * bugs 19:06:04 ok we'll keep that one. :) 19:06:09 * reviews 19:06:14 also one I think we need to discuss 19:06:40 * Projects needing releases 19:07:12 I feel like this one is usually just a nomination for somebody to volunteer and it's done. 19:07:18 But it seems to be working so why change it? 19:07:21 * SpamapS taps the mic 19:07:23 is this thing on? 19:07:25 sure, its reasonably quick 19:07:29 to select a volunteer 19:07:36 hell, I'll make this one easy this week: I'll do it 19:07:37 done 19:08:15 can we just automate the releases? :D 19:08:25 btw I may go dark for a moment if the people installing my new HVAC unit clip my coax with their crane.. I'll come back on 4G tether if it happens. 19:08:37 Ng: I often wonder that. ;) 19:08:49 * CD Cloud status 19:08:53 I feel like this one needs rethinking 19:09:03 we don't really run it like we used to 19:09:13 and there are really a bunch of TripleO clouds that don't really operate using CD 19:09:39 So I wonder if we can morph this into "Live Cloud Status" and offer it as a chance for those running our TripleO clouds to speak up. 19:10:15 Do those people come to the meeting? 19:10:29 do we want it to just be about the infrastructure clouds we're running for ourselves, or do we mean "anyone running a tripleo cloud can come and complain in this agenda item"? 19:11:11 bnemec; no way, they are off fixing things 19:11:22 :-) 19:11:40 As somebody who has struggled to bring up a TripleO cloud, I'd like it to be an agenda item where we can discuss known things affecting real clouds at a higher level than bugs. 19:11:52 +1 19:12:02 +1 19:12:22 Also poor tchaypo has been fighting hp2 for months alone, I want it to be a place where we offer support to tripleo-cd-admins. ;) 19:12:59 +1, we need a post-mortem 19:13:25 I'm not opposed to it, but if we want to do that we need to make sure the right people can be here is all. 19:14:06 #action SpamapS to change "CD Cloud Status" to "Live Clouds Status" in wiki 19:14:21 s/Live/Production/ maybe? 19:14:29 w/e 19:14:30 My only fear is same as bnemec, that the participants for the most part might not be here but it doesnt hurt to try - worst case well just move along quickly 19:14:39 so +1 :) 19:14:39 greghaynes: why aren't they here? 19:14:56 tchaypo is often very timezone afflicted 19:14:58 I say unto all of you.. ;) 19:15:07 I think most cloud operators dont want to be told to wait until the meeting to bring up their issues 19:15:08 We have an alt TZ meeting which will share this agenda. 19:15:16 greghaynes: this is not like that 19:15:36 SpamapS: indeed. Does anyone apart from him and StevenK go to those? ;) 19:15:55 I'm saying if we're talking about something affecting a real cloud in #tripleo or on the ML or in person, we should encourage people to share here so that developers are present to discuss. 19:16:04 Ng: dunno. :/ 19:16:28 * SpamapS hears the crane flexing 19:16:37 ok, so in addition to the normal issue-bringing-up 19:16:51 * CI 19:17:12 vital, don't change it, IMO 19:17:24 * Specs 19:17:29 also vital, need to do more here actually 19:17:36 and finally * Open discussion 19:17:39 duh, keeping that 19:17:42 ok so on to bugs? 19:18:29 +1 19:21:16 * bnemec wonders if SpamapS got craned ;-) 19:21:33 Yes, so bugs, lets make less of those ;) 19:21:45 And fix the ones we do have 19:21:47 no crane 19:21:49 #topic bugs 19:21:52 but almost :) 19:22:18 #link https://bugs.launchpad.net/tripleo/ 19:22:18 #link https://bugs.launchpad.net/diskimage-builder/ 19:22:18 #link https://bugs.launchpad.net/os-refresh-config 19:22:18 #link https://bugs.launchpad.net/os-apply-config 19:22:18 #link https://bugs.launchpad.net/os-collect-config 19:22:21 #link https://bugs.launchpad.net/os-cloud-config 19:22:23 #link https://bugs.launchpad.net/os-net-config 19:22:26 #link https://bugs.launchpad.net/tuskar 19:22:28 #link https://bugs.launchpad.net/python-tuskarclient 19:22:56 Can we close https://bugs.launchpad.net/tripleo/+bug/1405908 ? 19:22:57 Launchpad bug 1405908 in tripleo "Setuptools 8.4 fails to upgrade/install packages" [Critical,Confirmed] 19:23:08 We're multiple major versions past 8.4 now. 19:23:15 sounds like it 19:23:23 bnemec: seems like it's resolved for us anyway 19:23:23 bnemec: yep, the revert to that fix has even been marged 19:23:49 bug 1374626 is still stalled on me being too busy 19:23:50 Launchpad bug 1374626 in tripleo "UIDs of data-owning users might change between deployed images" [Critical,Triaged] https://launchpad.net/bugs/1374626 19:24:06 bug 1401617 is similarly stalled 19:24:08 Launchpad bug 1401617 in tripleo "Flavor based ramdisk/kernel ID is deprecated in Ironic since Juno" [Critical,In progress] https://launchpad.net/bugs/1401617 19:24:35 greghaynes: whats going on with bug 1385346 19:24:36 Launchpad bug 1385346 in tripleo "upstart service unreliable after introducion of pipe to logger" [Critical,Fix committed] https://launchpad.net/bugs/1385346 19:24:53 SpamapS: Its been fix commited - its as good as its going to get basically 19:25:16 we no longer do the | logger hack so aside from fixing upstart... 19:25:52 greghaynes: we are fixing upstart by moving to systemd. ;) 19:26:17 Out of the furnace ... 19:26:42 https://bugs.launchpad.net/tripleo/+bug/1401300 is stalled on me 19:26:43 Launchpad bug 1401300 in tripleo "Keystone Private Key not securely sent to host" [Critical,Confirmed] 19:26:46 I don't see any other criticals. 19:26:57 I plan to do a hacky temp fix for it very soon 19:27:00 any other bugs we need to discuss? 19:29:11 dont think so 19:29:14 #topic reviews 19:30:25 #info There's a dashboard linked from https://wiki.openstack.org/wiki/TripleO#Review_team - look for "TripleO Inbox Dashboard" 19:30:28 #link http://russellbryant.net/openstack-stats/tripleo-openreviews.html 19:30:31 #link http://russellbryant.net/openstack-stats/tripleo-reviewers-30.txt 19:30:35 #link http://russellbryant.net/openstack-stats/tripleo-reviewers-90.txt 19:30:38 So, I think I'm going to do a meta-review of tchaypo 19:30:55 seems like he'd make a good addition to the core review team 19:30:55 SpamapS: very +1 19:30:57 +1 19:30:59 yaya 19:31:09 Pretty sure a review of his reviews will confirm that. 19:31:17 THe stats are a little bit meaningless right now 19:31:33 I move we ignore them. 19:32:49 We had talked about sending a reminder in January that we would be potentially pruning the core list once everyone has had a chance to get back from the holidays. 19:34:00 bnemec: right, so it's hard to judge the core list with the remnants of December still dogging the stats. 19:34:03 bnemec: so maybe 2 more weeks? 19:34:36 anything else? Anybody want something specific reviewed, or feel a spec is ready for +A? 19:35:28 I'd like eyes on my swift puppet stuff 19:36:03 I'm also finding some really good fixups cleanups as I'm reviewing things for puppet support as in https://review.openstack.org/#/c/146293/1 19:36:08 awesome 19:36:09 and https://review.openstack.org/#/c/146292/1 19:36:23 I'll put in a plug for giulio's Cinder HA spec: https://review.openstack.org/101237 19:36:24 Really good to see that progressing. 19:36:30 I'm not a swift expert though. So eyes :) 19:36:30 It's pretty much what we discussed at summit. 19:36:41 Yeah I feel like the cinder HA spec is pretty good and will be ready for +A once it has a few more reviews. 19:36:57 also I'm a ceph fanboi so doooo it ;) 19:37:55 ok moving on? 19:38:19 #topic Projects needing releases 19:38:34 * SpamapS spins the wheel of developers 19:38:42 tick... tick.......... greghaynes ? 19:38:46 sure 19:38:52 fantastic 19:38:59 greghaynes: you won! 19:39:02 \O/ 19:39:05 A NEW CAR! 19:39:14 Best releases ever 19:39:18 and by car I mean release of diskimage-builder 19:39:25 oh :( 19:39:32 #topic Live Clouds Status 19:39:57 I've been trying to run a cloud on blades backed by SAN and it's been rough 19:40:38 I've resorted to pre-formatting the SAN LUN's with an ext4 label and then overriding block-device-mapping.ephemeral0 to point at /dev/disk/by-label/.... 19:40:58 seems like it might work, multipath issues notwithstanding 19:42:52 I also had a situation where my blades were set to 250 days ago in their hwclocks 19:42:52 so had to go through and reset all the clocks 19:42:53 anybody else want to share? 19:42:53 (Feels like group therapy ... ;) 19:42:53 Going to move on then. 19:43:29 SpamapS: Your last five lines all came in within two seconds for me. 19:43:47 Not that I have anything to share anyway :-) 19:43:49 bnemec: which is why I pause. :) 19:43:56 #topic CI 19:44:10 SpamapS: too late for you now, but https://review.openstack.org/#/c/145743/ should have prevented that time horror 19:44:48 Ng: ah right maybe my cloud is old. ;) 19:45:01 I don't know how CI is doing lately. 19:45:08 Seems like it is stable right now 19:45:16 our failure rate seems pretty high ATM, I keep seeing networkey issues 19:45:27 #link http://goodsquishy.com/downloads/s_tripleo-jobs.html 19:45:27 this is just based on my random reviewing though 19:45:39 yeah ow 19:45:52 Actually, I'm seeing all red for our precise jobs atm: http://goodsquishy.com/downloads/tripleo-jobs.html 19:45:59 if people can devote a little time this week to debugging those fails.. it can get off the rails fast if we don't stay on top of it. 19:46:17 #link http://goodsquishy.com/downloads/tripleo-jobs.html 19:46:19 W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/precise-security/main/source/Sources 503 Service Unavailable 19:46:28 eeeenteresting 19:46:48 and OUTPUT=ERROR (ConnectionError): ('Connection aborted.', error(113, 'No route to host')) 19:47:06 anywho, something to debug 19:47:11 Yep 19:47:42 #topic Specs 19:48:55 SpamapS: (blah, that was poorly worded. that change hasn't landed yet. I meant it should prevent that, once landed) 19:52:32 Ng: ahh1 19:52:37 #topic open discussion 19:52:42 Meetup! 19:52:52 * greghaynes just booked 19:52:52 We may have a final attendee list at this point. 19:53:10 can you link the etherpad for that again? 19:53:13 #link https://etherpad.openstack.org/p/kilo-tripleo-midcycle-meetup 19:53:15 SpamapS: is there still space for additional attendees? 19:53:37 shardy: yes we have space for 30 and I count 13. 19:53:57 SpamapS: ok, thanks, just wondering as stevebaker and I were discussing it 19:54:01 o/' bring it on down to tripleo-ville o/' 19:54:07 What's the cutoff date? 19:54:19 geoffarnold: day of. :) 19:54:26 hopefully someone will eat an inadvisable amount of BBQ, in my absence :D 19:54:50 Curious where those who have booked are staying. 19:54:52 I'm in the Westin 19:54:55 thanks. 19:55:05 Im at crowne plaza 19:55:26 which I believe is literally across the street 19:55:36 I'm in the Hilton 19:55:47 optimal dispersement achieved! 19:55:58 Sheraton is across the street from the office. Crowne Plaza is a bit down toward Pioneer Square IIRC but I may be misremembering. 19:56:16 * dprince is in Vintage 19:56:33 awesome we'll be able to escape eachother properly then. ;) 19:56:42 like a fine wine 19:56:47 greghaynes: I think your like 5 blocks from the office 19:57:08 what! 19:57:21 the CWT map must have been lies if thats the case 19:57:25 If people can start filling out the agenda that would be great. 19:58:01 I think hammering HP2 into submission and pushing on the HA job stability are at the top of my list. 19:58:26 also getting puppety things landed 19:58:36 SpamapS: ++ 19:58:39 anyway, let's wrap up. Thanks everyone!!! 19:58:43 #endmeeting