Tuesday, 2016-08-23

« Monday, 2016-08-22 Index Wednesday, 2016-08-24 »
*** ducttape_ has joined #openstack-dns00:00
*** ducttape_ has quit IRC00:18
*** ducttape_ has joined #openstack-dns00:29
*** ducttape_ has quit IRC01:28
*** ducttape_ has joined #openstack-dns01:28
*** sonuk has quit IRC02:11
*** sonuk has joined #openstack-dns02:59
*** stanzgy has joined #openstack-dns03:30
*** ducttape_ has quit IRC03:39
*** ducttape_ has joined #openstack-dns04:40
*** ducttape_ has quit IRC04:44
sri_SamYaple: generally as well as using domains and records i am not getting answer section04:48
*** ducttape_ has joined #openstack-dns05:10
*** ducttape_ has quit IRC05:15
sri_i have configured designate and created domains & records but i am not getting answer section when using dig command05:35
sri_i dont know whether i have to specify records & domains in any config files of designate05:35
sri_i am using bind905:36
sri_can some one help as i was stuck in this issue from longback05:36
*** richm has quit IRC05:40
*** ducttape_ has joined #openstack-dns06:11
*** pcaruana has joined #openstack-dns06:14
*** ducttape_ has quit IRC06:17
*** f13o has quit IRC06:53
*** rackertom has quit IRC07:06
*** rackertom has joined #openstack-dns07:07
*** ducttape_ has joined #openstack-dns07:12
*** ducttape_ has quit IRC07:16
*** tg90nor has joined #openstack-dns07:52
*** tg90nor has quit IRC07:53
*** tg90nor has joined #openstack-dns07:56
*** nyechiel has joined #openstack-dns07:56
openstackgerritgecong proposed openstack/designate: Remove white space between print and ()  https://review.openstack.org/35901607:58
*** openstackgerrit has quit IRC08:03
*** openstackgerrit has joined #openstack-dns08:04
*** ChanServ sets mode: +v openstackgerrit08:04
*** f13o has joined #openstack-dns08:07
openstackgerritDavanum Srinivas (dims) proposed openstack/designate: [WIP] Testing latest u-c  https://review.openstack.org/31802008:10
*** ducttape_ has joined #openstack-dns08:13
*** ducttape_ has quit IRC08:17
*** f13o has quit IRC08:31
*** abalutoiu has joined #openstack-dns08:35
openstackgerritsonu proposed openstack/designate-specs: Add spec for YADIFA DNS backend  https://review.openstack.org/35457909:00
*** abalutoiu_ has joined #openstack-dns09:25
*** abalutoiu has quit IRC09:26
*** richm has joined #openstack-dns10:07
*** ducttape_ has joined #openstack-dns10:10
openstackgerritKiall Mac Innes proposed openstack/designate-tempest-plugin: Bump test timeout to 4 min  https://review.openstack.org/35908710:14
*** ducttape_ has quit IRC10:16
openstackgerritTim Simmons proposed openstack/designate: Worker Model  https://review.openstack.org/28378410:44
*** abalutoiu_ is now known as abalutoiu10:46
*** ducttape_ has joined #openstack-dns11:13
*** ducttape_ has quit IRC11:17
*** sonuk has quit IRC12:09
*** ducttape_ has joined #openstack-dns12:10
*** stanzgy has quit IRC12:19
*** ducttape_ has quit IRC12:21
*** Appa has joined #openstack-dns12:26
*** nkinder has joined #openstack-dns12:31
openstackgerritTim Simmons proposed openstack/designate: Worker Model  https://review.openstack.org/28378412:33
openstackgerritFederico Ceratto proposed openstack/designate: Add Monasca-statsd metric generation  https://review.openstack.org/32225212:44
*** sonuk has joined #openstack-dns12:56
*** chlong has quit IRC12:56
*** chlong has joined #openstack-dns13:13
*** ducttape_ has joined #openstack-dns13:21
*** mlavalle has joined #openstack-dns13:25
*** sonuk has quit IRC13:31
*** ducttape_ has quit IRC13:38
*** ducttape_ has joined #openstack-dns13:45
*** eandersson_ has quit IRC13:47
SamYaplesri_: are you sure bind9 is getting informed properly?13:52
SamYaplesri_: as i unfortnualy discovered nothing complains when rndc exists with failure (due to bad config) and that was preventing the updates to bind913:53
Appahello team, I have installed bind9 and its working. Also installed openstack-designate* and trying to integrated with bind9, using it on centos 7. Is there ref. document from which i can configure dns to openstack instance using this?13:54
SamYapleAppa: what version of openstack?13:54
AppaSamYaple: openstack 2.2.013:55
SamYapleAppa: hmmm. thats not a version13:55
SamYapleoh thats the openstackclient13:55
SamYaplei meant like mitaka/liberty13:56
Appaits mitaka13:56
SamYaplethere are not really any docs unfortunately13:56
*** eandersson has joined #openstack-dns13:56
SamYaplethey are scattered about and dated13:56
Appayeah i seen that13:56
SamYaplethe big difference from a Liberty install will be the pool creation13:57
SamYaplehttp://docs.openstack.org/developer/designate/install/ubuntu-liberty.html13:57
SamYaplefollow that doc13:57
SamYaplebut look at this for the pool updates http://docs.openstack.org/developer/designate/upgrade/mitaka.html13:57
AppaSamYaple: yes i hv followed first link that you have given, but with this i am getting problem with designate-pool-manager13:58
AppaWhen i see status of systemctl status designate-pool-manager. its showing me as ...13:59
AppaERROR designate.pool_manager.service [req-7906e775-169c-4a42-aa65-b51...> found.13:59
*** devkulkarni has joined #openstack-dns14:00
SamYapleremove all the pool ids and sections from the configs (if you have any)14:02
SamYapletechnically you are only supposed to start designate-central14:02
SamYaplethen add in the new pools via designate-manage and that yaml file14:02
*** pcaruana has quit IRC14:02
SamYaplethen start the rest14:02
SamYapleor at least thats all ive been able to figure out. piecing it all together14:02
openstackgerritMerged openstack/designate: Get ready for os-api-ref sphinx theme change  https://review.openstack.org/35792514:04
AppaSamYaple: Thanks will try meanwhile you have given second based on powerdns and hv configured bind914:04
SamYapleAppa: the second part is showing you how to build the pools yaml14:06
Appaand it is regardless of any dns service correct?14:07
alberkmaneandersson: hi, how are you?14:10
AppaSamYaple: One more question, is there any other option where we can define dns to openstack instances without designate. Its just question, as i am new to openstack.14:11
*** pcaruana has joined #openstack-dns14:17
Appaanyways thanks trying that...14:29
eanderssonAll good, sup alberkman?14:31
*** devkulkarni has left #openstack-dns14:35
AppaSamYaple: its worked!14:36
AppaThanks very much!14:36
openstackgerritFederico Ceratto proposed openstack/designate: Add Monasca-statsd metric generation  https://review.openstack.org/32225214:40
*** pglass has joined #openstack-dns14:41
KiallSamYaple / Appa: mugsie is working on re-doing our install docs to solve the outdated + scattered issue :(14:44
alberkmaneandersson: i'm fine, designate its work's :)14:44
AppaKiall: ack* thanks14:44
eanderssonAwesome!14:44
alberkmanon mitaka the configure is different14:46
alberkmanin this moment, allow_reverse_dns_lookup not work, but not problem for now14:46
SamYapleAppa: glad it worked, i just had to figured the whole mess over the weekend14:47
alberkmani use http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.html instead of designate-sink14:47
SamYaplealberkman: i could be wrong here, but im pretty sure that config _uses_ designate-sink if you are using the "external dns" part of it14:51
SamYapleif you are just using it with the standard dnsmasq, no you want have PTR stuff14:51
*** Appa has quit IRC14:58
eanderssonSamYaple: Actually, that uses the Designate Api afaik15:09
openstackgerritTim Simmons proposed openstack/designate: Worker Model  https://review.openstack.org/28378415:10
eanderssonWhich is both good and bad. It's bad, as it adds additional latency when starting VMs, but good, as a VM won't be created unless the DNS was created successfuly.15:11
eanderssonA common issue we have is that the notifications gets lost (e.g. compute is in a bad state) and the DNS record never gets removed.15:11
eanderssonWhich is solved by the advanced dns config for neutron.15:11
SamYapleeandersson: ah ok. that makes more sense. "designate-sink is an optional service which listens for event Notifications, such as compute.instance.create.end, handlers are available for Nova and Neutron. Notification events can then be used to trigger record creation & deletion."15:12
eanderssonYep15:12
SamYaplethat line confused me a bit then, but i get what youre saying now15:12
eanderssonAlthough I don't want to upgrade to Mitaka :915:13
eanderssonNot looking forward to the configuration changes.15:13
eanderssonfor Designate15:13
SamYaplemmmmm pools15:13
SamYapleit really wasnt that bad, the worst part was writing it into the deploy tool15:13
SamYaplebut since i was using ansible, it has a to_yaml filter that i used and the entire config is now in a dict var. so it wasnt the worst15:14
*** tyr has joined #openstack-dns15:16
*** tyr has quit IRC15:30
*** tyr_ has joined #openstack-dns15:30
*** pcaruana has quit IRC15:56
*** pglass has quit IRC16:04
*** pglass has joined #openstack-dns16:06
*** pcaruana has joined #openstack-dns16:09
*** nkinder has quit IRC16:11
*** venkat has joined #openstack-dns16:14
*** venkat has quit IRC16:17
*** abalutoiu has quit IRC16:25
*** rmcall has joined #openstack-dns16:35
*** nyechiel has quit IRC16:46
*** penick has joined #openstack-dns16:55
*** selena_091 has joined #openstack-dns16:58
selena_091can some verify this? when we create a record,lets say A record, designate-central first notifies the change in mdns, which later notifies the actual dns backend(bind) for the change..,16:59
SamYapleselena_091: thats backwards i believe17:05
*** nkinder has joined #openstack-dns17:05
SamYaplei know after bind9 gets notified it contacts mdns17:05
*** brandor5 has joined #openstack-dns17:05
SamYapleso maybe mdns does get notified first? or its a parallel op17:05
brandor5Hey guys, I'm working on setting up designate in mitaka... I think I'm just about there... I can create records, domains, servers and everything... but the dns server (bind9) isn't actually getting the updates... I'm seeing the following error in pool-manager.log http://pastebin.com/X6Bj2gUw Anyone have any ideas what is going on?17:08
selena_091SamYaple: in my case, whenever i create a record, i do a `dig -p 5354 @ip of mdns` and isntantly get answer..however for `dig` on my dns back it takes a lot of time17:09
*** Appa has joined #openstack-dns17:09
selena_091brandor5: pools were added in mitaka..you must define `/etc/designate/pools.yaml` and then run `designate-manage pool update`   http://docs.openstack.org/developer/designate/backends/bind9.html17:10
selena_091SamYaple: in pools.yaml, mdns is always the master , so i think it gets notified first, and later it notifies the dns nameservers that are listed there...hope someone from designate team clarifies here17:12
brandor5selena_091: so i should or should not be using /etc/designate/designate.conf [pool:<<UUID>>], pool_nameserver:<<UUID>>], and [pool_target:<<UUID>>] sections? it does appear that designate in rhel land is still at 2.x, not 3.x17:13
alberkmanbrandor5: i use this guide; http://docs.openstack.org/developer/designate/install/ubuntu-dev.html17:13
brandor5alberkman: thanks I'll look through that link, currently I'm using https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/paged/dns-as-a-service-guide/chapter-2-manual-dnsaas-installation17:15
SamYapleserverascode: i think youre right17:16
SamYaplebrandor5: with mitaka you need to be doing the pool.yml thing17:16
SamYaplenot the [pool:UUID] thing17:16
alberkmanbrandor5: in designate.conf not configure targets and nameserver; this is configured in the poolsf.yaml file17:18
brandor5SamYaple: just to be sure, even on designate-2?17:18
brandor5alberkman: yep, i'm seeing that now :) just want to make sure that designate v2 supports that model17:18
SamYaplebrandor5: its the only thing you can do for mitaka and up17:21
SamYaplebut that config stuff has nothing to do with the v2 api17:21
brandor5SamYaple: okie, I'll try that now, thanks :)17:21
alberkmanSamYaple: its possible set "formatv4" in neutron.conf ?17:24
SamYaplealberkman: im not an expert here. ive only be using it for 2 days17:25
alberkmanoh, :)17:26
brandor5running `designate-manage pool update` is failing out with "TypeError: string indices must be integers, not str" error... any ideas on that?17:42
selena_091brandor5: can you pastebin your pools.yaml??17:43
SamYaplebrandor5: bad yaml17:43
brandor5http://pastebin.com/NyPGcHqs17:43
brandor5copied from the link provided17:43
SamYapleis that the whole yaml?17:44
brandor5yes17:44
SamYapleseem to be missing a bit then17:44
*** rmcall has quit IRC17:44
brandor5I got it from this link that was posted above: http://docs.openstack.org/developer/designate/backends/bind9.html17:45
selena_091you didnt define complete name and ns records/nameservers17:45
selena_091let me send u link17:45
selena_091brandor5: https://github.com/openstack/designate/blob/master/etc/designate/pools.yaml.sample-bind17:45
brandor5awesome, thanks17:45
SamYaplehttp://paste.openstack.org/show/562527/17:46
SamYaplebrandor5: thats my working one17:46
*** rmcall has joined #openstack-dns17:49
brandor5thanks, working through it now17:50
*** alberkman has quit IRC18:02
brandor5good news everyone! manually creating records is working now! wahoo! :) thanks for your help18:38
selena_091haha enjoy :) might wana go ahead try 'dig @' your dns nameserver to see you find the records there too ;)18:39
brandor5I did :)18:39
selena_091awesome possum ;)18:39
brandor5ya, just need to test automatic creation on instance up18:40
selena_091oh for that u need sink i think...you want to create vm records right?18:40
brandor5yep18:41
SamYaplei believe earlier we were talking about that and that sepcific thing does _not_ require sink18:41
selena_091yes, just set "enabled_notification_handlers = nova_fixed, neutron_floatingip" in your [service:sink] in designate.conf..18:42
SamYaplelook at the first section in http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.html18:42
SamYaplefloatingips it might need sink, yea18:42
selena_091there are actually two ways to auto creation of records of vms and floating ips: 1) use sink , but its bad design, you need to manually add the zone_id in designate.conf and restart all services 2) use neutron native integration of which SamYaple has posted link ...18:43
brandor5ok, i'll take a look and update with success/issues :) really appreciate the help18:44
openstackgerritMerged openstack/designate: Add support for Microsoft DNS Server backend  https://review.openstack.org/33270318:57
*** penick has quit IRC19:05
Appai can see create record event in logs19:07
*** tyr__ has joined #openstack-dns19:07
AppaI can't see create record event in logs19:07
Appahow i can make sure its bind9 is  properly configured with designate19:07
openstackgerritMerged openstack/designate: Use upper constraints for all jobs in tox.ini  https://review.openstack.org/35843619:08
SamYapleAppa: from what I can tell, it doesnt log anything when it fails to talk with rndc correctly19:08
*** tyr_ has quit IRC19:08
SamYapleso test out rndc locally and get it to work, then setup designate19:08
*** nyechiel has joined #openstack-dns19:09
selena_091Appa: actually you should search for `rndc` in designate-pool-manager.log ..that will tell you if the call succeeded or not..also rndc calls are made only for zone creation or deletion..for record logs, for exampe you create A record, its logs are in designate-central.log19:09
Appaif i create manual zone and dns entry in bind its working19:10
Appai see thanks SamYaple and selena_091 let me try to get rndc19:10
selena_091yep,that means rndc cannot work properly19:10
SamYapleselena_091: are you sure? because there was no failure logs for me in pool-manager, with debug on (though that shouldnt be needed)19:11
selena_091SamYaple: pretty sure..i see all rndc calls in pool-manager.log  ..its literally opening a subprocess to call rndc ..let me find an example log for you19:12
AppaSamYaple: true i can't see any failed logs in pool-manager19:12
selena_0912016-08-22 18:39:34.202 133572 DEBUG oslo_concurrency.processutils [req-766640ac-3d8b-445e-afb1-6bcfb6a945eb - - - - -] u'rndc -s 127.0.0.1 -p 953 -c /etc/rndc.conf -k /etc/rndc.key addzone my-domain.com  { type slave; masters { 10.240.134.150 port 5354;}; file "slave.my-domain.com.4f30f168-ce69-46ee-9e80-a2dbfc73f98d"; };' failed. Not Retrying. ex19:13
selena_091ecute /usr/lib/python2.7/site-packages/oslo_concurrency/processutils.py:42219:13
selena_0912016-08-22 18:39:34.204 133572 DEBUG designate.backend.impl_bind9 [req-766640ac-3d8b-445e-afb1-6bcfb6a945eb - - - - -] RNDC call failure: Unexpected error while running command.19:13
selena_091Command: rndc -s 127.0.0.1 -p 953 -c /etc/rndc.conf -k /etc/rndc.key addzone my-domain.com  { type slave; masters { 10.240.134.150 port 5354;}; file "slave.my-domain.com.4f30f168-ce69-46ee-9e80-a2dbfc73f98d"; };19:13
selena_091Exit code: 119:13
selena_091Stdout: u''19:13
selena_091Stderr: u"rndc: 'addzone' failed: already exists\n" _execute_rndc /usr/lib/python2.7/site-packages/designate/backend/impl_bind9.py:14419:13
SamYapleselena_091: right but if rndc isnt configured correctly, it isnt failing19:13
selena_091i have debug=true in designate.conf ..thats it..19:13
SamYaplei too have debug of course19:14
selena_091SamYaple: true..but actuall error for rndc is seen from pool-manager.log..i had "connection refused" which i first noticed in pool-manager.log and later fixed it19:14
SamYaplecool. look me a while to figure out whats wrong19:15
*** pcaruana has quit IRC19:20
*** nyechiel has quit IRC19:24
AppaSamYaple: rndc status is working19:56
Appaalso confirmed key and conf file path19:56
Appaactually designate record-create is working but i can't able to dig on the same19:59
SamYapleAppa: give it a minute20:00
Appasure np20:01
SamYaplei had my first few records take ~5m for whatever reason20:01
*** pglbutt has joined #openstack-dns20:08
*** pglass has quit IRC20:11
*** rudrajit has joined #openstack-dns20:13
*** haplo37__ has joined #openstack-dns20:14
openstackgerritTyr Johanson proposed openstack/designate-dashboard: [WIP] API v2 Dashboard  https://review.openstack.org/34118220:18
*** penick has joined #openstack-dns20:25
*** brandor5 has quit IRC20:25
AppaSamYaple: going to sleep now, tired no luck will continue in the morning. Thanks very much for the help20:32
SamYapleAppa: good luck!20:32
*** nkinder has quit IRC20:40
*** Appa has quit IRC20:41
*** nyechiel has joined #openstack-dns21:05
*** ducttape_ has quit IRC21:23
*** tyr_ has joined #openstack-dns21:27
*** nyechiel has quit IRC21:28
*** tyr__ has quit IRC21:28
*** sonuk has joined #openstack-dns21:29
*** rudrajit has quit IRC21:45
*** rudrajit has joined #openstack-dns21:45
*** ducttape_ has joined #openstack-dns21:46
*** rudrajit has quit IRC21:50
openstackgerritOpenStack Proposal Bot proposed openstack/designate: Updated from global requirements  https://review.openstack.org/35945222:15
*** rmcall has quit IRC22:15
*** pglbutt has quit IRC22:31
*** baffle has quit IRC22:34
*** baffle has joined #openstack-dns22:48
*** chlong has quit IRC23:03
*** eandersson_ has joined #openstack-dns23:40
*** eandersson has quit IRC23:43
openstackgerritTyr Johanson proposed openstack/designate-dashboard: [WIP] API v2 Dashboard  https://review.openstack.org/34118223:55
*** mlavalle has quit IRC23:55
*** ducttape_ has quit IRC23:57
*** ducttape_ has joined #openstack-dns23:58
openstackgerritTyr Johanson proposed openstack/designate-dashboard: [WIP] API v2 Dashboard  https://review.openstack.org/34118223:59
*** tyr_ has quit IRC23:59
« Monday, 2016-08-22 Index Wednesday, 2016-08-24 »

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