15:00:37 #startmeeting third-party 15:00:38 Meeting started Wed May 13 15:00:37 2015 UTC and is due to finish in 60 minutes. The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:41 The meeting name has been set to 'third_party' 15:01:15 who's here for third party CI working group meeting? 15:01:15 hi 15:01:20 hello 15:01:22 hi o/ 15:01:23 o/ 15:01:34 hello 15:02:04 hi everybody, full agenda today 15:02:11 hi 15:02:18 #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#5.2F13.2F15_1500_UTC 15:03:02 so first off, I want to make sure that everyone knows that next weeks meeting is canceled due to summit 15:03:14 it is the 0400UTC meeting 15:03:19 Hi 15:03:51 so we will resume meetings after summit with the 1500UTC 15:04:57 and, its a topic I'd like to discuss there, whether the continued use of all the meetings continues to be necessary 15:05:29 or if we could go to every other week, or combine with some of the infra office hours meetings 15:05:44 might be a good email thread also 15:06:02 anyway, on to topics 15:06:30 #topic TPCIWG Session in Vancouver 15:07:18 our design session was not accepted, but the good news is that we have a infra work session for downstream-puppet and a BoF 15:07:57 asselin, I believe that the infra times have been set for your meeting, part 1 and 2 correct? 15:08:32 krtaylor, yes I think so 15:08:48 #link https://etherpad.openstack.org/p/infra-liberty-summit-planning 15:09:05 not sure where they get officially scheduled? 15:09:31 Surely on https://libertydesignsummit.sched.org/ ? 15:10:26 I think those are the general public meetings.... 15:10:29 yes, Thursday 3:10 and 4:10 15:10:40 http://libertydesignsummit.sched.org/event/2fc3cbea0ca84febf5a334cd5ca4d723 15:10:49 see the description 15:11:57 and the Bof is Wed, 1:50 local time 15:12:28 #link https://openstacksummitmay2015vancouver.sched.org/event/3d1a571f8e295eaeedee9af0ac03de57 15:12:43 I encourage everyone to attend these 15:12:45 * asselin adds to schedule 15:14:14 BobBall and I have been discussing how we could work some of the working group agenda items into the BoF session 15:14:52 so there may be time to discuss and brainstorm some of those topics we listed 15:15:28 any questions on those sessions? 15:15:51 I do hope so; a number of the items in the etherpad are also specific questions that we already wanted to talk about at the BoF 15:16:34 BobBall, excellent, are you or stefano_s leading that? 15:16:53 krtaylor: we are going to co-chair the BoF 15:18:15 * krtaylor is looking forward to meeting everyone 15:18:34 yep, me too 15:18:35 when is bof scheduled? 15:18:56 asselin, see the link, wed 1:50 15:18:56 The BoF was the second link krtaylor postedhttps://openstacksummitmay2015vancouver.sched.org/event/3d1a571f8e295eaeedee9af0ac03de57 15:19:31 thanks 15:20:10 I'm not sure the format since it is a user session, we may have to make it more fishbowl-ish so that we can promote a discussion 15:20:55 but, we'll see, the good news is that we have several opportunities to discuss things at summit 15:20:58 We're not sure of the format either - but discussion is certainly what we want to encourage so I'm sure we'll make it work 15:21:24 and I am always available for lunch/dinner discussions too 15:21:35 krtaylor: that would be great, actually 15:21:58 it is my first time at openstack summit, I am looking forward to getting to know the community better 15:21:59 Is the Friday sprint session also relevant with the focus on puppet-openstackci? 15:22:19 BobBall, yes 15:22:21 BobBall, absolutely 15:22:37 Good good - as I assumed 15:22:43 it is everyone packed into a room all working on related topics 15:22:51 * BobBall will be there for that too. 15:22:55 so any questions are quickly answered 15:23:05 = fast progress 15:23:48 lots of little meetings happen, its one of my favorite times at summit 15:24:15 ok, anything else on summit meetings? 15:24:53 #topic Repo for third party tools 15:25:12 so our repository is waiting for code 15:25:31 and I know some of you have nice tools that you have written 15:25:43 so the call is out to start pulling them together 15:25:50 +1 15:25:56 What sort of tools are you looking for in this repo? 15:26:19 sweston has pushed a patchset for radar, the proposed CI monitoring dashboard 15:26:45 oh so i had a question about that, isn’t radar already in a stackforge repo? 15:26:51 BobBall, anything that helps you with your environment, that falls outside of infra code 15:27:14 patrickeast, yes, and after seeing how big the patchset was, maybe it should stay there 15:27:49 the argument for it in our repo is that we have multiple cores that can take care of it 15:28:07 ah yea thats true, we would take ownership of it 15:28:30 we can add cores to the other project 15:28:49 I guess if it stayed in radar repo, then we'd need to add more of us to the core roles for it 15:29:20 either way, I kind of lean toward centralizing everything 15:29:31 -1 15:29:36 iirc at one point we talked about when some project in this repo got big enough it could split into its own repo… radar might already be there 15:29:36 but the downside is cloning would get everything 15:29:46 right 15:29:50 I think it's better to keep it separate when it makes sence 15:30:03 infra started central with all puppet modules and split them out. 15:30:21 I think eventually some parts of the thirdparty tools would follow the same fate 15:30:57 BTW - is there an instance of radar running centrally? 15:31:02 asselin, I think that is a good point, let's start documenting our position in the patchset 15:31:15 +1 keep separate if makes sense. It is easy to merge, hard to split 15:31:49 #link https://review.openstack.org/#/c/181562/ 15:32:42 cool, so we all agree to keep it separate? 15:33:03 BobBall, no, that would hopefully be the eventual outcome 15:33:21 Good good. I'd like to talk about that too :) 15:33:53 yes, it is an important tool to help increase the trust in third party CI reporting results 15:34:06 * asselin added a comment 15:34:40 devs need to be able to quickly see if a system can be trusted, or even compare its result statistics to those of upstream jenkins 15:34:51 thanks asselin, I will too 15:35:34 ok, so get those other tool patchsets flowing to the repo 15:36:08 we have a few also, ping mmedvede :) 15:36:35 any questions on the repo? 15:36:49 did we have the directory layout documented somewhere? 15:37:15 i put some stuff up for review but just kind of threw things in folder willy-nilly 15:37:23 patrickeast, I realized that I never pushed that 15:37:25 yeah...was wondering that when reviewing the fc passthrough patch 15:37:25 krtaylor: yes, I need to work on adding some 15:38:37 I like the proposed 15:38:42 patrickeast: your layout seems sane. I am not sure we can know ahead of time how to best organize it 15:39:10 I think it can be moved around if need be 15:39:31 but I like the general functional, then subdir for tool approach, thats what we discussed 15:39:49 I didn't put that into the readme, will do immediately 15:40:04 thanks for bringing that up patrickeast 15:40:12 np 15:40:39 any other repo questions? 15:41:11 #topic Monitoring dashboard status 15:41:37 we have discussed this partially already, but the spec is ready to go 15:41:53 maybe we can get a +2 during summit 15:42:22 it has been simplified and all reviews are positive 15:42:35 #link https://review.openstack.org/#/c/135170/ 15:43:13 but, it will stay in the radar stackforge repo, and we'll need to add others to it for care and feeding 15:44:28 asselin, would you bring up merge/approval to infra folks in case I forget 15:44:44 krtaylor, sure...perhaps a ping later today would be helpful 15:44:59 asselin, sure 15:45:34 so any questions on the radar monitoring dashboard? 15:45:49 Well maybe it's easier to talk about it at the summit 15:46:06 asselin, maybe we can discuss with sweston about adding others to the radar core 15:46:07 but as I said I'm interested in understanding what needs to be done to get an instance running :) 15:46:49 BobBall, agreed, unfortunately I think sweston isn't going to be able to make it to summit 15:47:48 OK - maybe we can talk in this meeting after the summit 15:48:14 is everybody coming in to Vancouver Sunday? 15:48:39 +1 15:48:41 o/ 15:48:45 maybe we can meetup before? 15:48:55 yea ill be there sunday 15:49:19 I'd be up for that. 15:49:23 (wandering in late) I'm not at summit but Emily will rep us if you tell her 15:50:00 to first order I doubt we'll need anything new/different 15:50:12 nice, that might be a good beverage session somewhere close tot he convention center 15:51:09 +1 15:51:35 maybe meet at the Sun ubuntu party 15:52:14 Yes...I think I registered for that. I need to double-check what time I arrive...might be later than I remember... 15:52:48 anyway, one last topic 15:53:00 #topic downstream-puppet 15:53:12 anything you want to say asselin ? 15:53:33 well the log server patches merged and are now in production! 15:53:35 it was pretty well discussed at the office hours meeting on Monday 15:53:41 excellent! 15:53:59 there's active patches now for jenkins & zuul. 15:54:15 still looking for volunteers for a few more parts. 15:54:22 I am trying the zuul in-progress patch to deploy zuul 15:54:32 mmedvede, cool! 15:55:11 would be good to get started pre-summit and maybe we can fix up whatever's left during the sprint next friday 15:56:12 yes, with the working sessions and the sprint, it should make huge progress next week 15:57:17 alright I'll open the floor for the last few minutes 15:57:22 #topic Open Discussion 15:57:36 quick questions? comments? 15:59:39 remember: next weeks working group meeting will be canceled 15:59:55 thanks everyone, great meeting, looking forward to seeing everyone at summit that can make it 16:00:08 thanks krtaylor 16:00:08 indeed, see you next week 16:00:12 o/ 16:00:28 #endmeeting