18:01:18 #startmeeting third-party 18:01:19 Meeting started Mon Dec 8 18:01:18 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:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:22 The meeting name has been set to 'third_party' 18:01:31 o/ 18:01:35 o/ 18:01:41 any third-party CI operators around? 18:02:38 o/ 18:03:08 well, I hope my connection holds out, seems network is more flaky than normal 18:03:38 we'll wait for you ;-) 18:03:53 hehheh, hopefully we have more lurking 18:04:02 #topic Welcome & Reminder of OpenStack Mission 18:04:10 #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:24 we have a pretty full agenda today 18:04:42 #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#12.2F8.2F14 18:05:01 #topic Review of previous week's open action items 18:05:16 so we had 2 from last week, both mine 18:05:40 I completed the wiki and kickoff email for the 3rd party doc refresh 18:05:48 hope all saw that email 18:05:58 we'll get to that in a bit 18:06:29 second was to ping PTLs for deadlines, and I have some updates there as well 18:06:53 #topic Announcements 18:07:00 any announcements? 18:07:37 I'll take silence as no 18:07:39 #topic OpenStack Program items 18:08:27 so, the third-party CI documentation is underway 18:08:32 #link https://etherpad.openstack.org/p/third-party-ci-documentation 18:09:03 if you want to help, comment on the email thread, read the current docs, think through changes 18:09:10 and sign up on the etherpad 18:09:49 we'll see the response, if we get several people wanting to help, we may try the virtual sprint that infra manual did 18:10:31 that was to use the sprint irc channel for 2-3 days of working as a team to bang out all the updates 18:11:03 but if not, we'll just use the etherpad to coordinate the patches and figure out what is being worked on 18:11:27 any questions on that? 18:12:01 else, onward, to third-party CI monitoring and the associated spec 18:12:05 #link https://review.openstack.org/#/c/135170 18:12:39 I see some comments, sweston were you going to rev that spec? 18:12:46 or did you need more input? 18:12:57 I am still responding to the latest comments, but there is only one noteworthy comment so far. I need more input. 18:13:28 ok, I was thinking of proposing a command line tool, that could be a subset of the vision to get started 18:13:37 jhasketh would like some functionality included for the rest api, and that is fine. 18:14:18 krtaylor: yes, that would be helpful. the command line tool would be used to access the rest api 18:14:23 did anyone else have any questions or comments on the spec for sweston ? 18:15:34 sweston, the process used to test a system in question could use more detail, as well as how the data will be represented, early feedback from other projects was for a radar-like ui 18:15:54 krtaylor: ok, noted 18:16:33 krtaylor: thank you 18:16:51 so, if nobody has any questions or comments, please review the spec 18:17:56 and finally for this section, I hope everyone has heard about the third-party self serve system accounts 18:18:13 go read all about it at: 18:18:18 #link https://review.openstack.org/#/c/137240 18:18:30 woot!! 18:18:41 yes, very nice 18:18:43 yes, fantastic work by infra team 18:18:50 +1000 18:19:05 I have not heard of anyone using it yet, any feedback? 18:19:54 ok, onward then 18:19:59 #topic Deadlines & Deprecations 18:20:29 neutron mid-cycle is underway, we may get feedback for this topic following that 18:20:58 cinder said "Current plan is that we are warning people with existing drivers that they need CI working K-2. New drivers need it by the end of Kilo." 18:21:11 as per jungleboyj 18:21:58 I have not head of any changes or new deadlines coming for nova driver testing 18:22:35 except that they are looking for better reporting on the health of CI systems (what our monitoring dashboard addresses) 18:22:43 #link https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers 18:22:50 ^^ cinder 3rd party ref 18:23:03 asselin, thanks! 18:23:43 asselin, are you the cinder liaison? 18:24:03 krtaylor, not officially, but I work on cinder-ci 18:24:19 asselin, I would be it will be official soon :) 18:24:26 lol 18:24:26 s/be/bet 18:24:51 any questions or comments on deadlines? 18:25:15 #topic Highlighting a Program or Third-Party CI Service 18:25:47 just another quick mention on the split out of the puppet modules, see links in agenda 18:26:04 that will be ongoing for a while I imagine 18:26:29 the split script has been running successfully for a week now, so yay for that 18:26:30 sweston, how's your script doing with that? 18:26:46 ok, great. I was going to start another one and ref your repo 18:27:03 it has also been proposed to the repository, one sec, i'll have the link 18:27:30 https://review.openstack.org/#/c/137991/ 18:27:52 asselin: waiting for your respected review ;-) 18:28:10 (and anybody else who would like to test it) 18:28:24 sweston, can you change the topic to module-split 18:28:31 sweston, will be easier to find :) 18:29:01 asselin: yeah, I must have reset it to master when doing the check-in 18:29:10 will do 18:29:13 thanks 18:29:41 excellent, so that brings us to your items asselin 18:29:43 In-tree Third Party CI Solution 18:29:55 #link https://review.openstack.org/#/q/topic:thirdpartyci,n,z 18:30:29 I wrote a spec to get an in-tree ci solution based on what infra is using (jenkins/zuul/nodepool) 18:30:57 I also took a baby-step to get the log server directly reusable by 3rd party ci operators 18:31:04 looks good 18:31:12 yes, lots of comments there :) 18:31:12 Lots of good comments, and I'd like to get some more 18:31:21 asselin: this is interesting, thanks, will definitely review 18:31:28 and see if anyone has ideas/solutions to address the comments 18:31:39 we've needed this for a long time :-) 18:31:49 agreed 18:32:08 asselin: +1000 18:32:47 my 'internal' stretch goal is to get something working/proposed by K1. 18:33:00 (before k2 starts) 18:33:06 asselin: i'll work with you on this, would you add me as a primary assignee? 18:33:12 or before christmas :) 18:33:19 sure can, thanks! 18:33:39 awesome, and thanks for the spec! 18:33:52 great work 18:34:09 if anyone else is interested, just ping me, or add a comment to the spec asking to be added :) 18:34:35 * krtaylor wishes he had more time to work on this 18:35:03 krtaylor, reviews/ideas would be great 18:35:15 asselin, will do 18:35:24 thanks 18:35:38 and I'll see if I can encourage others to review as well 18:36:05 any other questions or comments from anyone for this topic? 18:36:50 onward then 18:37:01 #topic CI System issues 18:37:09 anyone have anything here? 18:37:40 I did see some great comments left for other systems that were wishing to have their account re-enabled 18:38:23 exactly the value that this team can bring to the community, reviewing other systems and recommending their enabling or voting, ect 18:38:42 any systems needing review? 18:39:16 #link https://wiki.openstack.org/wiki/ThirdPartySystems 18:39:33 the systems page shows several that are still down 18:39:50 4 I believe 18:40:44 I don't know how current this page is, it may need refreshing, I'll email those systems 18:41:30 next then 18:41:45 #topic Open Discussion 18:41:58 I had one item, meeting time/date 18:42:15 there is an email thread, currently with 2 proposals 18:42:34 1) for 2 meetings a week 2) for one meeting a week at alternating times 18:42:45 please read that thread and comment 18:42:57 I'd like to get that wrapped up this week 18:43:36 so far, the alternating meeting proposal has the most votes, if that continues, I'll propose times to vote on shortly 18:43:48 any comments? 18:44:07 +1 for alternate meeting times 18:44:24 ditto 18:44:28 same 18:44:39 thanks asselin, sweston, mmedvede 18:44:58 ok, then I'll open the floor 18:45:13 any topics to discuss, questions to answer? 18:48:31 ok, well since the discussion has wound down quickly, I'll close it out 18:48:39 thanks everyone, great meeting! 18:48:49 thanks krtaylor 18:49:03 thanks everyone! 18:49:07 #endmeeting