15:00:51 #startmeeting third-party 15:00:53 Meeting started Mon Jan 19 15:00:51 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:56 The meeting name has been set to 'third_party' 15:01:01 hello 15:01:10 anyone here for the third-party meeting? 15:08:00 hi anteaya 15:08:07 hello wznoinsk 15:08:17 I don't believe we have met before 15:08:19 welcome 15:08:28 we haven't, pleased to meet you 15:08:35 likewise 15:08:42 what is on your mind today? 15:09:48 I'm setting up a 3rd party CI here and I wonder is there a prefered hosting solution for the yet-to-come infra-ci-suite - ideally I would you the same one if there's any preference 15:10:05 hosting solution 15:10:13 for the artifacts 15:10:19 as in what os to use? 15:10:21 ah 15:10:43 well we support you setting up an apache server that serves the logs 15:11:10 at one point asselin_ offered a patch to make that a generic setup for folks 15:11:42 but I do believe that we felt that having a generic setup for a log server wouldn't actually be that generic 15:12:01 and setup up an apache server already has a puppet module 15:12:14 so we would just be duplicating what already exists 15:12:18 if that makes sense 15:12:35 sure, while it's everyone's own preference I think it's easier to use some cloud provider to keep your logs there 15:12:46 if you like 15:13:01 it does and I do agree that the suite should be able to do that for you - like it will with apache 15:13:33 from operational/maintenance point of view other options should be considered I guess - but that's again preference 15:14:29 sorry, I misread the puppet/apache line... 15:14:50 I found ramy's patch: https://review.openstack.org/#/c/138913/ 15:15:23 I mis-remembered seems the hold up is finding the right place for the code 15:15:47 but if you like you could pull down the patch and use the code 15:16:00 if you do so, comments on how the code works for you would be helpful 15:18:06 so far we have jenkins/gerrit trigger aiming to run in lxc containers with some external logs hosting but I'll keep an eye on the infra ci suite for sure 15:18:27 wznoinsk: terrific thank you 15:18:40 would be glad to have your contributions here 15:18:50 how is your current set up working for you? 15:21:12 as for its early stages quite good, I reckon its way simpler to setup a CI now than it was some time ago (judging from the size of jaypipe's guides), gerrit trigger plugin in Jenkins doing significant portion of work for you and for simple setup you don't need Zuul 15:21:38 glad to hear you are getting good results 15:22:15 as for way simpler, well I think there are more people involved so more folks with experience falling down holes 15:22:28 there are efforts to make the tools easier to consume 15:22:48 but it is still a commitment to operate a CI system 15:24:35 I wonder is there any place I could get the gerrit stream stats from? like how many patchsets/comments per day/week/month on a project was created? 15:25:44 well gerrit 2.8 has a REST API: https://review.openstack.org/Documentation/rest-api.html 15:25:57 you might get some of the things you are looking for from that 15:27:03 wznoinsk: did you create your CI account yourself using launchpad? 15:27:39 https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI 15:28:25 thanks for sharing your wikipage, it looks good 15:28:41 did you create your CI account using launchpad? 15:28:50 yes, self-driven 15:28:55 great 15:29:10 you should also be able to query gerrit via ssh: https://review.openstack.org/Documentation/user-search.html 15:30:02 thanks for that, I'll see what I can get from there 15:30:07 great 15:30:16 if you end up with something useful 15:30:23 sweston is working on radar 15:30:55 #link http://git.openstack.org/cgit/stackforge/radar/ 15:31:12 he is looking for queries that folks find useful 15:31:16 to add to the dashboard 15:33:34 anteaya: thanks! 15:33:42 sweston: welcome 15:34:06 If anyone has any queries, please feel free to chat with me on IRC 15:34:44 sweston: hi there 15:35:08 wznoinsk: hi 15:35:42 the stats I'm looking for would be useful when planning a new CI system, to have rough idea how many patchets/build the CI would have to deal with, not sure whether these stats be useful at any later stages 15:36:56 wznoinsk: interesting... Yes I imagine they would be useful in a planning context 15:39:40 I can get away with my gerrit stream log for now, so I'll leave it with you whether you find it useful to be in the Radar 15:40:55 wznoinsk: I will incorporate it, yes I think it will be useful 15:41:34 cool, looking forward to it 15:50:15 I think that wraps it up for this meeting 15:50:25 thanks wznoinsk and sweston for your participation 15:50:29 see you next week 15:50:33 #endmeeting