17:00:16 #startmeeting designate 17:00:17 Meeting started Wed Jan 22 17:00:16 2014 UTC and is due to finish in 60 minutes. The chair is kiall. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:20 The meeting name has been set to 'designate' 17:00:31 o/ 17:00:32 Hey all - Who's about today? 17:00:36 here 17:00:38 o/ 17:00:46 o/ 17:00:52 Cool :) 17:00:54 here 17:01:29 Good day folks! 17:01:54 So - We have no pre-prepared agenda for today, With the mini-summit so close, I've been full steam ahead on some internal work. Trying to complete a good chunk of it before travelling 17:02:09 same ^ 17:02:17 #topic Review action items from last week 17:02:38 so, we had 1 item from last .. "send email to Openstack mailing list" 17:02:44 that was re the mini-summit 17:03:08 jmcbride sent that during the week 17:03:08 #link http://lists.openstack.org/pipermail/openstack-dev/2014-January/024862.html 17:03:25 any extra interest form that jmcbride ? 17:03:29 jmcbride: did you get any response privately? or via eventbrite? 17:04:21 so, mostly Redhat folks are now trickling in 17:04:26 I said I'd attend via Hangouts... 17:04:27 but otherwise, I have not seen anything 17:04:38 Not sure how that will work out... 17:04:58 I'll check our current registration 17:05:18 artom: we'll be as inclusive as possible :) 17:05:34 I have 10 folks registered. 17:05:50 1 red hatter has confirmed but not registered 17:05:57 2 are TBD in person attendance. 17:06:11 Cool - So 10-13 in person? 17:06:31 14 if you include me. 17:06:44 Cool :) This should be fun! 17:06:55 I'm looking forward to it 17:06:56 yup 17:07:05 yep. I'm hoping to get some tasty austin lunch staples too, so keep your fingers crossed. 17:07:06 I also see you've updated the agenda you wrote up 17:07:08 #link https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-01 17:07:22 Yes, I was hoping to get feedback from you guys 17:07:58 Looks good, I think on the morning of day 1 we can fill in the "Design sessions" topics, based on "Review Icehouse progress and start blueprint review" 17:08:10 kiall: agreed 17:08:32 #action kiall find 2 hours to write mini-dns spec ahead of time -_- 17:08:57 I'm still on the fence over ^ - hence this would be a great time to discuss it ;) 17:08:58 kiall: that would be great - or at least refine it in your head and we can do a bit of whiteboarding 17:09:12 kiall: we also have some feedback for you on it 17:09:22 kiall, actually, about that... you want to discuss that now? 17:09:27 hey folks 17:09:39 myself and mugsie have had a few pub conversations about it, generally refining more each time, but I'm not sure I'm in a great position to articulate it correctly yet 17:10:06 kiall: I'm adding it to the agenda to specifically address 17:10:08 The act of writing it down should help get the final pieces cleared up 17:10:41 Cool - Thanks Joe 17:11:29 "The design sessions priorities" section is where you can add more topics you would like to address outside of icehouse 17:11:30 So, other than HP and RAX folks, are there any other folks here today that will be there in person? or hangouts? 17:12:01 If we have time left over, we can simply start at the top of all known blueprints and prioritize/discusss 17:12:03 i'll be on via hangout 17:12:21 Artom will also be on hangout 17:12:45 rjrjr_: Great :) So, we'll have a few via hangouts. 17:13:06 If you go out for food/beers, I'll bring my laptop to a local Irish pub ;) 17:13:11 Rackspace will also have our DNS operations lead in person (Jason Bratton). 17:13:15 I own't be there :p, hangout though ! 17:13:20 jmcbride: "If we have time left over," <-- you mean today, or in person? 17:13:31 ekarlso, can you register so I know to expect you? 17:13:47 ekarlso: in person during workshop 17:13:59 ^kiall: in person during workshop 17:14:26 I'm not sure I want to take you guys to an irish pub in Austin 17:14:35 Your expectations will be TOO high! 17:14:37 jmcbride: perfect :) The last week, myself / mugsie / ekarlso's heads has been been in Ops mode rather than Dev mode ;) 17:15:05 jmcbride: I learnt a long time ago about irish pubs abroad :) 17:15:19 Yea - There always .. Interesting places ;) 17:15:34 Hey, having been in Scotland (not the same, I know) and here in Montreal... We're doing quite OK here :) 17:15:52 nice, well, I'll try and find an Austin favorite that measure up... 17:16:08 rjrjr_ / artom - Whats your TZ difference to Austin? And - Are they any topics you have a particular interest it? 17:16:21 (To try and schedule those conversations for your working hours!) 17:16:33 I'm EST, so +1 17:16:41 Reverse DNS for me, mostly 17:16:48 Possible better BIND support 17:16:58 MST 17:17:25 It'll depend on what I get fed in my backlog and what gets decided, if anything 17:18:13 Sweet, so you guys will be an hour in both directions timezone wise. Will the proposed times be cool? 17:18:19 Okay - rjrjr_ - could you add any topics (even if there listed on the page) that you're interested in to the bottom of https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-01 17:18:35 yes 17:18:37 artom: feel free to update what I put down for you ;) 17:19:03 Thanks! 17:19:21 richm: Are there any topics that you would be interested in? 17:19:40 kiall, sure, I'll keep that info fresh. 17:19:44 richm - welcome, do you know if you will be able to make it (at least via hangout) 17:20:19 artom & rjrjr_ - can you send me your google usernames? 17:21:14 Let's take that as a yes ;) Otherwise mugsie has them 17:21:19 rjrjr@cox,net 17:21:43 yes 17:22:16 One other note about next week priorities, a dev from our Load Balancer team will also be attending (his name is jorge). He has some ideas about "global load balancing". 17:23:05 Worth mentioning - next weeks Wednesday IRC meeting will obviously be cancelled, as we'll have just wrapped up the few days in person .. Just making sure that's clear :) 17:23:26 jmcbride: excellent :) 17:24:14 Anyway - So, Since we have no pre-prepared agenda today, if anyone has anything to bring up, or that they want to discuss, jump in at any time please :) 17:24:51 Well, re mini-dns... 17:25:01 Or you want to save that for the workshop? 17:25:08 betsy: you're Blacklisted Domains review, is that ready to look over? Last time i looked, you had left a comment saying "not ready yet" :) 17:25:28 I've got some changes that I'll submit today and that should be it 17:25:46 Sorry, but I've been ill 17:26:02 artom: I think we need to get that written up, it's a complex idea with lots of tradeoffs.. And I know I personally still haven't quite got the idea clear in my head 17:26:07 betsy: unacceptable ;) 17:26:14 :) 17:26:32 No worries - I just didn't want it to sit there ready for review for ages without getting looked at ;) 17:27:27 Okay - Well, If nobody has anything else, we can call it a day? 17:27:57 yep, have a great week, see ya'll in Austin! 17:28:05 jmcbride: BTW 17:28:11 see you 17:28:17 kiall, well, I just have... an "alternative"? 17:28:29 Not comments about the idea itself. 17:28:55 jmcbride: Myself and mugsie be in Austin on Sunday, and staying in the Radission .. Just FYI 17:29:02 artom: an alternative? 17:29:43 Well, instead of implementing mini-dns, the same effect can be achieved by mandating the multi backend with a PowerDNS master. 17:29:47 kiall: sweet, I emailed all attendees my contact info. I might be able to slip away for dinner/drinks Sunday, so let me know. 17:30:17 jmcbride: depends how tried we are ;) Land at like 6am or something. 17:31:06 artom: That's certainly an option, but has some drawbacks in terms of the potential phase 2 features.. 17:31:45 Inbound AXFR, RFC / nsupdate Dynamic DNS, anything that modifies the content of the zone, would be really really awkward to fit into that model 17:32:29 Do we need to allow zone modification by means other than the API? 17:33:15 I think we do, and I know rjrjr_ would agree ;) one of the pieces he discussed in the past was accepting RFC / nsupdate dynamic DNS updates 17:33:20 artom: we should not rule out use of nsupdate 17:33:38 afik redhat openshift needs it as well 17:33:42 kiall/artom: regarding mini-DNS, I think it sounds feasible, but I think it will only work for use cases in which either zone transfers or dynamic dns protocol is supported. 17:33:49 RedHat I'm sure are interested in that too - OpenShift / Origin requires a a RFC style dynamic DNS server 17:34:22 And so mini-dns would implement said RFC-style server? 17:34:42 And reflect any changes it receives via not-API in Designate's state? 17:34:45 jmcbride: absolutely - this would never be a target of end user queries - that would be an epic failure waiting to happen IMHO ;) 17:35:39 artom: yea, so, RFC dynamic DNS is actually quite simple to impelement (with the exception of transactional / atomic commits of whole changeset - but that's another topic to solve independently) 17:35:43 kiall: agreed. My comment was targetted at how to get zone data transferred from master to slaves. 17:36:00 When I say simple - I mean, simple once you have the other pieces in place 17:36:59 kiall: I think we will benefit from that 2 hour homework assignment you gave yourself… 17:37:20 jmcbride: and lots of RFC reading ;) 17:37:38 kiall: before bed is the best time for that 17:37:55 You'll never get past the first sentence that way 17:38:34 our mini-dns also needs to respond to refresh requests from slaves 17:38:48 artom: Anyway - I know I see huge advantages by being able to alter the data we have via the standard DNS mechanisms, I think supporting that is key if we go with the "mini-dns" suggestion , or the enforce powerdns alternative route you suggested 17:39:18 Kiall: regarding RFC's that you plan to read 17:39:31 can you tell us which ones you plan to look at? 17:39:34 eankutse: I meant you guys ;) I've read them all 17:39:37 I am interested as well 17:39:42 :-) 17:39:57 sleep reading RFC's? 17:40:19 rfc1034, rfc1035, rfc2181 are some the main ones 17:40:25 cool 17:40:28 kiall, was just throwing the alternative out there. It seemed like mini-dns was reimplementing existing stuff for benefits that were unclear to me. But if we want storage <-> backend "bidirection" communications, I don't think we have the choice... 17:40:41 2136 is nsupdate / RFC style dynamic DNS 17:41:10 Unless we start doing funky stuff like polling the PowerDNS db to import changes into storage... 17:41:14 Ehh - And I'm sure theres 100 others that aren't coming to mind right now 17:41:49 That's a good start 17:41:59 there'll be references from those to others 17:42:01 artom: Well, powerDNS supports custom backends, lua based from memory, but we enter pretty dangerous territory there with ever becoming core OpenStack ;) 17:42:33 That's a whole other level of meta right there... 17:42:47 And - Choosing PowerDNS as a core piece, as much as I like that idea, would likely be a roadblock for us over time as people have their favourite 17:42:49 "We put a backend in your backend so you can DNS while you DNS" ;) 17:43:11 artom: hah :) Yep 17:43:36 We should have a blueprint for the idea of supporting bidirectional updates (e.g. using dynamic DNS to update zones). 17:44:28 oh eankutse .. rfc2845 would be another core piece.. providing a method of identification of users making queries etc to this 17:45:07 http://i.imgur.com/kQ7DHB4.jpg 17:45:22 lol 17:45:36 jmcbride, I didn't think anyone would actually do that :D 17:45:42 Bravo. 17:46:01 artom: CloudFlare was (is?) based on PowerDNS and a custom backend for it ;) 17:46:10 Okay - Well, I think it's time to wrap this up and call it a day :) 17:46:12 Kiall: thx. Keep them coming :-) 17:46:20 hub_cap got here, so .. everyone leave please. 17:46:23 ;) 17:46:28 YEA BOI 17:46:48 hi kiall ;) i totally saw a half past / half 30 thing on tv the other day 17:46:49 Hey, we got 15 more minutes officially, I intend to fill every last second with more memes :D 17:47:01 Okay - Thanks all :) Cya next week ! 17:47:12 cya 17:47:18 #endmeeting