18:00:16 <anteaya> #startmeeting third-party 18:00:17 <openstack> Meeting started Mon Aug 18 18:00:16 2014 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:20 <openstack> The meeting name has been set to 'third_party' 18:00:26 <anteaya> hello and welcome 18:00:35 <lyxus> Hello ! 18:00:39 <sweston> Hello ! 18:00:41 <anteaya> do show yourselves if you are here 18:00:43 <e0ne> hi! 18:00:46 <smcginnis> o/ 18:01:01 <krtaylor> o/ 18:01:03 <nuritv_> Hi 18:01:05 <kevinbenton> o/ 18:01:05 <omrim> Hello 18:01:09 <ignacio-scopetta> o/ 18:01:23 <anteaya> great thank you 18:01:27 <anteaya> off we go 18:01:38 <anteaya> #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_meeting 18:01:42 <anteaya> today's agenda 18:01:57 <anteaya> #topic Welcome & Reminder of OpenStack Mission 18:02:11 <anteaya> #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:02:14 <emagana> hello! 18:02:16 <dougwig> o/ 18:02:29 <dane_leblanc> O/ 18:02:34 <anteaya> for those of you for whom this might be your first meeting, being aware of the OpenStack mission is helpful 18:02:37 <vjay3> hello 18:02:37 <jaypipes> o/ 18:02:38 <anteaya> and welcome 18:02:53 <anteaya> next topic 18:02:59 <anteaya> #topic Review of previous week's open action items 18:03:13 <anteaya> #link http://eavesdrop.openstack.org/meetings/third_party/2014/third_party.2014-08-11-18.00.html 18:03:20 * krtaylor is thankful for anteaya running the meeting this week 18:03:23 <anteaya> there were two items from last week's meeting 18:03:24 <markmcclain> o/ 18:03:39 <salv-orlando> aloha 18:03:43 <anteaya> :D thanks to you krtaylor for doing such a great job chairing the last month or so of meetings 18:03:56 <anteaya> it makes is so much easier to have someone to share with, you do a great job 18:04:06 <krtaylor> nice to see huge crowd today! 18:04:10 <anteaya> #info third-party review and sync in infra on https://review.openstack.org/#/c/99990/ 18:04:13 * krtaylor blushes 18:04:16 <daya_k> hello 18:04:27 <anteaya> so we are working on getting the ci modules to a more consumable state 18:05:13 <krtaylor> I created an action for all to review puppet module split 18:05:15 <anteaya> to that end we are going to identify patches to review to help that effort 18:05:19 <anteaya> this is one 18:05:23 <anteaya> #link https://review.openstack.org/#/c/99990/ 18:05:33 <krtaylor> yep, yet to review that one myself 18:05:44 <anteaya> and the latest patchset looks like it could use some reviews 18:05:52 <anteaya> so let's action that for this week as well 18:06:10 <anteaya> when I say we should review something, show of hands who knows what I mean? 18:06:12 <anteaya> o/ 18:06:30 <krtaylor> o/ 18:06:33 <anteaya> #action third party team to review https://review.openstack.org/#/c/99990/ 18:06:49 <anteaya> there has got to be more attendees who know how to review 18:06:53 <anteaya> I know you are there 18:07:09 <sweston> o/ 18:07:09 <dougwig> i'm not familiar with puppet, nor if splitting is best practices. my review wouldn't be useful. 18:07:11 <anteaya> not much sense to put out a call to review if folks don't know how to review 18:07:12 <e0ne> o/ 18:07:15 <krtaylor> anteaya, as always, it would be nice for the third-party tag, but in this case, it is secondary, can we add multiple tags with -t? 18:07:31 <krtaylor> it may be that some don't know the interest as it applies here 18:07:31 <anteaya> dougwig: I disagree, can you identify a spelling mistake or a whitespace error? 18:07:37 <anteaya> dougwig: if yes, your review is helpful 18:07:45 <dougwig> i'm happy to do that. 18:07:53 <daya_k> do we review with a +1 if we agree with the item? 18:08:03 <anteaya> krtaylor: no I don't think we can add multilple topics, let me think on that 18:08:09 <e0ne> daya_k: yes 18:08:16 <anteaya> dougwig: great thanks, I look forward to your review 18:08:35 <anteaya> next item from last week 18:08:41 <krtaylor> daya_k, looks good to me (+1) or if you see a problem, you add a comment and -1 18:08:49 <anteaya> #info joa and krtaylor to discuss doc improvement sections to focus on 18:09:04 <anteaya> so joa can't make today's meeting 18:09:07 * krtaylor I'll go play with -t and multiple tags 18:09:26 <krtaylor> anteaya, joa never pinged, I should have followed up 18:09:31 <anteaya> and he is caught in the void between the infra-manual repo and config/third-party.rst 18:09:36 <anteaya> so I will help him out 18:09:45 <anteaya> he just in in -infra 10 minutes ago 18:09:58 <krtaylor> he was looking for advice on how to bust up what he has into reviewable sections 18:10:04 <anteaya> and will offer some patches to config based on his work, with him as co-author this week 18:10:07 <anteaya> right 18:10:14 <krtaylor> ++ 18:10:32 <anteaya> #action anteaya to offer joa's work as config patches with joa as co-author by next meeting 18:10:40 <anteaya> I'll need some reviews from folks 18:10:43 <anteaya> next topic 18:10:59 <anteaya> #topic Announcements 18:11:03 <anteaya> this is me 18:11:15 <anteaya> #info Avoid comment generator scripts (anteaya) 18:11:26 <anteaya> salv-orlando: would you like to share your thoughts here? 18:11:35 <dougwig> can you expand on what that means? 18:11:38 <anteaya> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/042880.html 18:12:04 <anteaya> so the vmware ci had an issue and had to reboot, losing its queue 18:12:08 <asselin> o/ 18:12:20 <sc68cal_> Ah, I think I can jump in here as well - we have an ipv6 patch that is trying to re-trigger NEC CI 18:12:22 <salv-orlando> I think I should apologise publicly again? Yeah our ci had a script that did recheck by pushing ‘recheck’ comments to gerrit 18:12:33 <anteaya> so it used a generator script to mass comment on patches in gerrit to recheck theim with their system 18:12:50 <anteaya> salv-orlando: no apology necessary, just a look so other folks avoid the problem 18:12:51 <salv-orlando> this script was ran on all openstack/nova patches in the CI build’s queue. 18:13:14 <kevinbenton> mass retries should be internally triggered with no public side effects other than a new vote when finished, right? 18:13:21 <salv-orlando> Apart from annoying people with an extra comment coming from nowhere, this also had a side issue which was totally our fault. 18:13:39 <salv-orlando> We missed the email where we said that recheck.* is a verboten namespace for rechecks 18:13:50 <salv-orlando> and ended up pushing all those patches upstream as well to zuul 18:14:02 <dougwig> is it still ok to do manually on an occasional basis, or do we need internal mechanisms for anything we re-trigger? 18:14:07 <salv-orlando> at the end of the day minesweeper choked zuul, and the account was disabled. 18:14:10 <anteaya> dougwig: manual is fine 18:14:43 <salv-orlando> so if you have a similar mechanism for recheck and more importantly if you use recheck* for doing rechecks you are at risk of being disabled at any moment 18:14:44 <anteaya> yeah so the point is the automation of comments ended up taking out openstack's zuul 18:15:00 <anteaya> and more importantly bringing down infra 18:15:04 <anteaya> so please don't do that 18:15:17 <anteaya> once we can handle as a learning item, so let's learn 18:15:27 <anteaya> more than once and we risk mutiny 18:15:32 <anteaya> so let's not do that 18:15:37 <anteaya> questions? 18:15:39 <salv-orlando> what anteaya is saying happened because the pattern was recheck-vmware. Now.^.*recheck.*$ triggers zuul 18:16:08 <dougwig> do we have a recommended syntax for 3rd party retriggers? 18:16:15 <anteaya> also the point is automation can provide a ddos very quickly 18:16:22 <anteaya> dougwig: we are working on that 18:16:36 <anteaya> dougwig: would you like to add that to the infra team meeting tomorrow so we can discuss it 18:16:43 <sc68cal_> anteaya: what can devs do in the meantime for retriggering specific CIs that are blocking work? 18:16:54 <anteaya> it is a discussion item but we haven't reached consensus yet 18:17:05 * sc68cal_ feels bad for being pushy 18:17:17 <anteaya> sc68cal_: good question, I have to be honest and say I don't currently know the safe way to do that 18:17:25 <anteaya> sc68cal_: never feel bad for being pushy 18:17:37 <anteaya> better than staying quiet and wreaking havoc 18:17:40 <sc68cal_> anteaya: OK - do you have that link handy for the contact info for 3rd party CI contacts? 18:17:47 <sc68cal_> I had it at some point but lost it :( 18:17:49 <kevinbenton> isn’t manually retriggering still fine? sc68cal_, anteaya 18:17:50 <salv-orlando> sc68cal_: maybe for vmware I’ll try “"Bibbidi bobbidi boo!”” 18:17:51 <dougwig> anteaya: sure. i'm not picky on what it is, as long as we do something to retrigger without affecting openstack jenkins. 18:17:54 <sc68cal_> salv-orlando: lol :) 18:17:57 <anteaya> sc68cal_: can you ask in -infra and report back if you learn before the top of the hour? 18:18:08 <anteaya> kevinbenton: manual retrigger is fine 18:18:09 <sc68cal_> anteaya: sure - thank you :) 18:18:16 * krtaylor looks for sdague's recheck proposal 18:18:22 <anteaya> kevinbenton: since even if you do an oops it is one oops, not 600 18:18:31 <krtaylor> https://review.openstack.org/#/c/109565/ 18:18:35 <anteaya> salv-orlando: I like it 18:18:45 <anteaya> dougwig: agreed 18:18:48 <dougwig> i think we're going to see a lot of creative retrigger prefixes in the short-term. :) 18:18:55 <anteaya> dougwig: and right now I don't know what that is 18:19:19 <anteaya> krtaylor: that is more of the conversation, not the decision about what the safe way is yet 18:19:26 <krtaylor> lots of discussion on that topic 18:19:28 <kevinbenton> anteaya: right. so if sc68cal_ is blocked by a negative he can just issue rechecks on that one safely 18:19:40 <krtaylor> anteaya, just posted for background 18:19:44 <anteaya> dougwig: unfortunatly, which is why if you can add an item to the infra agenda it would help many others 18:19:49 <anteaya> krtaylor: right, thank you 18:19:57 <anteaya> kevinbenton: yes 18:20:14 <anteaya> so more here or moving on for the moment? 18:20:28 <anteaya> allowing sc68cal_ to chime in if he gets an answer 18:20:51 <anteaya> sorry this was supposed to be under announcements as well 18:20:55 <anteaya> #info Helping out on the mailing list 18:21:08 <anteaya> it would be great if people could help out on the mailing list 18:21:16 <anteaya> some have and it is great to see, thank you 18:21:25 <e0ne> anteaya: thanks for raising this topic on meeting 18:21:26 <anteaya> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/043392.html 18:21:39 <sc68cal_> I'm just going to shoot an e-mail to the e-mail address the NEC CI account is listed as - and hope for the best :-\ 18:21:48 <anteaya> this item currently needs some attention and a response from cinder 18:22:02 <anteaya> jungleboyj: can you take it? 18:22:07 <jungleboyj> Did someone say Cinder? 18:22:12 <anteaya> e0ne: my pleasure 18:22:23 <anteaya> jungleboyj: yes the above linked email needs your attention 18:22:27 <e0ne> jungleboyj: yep:) 18:22:28 <anteaya> jungleboyj: can you reply? 18:22:37 <anteaya> sc68cal_: go you 18:22:37 <kevinbenton> sc68cal_: amotoki handles NEC if that’s what you are looking for... 18:23:07 <sc68cal_> anteaya: kevinbenton: thanks :) 18:23:08 <jungleboyj> anteaya: Yeah, I can follow up on that e-mail. 18:23:09 <asselin> anteaya, I don't think this is a cinder question but an infra question 18:23:21 <anteaya> jungleboyj: thank you 18:23:23 <e0ne> i'm not sure thas such issue is onlu cinder related. maybe neutron too 18:23:32 <jungleboyj> anteaya: Wait, asselin is right. 18:23:33 <anteaya> asselin: please expand 18:23:57 <asselin> anteaya, the question is how to configure zuul to limit which patches it checks to a file being changed 18:24:21 <anteaya> asselin: great, do you have any knowledge you can share to help find an answer to that question? 18:24:25 <asselin> rule: when change includes file_regex, run test 18:24:26 <anteaya> or does anyone else? 18:24:47 <jungleboyj> Ok, so it sounds like you have that one asselin ? 18:24:49 <asselin> anteaya, no, but I'm also interested in the answer :) 18:24:50 <anteaya> there is a lot of knowledge in this group about how to run a ci 18:25:13 <anteaya> does anyone in channel have even a bit of info to respond to this email? 18:25:25 <anteaya> since waiting for infra to answer may take some time 18:25:38 <salv-orlando> asselin: I’m sure zuul/layout.xaml or some similar file have a section where you configure a filter similar to those of a jenkins’s gerrit trigger 18:25:40 <asselin> well I can take the action to ask -infra how to do it, if it's even possible today.It's possible that feature is not supporeted 18:25:46 <salv-orlando> * layout.yaml 18:25:49 <dougwig> i'm currently running against all commits, because i haven't had a chance to run this down. i'd love an example as well. 18:26:00 <anteaya> asselin: thanks, that will be a help indeed 18:26:23 <e0ne> asselin: is it ok to have one ci for two or more proejects? in my case it is cinder and nova 18:26:36 <dougwig> i think it's Jobs -> Files, but i haven't tested it. 18:26:45 <anteaya> #action asselin to ask infra about zuul configration to filter patches 18:26:52 <anteaya> asselin: did I get that right? 18:26:59 <asselin> salv-orlando, yes, I noticed this recent patch is similar idea, (wait for jenkins +1 before running) which is nice for 3rd party as well: https://review.openstack.org/#/c/114712/1/modules/openstack_project/files/zuul/layout.yaml 18:27:11 <salv-orlando> anteaya: I can confirm it’s zuul/layout.yaml in oepnstack-infra/config 18:27:18 <anteaya> salv-orlando: thanks 18:27:18 <asselin> yes, filter patches on changed files 18:27:26 <salv-orlando> there is a section for configuring the gerrit trigger on each pipeline 18:27:43 <anteaya> asselin: great, are you also willing to reply to the email with what you learn or would you like someone else to? 18:27:51 <asselin> anteaya, sure 18:27:57 <anteaya> thanks 18:28:04 <krtaylor> e0ne, yes, one account can test multiple projects, does that answer your question? 18:28:13 <anteaya> #action asselin to reply to http://lists.openstack.org/pipermail/openstack-dev/2014-August/043392.html with what he learns 18:28:15 <anteaya> thanks 18:28:21 <e0ne> krtaylor, yes, thanks 18:28:29 <krtaylor> e0ne, let's bring it up in the open discussion 18:28:34 <anteaya> more on this or moving on? 18:28:39 <krtaylor> e0ne, oh, ok, nm 18:28:56 <anteaya> okay moving on 18:29:03 <anteaya> #topic OpenStack Program items 18:29:15 <anteaya> #info Review Nova requirements progress and timeline https://wiki.openstack.org/wiki/HypervisorSupportMatrix/Requirements (jaypipes) 18:29:21 <anteaya> jaypipes: you're up 18:29:22 <jaypipes> heyo. 18:29:33 <anteaya> #link https://wiki.openstack.org/wiki/HypervisorSupportMatrix/Requirements 18:29:37 <anteaya> hello jaypipes :D 18:30:18 <krtaylor> jaypipes, thanks, was just looking for brief summary state and timeline, ect 18:30:28 <jaypipes> anteaya: not sure there's all that much to discuss. basically, dansmith put together the above link, and it was discussed at the nova mid-cycle meetup. nobody had any problems with the requirements as listed on the above wiki page. 18:30:38 <anteaya> jaypipes: great 18:30:45 <jaypipes> anteaya, krtaylor: no timeline AFAIK. 18:30:53 <anteaya> thanks for bringing it here so we know as well 18:31:03 <jaypipes> np 18:31:21 <anteaya> jaypipes: so there isn't much of a description on the page 18:31:32 <anteaya> can you share a bit of context for the travel weary? 18:32:03 <krtaylor> right, not much for when this would be a hypervisor minimum set of functionality 18:32:15 <krtaylor> I was wanting to discuss here as that is also tied to testing 18:32:49 <krtaylor> but, prob only interesting to those testing nova drivers 18:32:55 <jaypipes> I don't know that information, unfortunately. I think Mikal is the arbiter of that. 18:33:10 <anteaya> jaypipes: ah okay 18:33:25 <anteaya> anyone implimenting testing for nova drivers with questions? 18:33:41 <jaypipes> anteaya: I'm sorry. It's still something under active discussion what exactly the rigid requirements are for a virt driver staying in tree. 18:33:53 <anteaya> jaypipes: ah okay great 18:33:59 <anteaya> jaypipes: thanks for the early heads up 18:34:17 <anteaya> so if folks have a stake in this, be sure to participate in the discussion 18:34:33 <krtaylor> jaypipes, thanks 18:34:38 <anteaya> all the usual places, I presume? irc, ml, meetings, correct jaypipes? 18:35:03 <jaypipes> anteaya: ML, followed by IRC, yeah. 18:35:13 <anteaya> jaypipes: great thanks 18:35:19 <anteaya> any more here? 18:35:19 <jaypipes> anteaya: the "fair standards for all hypervisors" ML thread speciically 18:35:29 <anteaya> jaypipes: ah yes, of course 18:35:45 <anteaya> anyone with a quick link to the parent post of that thread for the logs? 18:35:53 * krtaylor looks 18:35:55 <jaypipes> one sec, will do. 18:36:12 <jaypipes> http://lists.openstack.org/pipermail/openstack-dev/2014-July/040421.html 18:36:22 <anteaya> #link http://lists.openstack.org/pipermail/openstack-dev/2014-July/040421.html 18:36:25 <anteaya> thanks jaypipes 18:36:29 <jaypipes> http://lists.openstack.org/pipermail/openstack-dev/2014-August/042284.html 18:36:38 <jaypipes> it spans both months/ 18:36:50 <anteaya> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/042284.html 18:37:00 <anteaya> jaypipes: yes, a chewy chat indeed 18:37:05 <jaypipes> yup. 18:37:11 <anteaya> okay any objection to moving to the next topic? 18:37:25 <krtaylor> nope 18:37:26 <anteaya> next topic it is 18:37:33 <anteaya> #topic Deadlines & Deprecations 18:38:18 <anteaya> #info Cinder update (jungleboyj) 18:38:28 <anteaya> jungleboyj: your floor 18:38:47 <jungleboyj> anteaya: Thank you. 18:39:15 <jungleboyj> Sorry, I forgot to hit save on the agenda page earlier, but it should be there now. 18:39:21 <anteaya> jungleboyj: it is 18:39:28 <jungleboyj> Ok, good. 18:39:34 <anteaya> fill in the blanks 18:40:00 <jungleboyj> So, as far as your dates are concerned, DuncanT is pinging people this week if they have not indicated some progress. 18:40:30 <jungleboyj> There will be a mailing list e-mail next week if still no response and then patches to remove the non-compliant drivers will beging. 18:41:16 <jungleboyj> People are making progress though. IBM has their CIs running, but not all of them are against the main gerrit stream riht now due to being unreliable. 18:41:26 <anteaya> great so Cinder driver folk, make sure DuncanT is aware of your progress even if you are not yet in full compliance, don't stay quiet 18:41:30 <jungleboyj> HP and EMC are pretty reliably post results. 18:41:33 * anteaya nods 18:41:38 <anteaya> good work 18:41:42 <anteaya> anything else here? 18:42:00 <jungleboyj> anteaya: +2 to not being quiet. 18:42:09 <jungleboyj> I can cover the rest in open discussion. 18:42:12 <anteaya> okay 18:42:17 <anteaya> moving on 18:42:30 <anteaya> #topic Highlighting a Program or Gerrit Account 18:42:41 <anteaya> #info Communicating CI status changes and updates, posting to the -dev ml becomes seen as spam, options? 18:42:57 <anteaya> so we currently have about 87 gerrit accounts 18:43:14 <anteaya> if every one of them posts to the ml for status outages and return of service 18:43:18 <anteaya> that doesn't work 18:43:24 <kevinbenton> anteaya: just a wiki page with the current status of all CI seems adequate 18:43:29 <dougwig> anteaya: sorry, on previous topic, neutron is doing a CI housecleaning as well: http://lists.openstack.org/pipermail/openstack-dev/2014-August/043218.html 18:43:29 <anteaya> how do we communicate status? 18:43:47 <anteaya> dougwig: ah yes, sorry I forgot to ask about that 18:43:57 <anteaya> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/043218.html 18:44:10 <anteaya> #info neutron ci housecleaning 18:44:19 <anteaya> kevinbenton: that is a good idea 18:44:25 <anteaya> any other options? 18:45:08 <krtaylor> anteaya, re: status topic, I had a discussion on nova about this last week, we decided that short-term we would report status on our third-party wiki page 18:45:11 <nuritv_> anteaya - the problem is when a system is down no point in doing recheck. will a developer look at the wiki on all time? 18:45:11 <emagana> anteaya: Hi There! about Neutron CI I have received tons of responses 18:45:56 <anteaya> okay lets' finish status reporting and then circle back to neutron ci updates 18:46:03 <emagana> anteaya: I am planing to update the Neutron Wiki with the current status. What is clear is that CI requirements needs to be more specific 18:46:12 <dougwig> anteaya: my reaction to CI downtime is: why is it posting to gerrit at all for scheduled downtime, and similarly, why aren't the missed jobs being queued later? why announce at all? 18:46:16 <anteaya> nuritv_: agreed, unless it is one easy to access source it won't be referenced 18:46:28 <anteaya> dougwig: good points 18:46:37 <krtaylor> re: status - this works for a quick fix becaus we already link to that page in comments 18:46:39 <nuritv_> anteaya: maybe a comment in the gerrit? 18:46:53 <anteaya> no, not adding comments to gerrit 18:46:57 <anteaya> hmmm 18:47:10 <anteaya> I wonder if we can add info to this page: https://wiki.openstack.org/wiki/Category:ThirdPartySystems 18:47:14 <anteaya> #link https://wiki.openstack.org/wiki/Category:ThirdPartySystems 18:47:23 <anteaya> any wiki page experts here? 18:47:35 <krtaylor> no, but that is the best user story for why there needs to be a ci dashboard 18:47:50 <anteaya> willing to experiment to see if we can have a table of ci statuses on that same page 18:48:03 <anteaya> krtaylor: hmmm, that might be interesting too 18:48:19 <krtaylor> or just color code the name table cell 18:48:28 <anteaya> krtaylor: oh I like that 18:48:32 <lyxus> anteaya, I though emagana what trying to do that (at leat on the Neutron side) 18:48:50 <anteaya> green for up, red for down, amber for issues read the ci page for details 18:48:55 <emagana> lyxus: Yes, that is my goal 18:48:57 <krtaylor> there are several threads for how to fix this issue 18:49:10 <anteaya> we need the threads to converge 18:49:11 <dougwig> here is emagana's wiki: https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers 18:49:11 <krtaylor> anteaya, exactly, stoplight 18:49:19 <anteaya> and for one person to champion the solution 18:49:28 <anteaya> I don't care what it is, we need a champion for it 18:49:36 <emagana> lyxus: Unfortunately, it is quite manual right now 18:49:56 <lyxus> emagana, we just need to discuss how we define what is a good status for a CI :) 18:49:58 <krtaylor> need automatic solution, else stale = useless 18:50:00 <anteaya> krtaylor: can you see if you can change your ci table colours as described above and report back 18:50:12 <anteaya> lyxus: not good status, just the ci is running 18:50:28 <anteaya> okay no solution this week, but we need to find one 18:50:34 <anteaya> we can't continue to spam the ml 18:50:46 <krtaylor> anteaya, I know I can change it, just how to do it programatically is the issue 18:50:54 <anteaya> and we need folks to have an outlet to communiciate system status since that is encouraged 18:50:54 <lyxus> anteaya, then define what is a "running" CI 18:51:01 <anteaya> krtaylor: do it manually for this week 18:51:07 <krtaylor> anteaya, will do 18:51:12 <anteaya> lyxus: at a future meeting 18:51:26 <anteaya> I just need omrim to stop spamming the ml 18:51:37 <anteaya> so thanks for attending the meeting omrim 18:51:49 <kevinbenton> we had previously discussed requiring builds of master at given intervals 18:52:05 <kevinbenton> #link https://review.openstack.org/#/c/105299/ 18:52:11 <anteaya> right but calibration is different from ormi's ml spam 18:52:23 <omrim> Anteaya: Thanks for your comment 18:52:43 <kevinbenton> anteaya: i was just suggesting for an automated “status” page 18:52:53 <anteaya> #link http://lists.openstack.org/pipermail/openstack-dev/2014-August/043382.html 18:53:01 <anteaya> this is the problem I am trying to fix today 18:53:12 <anteaya> kevinbenton: yes and I would love that 18:53:37 <anteaya> reducing email spam is today's goal, having an automated setup is still a goal 18:53:58 <kevinbenton> yeah, i think we should just have a wiki page for that. if someone doesn’t want to check the wiki, they probably aren’t going to search their inbox anyway 18:54:01 <anteaya> okay any objections to moving to neutron ci cleanup? 18:54:10 <anteaya> kevinbenton: fair enough 18:54:17 <smcginnis> Just brainstorming, but can we have an #openstack-cistatus IRC that CI systems send status messages to. Then dashboard can parse those messages to display current status? 18:54:37 <anteaya> and wikipage or colouring table entries is something we can do shor term 18:54:48 <anteaya> smcginnis: I like the idea 18:55:05 <anteaya> smcginnis: do you have any space for a proof of concept? 18:55:24 <smcginnis> anteaya: Unfortunately better at suggesting ideas than implementing. ;) 18:55:33 <anteaya> #topic Neutron CI housecleaning 18:55:35 <smcginnis> anteaya: Maybe once my corp firewall lets out IRC I can. 18:55:41 <anteaya> emagana: your floor 18:55:47 <anteaya> smcginnis: okay 18:56:36 * anteaya hopes emagana is still around 18:56:45 <anteaya> markmcclain: can you jump in here? 18:56:49 <emagana> sorry! 18:56:51 <emagana> I am here! 18:56:53 <anteaya> np 18:56:54 <anteaya> great 18:57:00 * anteaya listens 18:57:15 <emagana> Neutron CI requiremets are not very clear 18:57:41 <emagana> that is the big summary after my investigation 18:57:47 <anteaya> link again? 18:57:56 <emagana> we need to work on very specific CI requirements 18:58:09 <dougwig> can you clarify? i've been going off of this: https://wiki.openstack.org/wiki/NeutronThirdPartyTesting 18:58:27 <anteaya> #link https://wiki.openstack.org/wiki/NeutronThirdPartyTesting 18:58:32 <emagana> link: http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg32385.html 18:58:39 <anteaya> thanks emagana 18:58:54 <anteaya> #link http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg32385.html 18:59:00 <emagana> all the responses that I got were explaining why their CI did not test the commit 18:59:09 <anteaya> one minute left and I think we need to wrap up 18:59:21 <emagana> the bottomline is that requirements should be clear 18:59:26 <anteaya> neutron ci systems please continue on the #openstack-neutron channel 18:59:31 <kevinbenton> we also need to establish time to report back test 18:59:33 <emagana> I will work with the Neutron community to do that 18:59:44 <lyxus> and clarify the -1 18:59:51 <anteaya> emagana: can we get a neutron agenda item for next week's agenda so we ensure you have more time 18:59:59 <emagana> anteaya: I will 19:00:06 <anteaya> I agree this is an important discussion 19:00:09 <anteaya> and I support it 19:00:16 <anteaya> and we need to end for today 19:00:25 <anteaya> so let's contiue to discuss 19:00:31 <anteaya> thanks to everyone for a great meeting 19:00:43 <anteaya> items we didn't cover will roll over to next week 19:00:45 <anteaya> thanks 19:00:50 <anteaya> #endmeeting