Friday, 2013-09-20

*** matsuhashi has joined #openstack-dns00:00
*** eankutse has joined #openstack-dns00:14
*** eankutse has quit IRC00:14
*** eankutse has joined #openstack-dns00:15
*** nosnos has joined #openstack-dns00:23
*** vipul is now known as vipul-away00:48
*** vipul-away is now known as vipul00:53
openstackgerritEmmanuel Ankutse proposed a change to stackforge/designate: Update domains when servers are created, modified or deleted  https://review.openstack.org/4507801:33
openstackgerritEmmanuel Ankutse proposed a change to stackforge/designate: Update domains when servers are created, modified or deleted  https://review.openstack.org/4507801:41
openstackgerritEmmanuel Ankutse proposed a change to stackforge/designate: Update domains when servers are created, modified or deleted  https://review.openstack.org/4507801:47
*** eankutse1 has joined #openstack-dns01:53
*** eankutse1 has quit IRC01:53
*** eankutse has quit IRC01:56
*** zane has joined #openstack-dns04:35
*** CaptTofu has joined #openstack-dns05:17
*** zane has quit IRC06:16
*** zane has joined #openstack-dns06:23
*** zane has quit IRC06:24
*** matsuhashi has quit IRC06:27
*** matsuhashi has joined #openstack-dns06:28
*** CaptTofu has quit IRC07:17
*** matsuhas_ has joined #openstack-dns08:03
*** matsuhashi has quit IRC08:03
*** matsuhas_ has quit IRC08:39
*** matsuhashi has joined #openstack-dns08:47
*** matsuhashi has quit IRC08:49
*** matsuhashi has joined #openstack-dns08:50
*** matsuhas_ has joined #openstack-dns08:51
*** matsuhashi has quit IRC08:55
*** leizhang has joined #openstack-dns09:31
*** matsuhas_ has quit IRC09:43
*** leizhang has quit IRC09:56
*** leizhang has joined #openstack-dns09:56
*** nosnos has quit IRC10:17
*** cflmarques has joined #openstack-dns10:54
cflmarquesHi Guys.11:08
cflmarquesDoes anyone knows if  Designate/APIv2 will be implemented on Havana release?11:08
mugsiecflmarques: we are not really tied to the Openstack release cycles yet11:09
kiallcflmarques: And - it's in progress, but .. not 100% confident on when it'll be "done"11:10
cflmarquesoh okay,11:11
cflmarquesThank's a lot11:11
*** cflmarques has quit IRC12:12
*** jmcbride has joined #openstack-dns12:15
*** jmcbride has quit IRC12:19
*** betsy has joined #openstack-dns13:03
*** CaptTofu has joined #openstack-dns13:03
*** eankutse has joined #openstack-dns13:17
*** eankutse has quit IRC13:17
*** eankutse has joined #openstack-dns13:17
*** CaptTofu has quit IRC13:39
*** tsimmons has joined #openstack-dns14:14
*** msisk has joined #openstack-dns14:23
*** tsimmons has quit IRC14:44
*** tsimmons has joined #openstack-dns14:46
*** jmcbride has joined #openstack-dns14:47
*** tsimmons has quit IRC14:47
*** jmcbride has quit IRC14:57
*** jmcbride has joined #openstack-dns14:57
*** CaptTofu has joined #openstack-dns15:05
artomhttps://blueprints.launchpad.net/designate/+spec/domain-import-export15:19
artomI'm sorta working on that already (while waiting for higher up to approve (or not) me contributing to Designate).15:20
*** zane has joined #openstack-dns15:20
artomPowerDNS's zone2json tool does a good chunk of the job already...15:20
artomAt least for importing.15:21
artomBut that's the 'hacky internal script' way of doing it...15:25
*** openstackgerrit has quit IRC15:33
*** openstackgerrit has joined #openstack-dns15:33
*** ChanServ sets mode: +v openstackgerrit15:33
betsyartom: Looks like the blueprint you're referencing is talking about import/export for BiND9 format zone files. Is that what you're working on? Or, is it import/export for PowerDNS?15:37
artomIt's BIND zonefiles.15:42
artomBut PowerDNS (since version 3.3) comes with a tool called zone2json.15:42
artomYou give it a BIND named.conf and it spits out all the zones in JSON.15:42
artomHandy because while I found python modules to parse zonefiles, so far I haven't see anything that can parse an entire BIND config starting from just the named.conf.15:43
artomActually, there's https://pypi.python.org/pypi/bicop15:45
artomBut not updated since 2009 and in RC status...15:45
*** vinodmr has joined #openstack-dns15:47
artomHeh, and it just failed on the named.conf I have.15:47
betsyAh. If it puts them in JSON, that's handy 'cause you can import them into anything - db, flat file, etc15:48
*** CaptTofu has quit IRC16:01
kiallartom: I have some *aful* code laying around that makes use of https://pypi.python.org/pypi/dnspython/1.11.1 for parsing zone files..16:07
kiallThe library works well, but doesn't go from named.conf -> a bunch of zones.. It just does 1 zone file at a time..16:08
kiall(It's also the most painful library in the world to use.. but it does work reliably)16:08
artomHow do you see import/export fitting into the rest of Designate?16:10
artomFor example, the importing - as a standalone tool that performs API queries?16:10
artomOr more... 'baked in'?16:11
kiallartom: I think the best solution for users is an import API, upload a zonefile .. then have it do it's thing.16:11
artomAh!16:12
kiallThat way, people using perl/ruby/java/python/node/<insert hipster language here> can make use of it without re-implementing the whole thing :)16:12
artomScheme ;)16:12
artomThe problem with that (that I'm facing now) is that zonefiles could be split into different files.16:15
artomSo the file containing the SOA is included from a bunch of other files.16:16
vinodmrAlso if we have something like description fields that are not present in zonefiles buy present in central, how do we handle the import/export for those - we just ignore them?16:17
kiallFor built into designate's API, I'd argue that shouldn't be something we support.16:17
*** CaptTofu has joined #openstack-dns16:17
kiallvinodmr: Yea, I think import/export should care most about the standard zonefile content, I'd rather not add any "extra syntax" on top ..16:18
artomWhich is why I was thinking of something standalone...16:18
artomAnd then I saw the blueprint and came here ;)16:18
kiallOn export, comments might just be comments in the zonefile.. But importing that might not be so easy (multi line comments might get split over 2 records etc)16:18
artomSo maybe a designte-manage command?16:18
kiallartom: Well, it depends.. I think we want an API that accepts a whole and complete zonefile, then does it's thing..16:19
kialldesignateclient could be given just enough smarts to assemble multi file zones into a single one for upload.16:19
artomAh!16:20
kialli.e. it should be possible to "parse" the include statements without doing a full-blown zonefile parser on the client side.16:21
artomI can't argue on correctness - but that may end up being impractical for some (most?) users...16:21
kiallI'd argue 99% of people with existing zonefiles have each zone self contained in a single file :) But - I'm totally making numbers up and going on gut ;)16:22
artomThey would have to triage their zonefile to exclude the bits and pieces that are included.16:22
kiallOr, are you talking about importing multiple zones at once?16:23
artomYeah.16:23
artomWe shouldn't make assumptions, but why else would anyone use the importer?16:24
kiallSo, if I run my own DNS for example.com today and decide I want to switch to, say, HP Cloud DNS, a single zone, single file, import makes lots of sense, and will be a common thing for any public Designate deployments16:25
kiallOn the other hand, if run HP, and decide I want to switch all of HP's DNS to designate, then that's a totally different scenario where they may be hundreds of zones to move16:26
artomTrue, true...16:26
artomAnd you want to target the first one with import/export...16:26
artomIf both can be done in a semi-elegant way...16:27
kiallIf the API has a 1 zone, 1 file importer, then that covers use case #116:27
*** pasquier-s has quit IRC16:28
kiallThen, the client can be given a really minimal parser to take a multi file zonefile (still 1 zone) and parse the includes to generate 1 file for upload..16:28
eankutseCase #2 is a very important one as well16:28
eankutsefor initially migrating to Designate from an existing system16:28
eankutsewhat is a suggested best approach for that?16:29
eankutseimport/export as well?16:29
kiallAnd finally, for whole company / 200 zones style moves, we again layer on top of that, with a small named.conf parser that gets builds (zonename, main_zone_file) pairs to pass to ^16:29
kialls/builds//16:29
kiallBut, I think the key thing for me is, the main zonefile parsing (extracting all the records, their types, their TTLs etc) should be server side.16:30
kiallAnd, multi file stuff should be handled client side... Since, we can't resolve the include paths server side16:31
kiallinclude "/etc/somepath/bla.conf"; \n include "/etc/someotherpath/bla.conf";16:31
kialland include "../../../bla.conf"16:31
kiallall those need to be parsed on the client, as they have no meaning once the set of files are uploaded16:32
kiall(Also .. We'd need to find the set of files to upload in the first place, making the minimal include parser necessary anyway!)16:32
artomWhat about fixes/changes to zonefile parsing?16:32
vinodmrI would think for case #2, there should be a separate tool.  Things like these are not done frequently and they are run with admin privileges16:32
artomIt's apparently very difficult to do.16:32
artomSo if there's ever a fix for a specific thing that we didn't think of, people need to wait for a new server release.16:33
kiallThat goes both ways!16:33
artomWhereas if it's done client-side, it's easier to release a client update, no?16:33
kiallIf the client side parser has a bug, then I hope your application is compatible with the new release!16:33
artomNot sure I understood that...16:34
kiallAnd .. On top of that, perl/ruby/java/python/node/<insert hipster language here> would each need a full parser if it's client side..16:34
eankutseKiall: for case #2, what do you think are downsides to using an approach where a db ETL tool is used to move (Export/Transform/Load) data across from existing db into designate-central?16:35
kialleankutse: I think that's perfectly okay for something in-house you plan on building and running once, for something we include with designate, I believe it would require the maintenance of lots of duplicated code16:36
eankutseagree16:36
eankutsedo you think it's a viable approach though?16:37
artomWhy would perl/ruby/java/python/node/<insert hipster language here> need a full parser?16:37
artomOr maybe I'm not getting what your idea of client-side is.16:37
kialleankutse: For 1 off bulk importers, I'd probably call straight into designate-central via RPC, bypassing the API, but not going straight to the database..16:41
eankutseAhh. Thx16:42
kiallartom: For me - client side is the customer..16:42
*** CaptTofu has quit IRC16:43
*** CaptTofu has joined #openstack-dns16:43
artom(Sorry for the haggling - not trying to be a pain in the ass - it's work that I'll end up doing one way or another, so I want to gage where the project is heading and why to avoid duplicate work if possible).16:44
artomNow, back to haggling ;)16:44
kiallartom: no problem at all - the more haggling, the better everyone understands :)16:44
artomIf designateclients gets a import command...16:45
artomWhy does that require Perl/Java/etc parsers?16:46
kiallFor the same reason we have multiple languages here: https://wiki.openstack.org/wiki/SDKs16:46
kiallNot all imports will be someone typing out a command on the CLI, some will be integrating with existing systems in ways we've never even considered.16:47
artomAh, gotcha.16:48
kiallMoving the complexity of full zonefile parsing to the server keeps the language bindings simple16:48
kiallThen, the CLI that wraps the Python bindings can be given just enough of a parser to understand what an "include" is..16:48
*** CaptTofu has quit IRC16:48
*** CaptTofu has joined #openstack-dns16:49
kiallAt that point, single zones spread over multiple files should be importable..16:49
kiallAnd finally, on top of that, you might layer something that can read a named.conf to determine the all zone names and "top" zonefiles for each zone, at that point, importing all zones from an existing bind server should work16:50
artomOk, I get use case #116:52
artomIn use case #2 where a large org is deploying Designate and moving all their domains to it...16:52
artomThey have access to the server.16:53
artomEh, it would be duplicate code.16:55
artomI was thinking of a bulk importer server-side as a designate-manage command, for example.16:55
artomBut if you already have zone parsing in the API, there's no point in recoding something that does the same thing with named.conf parsing on top.16:56
*** CaptTofu has quit IRC16:58
*** CaptTofu has joined #openstack-dns16:59
*** vinodmr has quit IRC16:59
*** jmcbride has quit IRC17:00
kiall(sorry - AFK dealing with something)17:05
*** CaptTofu has quit IRC17:20
*** CaptTofu has joined #openstack-dns17:20
*** jmcbride has joined #openstack-dns17:23
*** jmcbride1 has joined #openstack-dns17:26
*** jmcbride has quit IRC17:27
*** tsimmons has joined #openstack-dns17:33
*** shakayumi has joined #openstack-dns17:41
*** eankutse has quit IRC17:41
*** CaptTofu has quit IRC17:49
*** CaptTofu has joined #openstack-dns17:50
*** CaptTofu has quit IRC17:57
*** eankutse has joined #openstack-dns17:59
*** vinodmr has joined #openstack-dns18:01
*** jmcbride1 has quit IRC18:08
artomNo worries, was AFK pheeding ;)18:24
*** jmcbride has joined #openstack-dns18:33
*** vipul is now known as vipul-away18:47
*** vipul-away is now known as vipul18:47
*** vinodmr has quit IRC18:53
*** leizhang has quit IRC18:55
*** tsimmons has quit IRC18:58
*** eankutse has quit IRC19:02
*** eankutse has joined #openstack-dns19:03
*** vinodmr has joined #openstack-dns19:07
*** jmcbride has quit IRC19:11
*** tsimmons has joined #openstack-dns19:12
*** CaptTofu has joined #openstack-dns19:12
*** msisk has quit IRC19:22
*** vinodmr has quit IRC19:23
*** tsimmons has quit IRC19:24
*** eankutse has quit IRC19:24
*** vipul is now known as vipul-away19:24
*** CaptTofu has quit IRC19:29
*** dmakogon_ has joined #openstack-dns19:45
*** tsimmons has joined #openstack-dns19:46
*** tsimmons1 has joined #openstack-dns19:51
*** tsimmons has quit IRC19:51
*** jmcbride has joined #openstack-dns19:59
*** msisk has joined #openstack-dns20:00
*** tsimmons1 has quit IRC20:00
*** jmcbride has quit IRC20:18
*** msisk has quit IRC20:19
*** vipul-away is now known as vipul20:20
*** shakayumi has quit IRC20:36
*** EmilienM has quit IRC21:22
*** EmilienM has joined #openstack-dns21:23
*** zane has quit IRC22:07
*** dmakogon_ has quit IRC22:24
*** openstack has quit IRC22:35
*** openstack has joined #openstack-dns22:35
*** ChanServ sets mode: +v openstack22:36
openstackgerritBetsy Luzader proposed a change to stackforge/designate: docs: Correct errors in the Create Record examples  https://review.openstack.org/4764822:41

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!