15:02:14 #startmeeting third-party 15:02:15 Meeting started Mon Jun 8 15:02:14 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:18 The meeting name has been set to 'third_party' 15:02:21 hello 15:02:35 hi 15:02:41 morning ctlaugh_ 15:02:53 or appropriate time of day for you 15:02:57 :) 15:03:01 :) 15:03:01 hi 15:03:11 morning asselin_ 15:03:19 * anteaya knows it is morning for asselin_ 15:03:24 o/ 15:03:34 o/ 15:03:34 hey ameade 15:03:35 hi 15:03:35 good morning :) happy monday :) 15:03:39 o/ 15:03:40 and to you 15:03:51 so what shall we talk about today? 15:04:11 anyone have anything on their mind? 15:04:15 hi 15:04:57 asselin_: did you want to post a link to your email to the infra list about the virtual sprint? 15:05:09 yeah...looking it up 15:05:10 perhaps we can start there 15:05:13 thanks 15:05:48 #link http://lists.openstack.org/pipermail/openstack-dev/2015-June/065876.html 15:05:54 thank you 15:06:09 I'm proposing a virtual sprint for the common ci solution in early July 15:06:16 after the us and canada holidays 15:06:48 goal is, after the virtual sprint, to have 3rd party ci and upstream infra using the same puppet modules to setup a ci system 15:07:01 ++ 15:07:27 the email links to an etherpad 15:07:30 #link https://etherpad.openstack.org/p/common-ci-sprint 15:07:43 I have a VM or two that can be used for testing 15:08:10 lennyb: wonderful thank you 15:08:19 lennyb, that's be great! yes, right now there's lots of patches that need manual testing and critical reviews 15:08:52 #link https://review.openstack.org/#/q/topic:downstream-puppet+status:open,n,z 15:08:52 asselin_: in addition to folks knowing about it, do you need anything else from them? 15:09:00 I can help test 15:09:26 ctlaugh_: wonderful thank you 15:09:29 there's a lot of patches. I think the ones related to 'jenkins' should be close to merging 15:09:45 so if we can focus on that this week, we can get another one done 15:09:54 asselin_: good plan 15:10:28 asselin_: have you had any feedback on dates at all? 15:10:57 nothing not already publuc 15:11:20 asselin_: are you comfortable making July 8 and 9 the dates for the sprint 15:11:25 seems those dates are good except devvesa 15:11:26 removing the uncertainty there 15:11:40 yes, can confirm those dates. 15:11:43 thank you 15:11:50 we can never get everybody 15:12:13 and hopefully there will be enough access to artifacts that devvesa can follow along 15:12:29 any questions or comments on this topic? 15:12:50 yes, we can also plan to focus on jenkins job builder (his area) e.g. next week after jenkins merges. 15:12:57 awesome 15:13:01 another good plan 15:13:31 are we okay to move on now? 15:13:36 yes, thanks 15:13:43 great, thank you 15:13:52 I really appreciate you setting this up 15:14:04 and all your consistent hard work making this happen 15:14:15 so now let's take a look at this spec 15:14:22 it is a spec for a ci dashboard 15:14:30 #link https://review.openstack.org/#/c/135170/ 15:14:48 this spec started last november 15:14:53 and is taking a long time 15:15:16 one possible solution that the spec aims to build already exists 15:15:22 and the code is in stackforge 15:15:45 to my way of thinking we could choose to do the useful thing here and stand it up 15:15:56 I'm interested in hearing other folks thoughts 15:16:07 anybody care to speak up? 15:16:07 I was going to propose in this weeks working group meeting that we abandon this spec 15:16:31 everyone is already using patrickeast's 15:16:34 are you able to put a comment to that effect on the spec now? 15:16:42 sure, np 15:16:45 thank you 15:17:06 yeah, my concern at this point is that there's no one to work on the spec even if it's approved. 15:17:15 yes I share that concern 15:17:15 I can add that too 15:17:19 it was just too much to drop all at once, and then sweston got busy 15:17:27 I really like steve and think he is a wonderful person 15:17:35 and am grateful for all his hard work 15:17:42 anteaya, +1 15:17:45 however he is busy on other things 15:17:49 which I also respect 15:17:59 yes, it represents a tremendous amount of work 15:18:34 anteaya, so along the lines of what you were mentioning, perhaps we can get patrick east's solution up in -infra? 15:18:46 on an openstack.org hosted site? 15:18:48 anyone feel like offering a spec that we propose to stand up patrick's dashboard in infra? 15:18:54 asselin_: good idea 15:18:57 :) 15:18:58 krtaylor: you rang? :-) may I have a moment to read the scrollback? 15:19:06 sweston: hey there 15:19:16 patrickeast 's is already in the third-party-tools repo, we should re-spec it to include things it needs to get it to stage 1 15:19:24 sweston: we were admiring how much hard work you do 15:19:28 anteaya: hello, anteaya 15:19:37 sweston, re: monitoring spec 15:19:54 sweston: and acknowledging that your ci dashboard spec is kind of pointless as we already have a dashboard folks us 15:20:06 sweston: so it would be easier all the way around if we just use that 15:20:23 sweston: and we wanted to acknowledge how much we appreicate your hard work on this 15:20:50 ++ 15:21:11 krtaylor: no patrick's doesn't need to include anything else 15:21:14 that is the point 15:21:19 it works now, stand it up 15:21:33 agreed, and it is 15:21:39 trying to make a dash do everything is what ensured it couldn't get built 15:21:47 it would be nice to have it in infra though 15:21:49 anteaya, +1...it can be updated as needed just like the rest of infra services 15:21:59 exactly 15:22:02 yes, it would be nice to have infra stand it up, let's focus on that 15:22:11 asselin_: yes, once it is stood up 15:22:25 sweston: you okay with this? 15:22:43 sweston: noone wants you to feel that we don't appreciate your work because we do 15:22:53 sweston: we are just trying to solve the problem here 15:23:40 anteaya, krtaylor thanks for the recognition ... I appreciate it ... need a moment to formulate a thought, am feeling surprised 15:23:42 sweston: I know it is important to you to contribute, and there are still lots of ways for you to do so, if you agree we can abandon this spec 15:23:48 sweston: okay 15:24:07 I think part of the reason you are feeling surprised is you aren't around as much as you used to be 15:24:18 as this is a feeling a lot of folks have had for a while 15:24:25 just haven't articulated it 15:25:01 so the current proposal right now is to use a different solution, does someone have a link to patrick's dashboard? 15:25:22 sweston, http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack%2Fcinder&user=&timeframe=24 15:25:36 it is in his comment of June 4 15:26:25 * anteaya asselin_ is patrickeast pure storage? 15:26:35 yes 15:26:45 could explain why he isn't here today 15:27:34 the whole reason for creating the radar project was to create a base of code which folks could pick up and run with themselves 15:28:16 sweston: which is fine 15:28:22 that can still exist 15:28:30 but we don't need an infra spec for it 15:29:36 I feel that I got everyone started, but nobody was willing to work with the code .. I went to significant efforts to create a code base which was standardized across openstack projects, and am disappointed that I have received no help with the project at all 15:29:51 understood 15:30:10 yes, I understand the current topic, I would just like to make my feelings on the radar project known 15:30:16 it is frustrating to put time and effort into a direction and fail to achieve the support you hoped 15:30:28 thanks for sharing them 15:30:43 I appreciate you trusting us enough to express them 15:31:10 * anteaya waits in case there is more 15:31:17 I am ok with abandonment of the spec, but I would like some help to move the radar project forward, perhaps this could be a topic of another meeting 15:31:39 sweston: could you comment on the spec to this effect? 15:32:01 and certainly if you would like to discuss radar at another meeting, I think that would be fine 15:32:08 as far as I am concerned 15:32:09 sweston, if you can make the Wed working group meeting, you'll have the floor as long as you'd like 15:32:09 anteaya: yes, I can do that 15:32:15 sweston: thank you 15:32:25 or, maybe an infra meeting? 15:32:33 sweston: thanks for sharing your thoughts 15:32:45 krtaylor: I think a third party meeting is the place 15:32:55 krtaylor: yes, I can attend either meeting, which ever would be the most effective 15:33:32 sweston, lets use Wed, and I'll send out a reminder email 15:33:50 hopefully that will increase attendance 15:33:55 anteaya, krtaylor thanks for listening and hearing my concerns 15:34:19 sweston: thanks for sharing them 15:34:25 sweston: I appreciate it 15:34:27 :) 15:34:31 any more on this topic? 15:35:00 anteaya: :-) no, I think I've beaten this horse long enough. I will post my comments to the spec 15:35:20 sweston: thank you 15:35:26 let's move on then 15:35:28 anteaya: welcome 15:35:29 and thanks 15:35:32 :) 15:35:44 does anyone have anything else they would like to discuss today? 15:36:28 everyone's system is working as expected? 15:36:36 happiness abounds? 15:36:46 +1 15:36:48 hehheh 15:36:55 not sure about the happiness statement 15:37:08 akerr: did you want to talk about it? 15:37:18 mine ran out of disk space on the log server...fixing now... 15:37:23 or have you accepted it as working level frustration? 15:37:26 nah, I think it'd take a professional to get me out of my rut 15:37:27 asselin_: fun 15:37:40 akerr: enjoy the peace and quiet of your rut 15:38:05 well unless anyone stops me, I'll end the meeting 15:38:16 thanks to all for your attendance and participation 15:38:25 see you all next week 15:38:27 thanks anteaya 15:38:30 #endmeeting