19:00:59 #startmeeting tripleo 19:01:00 o/ 19:01:01 Meeting started Tue Jan 21 19:00:59 2014 UTC and is due to finish in 60 minutes. The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:03 hi 19:01:04 The meeting name has been set to 'tripleo' 19:01:06 hello 19:01:10 hi 19:01:11 Hiya 19:01:20 #topic agenda 19:01:27 bugs 19:01:28 reviews 19:01:28 Projects needing releases 19:01:28 CD Cloud status 19:01:28 CI virtualized testing progress 19:01:30 Insert one-off agenda items here 19:01:32 open discussion 19:01:35 #topic bugs 19:01:39 #link https://bugs.launchpad.net/tripleo/ 19:01:40 #link https://bugs.launchpad.net/diskimage-builder/ 19:01:40 #link https://bugs.launchpad.net/os-refresh-config 19:01:40 #link https://bugs.launchpad.net/os-apply-config 19:01:42 #link https://bugs.launchpad.net/os-collect-config 19:01:44 #link https://bugs.launchpad.net/tuskar 19:01:47 #link https://bugs.launchpad.net/tuskar-ui 19:01:49 #link https://bugs.launchpad.net/python-tuskarclient 19:02:02 hi 19:02:05 hi 19:02:18 hiya 19:02:25 Heya! o/ 19:02:36 hey 19:02:40 so bugs 19:02:48 we've got untriaged bugs second week in a row :( 19:02:56 https://bugs.launchpad.net/diskimage-builder/+bug/1268678 19:03:33 we've also got a non-working devtest right now. 19:03:47 ruh roh 19:03:48 https://bugs.launchpad.net/heat/+bug/1271190 19:03:53 breaking all Heat in-instance users 19:04:00 the patch to fix has been approved 19:04:38 Not sure if it is worth marking as affecting TripleO since it will be resolved in Heat within a few hours. 19:05:01 I am not a big fan of paperwork for paperwork sake 19:05:03 so meh 19:05:07 I suppose knowing what patch to cherry-pick while it wends its way through the gate might be helpful 19:05:09 we have criticals already 19:05:11 https://bugs.launchpad.net/tripleo/+bug/1270646 19:05:22 this breaks tenants 19:05:29 ahoy 19:05:37 2kbps if you're lucky 19:06:17 anyone with deep network experience feel like owning that and chasing it down to ground? 19:06:38 I think I am the opposite of that person. :) 19:07:54 hehe 19:08:03 ok, so no volunteers; will take it to the list 19:08:14 https://bugs.launchpad.net/tripleo/+bug/1266513 19:08:22 SpamapS: you're assigned on this, whats the status ? 19:09:02 lifeless: I have been badgering the upstreams to host on pypi... netaddr responded immediately, the others did not. 19:09:31 lifeless: We can of course do the exception thing for pip. I dropped it late last week hoping to give the upstreams more time. 19:09:46 I think there are two.. netifaces may be abandoned.. and I forget the other one. 19:09:56 SpamapS: so AIUI it's critical because our builds fail right? 19:11:00 lifeless: I think invididual projects all adapted .. not sure how. 19:11:12 Just never revisited to lower it to High. 19:11:52 SpamapS: since we don't seem to have any actual symptoms at the moment, I think High is better 19:11:53 Didn't the other projects whitelist the externally hosted deps in tox.ini? 19:12:04 lifeless: ah, we're not installing any of the ones that need netifaces 19:12:11 SpamapS: either way :_ 19:12:18 and we don't install review-day so lazr.restful is not needed 19:12:21 SpamapS: sounds like its either not a bug for us 19:12:26 SpamapS: or not hitting us 19:12:32 lifeless: I think I may close it. 19:12:35 SpamapS: I'd F-R it for us 19:12:51 i want to verify that swift is not affected somehow and we're just not testing swift 19:12:52 ok https://bugs.launchpad.net/tripleo/+bug/1254246 is also assigned to SpamapS 19:13:06 this can be probably be closed too 19:13:17 as I already said it's kind of fixed for us 19:13:29 and we aren't hitting this, I believe 19:13:44 rpodolyaka1: you were going to do some validation or something last week? 19:13:46 though, there is 'proper fix' waiting on review 19:14:02 lifeless: yeah, it works for me 19:14:21 so, f-r for tripleo? 19:14:28 I think, so 19:14:34 Yeah agreed 19:14:41 Though it may also just be masked now. 19:14:42 will continue to track this in neutron 19:14:55 ok 19:15:23 what about https://bugs.launchpad.net/tripleo/+bug/1254555 19:15:33 I'm fairly sure we still have a hack in our tree 19:17:13 hasn't it been removed? 19:17:34 I thought, it was here https://github.com/openstack/tripleo-image-elements/blob/master/elements/tripleo-cd/tripleo-cd.sh 19:17:53 38ac22ce7c4ea4ee9a86e1b6f2c3e5e31c8ba652 19:17:57 in incubator 19:19:29 Date: Thu Dec 19 10:36:48 2013 +0000 19:19:29 Merge "Revert "Work around neutron floatingip race condition"" 19:19:32 ok, so its gone 19:19:39 we can f-r that bug too 19:20:26 ok so that gives us two criticals, one with a fix landing in heat, one that may go all the way to ovs 19:22:04 #action lifeless to seek owner for network bug on list 19:22:14 #topic reviews 19:22:19 #undo 19:22:20 Removing item from minutes: 19:22:29 heh, undo fail 19:22:58 anyhow, I was going to say - please do do one day of triage, collectively we can make sure all the projects are triaged easily 19:23:05 #topic reviews 19:23:16 http://russellbryant.net/openstack-stats/tripleo-openreviews.html 19:23:23 19:23:23 Stats since the last revision without -1 or -2 : 19:23:28 3rd quartile wait time: 0 days, 21 hours, 40 minutes 19:23:39 still in ok shape - good stuff 19:23:58 however 19:24:43 19:24:43 Longest waiting reviews (based on oldest rev without -1 or -2): 19:24:43 12 days, 4 hours, 1 minutes https://review.openstack.org/65699 (WIP: Make rabbitmq-server keep state in /mnt/state) 19:24:46 8 days, 2 hours, 42 minutes https://review.openstack.org/52045 (Using merge.py from tuskar to generate overcloud.yaml) 19:24:49 4 days, 17 hours, 28 minutes https://review.openstack.org/67348 (Add SSL configuration metadata for overclouds.) 19:24:52 4 days, 16 hours, 47 minutes https://review.openstack.org/67356 (Permit deploying an overcloud with SSL endpoints.) 19:24:55 4 days, 13 hours, 26 minutes https://review.openstack.org/67358 (Use OS::Heat::UpdateWaitConditionHandle) 19:24:58 sorry for the size 19:25:00 this is a collective fail 19:25:15 this means we're not starting at oldest first maybe? 19:25:23 I don't know 19:25:27 but if you look at those reviews 19:25:34 they haven't been -1 or -2'd 19:25:42 they've been sitting for days 19:25:59 i just reviewed the ssl stuff this morning 19:26:01 i wanted to test it 19:26:24 lifeless, I will review the merge.pz, though I think it is still work in progress 19:26:32 although, somehow i missed 67348 19:26:35 lsmola: if its work in progress, it should be marked WIP 19:26:45 lifeless, I will ask marios 19:26:48 i don't think this reviewable reviews query is very accurate. b/c that one is not in my list 19:26:51 This isn't an individual responsibility issue 19:27:01 slagle: what reviewable reviews query ? 19:27:04 lsmola: lifeless: it *is* still wip in the sense that the models/controllers are yet tbd in tuskar 19:27:17 lifeless: lsmola : but -1 with appropriate comments are very very welcome at this stage 19:27:26 lifeless: lsmola: hence i removed the wip 19:27:30 marios: if its not ready for review yet; please mark it WIP, otherwise folk will be trying to review it to get it landed 19:27:34 lifeless: very last link on https://wiki.openstack.org/wiki/TripleO#Review_team 19:27:36 marios: ack 19:27:56 marios, ok 19:28:37 i don't typically use it, unless there's lots of reviews. which there have been last few days 19:29:09 slagle: indeed, that review is missing! 19:29:23 weird 19:29:27 tripleo-heat-templates is in the query 19:29:30 ah 19:29:34 remove is:reviewable 19:29:39 that means 'passed jenkins' 19:29:49 but jenkins was on holiday 19:30:14 slagle: I'm inclined to suggest we remove that from the wiki page link 19:30:14 right, but then you just get all reviews, including ones you've already reviewed 19:30:26 whereas is:reviewable removes one you've already done 19:30:46 and your own changes for that matter 19:30:51 slagle: does it put them back once someone else comments ? 19:31:07 i don't know 19:31:16 slagle: sounds like the baby went out with the bathwater there.. 19:31:21 it seems to do several things. not all of them well 19:31:30 slagle: I'd rather work around ones I've done and my own than miss stuff. :-P 19:31:38 so, yes, i'm with you. let's just remove from teh wiki 19:32:01 FTR I just use gerrit and round-robin among the various tripleo projects. 19:32:18 ok, so this isn't about individual reviewers; we have a large team 19:32:22 good evening 19:32:40 but we've consistently missed 5 reviews for 2 whole days (ignoring the weekend) 19:32:59 has everyone else been using the unified link as well? 19:33:21 me 19:33:22 i use the second to last one, the All one 19:33:29 not the Reviewable one 19:33:48 jdob: ok so you'd see everything 19:34:05 i do see my own and things I've commented on, so assuming it aggregates right with no special sauce, then yes 19:34:30 yeah 19:34:55 so I don't think 'work harder' will fix this, we've something systemic thats happened; assuming everyone is doing some daily review 19:35:03 I've been a bit slack this week - sorry 19:35:53 so - experiment, can folk please try to review the *oldest by submission date* first ? 19:36:08 makes sense 19:36:13 ack 19:36:16 hmm, but I can't see how to get that from the unified review 19:36:20 so this might be a wishlist 19:36:25 i normally tend to check the newest, so i'll start going in reverse 19:36:25 shall we move on? 19:36:54 well, oldest on that page will be least update - which for a change w/out updates will also be oldest submitted 19:37:04 so yeah, oldest is probably an ok metric 19:37:15 trivial rebases will inherit -1's 19:37:35 er, the ones at the top of the list is what I meant by newest, not sure if that meant by submission or state 19:37:50 so it should be pretty fast to open and check there is no replies etc 19:38:01 jdob: thats the newest by last-modification 19:38:06 reviewing counts as a modification 19:38:22 ok, moving on 19:38:25 #topic Projects needing releases 19:38:43 AFAIK all our projects are in reasonable shape - the issue right now is just heat, right? 19:39:01 seems so 19:39:14 lifeless: tuskar is obviously still in flux, working out models/controllers etc 19:39:22 do we have a release volunteer this week? excluding tuskar* ? 19:39:24 lifeless: but no blockers atm 19:39:34 marios: or do you want a release cut? 19:39:45 lifeless: i don't know what we'de release (no) 19:39:52 imo 19:39:56 i second that no 19:40:01 ok, so excluding tuskar* 19:40:16 lifeless: I can take it for this week, but will need a rain check for the next two weeks 19:40:23 rpodolyaka1: ok! 19:41:04 #topic CD Cloud status 19:41:15 marios: see #tripleo 19:41:27 HP region - generally good shape, though we've got a number of DC tickets open at the moment 19:41:51 undercloud is happy; cd-overcloud is I believe paused while we put the finishing touches on stateful upgrades 19:42:08 lifeless: I don't actually recall why we paused most recently 19:42:11 ci-overcloud is happy 19:42:21 ovs maybe? 19:42:35 SpamapS: no, not sure 19:42:45 lets make sure there's no local patches and restart it 19:43:02 in incubator/templates/elements 19:43:13 dprince: hows the RH region ? 19:43:16 lifeless: ok, I need to get some Heat retry-on-update patches in shape in the review queue and then I will see if we can resurrect it. 19:43:32 SpamapS: do we have the waitcondition fix we needed ? 19:43:53 SpamapS: if you say 'thats waiting for review' I will lol. 19:43:53 lifeless: it is awaiting review in Heat. We cherry picked it into the undercloud's heat. 19:44:04 SpamapS: ok, cool 19:44:11 https://review.openstack.org/#/c/63245/ 19:44:14 lol away :) 19:44:17 lol 19:44:31 Heat review team seems overwhelmed with i2 surge. 19:44:36 we'll come back to dprince I think, time is short 19:44:54 #topic CI virtualized testing progress 19:45:02 pleia2: you is up 19:45:48 * dprince tunes in 19:46:19 this morning I went through the etherpad of our most recent todo list from last week and crossed off what I know was done 19:46:25 #link https://etherpad.openstack.org/p/tripleo-test-cluster 19:46:57 we might want to add the ongoing review nodepool work to that (but it was a holiday here yesterday, so I'm still catching up) 19:47:12 the node pool patches we need are merged 19:47:17 that was just network support 19:47:27 the big set thats open is trying to help infra with overload 19:47:48 ah, gotcha 19:48:18 whats next for ci virt testing ? 19:49:06 I think derekh would have a better view of that 19:49:38 ENODEREK 19:49:43 ok 19:49:54 dprince: RH region of tripleo-cloud, status update? 19:50:36 lifeless: They are disconnecting ports from our internal network to prep for making it public. 19:50:44 \o/ 19:50:46 sweet 19:50:54 lifeless: in prep for this they downed the ports on the switches 19:51:00 So I've lots access :( 19:51:09 * dprince is sad not having access 19:51:13 progress is great news 19:51:24 ok 19:51:28 Still waiting on the IPv4 request too though 19:51:38 #topic open discussion 19:51:46 dprince: shall we have our weekly syncup tomorrow? 19:52:07 pleia2: yes. I think they are still productive for everyone 19:52:15 great 19:52:33 i'd like to discuss the stable branches for our projects 19:52:45 sounds like we got somewhat of a general concensus on the mailing list discussion 19:53:00 pleia2: although I myself feel like I'm struggling to make progress sometimes :-| 19:53:04 i don't honestly know if there is enough time to do something by I2 which is the 23rd 19:53:24 but, i plan to start making progress towards it 19:53:26 sound ok? 19:53:33 slagle: I'd like some time to talk package install stuff with you too :) maybe after my run of meetings today 19:53:46 Q: is there a easy way to setup a testing env for tuskar ? 19:54:04 ekarlso, devtest 19:54:17 Hm 19:54:23 lsmola: ? 19:54:25 we don't currently include horizon/tuskar in devtest do we? 19:54:26 devstack ? 19:54:40 ekarlso: http://docs.openstack.org/developer/tripleo-incubator/devtest.html 19:54:52 lifeless: sure, just ping me at some point. i'm on EST time (utc - 5), but am often on in the evenings 19:55:00 SpamapS, though it easy to install it in undercloud 19:55:01 slagle: cool 19:55:03 ekarlso: devtest is a way of setting up tripleo for development/testing 19:55:06 There is a horizon element for use in devtest. 19:55:20 does that do tuskar ? :) 19:55:20 so stable branches - yeah, I think if someone's going to do it, they should do it in the tent ;) 19:55:46 ekarlso: you'll need to add it to the undercloud image elements 19:55:53 not sure if we have the UI elementized yet though 19:55:54 ekarlso: you'll need to setup tuskar once you've got devtest and an undercloud running 19:56:02 lifeless: the tent? 19:56:14 marios: iirc the tuskar element's in, the UI maybe not 19:56:21 shadower: ic 19:56:29 marios: https://github.com/openstack/tripleo-image-elements/tree/master/elements/tuskar 19:56:31 slagle: oh, there's a saying do you want the camel outside the tent pissing in, or inside the tent pissing out 19:56:43 slagle: its rather vivid :) 19:56:53 lol. i think i get it :) 19:56:56 slagle: and I'm not actually comparing you to a camel :) 19:57:16 plus 19:57:17 i had no idea it was LBJ: http://izquotes.com/quote/241192 19:57:19 shadower: we should have a look on that 19:57:22 on incubator specifically 19:57:45 I don't want stable releases being done to be blocked on, or force premature matriculation, of incubator contents 19:57:51 ekarlso: so before the step 1. here: http://docs.openstack.org/developer/tripleo-incubator/devtest_undercloud.html you'd do `export UNDERCLOUD_DIB_EXTRA_ARGS=tuskar` 19:58:08 It's not that I *want* incubator released, but if you're taking a snapshot, it is what it is 19:58:26 ekarlso: once it's launched, you'd have to ssh in and install the tuskar UI manually (for now) 19:58:41 right, well the first thing i was going to do was to get the docs updated to say "it is what it is" and set expectations 19:58:47 ekarlso, install devtest then this https://github.com/openstack/tuskar-ui/blob/master/docs/install.rst 19:58:58 slagle: cool 19:59:13 ok folks, we're out of time. -> #tripleo for more 19:59:15 #endmeeting