18:01:51 <krtaylor> #startmeeting third-party
18:01:53 <openstack> Meeting started Mon Dec 15 18:01:51 2014 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:57 <openstack> The meeting name has been set to 'third_party'
18:02:02 <mmedvede> o/
18:02:08 <asselin> o/
18:02:12 <sweston> o/
18:02:23 <luqas> o/
18:02:24 <ameade_> o/
18:02:26 <akerr> o/
18:02:44 <krtaylor> Hi everyone! anyone else here for third-party meeting?
18:03:13 <sarob> sorry about running long
18:03:31 <krtaylor> sarob, np, voting is important
18:03:36 <krtaylor> #topic Welcome & Reminder of OpenStack Mission
18:03:45 <krtaylor> #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:04:08 <krtaylor> we have another nice agenda today
18:04:16 <krtaylor> #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#12.2F15.2F14
18:04:40 <krtaylor> #topic Review of previous week's open action items
18:05:04 <krtaylor> we didn't have any, that's easy
18:05:34 <krtaylor> although I did take a note to email everyone to update their ThirdPartySystems status
18:05:41 <krtaylor> done
18:05:55 <krtaylor> #topic Announcements
18:06:02 <krtaylor> also none listed
18:06:17 <krtaylor> oops
18:06:33 <krtaylor> yes, the self service accounts!
18:06:48 <krtaylor> #link http://ci.openstack.org/third_party.html#creating-a-service-account
18:07:24 <krtaylor> I'll prob leave that there for a few weeks, good to spread that around
18:07:39 <krtaylor> any other announcements?
18:08:01 <krtaylor> onward then
18:08:04 <krtaylor> #topic OpenStack Program items
18:08:35 <krtaylor> so the first is the CI doc rewrite
18:08:53 <krtaylor> I have seen a couple of comments on the etherpad
18:09:13 <krtaylor> I am hoping to see more, and if we can get enough interest, have a virtual sprint
18:09:31 <krtaylor> lik ethe one that infra did for infra manual, it was very successful IMO
18:09:50 <krtaylor> the link to that etherpad is in the agenda
18:09:58 <krtaylor> but here it is again for completeness
18:10:00 <krtaylor> #link https://etherpad.openstack.org/p/third-party-ci-documentation
18:10:22 <krtaylor> if you want to help, please go sign up on the etherpad
18:10:35 <krtaylor> any questions?
18:11:02 <krtaylor> next is the spec for the third-party CI monitoring dashboard
18:11:13 <sweston> ok, so I have reworked the code to be more rest api oriented.
18:11:15 <krtaylor> #link https://review.openstack.org/#/c/135170
18:11:33 <krtaylor> sweston, great!
18:11:33 <sweston> jhesketh suggested a better design based on storyboard
18:11:48 <krtaylor> it is getting good feedback, could use more
18:12:02 <sweston> I have removed django completely.  I am using pecan now for the controller, sqlalchemy for the database orm, and wsme for the rest api.
18:12:35 <sweston> I will post the updates to the spec today
18:12:39 <krtaylor> ok, interesting, I didnt have a problem with the framework
18:12:57 <krtaylor> sweston, thanks for taking the lead on this, so much appreciated
18:13:07 <sweston> krtaylor: very welcome
18:13:27 <sweston> yeah, there were some comments on django and celery
18:13:44 <sweston> much too heavyweight for this application
18:13:56 <krtaylor> for all: please go review the spec, it needs comments now for how your system will be represented on the dashboard
18:14:19 <krtaylor> now is the time to comment on how your system will be monitored
18:14:35 <sweston> yup
18:14:49 <krtaylor> anything else sweston?
18:15:07 <sweston> krtaylor: I am finished, thank you!
18:15:13 <krtaylor> or any questions from anyone?
18:15:42 <krtaylor> excellent
18:16:05 <krtaylor> so the next is a recurring item, for the next bit anyway
18:16:34 <krtaylor> splitting out puppet modules
18:16:45 <krtaylor> so there are 2 patches out for review
18:16:51 <krtaylor> that push everything at once
18:17:17 <krtaylor> #link https://review.openstack.org/#/c/140523/
18:17:38 <krtaylor> #link https://review.openstack.org/#/c/140548/
18:17:58 <asselin> I'm in the process of updating those to remove the "TODOs"
18:18:16 <asselin> otherwise quite a few ppl expressed suport for the idea
18:18:50 <sweston> also, the split script is here https://review.openstack.org/#/c/137991/
18:18:51 <krtaylor> asselin, I like it, but it does remove the control of one at a time, until time of uncommenting
18:19:03 <krtaylor> sweston, yes, thanks!
18:19:58 <sweston> asselin and I will be working on testing it this week.  we ran out of time last week
18:20:31 <asselin> yes, it's a compromise, but should make the whole process more robust & with less effort
18:20:31 <krtaylor> mmedvede and I had discussed it a bit, I support the first patch, but not sure about the second
18:21:03 <krtaylor> but the question is whether the discussion happens at insertion, or uncommenting, as long as it happens
18:21:23 <asselin> the plan is to do the discussion at uncommenting.
18:21:45 <krtaylor> anyway, another great place for CI operators to get involved, reviews please
18:21:57 <asselin> the other advantage is to do more in parallel/ avoid conflicts for updating the same file
18:22:01 <mmedvede> I had a few concerns about pushing everything at once. Mainly, it is not a work flow I am used to. It might be separating the change from its effect
18:23:13 <mmedvede> I support the direction. And it is just a concern, would be interesting to see how it works out in a long run
18:23:29 <asselin> all these changes are effectively no-ops
18:23:58 <krtaylor> yeah, I guess removal (instead of uncommenting) would also work if the discussion necessitated
18:24:35 <asselin> krtaylor, yes, the plan is to remove all the leftovers after we're 'done'
18:24:45 <krtaylor> but I understand mmedvede 's point, it would require 2 patches for removal
18:24:55 <krtaylor> asselin, is the idea to still have a infra "sponsor" that shepherds the patch through the discussion?
18:25:23 <asselin> krtaylor, yes, infra would sposore the uncommenting patch for project-config
18:26:37 <asselin> so the process doesn't change. Only the number of changes made per puppet-module is less & simpler
18:26:57 <asselin> b/c the others have been pre-approved
18:27:46 <krtaylor> sure, it is a good thing, my concern is a minor nit
18:28:24 <krtaylor> the more reviews the better
18:28:29 <krtaylor> ok, anything else on the split out?
18:28:57 <asselin> I'd like to know what ppl think of doing a mini split out sprint
18:29:19 <asselin> or better to spread out e.g 1-2 a week?
18:29:53 <krtaylor> good idea, with infra would make it less painful, get it done
18:30:12 <mmedvede> asselin: I support that. But it depends if cores would be able to handle it :)
18:30:12 <krtaylor> else, it is an agenda item on a busy infra meeting
18:30:27 <krtaylor> exactly
18:30:43 <asselin> yes, thinking about next week before the break, since maybe it'll be a quiet day.
18:30:57 <krtaylor> but, it is worth asking them
18:31:22 <asselin> ok, will do. thank
18:31:54 <krtaylor> anything else? any questions from anyone?
18:31:57 <mmedvede> The only thing is I am on vacation starting next week
18:32:17 <krtaylor> yeah, I'll be around, but infrequently
18:32:20 <mmedvede> so might not be able to as active for the sprint as I wanted to
18:32:48 <krtaylor> asselin, maybe the next week, before new year?
18:33:09 <asselin> I'm available
18:33:48 <krtaylor> works for me, else after next week's meeting here, I'll be very high-latency
18:34:15 <krtaylor> but a lot depends on when infra cores are available too
18:34:32 <krtaylor> so let's get that answered
18:34:54 <asselin> I think we can move to next topic
18:34:59 <krtaylor> alright  :)
18:35:06 <krtaylor> next is also yours asselin: In-tree Third Party CI Solution
18:35:43 <asselin> #link  https://review.openstack.org/#/c/139745/
18:35:53 <krtaylor> I kept it here in the agenda, in case anyone has questions
18:36:12 <asselin> would like some more reviews
18:36:43 <asselin> didn't up date the spec, but was thinking of implmenting as new module inside system-config, and then split out later.
18:37:47 <sweston> asselin: yup.  I will review this week, been busy with the dashboard the last few days
18:37:50 <mmedvede> asselin: why split out later?
18:38:02 <mmedvede> and not start with split out right away?
18:38:38 <asselin> I would like to, but seems simpler to do the work in-tree first
18:39:13 <asselin> b/c of the dependencies & changes requires to openstack_project module
18:39:25 <asselin> required*
18:40:02 <mmedvede> gotcha
18:40:25 <krtaylor> ok, everyone review please, I will too
18:40:35 <krtaylor> anything else asselin ?
18:40:38 <asselin> but if you've got ideas on how to build it, let me know.
18:40:41 <asselin> that's it thanks
18:40:55 <krtaylor> #topic Deadlines & Deprecations
18:41:23 <krtaylor> I left the cinder statement here
18:41:58 <krtaylor> I hope by now that is not a surprise to anyone
18:42:36 <krtaylor> the neutron mid-cycle was last week, I have not heard if there were any new testing deadlines established
18:43:00 <krtaylor> anteaya, are you around, you were there right?
18:44:14 <krtaylor> ok, well, I'll see if I can get neutron folks to comment on the mid-cycle, any impacts for CI test systems
18:44:51 <krtaylor> I have seen ironic comments about third-party testing, but nothing firm I am aware of
18:45:15 <krtaylor> any others?
18:45:31 <krtaylor> onward then
18:45:43 <krtaylor> 18:25:15 <krtaylor>
18:45:58 <krtaylor> yep, cut/paste fail
18:46:00 <anteaya> third party didn't get mentioned at the neutron mid-cycle
18:46:01 <krtaylor> #topic Highlighting a Program or Third-Party CI Service
18:46:17 <anteaya> talk to edgar for any neutron deadline issues or questions
18:46:24 <krtaylor> anteaya, ok, great thanks!
18:46:31 <anteaya> welcome
18:47:40 <krtaylor> cool, so we didnt have a system scheduled for this week, I am going to start tapping shoulders for "volunteers" after the new year, all at Paris agreed to share their best practices
18:48:02 <sweston> krtaylor: +1
18:48:46 <krtaylor> it was amazing to hear what teams had done to work around bits, or improve this or that
18:48:51 <krtaylor> anyway, onward
18:48:54 <krtaylor> #topic CI System issues
18:49:18 <krtaylor> any questions from systems having difficulty?
18:49:39 <krtaylor> any systems need review to turn voting on?
18:50:38 <krtaylor> the ThirdPartySystems  page did get refreshed
18:50:57 <krtaylor> which is goodness, but there are still systems indicating they are down
18:51:17 <krtaylor> or maybe not fully implemented yet
18:51:38 <krtaylor> so keep your eyes open for systems needing help or reviews
18:52:09 <krtaylor> alright, finally then
18:52:10 <krtaylor> #topic Open Discussion
18:52:20 <krtaylor> any questions, comments?
18:52:35 <asselin> I'd like a reminder why we're changing the meeting time
18:53:26 <krtaylor> Paris attendees indicated that they were not happy with the current time, almost all agreed
18:54:08 <patrickeast> im curious about the new meetings too, are all 3 meetings covering the same topics? are they just duplicates to make it easier for everyone to attend?
18:54:34 <krtaylor> actually, I think the current time got us started, but it is time to serve our global team
18:55:31 <asselin> anteaya, do you object to changing times? I'm confused by the mailing list post....
18:55:33 <krtaylor> we had an email discussion, the feedback was to have one weekly meeting, with times that alternate wekly
18:55:40 <krtaylor> weekly
18:55:53 <krtaylor> most other teams have a similar format
18:56:00 <reed> i think the meeting times are still in flux, there doesn't seem to be an agreement yet and the discussion will have to continue via email, irc, etc
18:56:12 <krtaylor> reed, agreed
18:56:38 <asselin> krtaylor, why is this time slot not kept, with an additional one added?
18:56:47 <krtaylor> patrickeast, do you have a preference? or do you like the current time?
18:57:03 <krtaylor> asselin, no one liked it, mainly that it was on Monday
18:57:26 <krtaylor> at least I did not see any comment supporting it
18:57:31 <patrickeast> patrickeast: im ok will any of the times that were proposed, my schedule is flexable
18:57:37 <patrickeast> krtaylor: ^
18:57:45 <krtaylor> patrickeast, great, thanks!
18:58:19 <krtaylor> sweston created a poll, with the link in the email thread
18:58:28 <sweston> 2 minutes left
18:58:33 <krtaylor> 14 have voted so far
18:58:42 <krtaylor> sweston, do you have that link handy?
18:58:54 <sweston> krtaylor: yes, one second
18:59:02 <krtaylor> hehheh, race is on...
18:59:43 <krtaylor> #link  https://www.google.com/moderator/#16/e=21b93c�
18:59:47 <sweston> https://www.google.com/moderator/#16/e=21b93c
18:59:54 <krtaylor> cool!
19:00:01 <krtaylor> and with that, we are out of time
19:00:02 <sweston> krtaylor: you win the race :-)
19:00:12 <krtaylor> thanks everyone for another productive meeting
19:00:17 <sweston> thanks everyone
19:00:24 <asselin> thanks
19:00:27 <krtaylor> #endmeeting