16:59:23 #startmeeting Designate 16:59:23 Meeting started Wed Feb 3 16:59:23 2016 UTC and is due to finish in 60 minutes. The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:59:27 The meeting name has been set to 'designate' 16:59:31 #topic Roll Call 16:59:35 o/ 16:59:39 o/ 16:59:40 o/ 16:59:45 o/ 17:00:16 federico3: ekarlso Kiall courtesy ping 17:01:14 #topic Action Items from last week 17:01:19 only one out standing 17:01:22 mugsie arrange sync re workshop 17:01:24 o/ 17:01:28 #action mugsie arrange sync re workshop 17:01:52 #topic Bug Triage (timsim - recurring) 17:02:11 Nothing new? 17:02:13 Really? 17:02:22 WE HAVE ACHIEVED STABILITY 17:02:40 wow! 17:02:41 \o/ 17:03:18 #topic Backports 17:03:26 #link http://paste.openstack.org/show/485874/ 17:03:38 so, please review and nominate patches 17:03:39 o/ 17:03:44 (There are no new bugs) 17:04:13 fe3f7df Fix wildcard NS record 17:04:27 thats all I can see 17:04:36 anyone else see anything that should be back ported 17:04:38 ? 17:04:57 c3dec4e Merge "Add docs for PATCH and DELETE call of Zone transfer request" 17:05:08 yeah 17:05:10 caa9cc6 Merge "Add validation for MX, TXT, and SSHFP records" 17:05:13 as well 17:05:16 lol thanks for catching up irc. I'm back now 17:05:26 nice 17:05:35 #useARealIRCClient 17:05:40 :P 17:05:43 #useslack 17:05:53 * timsim is kidding, don't open that can of worms 17:06:10 OK, anyone want to do these backports? 17:06:30 dont all jump at once 17:06:31 :D 17:06:58 <-- 17:07:08 #action federico3 to backport caa9cc6 c3dec4e fe3f7df 17:07:28 #topic https://review.openstack.org/#/c/247588/ 17:07:32 #link 17:07:36 #link https://review.openstack.org/#/c/247588/ 17:08:03 basically - me and federico3 wanted to see if there is anything else we need from this 17:08:15 or if there is an alternate direction 17:08:32 I'm not a fan. 17:08:34 if not - we should test the hell out of it before merging, as it could be risky 17:08:41 i got that from the comment :) 17:09:06 timsim: ...because it will require more work in future to extend it to other use cases? 17:09:19 or you want to propose a different implementation? 17:09:29 I think, as heavy handed as it is, it's not really solving the problems that it could be. 17:10:16 I think I could propose an alternate implementation, but definitely not in the next 2-5 minutes 17:10:23 hint: worker model 17:10:38 timsim: worker model could cover some of it 17:10:45 you can do anything with worker model (also zombo.com) 17:10:53 but not a global ratelimit 17:11:10 Some intelligent caching could get you a global rate limit 17:12:17 true 17:12:29 Rate limiting notifies basically solves that problem. 17:12:47 but this as a shorter term fix for the NS problem - should we merge this 17:12:47 Rate limit + queue 17:13:14 the worker model is ... unlikely to merge pre M 17:13:21 I think it's too much technical debt for something we'll "fix later" ;) 17:14:01 + performance overhead 17:14:05 But that's just me 17:14:14 certainly the worker model would require some major rework of this code 17:14:33 You basically wouldn't need it. 17:14:45 You'd probably solve the problem a different way. 17:14:47 yet, afaict we are talking about different timelines 17:14:59 yep 17:15:30 my issue is we may release something that currently causes all zones to go to pending 17:15:55 We already have, haven't we? 17:16:05 and when a periodic timer hits will flood the Downstream servers 17:16:18 we have, and I would like to avoid doing it again :) 17:16:48 what can we do in the short term to alivate this without causing issues when we come to the worker model 17:17:04 Document that you can shoot yourself in the foot if you create a bunch of resources and than change the NS records? 17:17:40 It seems like a thing that would give pretty much any operator pause. 17:18:08 If you've only got a few hundred zones (probably everyone running Designate) it wouldn't even be a huge issue. 17:18:33 well, apart from all your zones being in PENDING 17:18:41 Well yeah, but you're doing a migration at that point. 17:18:49 and they should fix themselves over time 17:18:57 and it's not like you can't continue to update them during that time. 17:19:33 OK. 17:19:59 can we at least give this a good dose of testing? 17:20:17 Probably not before the mid-cycle (from us) 17:20:36 OK - well that is very close anyway 17:20:55 we can stick an hour down to talk it through there if needs be 17:21:16 #action mugsie circle back to https://review.openstack.org/#/c/247588/ next week 17:21:37 federico3: anything else to add ? 17:22:05 no, we can discuss this more extensively next week 17:22:14 kk 17:22:16 #topic Designate/Neutron Integration Update (mlavalle - recurring) 17:22:20 hi 17:22:22 mlavalle: over to you :) 17:22:50 I submitted follow up patches to Nova https://review.openstack.org/#/c/271578/4 17:23:08 I added unit tests that I think are complete now 17:23:23 one of the jobs failed yesterday with 1 test 17:23:38 Took a look at the logs and it's unrelated to my patch 17:23:53 so I rechecked it an 1 hour ago. It should pass 17:23:57 OK, cool 17:24:13 I also continue working on the new chapter for the Networking Guide 17:24:26 great 17:24:30 I should push patchset at the end of the week 17:24:54 and I saw we have a talk proposed for Austin.... Looking forward to it! 17:25:05 and that's it from me this week 17:25:08 questions? 17:25:22 do we need to push nova for buy in? 17:25:41 or is it likely to get reviewed by in time? 17:25:49 I would apreciatte if you ping John, the PTL: 17:26:03 will do 17:26:21 #action mugsie ping johnthetubaguy about the DNS name patch 17:26:38 anyone else? 17:27:01 OK - thanks fopr the work mlavalle 17:27:04 #topic sonuk: tempest plugin implementation 17:27:10 sonuk: you around? 17:27:12 i am finding lots of issue in existing tempest in designate as it is outdated causing import and other issue. I am fixing the issues. I will submit the patch regarding tempest plugin soon. 17:27:32 OK, cool 17:27:42 if you need help, just shout 17:28:15 any questions for sonuk ? 17:28:35 musie:ok sure. 17:28:43 mugsie:ok sure. 17:28:49 I know pglass and ekarlso did most of the work on those tests, so they are good people to ping as well 17:28:56 ok 17:29:02 #topic Open Discussion 17:29:12 anyone have off agenda items? 17:29:19 sonuk: fyi, the functional tests don't actually use tempest. they use tempest-lib. 17:29:33 yep i saw that 17:30:05 mugsie: https://blueprints.launchpad.net/designate/+spec/zone-transfer-accept-list-delete 17:30:29 * mugsie reads 17:31:14 we actually ahve a way to list all accepted zone transfer requests 17:31:44 mugsie: but we cant do it through rest apiu right 17:31:50 we can 17:32:34 mugsie: i am not able to execute. 17:32:39 GET /zones/tasks/transfer_requests?status=COMPLETE 17:32:59 wil show all your requests that have been completed 17:33:29 you cannot delete an accepted request, as it is part of the history of another object 17:34:22 mugsie: ok thanks. but i think we should have a "accepted zone transfer request list" cli 17:34:49 ah, in the CLI that could bu useful 17:34:52 be* 17:35:08 mugsie: yep 17:35:52 cool - that sounds good to me 17:36:04 anything else? 17:36:11 https://blueprints.launchpad.net/designate/+spec/tenant-domainid-for-designate-sink 17:36:30 MPBNKA: did the spec get updated for this? 17:36:52 no I am not sure how to proceed from here 17:38:20 OK - last week we said it should be aimed at the v2 api 17:38:41 and that it should not be part of the zones api itself - it needs to be separate 17:39:36 there is an example of a generic one -that should be made for just a domain per tenant 17:39:44 #link https://review.openstack.org/#/c/89689/ 17:40:00 ok 17:40:40 so, there should be a new API endpoint (like /project/default-domain ) that people can POST a zone ID to 17:40:42 but they still wont be able to change the fqdn assigned by default by sink 17:40:51 they would need admin creds 17:41:06 no - that would be stored on a per tenant basis 17:41:39 ok will check this 17:41:46 it would be a new table in the DB, with project_id, default_zone_id as the columns 17:42:00 if you have any trouble ping me in IRC 17:42:34 anything else? 17:43:02 timsim: ready for a long flight? 17:43:10 Always 17:43:19 * timsim needs to figure out how to get from dublin->galway 17:43:26 welcome to how the rest of the world feels :) 17:43:31 timsim: will ping on that after 17:43:56 OK - if that is it - see ya'll in IRC / inperson next week for some 17:43:59 #endmeeting