17:00:45 #startmeeting third-party 17:00:46 Meeting started Tue Mar 22 17:00:45 2016 UTC and is due to finish in 60 minutes. The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:49 The meeting name has been set to 'third_party' 17:01:37 hi, anyone here for third-party working group meeting? 17:04:08 #topic announcments 17:04:49 #topic Gerrrit IP Change 17:04:54 ola 17:05:02 hey ja3 17:05:11 #link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088985.html 17:05:57 review.openstack.org would have new IP on April 11 17:07:17 so if you are running any filtering, you would need to make sure you still have access to the new IP 17:08:06 also, zuul might need to be restarted anyway, so it can reconnect to gerrit event stream 17:08:35 ok misha I'll let bob know 17:09:18 good :) 17:09:40 that is all for announcements from me 17:10:33 #topic CI Watch 17:11:28 I did not have time to work on it. The patch queue still remains the same 17:11:38 #link https://review.openstack.org/#/q/status:open+project:openstack-infra/ciwatch+branch:feature/unit-tests+topic:ci-dashboard 17:12:27 #topic Common-CI Solution 17:13:10 there is the patch for fixing gerrit key 17:13:13 #link https://review.openstack.org/#/c/266041/ 17:13:32 ja3: I assume that works for you? 17:14:25 actually, there was -1, so the new line is still required for the key 17:14:51 we're not on ci-watch yet, so "sure" 17:15:08 ja3: that patch is for common ci solution 17:15:49 #topic Open Discussion 17:16:05 anyone else is around? 17:16:15 ja3: do you have anything to discuss? 17:16:52 no; we are to the point now where we're triggering off of nova patches instead of sandbox 17:17:02 but that's not visible externally, since we're not voting 17:17:34 how stable is your test? 17:17:56 I think if it is stable enough, you could ask for permission to comment (but set it to non-voting) 17:18:36 bob is running smoke tests only now, they are 80-90% successful, and in at least some of the cases he had looked at last time we talked the failures were Good Things (gate also failed) 17:19:02 80-90% success rate is very reasonable 17:19:22 stability here = if it fails, it fails again on recheck 17:19:25 we still need to get our log server. THAT process is not for the faint of heart I'm finding, since the process was re-structured last May. 17:20:38 ja3: are you planning to host your own logs, or use outside server? 17:23:49 CIO-hosted. That's what we're supposed to use, is my understanding. 17:24:47 Kurt said it's notionally the same setup you have, it's just that the request process has completely changed so no one with an existing CI system knows how to answer the onboarding questions. 17:26:00 ja3: ah, I see 17:26:25 I think it is still better than maintaining your own server 17:27:44 If there is nothing else, I'll close the meeting 17:27:50 ja3: thanks for attending 17:28:13 good IRCing with you misha 17:28:57 #endmeeting