17:00:42 <asselin> #startmeeting third-party 17:00:43 <openstack> Meeting started Tue Sep 15 17:00:42 2015 UTC and is due to finish in 60 minutes. The chair is asselin. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:47 <openstack> The meeting name has been set to 'third_party' 17:01:44 <asselin> anyone here for third party working group meeting? 17:01:56 <ja2> hi rami 17:02:05 <sweston> \o 17:02:05 <asselin> hi ja2 17:02:09 <asselin> hi sweston 17:02:18 <sweston> asselin: hi! 17:02:55 <asselin> patrickeast you around? 17:03:46 <asselin> #link agenda https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_Working_Group_meeting 17:04:08 <asselin> #topic announcements 17:04:27 <asselin> #link Upcoming backwards incompatible nodepool change: http://lists.openstack.org/pipermail/openstack-infra/2015-September/003185.html 17:05:03 <asselin> in case you missed it in the mailing list nodepool is going to be updated as part of the move to common-ci 17:05:13 <asselin> #link https://review.openstack.org/#/c/189762/ 17:05:23 <ja2> reading that email, "going to be" happened yesterday 17:06:02 <asselin> ja2, well it didn't merge yet....but it should in the near future 17:06:29 <asselin> this was based on discussion in yesterday's third party meeting 17:06:39 <ja2> interesting, it says "deploying... today", but I believe you ;-) 17:08:00 <asselin> I suggest you subscribe to the patch to know when it get's +2 and +A :) 17:08:18 <asselin> any other questions on this? 17:08:53 <asselin> #topic Comparison of CI Dashboards: 17:09:26 <asselin> Last time we met we were looking at comparing difference ci dashboard solutions 17:09:33 <asselin> #link https://etherpad.openstack.org/p/third-party-ci-dashboard-comp 17:09:46 <asselin> a few of us got together and populated this etherpad to help ^^ 17:10:16 <asselin> patrickeast, you around to discuss scoreboard? 17:11:26 <asselin> ja2, have you used any of these ci dashboards? 17:11:52 <ja2> asselin, only via these mtgs. 17:11:58 <asselin> sweston, I see you have one up now: http://dashboard.triniplex.com/#!/ 17:12:04 <sweston> open discussion might be a better time for this, but I would like to query folks on how they like the way the information is presented in the current solutions, since I am currently writing the first queries for radar 17:12:40 <ja2> ...still beating mine into working order. comparing multiple is, for my z/vm group, for the moment, a good problem we'd like to mature enough to have 17:12:42 <asselin> sweston, let's discuss it now as it seems it's just the 3 of us now 17:12:48 <sweston> yup, right now it's just a list of ci systems, not very exciting, but should soon have some good information 17:13:03 <sweston> ok 17:13:45 <asselin> in my opinion, I like the ci-watch infromation 17:14:24 <asselin> mostly b/c we have a lot of jobs and I care more to see how each one is doing individually than how my ci is doing as a whole 17:15:17 <sweston> ok, what is the time window most important to you? 17:15:26 <sweston> 24 hours? 7 days 17:15:48 <asselin> ci-watch has fixed time windows such as 24 hours & 7 days. 17:15:56 <asselin> scoreboard is more flexible 17:16:32 <ja2> looking at these for the first time, I do like the quantity of info available in one glance with ci-watch 17:17:01 <asselin> from operator monitoring, I think 24 hours is a good default. 17:17:44 <sweston> I was trying to find a query that would catch ci systems reporting failed on a job which Jenkins reports success on, but when I try to combine the queries together I am getting an or result 17:17:44 <asselin> for 'policing' or trying to find out when something broke 7 days or longer is helpful 17:18:12 <sweston> ja2, asselin ok, that helps a lot, thanks 17:18:12 <ja2> asselin's answer might hint at a deeper pattern - the view of interest depends on the role the user is playing, so if you're thinking about adding filtering of some sort maybe role is the basis for that. 17:18:13 <asselin> sweston, I don't think we need such a query at this time. 17:18:24 <asselin> ja2 17:18:48 <sweston> ok, I hear you 17:18:52 <asselin> ja2, yes, so ci-watch as an option to highlight when jenkins -1 17:19:10 <asselin> I suggested to skylar last week it's also useful to highlight when jenkins +1 17:19:33 <asselin> sweston, so I think those overlays are useful 17:19:58 <sweston> ok 17:21:40 <ja2> sweston, one thing I see is, for a 3PCI, if I get a failure amongst a sea of successes, no apparent way to see which patch it is... the col headers have long-since scrolled off the top 17:22:49 <ja2> ...independent of that, if I'm going triage my first 'ask' would be tell me where my CI disagrees with Jenkins 17:23:16 <ja2> s/going/doing 17:23:48 <sweston> ja2: I noticed that as well ... I can put floating headers in the UI to account for this 17:23:59 <asselin> is http://ci-watch.tintri.com/ down for you guys? 17:24:28 <sweston> asselin: yes, I cannot get to it 17:25:10 <sweston> ja2: ok, I will keep your second comment in mind as well 17:26:01 <ja2> asselin, that's what I'm looking at. 17:26:31 <ja2> ...displayed a few minutes ago, seems to be hung refreshing now that I banged that icon 17:26:46 <asselin> sweston, when do you think you'll have some queries running? 17:27:43 <sweston> asselin: working on them now .. am pretty busy these days, but I think I should have something useful by the end of the week 17:28:13 <asselin> ja2, sweston fyi we were using this room to look at the dashboards offline: #openstack-third-party-ci 17:28:30 <asselin> we = folks from last meeting 17:28:43 <sweston> asselin: ok, good to know 17:29:57 <ja2> asselin, not quite grasping how one looks at them offline but that aside "ok" 17:30:13 <ja2> ...I did look in that channel, but nothing visible 17:30:24 <asselin> ok, well I don't think we have enough people today to make a decision today 17:30:36 <asselin> ja2, offline means not in a recorded meeting 17:30:50 <ja2> asselin 17:30:57 <ja2> ... ok got it 17:31:32 <asselin> #topic Open Discussion 17:31:50 <asselin> any other topics to bring up or discuss? 17:32:14 <sweston> asselin: that's all I had 17:32:28 <ja2> asselin, nothing more from me 17:33:11 <asselin> ok thanks for attending 17:33:30 <asselin> #endmeeting