18:01:01 #startmeeting third-party 18:01:02 Meeting started Mon Dec 1 18:01:01 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:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:06 The meeting name has been set to 'third_party' 18:01:22 anyone here for third-party? 18:01:27 o/ 18:01:33 o/ 18:02:07 hi everyone 18:02:07 o/ 18:02:45 note quite awake, but here 18:02:49 /note/not/ 18:03:02 * jesusaurus lurks 18:03:08 I hope everyone had a nice break, or at least a break from those that did have a break 18:03:28 ok, let's get started 18:03:33 #topic Welcome & Reminder of OpenStack Mission 18:03: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:52 today's agenda: 18:04:02 #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#12.2F1.2F14 18:04:17 and yes, I was late updating it 18:04:36 #topic Review of previous week's open action items 18:05:01 the only action from last week was mine, and I did not get that done 18:05:23 it was to kick off the third-party documentation wg 18:05:52 but, I wanted to be a part, and was about to leave for US holiday, so I punted 18:06:00 but I will get that going asap 18:06:25 yay :-) 18:06:30 hehheh 18:06:40 so next 18:07:02 #action krtaylor to finish initial CI doc work group formation 18:07:02 18:14:14 altright then, sweston had the second 18:07:21 oops too many line pasted 18:07:33 #topic Announcements 18:07:42 any announcements? 18:08:23 I guess I'll mention that infra manual sprint is happening now 18:09:17 jump on that if interested, email announce went out 18:09:52 although I cant find it atm 18:09:59 any others? 18:10:28 #topic OpenStack Program items 18:11:01 ready? 18:11:11 third-party CI documentation is a carry-over 18:11:27 yeah, so you are up sweston 18:11:35 I will respond to the comments already posted in the review today, still waiting for input from the other reviewers. When would you like the spec to be finalized? 18:12:25 sweston, I think we had hoped for this month, before everyone disappears for more holiday festivities 18:12:44 by the end of next week at the lates 18:12:48 latest 18:13:03 I dont think that is moving too quickly 18:13:17 ok 18:13:27 especially now since folks are back from holiday/vacation 18:13:48 I have been playing around with the poc, it is nice 18:14:05 search works good, etc 18:14:55 and I need to re-read the spec and comment, hopefully jhesketh will too 18:15:07 good :-) glad you like it. I am looking for input on how to put together some status areas for the top of the dashboard. 18:15:24 yes, that would be good 18:15:57 a small section with all the CI systems represented somehow and a color-coded status 18:16:13 Ok. What are some good metrics to report on the status? 18:16:21 maybe just a small font and 3 or 4 columns 18:16:26 good question 18:16:58 thats where we need to agree on the formula on what is a healthy system 18:17:29 and how often it can be queried for a test re-queue, or some other demand status 18:17:39 so are you thinking a table format, with some colors for systems in different states, maybe 18:17:59 sweston, sure, that would work, I'm not too picky 18:18:24 krtaylor: ok, I will come up with something nice for that 18:19:39 next task is hooking into the gerrit event stream. I suspect that part will probably take the rest of the week, given the time I have set aside for this 18:19:55 actually, maybe the top page is the status and the details you list there are linked to the name in the status table, just an idea 18:20:15 sweston, your work on it is very much appreciated 18:20:21 ok, that will work. 18:21:10 for reference, here is the link for that page we are discussing: 18:21:13 #link http://dashboard.triniplex.com/# 18:21:22 krtaylor, thank you. that's all I have for this week. 18:21:50 any other comments or suggestions on the dashboard spec or design? 18:22:00 yes, if any one else has comments or input on the ui, please feel free to send me an email or ping me on irc 18:22:23 thanks sweston 18:22:34 krtaylor: np 18:22:39 ok, next is self service accounts 18:22:53 I posted the link to the doc changes, please review 18:23:13 #link https://review.openstack.org/#/c/137240 18:23:45 there is some nice re-write on the old wording there too 18:24:31 anteaya, are you around to comment on self-service accounts? 18:24:59 busy on infra manual sprint I am sure 18:25:31 yes 18:25:41 creating accounts will soon be self service 18:25:42 anyway, everyone should follow this work 18:25:47 hi anteaya 18:26:08 once that happens we will post an email to the mailing list instructing people about what to do now 18:26:16 to the -dev mailing list 18:27:14 excellent 18:28:05 so, everyone can help this along by staying active in the review for these patches 18:28:18 thank you 18:28:27 if you have suggestions for how to improve the process, now is the time 18:28:32 thanks anteaya 18:28:50 oh ping me when you are at open discussion please 18:28:58 anteaya, will do 18:28:58 sorry not following the meeting 18:29:00 thanks 18:29:07 anteaya, np 18:29:48 onward then 18:29:49 #topic Deadlines & Deprecations 18:30:01 I don't know of any yet 18:30:23 anything coming out of cinder? or neutron? 18:31:37 I'll take an action to get with their cores and see if they would like to bring anything up to this group in the next few weeks 18:32:21 #action krtaylor to ping cinder, neutron, nova for any CI testing deadlines 18:32:46 anything else? 18:32:56 next 18:33:05 #topic Highlighting a Program or Gerrit Account 18:33:47 so I have here a reminder for anyone that wants to jump in on the patches for splitting out puppet modules 18:34:09 I have proposed a change to the system-config repo with the split script I created for the module split. reviews are welcome. 18:34:10 I know sweston, mmedvede and asselin were working on some automation - any status 18:34:18 ^ 18:34:19 sweston, thanks 18:34:38 https://review.openstack.org/#/c/137991/ 18:35:00 #link https://review.openstack.org/#/c/137991/ 18:35:16 so it will show up on links summary :) 18:35:50 the script is running live against my github account now. the initial filter for the branches takes about 10 minutes. 18:36:10 ok, good to know 18:36:22 the resync process takes less than a minute for each module with updates 18:36:39 and only if there are updates, right? 18:36:49 correct. 18:37:06 no longer using the branch split, it was taking too long 18:37:11 great 18:37:57 I think that is all the info for this week, asselin is still on vacation today, I believe 18:38:08 regarding the module split, that is 18:38:20 ah, ok 18:38:37 well there are plenty of tasks left 18:39:03 mmedvede, anything to add? 18:40:09 we dont have a third-party system to discuss this week 18:40:41 so any systems that need help? currently down? reporting incorrectly? 18:41:14 #topic CI system issues 18:42:13 this is the part of the meeting where we will point out systems that we may have seen that are not working properly, or review systems that have previously had issues 18:42:45 this will become more important later, as we become a more self-regulating wg 18:43:13 ok then, open discussion time 18:43:24 #topic Open Discussion 18:43:46 ping anteaya open discussion time 18:43:57 thanks sweston 18:44:03 yup 18:44:34 any systems that need help working through a problem they are seeing? 18:46:44 hm, maybe anteaya got busy on infra manual 18:47:40 ok, well if no one has any questions, then we can wrap this up 18:47:48 last chance, anyone? 18:48:03 okay where are we on the email to have an additional meeting time 18:48:09 because I need that to happen 18:48:27 do we have an etherpad with some text yet 18:48:28 anteaya, me too, I am driving that, need to finish now back to work 18:48:45 anteaya, I was going to do that via email 18:48:49 krtaylor: okay so I need to have a link to an etherpad with a draft 18:48:59 not sure it needs an etherpad, do you? 18:48:59 krtaylor: lets have an etherpad please 18:49:03 yes 18:49:10 put some text in an etherpad 18:49:13 link me 18:49:15 * krtaylor shrugs 18:49:17 we agree on content 18:49:18 ok will do 18:49:21 we send it today 18:49:44 content meaning a meeting time right? 18:50:09 anteaya, ^^ 18:50:15 content meaning the draft of the email asking for input on an additional meeting time 18:50:24 oh, ok, sure 18:50:35 if I don't see an etherpad link in 70 minutes, I'll do it myself and link you 18:50:42 anyone else want to be linked? 18:50:57 include me please 18:51:00 I can't imagine it would take me that long 18:51:05 me too 18:51:07 sweston: very good 18:51:13 luqas: great 18:51:19 will do 18:51:22 anteaya: thank you 18:51:22 krtaylor: okay thank you 18:51:30 * anteaya returns to sprint 18:51:37 thanks anteaya 18:51:46 alright, anyone else? 18:52:58 ok, well thanks everyone for another good meeting, I'll get on these actions 18:53:05 see everyone next week then 18:53:06 Good meeting, krtaylor 18:53:13 krtaylor: thanks 18:53:19 sure, np 18:53:35 #endmeeting