16:59:29 #startmeeting Designate 16:59:30 Meeting started Wed Sep 2 16:59:29 2015 UTC and is due to finish in 60 minutes. The chair is Kiall. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:59:33 The meeting name has been set to 'designate' 16:59:44 Hey Folks - Who's about? 16:59:49 o/ 17:00:23 hi 17:00:58 mlavalle: hello! 17:01:03 timsim ? 17:01:06 jmcbride? 17:01:10 elarson: hey..... 17:01:17 Kiall: timsim might need to head out 17:01:24 federico3 ? ekarlso? 17:01:45 elarson: K :) 17:01:50 * elarson is trying to get the skinny on bug triage in his absence 17:02:00 lol - thanks :) 17:02:02 #topic Announcements 17:02:36 Libery-3 release will be cut about this time tomorrow. Anything that doesn't land before then will need to wait for RC1 - and possibly M, if it's too big a change. 17:03:00 Any other Announcements from folks? 17:03:27 Nope, moving on so. 17:03:27 #topic Action Items from last week 17:03:50 3 actions, all backports, all either not needed or done. 2 done = https://review.openstack.org/#/c/219769/ and https://review.openstack.org/#/c/219771/ 17:03:55 pls review+approve etc 17:04:12 #topic Bug Triage (timsim - recurring) 17:04:21 timsim's AFK - elarson .. figured it out yet? ;) 17:04:57 sorry, my launchpad skills are up to snuff it seems 17:05:10 Sure.. I'll do it so :) 17:05:22 First one has actually been around a while - 1471165 17:05:26 bug 1471165 17:05:27 thats private 17:05:30 Ah 17:05:33 o/ 17:05:34 Moving on so 17:05:42 bug 1487934 17:05:45 bug 1487934 in Designate "500 error returned in List Records in a Domain" [Undecided,New] https://launchpad.net/bugs/1487934 17:06:09 Anyone managed to reproduce this one? 17:06:41 nope 17:06:52 I suspect it's a real issue knowing the V1 RRSet code.. High / rc1? 17:07:07 yeah 17:07:26 bug 1490843 17:07:27 bug 1490843 in Designate "ERROR message after not sourced request" [Undecided,New] https://launchpad.net/bugs/1490843 17:07:47 I think we have a better error now, is this valid? 17:08:00 eh, not sure 17:08:09 (It's using RHEL packages rather than latest versions) 17:08:22 Anyone willing to take + triage it? 17:08:35 its not valid anymore 17:08:45 and should be on the client anway 17:09:02 yeah, looks like a client issue to me 17:09:11 designateclient➜ python-designateclient git:(master) ./bin/designate server-list 2015:09:02::18:09 17:09:14 Yea, there's a few of those in there. 17:09:17 ERROR: No endpoint was found: 17:09:26 its not great as a message 17:09:36 but are we OK with it? 17:09:37 Oh - SO it's not fixed? 17:09:48 no, i dont think iot is actually 17:09:58 move to client - and med 17:10:09 done 17:10:24 bug 1490861 17:10:26 bug 1490861 in python-designateclient "Designate record create help" [Undecided,New] https://launchpad.net/bugs/1490861 17:10:51 valid, move to client, med 17:10:56 or low actually 17:10:57 I believe that's not a bug - OS CLI's expect "designate help command" 17:11:02 rather than "designate command --help" 17:11:13 (It's how Cliff, the framework works..)( 17:11:23 we are ah, so they do 17:11:31 s/we are// 17:11:43 yeah, invalid 17:12:25 Done 17:12:33 similar one again - bug 1490910 17:12:34 bug 1490910 in Designate "record deletion syntax is not clear- bad help" [Undecided,New] https://launchpad.net/bugs/1490910 17:12:42 its valid ish 17:12:58 but low. 17:13:03 and in the clientr 17:13:48 done 17:14:04 bug 1491248 17:14:05 bug 1491248 in Designate "Record is not deleted after terminating a VM+duplicate records " [Undecided,New] https://launchpad.net/bugs/1491248 17:14:12 i am pretty sure this was a missconfig 17:14:25 he had no pool_nameserver set up 17:14:37 Anyone willing to triage and verify ^? 17:14:48 so it was waiting for the domain to expire before PDNS would AXFR 17:15:13 so in the V1 api it was still showing 17:15:18 Will I assing to you for verification? ;) 17:15:20 assign* 17:15:25 as we dont have a "status" col in the V1 17:15:27 sure 17:15:33 done 17:15:33 Kiall: nice verb! 17:15:44 mlavalle: :D 17:15:48 last one - bug 1491348 17:15:50 bug 1491348 in Designate "sql DB is not updated after record creation " [Undecided,New] https://launchpad.net/bugs/1491348 17:16:02 same 17:16:16 Assigned to you again so ;) 17:16:44 That's all the new bugs - moving on so. 17:16:49 #topic Stable Backport Triage (kiall - recurring) 17:17:22 cmon paste.o.o -_- 17:17:26 http://paste.openstack.org/show/441825/ 17:17:28 #link http://paste.openstack.org/show/441825/ 17:18:00 As usual, take a few and nominate anything we need to backport. 17:18:08 2e30041 Merge "Remove unused dependency: discover" 17:18:10 none IMHO 17:18:45 Probably right to not change the deps, even if it's unused 17:18:53 Anyone have any others? 17:19:29 (what's the criterion for backporting things?) 17:19:44 federico3: No features, just low-risk bug fixes 17:20:13 Other than that - it's open for us to argue yay or nay case by case ;) 17:20:44 Okay.. Moving on since we have no other nominations :) 17:20:48 #topic Designate/Neutron Integration Update (mlavalle - recurring) 17:20:58 mlavalle: I see we have some good news? :) 17:21:14 Kiall: yeah, we merged https://review.openstack.org/#/c/200952/ 17:21:32 this is the the internal dns resolution side 17:21:40 Woo :) 1/3rd of the patches landed! (with 3/4 of the code from the looks of it) 17:22:08 I am making good progress with https://review.openstack.org/#/c/212213/ 17:22:15 this is the external side 17:22:31 right now I am being able to load the designate client 17:22:38 Yea, that's excellent! I have it checked out locally to experiment with :) 17:22:43 and use it to create recordsets 17:23:05 I am also deleting 17:23:23 with this in place, now I am working the floating ip extension and plugin 17:23:37 to add the code to call the designate driver 17:23:52 Cool 17:24:02 I expect to do rapid rpogress here, since it is similar to what I have already done with the other patchset 17:24:09 Considering Neutron ships L3 in the next day or so, is this part likely to get pushed to M? 17:24:24 yeah, i will push it to M1 17:24:40 Aww.. Oh well :( 17:25:09 I don't have functioning code yet, so I am hesitant to request FFE 17:25:40 but it will be done by the time of the Tokyo presentation, so we will be able to do a full demo 17:25:43 Yea, FFE without code is really unlikley! 17:26:03 Okay - Anything else? Any Q's for mlavalle from anyone else? 17:26:13 not know, that's all this week 17:26:46 Okay - Thanks mlavalle :)( 17:27:07 #topic Liberty 3 Release 17:27:15 #link https://launchpad.net/designate/+milestone/liberty-3 17:27:37 Tis been a quiet L3 (or, we've not been tracking the bugs and BPs properly.. which is more likely ;)) 17:27:52 Anything outstanding we should try and land that's not on that page? 17:29:07 Nobody? 17:29:25 i dont think so 17:29:37 need to dig through commits though 17:29:39 yeah, I can't think of anything 17:30:08 K - There's a few patches for adding more tests from pglass and sonu pending a +A 17:30:16 May as well +A them, if people have the time to review. 17:30:54 Okay, let's move on so :) 17:30:56 #topic Tokyo Summit Space 17:31:10 Thierry is looking for details.. Summit space this year is tight. 17:31:21 Venue is smaller and More Projects in the Teant 17:31:23 Tent* 17:31:52 I was thinking - 1fishbowl, 5workrooms, 1 half day contributers meet? 17:32:01 (Thierry was thinking the same, but 4 workroom) 17:32:16 yeah, that sounds ok 17:32:24 i think there will be less people in anycase 17:32:26 Considering it's Tokyo - and so few us us are going to make it out - that seems reaosnable! 17:32:45 4 or 5 would be fine 17:32:53 +1 with the caveat I have no clue what a fishbowl vs. a workroom actually is ;) 17:33:16 workroom is generally like a conf room, or a small room for 10 or so people.. 17:33:39 fishbowl is a bigger room, like a small "stage" kinda setup for wider feedback etc from folks 17:34:01 Okay - I'll pass that on to ttx :) 17:34:14 Kiall: thanks for descriptions 17:34:45 Okay.. Lets move on so .. Starving and need some dinner ;) 17:34:48 #topic Open Discussion 17:34:54 Any other topics from anyone else? 17:35:11 nothing from me anyway :) 17:35:25 Kiall: might have found a bug in the tcp socket handling in dnsutils where the socket doesn't close 17:35:30 I'm looking into it now 17:35:39 we found it in the agent when running more than one worker process 17:36:02 Is it a leak, or a leftover socket after shutdown? 17:36:24 for example, dig would run and get an answer, but the kernel wouldn't change the status back to LISTEN 17:37:08 timsim mentioned the same code is also in mdns so if anyone runs mdns with more than one process listening on the same address, you could probably try to repoduce it 17:37:16 Humm, that could be related to the SO_REUSEADDR/SO_REUSEPORT on TCP+UDP socks, or SO_KEEPALIVE on TCP's 17:37:26 yeah, that is what I'm thinking 17:37:50 (I have to admit, I have no clue why we have SO_KEEPALIVE on a TCP DNS sock) 17:38:10 Okay - Well, if you figure anything out let us know :) 17:38:30 will do! 17:38:38 Also - As near as I can tell, it's not causing any harm - right? 17:38:57 we have to limit the agent to using one process atm 17:39:04 that is where it came up 17:39:27 Humm, okay.. File a bug with any detail you have and we can try repduce :) 17:39:36 yeah, I'm researching it now 17:40:32 Okay, anything else before we call it a day? 17:42:22 I'm talking silence as a no! 17:42:29 +1 17:42:35 OH.. 1 last thing 17:42:53 Thanks RackSpace for hosting the mid-cycle - excellent hosts as alweays :) 17:42:55 always* 17:43:11 we did this last week, whil;e you were asleep :) 17:43:15 * mugsie ducks 17:43:21 as the official rackspace rep here, I'll take full credit :P 17:43:24 ;) 17:43:28 Okay - Cya! :) 17:43:31 #endmeeting