15:00:39 #startmeeting third-party 15:00:40 Meeting started Mon Jan 18 15:00:39 2016 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:45 The meeting name has been set to 'third_party' 15:00:47 hello 15:01:04 o/ 15:01:13 Hello, everyone! 15:01:40 hi 15:02:14 hey folks 15:02:22 so what shall we discuss today? 15:02:29 anyone have anything on their mind? 15:02:55 I just have one thing 15:03:05 next week I will be at the nova mid-cycle 15:03:10 I am waiting for another +2 from asselin on #link https://review.openstack.org/#/c/259083/ , but he is not here, so I will wait :) 15:03:28 I wanted to ask if anyone has CI scoreboard setup at their site? 15:03:36 if one of you are willing to chair this meeting, then I don't have to worry about working that into my schedule 15:03:41 any takers? 15:04:00 hi 15:04:03 hi 15:04:09 eantyshev: we do 15:04:43 lennyb: nice work on the patch 15:04:58 mmedvede: how is the ci scoreboard working for you? 15:05:09 anteaya: I did chair it before, so could sit in for you again 15:05:23 mmedvede: thank you, that would be great 15:05:40 mmedvede: I set it up last week, it's a great tool, but it doesn't provide any metrics on CI performance... 15:05:49 anteaya: but only this one, not the night one :) 15:06:09 mmedvede: right well the night one ends up being day for me in the uk so I'm fine keeping that one 15:06:18 mmedvede: thanks for the clarification 15:06:39 eantyshev: what metrics are you looking for? 15:07:04 my understanding was that it would provide an overview of success/failure of all cis on a project 15:07:26 I'm interested in something like the correlation between upstream Jenkins and our results 15:07:42 more like what radar used to provide 15:08:42 so if you clone the radar code and go back to this sha: http://git.openstack.org/cgit/openstack/radar/commit/?id=f12156a422a39e68f0c41155961b6bf4de62de9e 15:08:49 it might give you what you are looking for 15:09:03 your system compared to jenkins 15:09:27 eantyshev: we actually are working on another dashboard to get it deployed officially - ciwatch dashboard. We used to target ci-scoreboard, but for a few reasons decided to go with ciwatch: https://github.com/openstack-infra/ciwatch. 15:09:33 #link radar http://git.openstack.org/cgit/openstack/radar/tree/ 15:09:59 oh perhaps I am confused with the words scoreboard and dashboard 15:10:02 eantyshev: and we want to add more stats to ciwatch (which currently has none) 15:10:18 I never know if the speaker is using those terms in the general sense or the specific 15:10:24 anteaya, mmedvede: BTW, what are prerequisites to become a voting CI? 15:10:49 eantyshev: you need the project you want to allow you to vote +1 verified to allow you to vote +1 verified 15:11:00 so permission from the project you want to vote on 15:11:06 eantyshev: what project? 15:12:00 eantyshev: yes, normally you need to demonstrate a good reliable record for your CI, and be responsive to fix any problems with it 15:12:53 anteaya: nova, problably cinder. We should gather some stats for that, shouldn't we? And what is the measure for CI stability? What are the approximate expectations? 15:14:37 eantyshev: also refer to this doc, it has some good information 15:14:41 #link http://docs.openstack.org/infra/system-config/third_party.html#permissions-on-your-third-party-system 15:15:09 eantyshev: do you attend weekly cinder and nova meetings on irc? 15:15:21 eantyshev: and are you available in both channels? 15:15:43 anteaya: not me, but other team members - yes 15:15:46 do any of the devs on either team know who you are, have you reviewed any patches in either project or fixed any bugs? 15:15:52 eantyshev: which team members? 15:16:06 eantyshev: I think your CI would fail when it should, and not fail when it should not - that is reliable. One way is to compare it to upstream jenkins votes 15:16:18 anteaya: Virtuozzo 15:16:47 I've never interacted with that person 15:17:05 :q 15:17:06 anteaya: that's the company we work at 15:17:07 you need to develop some interactions with both projects 15:17:23 eantyshev: which team members have interacted with the projects? 15:17:53 anteaya: dguryanov and mnestratov 15:18:33 I haven't interacted with either of those people 15:18:41 okay so combination of the two things 15:18:49 do what mmedvede is telling you 15:19:10 but you need to get to know people in other projects 15:19:14 you have to create trust 15:19:17 anteaya: we don't have the prerequisites for becoming voting CI, but it is always good to know what it takes:) 15:19:28 eantyshev: yes, well that is what it takes 15:19:39 a stable ci and the trust of the team on the project 15:20:19 does any one have anything more on this topic? 15:20:29 my first question was about the procedure of this 'stability' estimation. I'm going to look at radar closely 15:21:01 eantyshev: sounds good 15:21:27 does anyone have a different topic they would like to discuss? 15:21:35 anteaya: no 15:21:39 lennyb: thank you 15:22:01 thanks to mmedvede who will be chairing next week's meeting in this time slot 15:22:13 I'll read the logs and hope you all attend 15:22:26 thanks for your kind attendance and participation 15:22:32 I'll see you in two weeks 15:22:32 anteaya: thankss 15:22:44 enjoy the rest of your day/evening 15:22:47 #endmeeting