18:00:39 #startmeeting third-party 18:00:41 Meeting started Mon Oct 13 18:00:39 2014 UTC and is due to finish in 60 minutes. The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:44 The meeting name has been set to 'third_party' 18:00:56 bye 18:01:02 anyone here for the third party meeting? 18:01:13 * jesusaurus is lurking 18:01:16 Good morning! 18:01:17 * ctlaugh is here 18:01:28 * ociuhandu is around 18:01:50 welcome everyone! 18:01:51 hi 18:02:02 hello all 18:02:05 hello 18:02:18 o/ 18:02:24 o/ 18:02:31 #topic Welcome & Reminder of OpenStack Mission 18:02:41 #info The OpenStack Open Source Cloud Mission: to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable. 18:03:09 we have a light agenda today, but I'm sure we'll have a lively open discussion later 18:03:12 here is the agenda 18:03:29 #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#10.2F13.2F14 18:03:44 #topic Review of previous week's open action items 18:04:49 I didn't record any actions from last meeting 18:04:57 did I miss anything? 18:05:19 next 18:05:21 #topic Announcements 18:05:34 again nothing on the agenda 18:05:41 anyone have an announcement? 18:06:01 onward then 18:06:10 #topic OpenStack Program items 18:06:18 I'm the only item here 18:06:44 and that is for all to review the kilo summit session priorities 18:07:06 I'd like to fill that out into an etherpad for the summit session 18:07:15 that session has been scheduled 18:07:28 #link http://kilodesignsummit.sched.org/event/9902dac01525691e60ac94bf236569c6# 18:07:38 I hope to see you all there 18:08:28 next 18:08:30 #topic Deadlines & Deprecations 18:08:37 nothing here, anyone? 18:09:12 * krtaylor is thinking we may have the shortest meeting ever 18:09:23 #topic Highlighting a Program or Gerrit Account 18:09:43 no one volunteered to speak about their system here, maybe next week 18:09:46 * ctlaugh is new here -- starting to get involved, but nothing to contribute yet 18:10:11 I'll see if I can drum up a third-party service to give us a overview next week 18:10:21 welcome ctlaugh 18:10:46 I would love to hear about an example of a working one -- I am with Linaro and we are highly interested in setting up third-party testing for ARM 18:11:22 ctlaugh, I can prob help there, I was in Linaro too, I'll ping you later 18:11:33 krtaylor: excellent 18:11:47 ctlaugh, say hi to ibiris for me :) 18:11:55 krtaylor: I will 18:12:19 ok, so this is the fastest we have ever gotten to the Open Discussion 18:12:29 #topic Open Discussion 18:12:37 the floor is open 18:13:22 #link https://review.openstack.org/#/c/118623/ 18:13:39 * krtaylor looks 18:13:57 We had quite a few talks around it 18:14:04 ah yes 18:14:12 I was looking at that this morning 18:14:31 I am thinking I will abandon that one, and revive the effort after discussions at summit 18:14:39 and I had the feeling that we will move towards a format to trigger only third-party CIs on our last talk 18:15:00 had this feeling, just wanted to confirm it :) 18:15:09 yes, although I'd like to see it addressed again across the board 18:16:05 maybe some of the other third-party folks can also take a look and express their views on it 18:16:19 if infra is still strong feeling that recheck fires everything, then we'll need a ci specific recommendation, which is basically for the CI systems to document it on their wiki page 18:16:38 I agree wth ociuhandu's comments 18:16:45 ociuhandu, yes, that would be helpful for when it is revived 18:17:58 * krtaylor is trying to locate another link he'd like to get feedback on... 18:18:16 how about this one? :-) https://bugs.launchpad.net/zuul/+bug/1370105 18:18:17 Launchpad bug 1370105 in zuul "feature request: gerrit files option for pipeline triggers" [Wishlist,Triaged] 18:18:29 aw, beat me to it 18:18:42 so I was looking at this last week 18:19:25 this one too: https://review.openstack.org/#/c/123578/ 18:20:17 sweston, are you working that one? 18:20:31 I will take it 18:20:56 asselin, and https://review.openstack.org/#/c/122896/ 18:21:07 sweston, excellent 18:21:24 sweston, I was hoping I could, not enough hours in the day 18:21:55 the asselin 's patch adds additional gate hooks. It is good to have for third-party. 18:21:59 so I will beg reviews for the 2 links for asselin 's patches 18:22:02 I have a few hours at the end of the week, I'll take it off your hands 18:22:04 mmedvede, ++ 18:22:11 thanks 18:22:24 sweston, thats perfect 18:22:35 krtaylor: ok 18:22:39 should I rebase https://review.openstack.org/#/c/122896/ now, or after it's dependency merges? 18:22:55 asselin, those are close, they just need another +2 right? 18:23:19 they both have 1 +2 18:23:24 so yes 18:23:57 let's bring those up at the infra meeting tomorrow, if they are still needy 18:24:20 ok...infra or qa? 18:24:39 infra was what I was thinking 18:24:56 ok I see..it's in openstack-infra. 18:25:07 asselin, they are infra patches 18:25:15 asselin: why not just run cleanup after d-g runs? 18:25:16 right, its tomorrow 18:25:23 +1 18:25:23 or before it runs? 18:25:38 I don't think we need this functionality in d-g. it exists to run devstack then tests. Not cleanup after them 18:26:08 clarkb, b/c the log file upload is there. 18:26:29 asselin: we can chat outside the meeting but I don't understand how that comes into play 18:26:39 ok 18:27:01 clarkb, we have also found this idea to be very useful 18:27:26 right I get that the functionality is useful, but if you run it after d-g returns don't ou get the same functionality? 18:27:42 (or before d-g runs depending on the context of pre vs post) 18:27:47 no, if it's a failure, then no other tasks run 18:27:58 asselin: thats an artifact of your job setup 18:28:01 asselin: you can change that 18:28:17 * asselin looking 18:28:17 mmedvede, rfolco ^^^ 18:28:48 and also, we sanitize some log files before they're uploaded 18:29:06 clarkb, the issue is that if we want to, for example, pull custom logs, we can not use post test hook, because it is not run if tests fail 18:29:14 mmedvede: but that can be changed 18:29:30 remove set -e, run d-g, record $?, run post options, exit recorded $? 18:31:41 clarkb, I can try that and see if that's sufficient for what we need to do 18:31:42 ok, that looks like it might require more discussion in -infra 18:31:44 clarkb, yes, we can do this. But would it not be more invasive and have a potential to break things? Also, as rfolco said, we might want to do additional work after cleanup 18:32:03 no I think adding more features to d-g is invasive 18:32:15 and likely to break things particularly since it will not be used upstream where we test d-g 18:32:50 I think the refactoring is good idea regardless 18:32:51 clarkb, the patch should not add anything unless there are post/pre hooks are defined 18:33:12 it also includes unit tests which were not there before 18:35:39 ok, it looks like this discussion is dying down 18:35:54 we can continue in -infra 18:36:01 ok 18:36:05 Are there any other recommended links to start with other than http://ci.openstack.org/third_party.html#the-jenkins-gerrit-trigger-plugin-way? 18:36:12 oops, sorry, wrong link 18:36:41 http://ci.openstack.org/third_party.html (without the anchor) 18:36:46 ctlaugh, there are several good ones 18:36:57 jaypipes has a couple 18:37:06 I have a list I'll forward 18:37:15 krtaylor: thank you 18:37:38 anyone else? 18:38:03 thats a new record for the fastest meeting 18:38:13 thanks everyone! 18:38:27 thanks! 18:38:38 #endmeeting