21:02:11 <mestery> #startmeeting networking 21:02:12 <openstack> Meeting started Mon Jun 30 21:02:11 2014 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:02:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:02:15 <openstack> The meeting name has been set to 'networking' 21:02:23 <mestery> #link https://wiki.openstack.org/wiki/Network/Meetings Agenda 21:02:33 <mestery> #topic Announcements 21:02:42 <mestery> The mid-cycle sprint is next week: https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting 21:02:52 <mestery> We'll cover this in detail in a few minutes, but wanted to note this here. 21:03:01 <mestery> Any other announcements the team should be aware of? 21:03:27 <mestery> #topic Mid-Cycle Sprint 21:03:39 <mestery> I wanted to ensure we spent some time on this early in this meeting. 21:03:53 <mestery> #link https://etherpad.openstack.org/p/lOiqsLmizl Sprint Work Items 21:04:01 <mestery> I've started that etherpad to collect work items for next week. 21:04:41 <mestery> I'm hoping those who arrive in beautiful Minnesota next week can all hit the ground running Wednesday morning. 21:04:42 <markmcclain> nice 21:04:53 <mestery> 3 intense days of closing nova-network gaps. :) 21:05:06 <mlavalle> mestery: +1 21:05:25 <mestery> We'll go from 9AM-6PM or so, though I will likely be in the office a bit before that if people want to come by earlier. 21:05:42 <sc68cal> tough boss! ;) 21:05:43 <salv-orlando> I hope none of the nationalities there in Minnesota will still be represented at the world cup 21:05:45 <mestery> One thing to note: If you are planning on attending, please send unicast me your [name, email, company] so I can get guest wifi setup for you 21:05:51 <mestery> sc68cal: :P 21:06:05 <mestery> salv-orlando: Ha! 21:06:08 <salv-orlando> So go Belgium! 21:06:21 <emagana> salv-orlando: Mexico is out :-( 21:06:22 <mlavalle> salv-orlando: we were kicked out by the Dutch yesterday, so i'll be ok 21:06:46 <mestery> Any other logistical questions I can answer from anyone about next week? 21:06:58 <banix> very unfortunate for Mexico! 21:07:17 <regXboi> mestery: *how* early will you be in the office? 21:07:28 <mestery> regXboi: How early is early for you? Now I'm afraid. :) 21:07:34 * markmcclain notes that neither the England or Italy are left for salv-orlando 21:07:42 <banix> mestery: I suppose the unicast of info will get us also in the building? 21:07:45 <regXboi> mestery: I'll probably be able to wander in about 7 am 21:07:54 <salv-orlando> I never cared for England. Italy is instead on a sabbatical 21:08:08 <salv-orlando> Italy literally got eaten by Uruguay 21:08:16 <regXboi> so yes, you should be afraid :) 21:08:18 <mestery> banix: That's a good point. You can get into the building past 8AM, take the elevator to the 4th floor and checkin with the lobby ambassador 21:08:20 <mlavalle> salv-orlando: oh that explains their poor performance 21:08:36 <mestery> regXboi: I don't know if I'll be there by 7AM. 8AM likely, though :) 21:08:38 <banix> mestery: thanks 21:08:54 <regXboi> mestery: no worries ... 21:09:06 <mestery> regXboi: I'll see what I can do :) 21:09:23 <pcm__> I'll likely come in early, I'm an early riser. 21:09:48 <mestery> Looking forward to working F2F with folks next week to close nova-network parity gaps! 21:09:50 <Sukhdev> mestery: the session kicks off at 9am though, right? 21:09:58 <mestery> Sukhdev: Correct. :) 21:10:10 * mestery notes Sukhdev is from PDT timezone :P 21:10:20 <Sukhdev> mestery: I will be on time :-) 21:10:21 <banix> Sukhdev: I see you are worried. You should be when 11m PST is early for you :) 21:10:31 <markmcclain> mestery: same here… am excited to close these gaps 21:10:47 <Sukhdev> banix: :-) 21:10:47 <mestery> OK, unless there's anything else, we'll proceed with the rest of hte meeting. 21:11:13 <mestery> #topic Bugs 21:11:20 <enikanorov__> hi 21:11:20 <mestery> enikanorov__: Hi! 21:11:38 <enikanorov__> nothing much new this wee. i'm trying to track gate failures 21:11:47 <mestery> Anything new on that front (gate failures)? 21:11:57 <enikanorov__> so far we have a list of rarely hit bugs related to lock wait timeouts 21:12:27 <enikanorov__> i hope most of the cases should be fixed by the patch 21:12:36 <enikanorov__> let me find the link 21:12:41 <mestery> Thanks enikanorov__ 21:12:45 <salv-orlando> enikanorov_: I think you’seen this already by anyway,… https://review.openstack.org/#/c/103540 21:12:57 <salv-orlando> that’s ihrachyshka take on the lock wait timeout problem 21:13:10 <enikanorov__> salv-orlando: yes, i've seen this, it seems as an overkill to me... 21:13:35 <enikanorov__> Elena Ezhova and me were analyzing different cases of timeouts 21:13:36 <salv-orlando> ok - I just wanted to raise awareness. comments are better placed on gerrit. 21:13:48 <enikanorov__> so far we've seen that they are still connected to port deletion 21:14:13 <enikanorov__> so the patch ihrachyshks has on review should fix most of them 21:14:15 <salv-orlando> only thing I want to avoid is to have 10 different solutions for the same problem on gerrit and none on git log ;) 21:14:44 <enikanorov__> #link https://review.openstack.org/#/c/100934/ 21:14:59 <enikanorov__> salv-orlando: sure 21:15:03 <enikanorov__> another question i have on this 21:15:08 <enikanorov__> is the e-r queries 21:15:36 <enikanorov__> i've pushed a few to gerrit, but infra folks are not happy to merge queries that give 2-4 hits per week 21:15:46 <enikanorov__> but when summed, those timeouts are several a day 21:15:51 <enikanorov__> what would you recommend? 21:16:30 <mestery> enikanorov__: I wonder if they don't want to explode e-r queries for bugs with such small hits. 21:17:17 <salv-orlando> so e-r queries are weighted for severity on gate hits 21:17:21 <mestery> enikanorov__: I would say lets bring this up in #openstack-infra and see what we can do. 21:17:22 <enikanorov__> then it would not be convenient to track hits of particular cases 21:17:31 <enikanorov__> and those cases are ~10 different ones 21:17:49 <salv-orlando> mestery: just like with beetlejuice you can try and say Joe Gordon’s name 3 times 21:17:53 <salv-orlando> he might appear here 21:18:00 <mestery> salv-orlando: :P 21:18:04 <enikanorov__> ok. the problem is that i don't know the policies about e-r queries, so i don't quite understand their reasoning 21:18:04 * markmcclain is starting descent…will stay rejoin when on ground 21:18:22 <mestery> markmcclain: Enjoy SLC for the short while you're there ;) 21:18:33 <salv-orlando> enikanorov_: usually they’re filed to bring down uncategorized failures to 0 21:18:55 <salv-orlando> so that’s why infra focuses on failures hitting the gate 21:19:20 <enikanorov__> anopther concern was that some failures happening on non-voting neutron-full job 21:19:26 <salv-orlando> but in the past I brought up the argument in openstack-infra or in gerrit and had them merged 21:19:44 <salv-orlando> enikanorov_: yeah lock wait timeout failures are more frequent there. 21:19:51 <mestery> salv-orlando enikanorov__: Is the full job not voting yet? The plan is to turn that on and make it voting soon right? 21:20:10 <salv-orlando> mestery: yes - there is an update on that on the mailing list 21:20:34 <enikanorov__> anyway, i'll followup with infra folks on their channel 21:20:36 <mestery> salv-orlando: Thanks! 21:21:22 <mestery> Anything else bugs related enikanorov__? 21:21:30 <enikanorov__> no 21:21:36 <mestery> OK, thanks enikanorov__! 21:21:39 <mestery> #topic Docs 21:21:41 <mestery> emagana: Howdy! 21:21:49 <emagana> mestery: Hi There! 21:22:08 <emagana> Wiki is updated with the High* priority bugs 21:22:18 <emagana> (only one open) :-) 21:22:38 <emagana> I have seen developers adding DocImpact.. and I would like to thank all for that!! 21:23:27 <emagana> Just a nice extra reminder! If you push a commit with "DocImpact" please, take a look to the Doc Bug and try to fix it as well :P 21:23:54 <mestery> emagana: One of the gap areas is around documentation of hte open source options, I'm hopeful you can assist those who want to narrow that gap next week in MN! 21:24:07 <mestery> emagana: You may need to boot strap some new docs contributors :) 21:24:14 <emagana> mestery: I will do that! 21:24:23 <mestery> emagana: Awesome, thanks! 21:24:24 * regXboi marvels at mestery's deft delegation 21:24:29 <mestery> regXboi: :P 21:24:36 <mestery> emagana: Anything else this week? 21:24:42 <emagana> mestery: good to know, I will prepare some overview of the Docs for newers! 21:24:54 <mestery> emagana: That would be even better! /cc regXboi 21:25:07 <regXboi> emagana: :) I'm looking for that info 21:25:12 <emagana> mestery: Yes, I dont like fake penalties!!!!!! 21:25:18 <regXboi> because I keep banging my head on doc issues 21:25:37 <mestery> emagana: Maybe we can even look at documentation options for DVR next week since carl_baldwin will be there too. But maybe it's too early, lets see. 21:25:58 <carl_baldwin> mestery: not a bad idea 21:26:03 <emagana> mestery: the sooner the better... I will discuss that with carl_baldwin 21:26:08 * mestery is bringing everyone together. :) 21:26:27 <mestery> Thanks for the updates emagana! 21:26:39 <mestery> #topic Tempest 21:26:42 <mestery> mlavalle: Hi there! 21:26:49 <mlavalle> hi: we are pretty much complete with the api coverage that we planned early this year. I have one test script for VPNaaS and zzelle_ for the provider network extension 21:26:51 <regXboi> no 21:26:59 <regXboi> oops... sorry - wrong window 21:27:06 <mestery> mlavalle: Nice! 21:27:33 <mlavalle> I will update mark_mccclain's etherpad for nova pairty with all the tests pmerged 21:28:39 <mestery> mlavalle: For next week, we may have some new tempest contributors, perhaps Wednesday you could spend some time boot strapping a few. 21:28:41 <mlavalle> I want to devote the next few minutes, though, to gather some feedback for the sprint next week, especially from markmcclain and salv-orlando: what do you see is needed next week for nova-parity and the full neutron job? 21:28:56 <mlavalle> in terms of tempest^^^ 21:29:06 <salv-orlando> mlavalle: I think for enabling the full neutron job we don’t need anything in tempest. 21:29:12 <mlavalle> mestery: yes, I will do that 21:29:24 <salv-orlando> The issues have been identified, bugs filed and root caused. 21:29:29 <salv-orlando> Patches wil follow up shortly. 21:29:49 <salv-orlando> So, I guess I will do my best to get the full job switched to voting this week 21:30:02 <salv-orlando> so that you guys next week can deal with inevitable spike in failure rate 21:30:04 <mlavalle> salv-orlando: any tests that should be redesigned? I think you mentioned something in the tempest irc meeting to that effect 21:30:07 <mestery> salv-orlando: Nice! 21:30:09 <mestery> salv-orlando: :( 21:30:37 <salv-orlando> mlavalle: the tempest design issue pertained the lbaas scenario test. Elena Ehzova already addressed that. 21:30:53 <mlavalle> salv-orlando: cool 21:31:00 <salv-orlando> mestery: problems? 21:31:16 <mlavalle> how about markmcclain? 21:31:19 <mestery> salv-orlando: No, just #sadpanda for the inevitable fallout 21:31:23 <salv-orlando> ah ok! 21:31:25 <mestery> mlavalle: markmcclain is landing right now :) 21:31:31 <mestery> mlavalle: I'll circle with him later :) 21:31:41 <mlavalle> mestery: ok, i'll follow up directly with him 21:31:47 <salv-orlando> markmcclain loves neutron meetings at 35k feet 21:31:47 <mestery> mlavalle: Thanks! 21:32:03 <mlavalle> any other input from the team as far as stuff that needs to be covered next week? 21:32:07 <mestery> salv-orlando: I don't think he takes neutron meetings from anyewher else :) 21:33:06 <mlavalle> if there is not more input, I am done. I will work the etherpad over this week 21:33:11 <mestery> Thanks mlavalle! 21:33:23 <mestery> #topic L3 21:33:26 <mestery> carl_baldwin: Hi there! 21:33:28 <carl_baldwin> hi 21:33:39 <carl_baldwin> Frist, DVR. We’ve seen a lot of great progress. 21:34:03 <carl_baldwin> We had a big push to clean up the test failures. We were 4 UT failures away this morning on only one patch. 21:34:17 <carl_baldwin> We’ve been addressing feedback about as quickly as it can come in. 21:34:35 <carl_baldwin> armax posted a demo video that was interesting. 21:34:46 <mestery> carl_baldwin: Sweet! 21:34:47 <mestery> Link? 21:34:57 <nati_uen_> awesome 21:34:58 * carl_baldwin is looking. armax? 21:35:14 <armax> hy 21:35:15 <armax> hi 21:35:35 <armax> I put the link to the video here: https://wiki.openstack.org/wiki/Neutron/DVR/HowTo 21:35:47 <mestery> #link https://wiki.openstack.org/wiki/Neutron/DVR/HowTo 21:35:51 <mestery> Thanks armax! 21:35:53 <armax> Not sure why, but it looks like Chrome does not render the video tag very well 21:36:12 <carl_baldwin> armax: mestery: that must be why I couldn’t see it. 21:36:19 <carl_baldwin> Anyway, we’ll get that taken care of. 21:36:30 <armax> I was going to send a mail to ML later to broaden the announcement 21:36:43 <banix> looks fine in Safari 21:36:47 <Sukhdev> armax: please do 21:36:54 <salv-orlando> armax: ml post is still good. I will forget about that link in 5 minutes or less 21:36:54 <carl_baldwin> I’ve also put up a temporary branch that merges all of the gerrit patch sets in to one commit a few times a day. 21:37:06 <amotoki> #link https://www.youtube.com/watch?v=p4BwAjLHd0M 21:37:10 <carl_baldwin> #link https://github.com/ecbaldwin/neutron-dvr.git 21:37:10 <gus> "The page at 'https://wiki.openstack.org/wiki/Neutron/DVR/HowTo' was loaded over HTTPS, but ran insecure content from 'http://www.youtube.com/embed/p4BwAjLHd0M?showsearch=0&modestbranding=1': this content should also be loaded over HTTPS." 21:37:21 <carl_baldwin> ^ This is just if you want a quick way to get all of the code together. 21:37:47 <mestery> carl_baldwin: Thanks for that, for people who want to test it out, that will be helpful! 21:37:59 <mestery> carl_baldwin: Is testing something which people can help with next week around DVR? 21:38:09 <carl_baldwin> Yes, it has helped me out as well. I thought I’d share. 21:38:54 <carl_baldwin> mestery: I think so. I’m working on it myself with a few others. If others are interested in testing please let me know. 21:39:10 <salv-orlando> mestery: ideally a soon as we merge that we might add a non-voting job that runs neutron with DVR 21:39:16 <mestery> carl_baldwin: If there are things people can assist the DVR team with next week, we can add them to the etherpad. 21:39:33 <mestery> salv-orlando: +1 to that, though that would require multi-node tempest testing to be useful, right? 21:39:36 <carl_baldwin> mestery: I’ll have a look. 21:39:41 <mestery> carl_baldwin: Thanks! 21:39:41 <enikanorov__> carl_baldwin: i'm interested in testing 21:39:56 <carl_baldwin> salv-orlando: Yes, we’re working on that. 21:40:00 <salv-orlando> mestery: yeah but even without we’ll add coverage for new paths 21:40:01 <carl_baldwin> enikanorov__: noted. Thanks. 21:40:24 <mestery> salv-orlando: True, dat. 21:40:52 <carl_baldwin> The rest is up to date on the meeting page. There were a couple of new High bugs but we’re on them. 21:41:05 <mestery> carl_baldwin: Awesome, thanks! 21:41:14 <carl_baldwin> yw 21:41:17 <carl_baldwin> That’s it. 21:41:32 <mestery> #topic Advanced Services 21:41:37 <mestery> SumitNaiksatam: Hi there! 21:41:42 <SumitNaiksatam> mestery: hi 21:41:57 <SumitNaiksatam> we had quite an interesting discussion in a special session on flavors on Friday :-) 21:42:18 <mestery> SumitNaiksatam: Indeed ;) 21:42:29 <SumitNaiksatam> we thought we were beginning to reach a conclusion at least on the user facing API, but then we ran out of time 21:42:53 <SumitNaiksatam> so for now, the plan is that markmcclain and enikanorov_ or going to reconcile on the items that we agreed upong 21:42:56 <SumitNaiksatam> *upon 21:43:07 <enikanorov__> right 21:43:27 <enikanorov__> i've left corresponding comment on markmcclain's spec 21:43:28 <SumitNaiksatam> we might decide to leave features like the “tags” defined in enikanorov_’s proposal as a future enhancement 21:43:31 <mestery> I think we're close, though I'm hopeful we can close this before the end of hte week. 21:43:33 <SumitNaiksatam> enikanorov_: great, thanks 21:43:43 <SumitNaiksatam> mestery: +100! 21:43:53 <markmcclain> I'll reply to those on next flight 21:43:58 <mestery> Flavors is important for all the services, so closing on this will be good. 21:44:04 <SumitNaiksatam> markmcclain: great! :-) 21:44:05 <mestery> markmcclain: Awesome! (And welcome back :) 21:44:18 <enikanorov__> markmcclain: is a pilot, isn't he? 21:44:28 <mestery> enikanorov__: :) 21:44:36 <SumitNaiksatam> other than that, we want to focus on the service insertion and chaining blueprint specs 21:44:51 <SumitNaiksatam> to the extent that we can without distracting people from their focus 21:45:07 <SumitNaiksatam> so expect this wednesday to have more of a discussion on the service insertion spec 21:45:19 <regXboi> SumitNaiksatam: :) 21:45:25 <SumitNaiksatam> regXboi: :-) 21:45:41 <SumitNaiksatam> mestery: thats the short summary 21:45:54 <mestery> SumitNaiksatam: Thanks for the summary! 21:46:10 <regXboi> SumitNaiksatam: I plan on reading through and adding comments on the other GBP patchsets... just trying to find blocks of time 21:46:18 <mestery> #topic IPv6 21:46:20 <mestery> sc68cal: Howdy! 21:46:22 <sc68cal> Hello! 21:46:28 <SumitNaiksatam> regXboi: thats a separate agenda topic, but thanks :-) 21:46:38 <sc68cal> So the two big ticket items are the IPv6 radvd spec and review 21:46:43 <sc68cal> #link https://review.openstack.org/#/c/101306/ IPv6 radvd spec 21:46:43 <sc68cal> #link https://review.openstack.org/102648 IPv6 radvd review 21:47:00 <SumitNaiksatam> mestery: thanks a bunch for chairing the flavors meeting! 21:47:07 <mestery> SumitNaiksatam: yw 21:47:21 <sc68cal> We also got tempest API tests for ipv6 attributes merged https://review.openstack.org/#/c/93502 21:47:26 <mestery> sc68cal: I saw those, that's great they are both there, given the movement to radvd 21:47:31 <mestery> sc68cal: woot! 21:47:46 <sc68cal> I also rebased and fixed conflicts on the python-neutronclient side for the ipv6 attributes 21:48:06 <sc68cal> #link https://review.openstack.org/#/c/75871/ python-neutronclient v6 support 21:48:17 <mlavalle> sc68cal: thanks! 21:48:18 <sc68cal> So, eyeballs and reviews appreciate 21:48:20 <mestery> sc68cal: You've been busy :) 21:48:42 <sc68cal> also check out the multi-prefix review https://blueprints.launchpad.net/neutron/+spec/multiple-ipv6-prefixes 21:48:54 <sc68cal> We'd appreciate some eyeballs on that, and feedback 21:49:07 <sc68cal> That's it for me 21:49:27 <mestery> sc68cal: Seems like IPv6 is making good headway here, which is good! 21:49:37 <mestery> #topic ML2 21:49:40 <mestery> Sukhdev: Hi! 21:49:47 <Sukhdev> mestery: Hi 21:49:54 <Sukhdev> Got few items to report 21:50:20 <Sukhdev> Team has been busy reviewing specs - some of them are ready to go and require core approvals 21:50:41 <Sukhdev> https://review.openstack.org/#/c/88101/ 21:50:45 <Sukhdev> https://review.openstack.org/#/c/91811/ 21:50:56 <Sukhdev> https://review.openstack.org/#/c/89728/ 21:51:10 <mestery> Sukhdev: Thanks for pre-reviewing those and noting their readiness for core reviews! 21:51:19 <Sukhdev> mestery: thanks for approving them - need other cores to 21:51:30 <Sukhdev> review as well 21:51:41 <emagana> I will help Sukhdev 21:51:50 <Sukhdev> emagana: tahnks 21:51:55 <mestery> emagana: awesome! 21:52:13 <Sukhdev> Another thing to report is that some of the team members met Friday to discuss ML2 Sync 21:52:40 <Sukhdev> We are beginging to plan the activities around ML2 Sync to solve some of the issues 21:52:57 <Sukhdev> https://bugs.launchpad.net/neutron/+bug/1193861 This is short term fix 21:52:59 <uvirtbot> Launchpad bug 1193861 in neutron "ML2 plugin needs to override bulk operations" [Medium,In progress] 21:53:13 <Sukhdev> but, we are looking to solve it with ML2 - 21:53:35 <Sukhdev> will work on the specs and BPs with the team members - so look out for that 21:53:50 <Sukhdev> That is all I have to report for now 21:53:53 <amotoki> Sukhdev: perhaps i am reviewing all three above. will look later today but i have some concern on wording. 21:53:55 <mestery> Sukhdev: Thanks for the updates! 21:53:57 <Sukhdev> unless there are questions 21:54:06 <Sukhdev> amotoki: thanks 21:54:17 <mestery> amotoki: Awesome and thanks! 21:54:30 <mestery> #topic Group Based Policy 21:54:33 <mestery> SumitNaiksatam: Howdy again! 21:54:44 <SumitNaiksatam> mestery: hi again 21:54:49 <SumitNaiksatam> short update 21:55:00 <SumitNaiksatam> we have lots of patches in review now, the model series is almost complete 21:55:21 <SumitNaiksatam> and the driver series is almost there (rkukura would be posting a patch sometime later today) 21:55:39 <regXboi> and now I'll say what I said before.... I owe you reviews - just need to find a block of uninterrupted time (who knows, maybe friday morning) 21:55:40 <SumitNaiksatam> with that one should be able to test a subset of the resources all the way to the data path 21:55:56 <SumitNaiksatam> regXboi: thanks, and appreciate your comments earlier 21:56:06 <SumitNaiksatam> thanks in general to all the other reviewers as well 21:56:13 <SumitNaiksatam> mestery: so good progress over all 21:56:25 <mestery> SumitNaiksatam: Excellent! 21:56:31 <SumitNaiksatam> CLI patch is also ready 21:56:47 <SumitNaiksatam> mestery: thanks for the time 21:56:52 <mestery> SumitNaiksatam: thank you for the updates! 21:56:56 <mestery> #topic Open Discussion 21:57:00 <banix> conflicting views on #link https://review.openstack.org/#/c/93866/ Small issue and patchset. Shouldn’t require too much of your time 21:57:35 <banix> https://review.openstack.org/#/c/93866/ 21:57:44 <mestery> #link https://review.openstack.org/#/c/93866/ 21:57:48 <mestery> banix: ^^^ 21:58:19 <banix> mestery: thx. yeah the first thing didn’t come out right for some reasons. 21:58:27 <mestery> banix: No worries :) 21:58:30 <mestery> OK, thanks everyone! 21:58:36 <pcm__> Need help on how to get oslo.messaging 1.4.0.0a2 in global rewuirements https://review.openstack.org/#/c/103536/ 21:58:38 <amotoki> it is a discussion on positional argument of internal class. we have similar discussion several times so far. 21:58:39 <mestery> Look forward to seeing some of you next week in Minnesota! 21:58:41 <yamamoto_> is 3rd party ci expected to test and vote stable branches? 21:58:49 <mestery> pcm__: See reply by markmc on the ML to that one. :) 21:58:56 <pcm__> ok 21:59:09 <mestery> yamamoto_: If your driver is upstream in a stable branch, yes. I'll clarify the wiki page for that. 21:59:22 <markmcclain> amotoki: I know implementations based on that class 21:59:24 <yamamoto_> ok, thank you 22:00:11 <mestery> OK, thanks everyone! 22:00:17 <mestery> Catch you all on the ML and IRC! 22:00:18 <mestery> #endmeeting