Wednesday, 2016-06-08

*** EricGonczer_ has joined #openstack-dns00:05
*** leitan has quit IRC00:13
*** leitan has joined #openstack-dns00:15
*** EricGonczer_ has quit IRC00:21
*** ducttape_ has quit IRC00:22
*** leitan has quit IRC00:32
*** kbyrne has quit IRC00:40
*** kbyrne has joined #openstack-dns00:42
*** johnbelamaric has joined #openstack-dns01:11
*** johnbelamaric has quit IRC01:16
*** rudrajit has joined #openstack-dns01:26
*** stanzgy has joined #openstack-dns01:39
*** ducttape_ has joined #openstack-dns02:23
*** ducttape_ has quit IRC02:33
*** richm has quit IRC02:45
*** openstackgerrit has quit IRC02:47
*** openstackgerrit has joined #openstack-dns02:47
*** ChanServ sets mode: +v openstackgerrit02:47
*** ducttape_ has joined #openstack-dns02:48
*** jhfeng has joined #openstack-dns02:51
*** ducttape_ has quit IRC03:24
*** jhfeng has quit IRC03:33
*** rudrajit has quit IRC03:59
*** rudrajit has joined #openstack-dns03:59
*** ducttape_ has joined #openstack-dns04:25
*** ducttape_ has quit IRC04:30
*** Alex_Stef has joined #openstack-dns04:46
*** fawadkhaliq has joined #openstack-dns05:33
*** rudrajit has quit IRC05:59
*** Alex_Stef has quit IRC06:23
*** ducttape_ has joined #openstack-dns06:26
*** darkxploit has quit IRC06:26
*** ducttape_ has quit IRC06:31
*** darkxploit has joined #openstack-dns06:43
*** openstackgerrit has quit IRC06:48
*** openstackgerrit has joined #openstack-dns06:48
*** ChanServ sets mode: +v openstackgerrit06:48
openstackgerritOpenStack Proposal Bot proposed openstack/designate-dashboard: Imported Translations from Zanata  https://review.openstack.org/32685706:49
*** jschwarz has joined #openstack-dns07:17
*** fawadkhaliq has quit IRC07:23
*** kodokuu has joined #openstack-dns07:31
*** kodokuu has quit IRC07:44
*** openstackgerrit has quit IRC07:48
*** openstackgerrit has joined #openstack-dns07:48
*** ChanServ sets mode: +v openstackgerrit07:48
*** Alex_Stef has joined #openstack-dns08:00
*** fawadkhaliq has joined #openstack-dns08:09
openstackgerritDavanum Srinivas (dims) proposed openstack/designate: [WIP] Testing latest u-c  https://review.openstack.org/31802008:10
*** ducttape_ has joined #openstack-dns08:27
*** ducttape_ has quit IRC08:33
*** dmk0202 has joined #openstack-dns08:37
*** kodoku has joined #openstack-dns08:43
*** bsv has joined #openstack-dns08:44
*** fawadkhaliq has quit IRC08:45
*** kei_yama has quit IRC08:45
*** openstackgerrit has quit IRC08:48
*** openstackgerrit has joined #openstack-dns08:48
*** ChanServ sets mode: +v openstackgerrit08:48
*** nyechiel has joined #openstack-dns08:51
kodokuhi bsv08:55
kodokuI solved my issue with SOA request yesterday ;)08:55
kodokuneed to open UDP 5354 port on mdns node ;)08:56
bsv:D08:58
kodokubut now I'am on sink service08:59
kodokuIn irc logs, I can see you conf sink service08:59
kodokuworks now ?08:59
bsvstill not working, it did work tho.09:00
bsvThen I reinstalled the entire setup, and from that point, sink stopped working.09:01
kodokuok you change anything in nova conf ?09:01
kodokujust notification_topics=notifications09:01
bsvchange the notification driver and topics09:01
kodokuok what driver ?09:01
bsvrpc_notifier09:02
bsvbut my setup is broken somehow, so I must have a configuration error somewhere.09:03
bsvJust weird that it DID work, solid even.09:03
kodokunow my sink no works09:03
bsvUsed the same playbook to recreate the configurations, but no cigar.09:03
kodokuBut I can see sink service in notification queue09:03
kodokulike a consummer09:03
bsvI did see a bugreport about reusing queues.09:03
kodokuI have notification_driver=nova.openstack.common.notifier.rabbit_notifier in nova compute09:04
bsvYou need to configure a seperate queue, or else ceilometer and designate will fight over the messages, and one of them will loose ;)09:04
kodokuyes I see ceilometer and sink in queue09:05
kodokuSo I can add designate-notification in nova09:06
bsvalso, notify_on_state_change = vm_and_task_state09:06
bsvim a bit busy, so I might be slow to respond here on irc ;)09:07
kodokuand need same control_exchange09:08
kodoku?09:08
kodokuno pb09:08
kodokumugsie hi09:19
kodokubsv I change topics in designate-notifications09:20
kodokuBut I can't see any message in my queue09:21
kodokunotification_topics=notifications,designate-notifications09:21
kodokunotification_driver=nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier,messaging09:21
*** fawadkhaliq has joined #openstack-dns09:32
*** fawadkhaliq has quit IRC09:33
*** fawadkhaliq has joined #openstack-dns09:33
*** fawadkhaliq has quit IRC09:33
*** fawadkhaliq has joined #openstack-dns09:42
bsvkodoku: thats the same issue Im having, no events in the queue.09:43
kodokuyes :/09:44
kodokuIn kilo, I had same pb09:44
kodokuI had messagingv209:45
kodokuin driver09:45
kodokubsv works09:51
kodoku:)09:51
kodokuI see message in designate-notifications09:51
kodokuKiall give me this tricks for kilo ;)09:52
kodokuok when I create a VM, sink issue => ZoneNotFound: Could not find Zone09:55
kodokuBut I have a domain-id in nova handler :/09:56
kodokuIll bb09:57
*** kodoku has quit IRC09:58
*** kodoku has joined #openstack-dns10:01
*** stanzgy has quit IRC10:22
*** ducttape_ has joined #openstack-dns10:29
mugsiekodoku: this is mitaka right?10:33
mugsiethe co fig option is now called zone id10:33
mugsiewe were a little over zelous with the domain -> zone refactor10:33
*** ducttape_ has quit IRC10:34
bsvkodoku: nice, i've been working at sink for 3 days solid, and you find it in 5 sec :)10:34
bsvcheating you must be ;)10:34
kodokubsv ;)10:37
kodokuI working on 3 days too in kilo10:37
bsveveryone should have a dev. standing by for questions :)10:37
kodokumugsie yes mitaka10:37
bsvyes, zone and zone_id10:38
bsvYou can see the available values in the logfile. You get a nice json object that you can pick from :)10:38
bsvIF SINK is working :p10:38
kodokuI don't know why but sink tell me ==> DEBUG designate.notification_handler.base [-] Using Zone ID: None10:38
kodokueach domain have a zone id ?10:39
bsvAre you using nova_fixed or neutron_floating?10:40
kodokujust nova10:40
bsv(or both=10:40
bsvok10:40
bsvthen you need to create a domain, get the ID and use that for zone_id.10:40
kodokufull log http://paste.openstack.org/show/508894/10:40
kodokuzone id ?10:41
kodokuin [handler:nova_fixed] ?10:41
bsvyes10:41
kodokuI don't have this option10:41
kodokujust domain_id10:41
bsvno10:41
bsvits a secret option10:41
bsv:)10:41
kodokuomg10:41
bsvas mugsie said10:41
bsvformat = "%(instance_id)s.%(zone)s"10:42
bsvzone_id = {{ designate_zone_id }}10:42
kodokuand zone_id is the ID of my domain ?10:42
bsvIn this example, i'm using the uniqe instance-id as hostname.10:42
bsvyes10:42
kodokuok I try10:42
bsvreplace {{ designate_zone_id }} with your ID.10:43
bsvits an Ansible placeholder.10:43
kodokuneed to remove domain_id ?10:45
kodokuoslo_messaging.notify.dispatcher KeyError: u'domain'10:46
kodokuuops10:46
kodokuneed to change fomrat :)10:46
bsv:)10:47
bsvkodoku: so you only changed the 3 lines in nova.conf on the controller?10:48
bsvor did you change anything on the compute-node?10:49
kodokujust on compute node add messaging10:49
kodokuand the notification topics10:49
kodokuno change on nova.conf on CTRL10:50
bsvso only designate.conf on the controller, and nova.conf on the compute node?10:50
kodokuyes10:50
bsvhmm ok10:50
bsvI have to check that.10:50
bsvI have an option also for neutron, but unsure if I actually need that.10:50
kodokuFor neutron you need to create port then create instance with this port10:51
kodokunobody create instance like that10:52
bsv:)10:52
kodokuok now designate dashboard10:52
kodokuRDO have no package dashboard, T_T10:52
bsvhttps://etherpad.openstack.org/p/designate-dashboard10:53
bsvplaybook for setting up the dashboard.10:53
bsvansible playbook, but I'm sure you get it :)10:54
kodokuyes thx10:54
bsvnp10:54
kodokubsv last operation is for ?11:06
kodokuenable drop down for floating ips11:07
kodokuI don't use floating IP so I need to change horizon option ?11:07
bsvmaybe11:07
*** abalutoiu has joined #openstack-dns11:08
bsvIts just an option, so if you assign a floating ip inside horizon, you can bind it easily using the GUI in the DNS management.11:08
bsvirrc11:08
bsviirc11:08
bsv:D11:08
kodokuok11:08
kodokuand where is the designate_policy.json ?11:09
bsvbeen a while since I create it, right about when Mitaka was released.11:09
bsvfind / -name designate_policy.json -print11:12
bsv:D11:12
*** fawadkhaliq has quit IRC11:12
kodokuvery strange, after python install11:14
kodokuI guess dashboard is not install11:15
kodokubecause I don't have /usr/share/openstack-dashboard/openstack_dashboard/dashboards/project/dns_domain fodler11:15
kodokuI have /usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains11:16
kodokubut horizon tell me TemplateDoesNotExist: project/dns_domains/index.html11:16
bsvwhat os are you using?11:18
kodokurhel 711:18
bsvhmm, im using centos, should work I guess11:19
kodokuok after install just restart apache ?11:19
bsvyes11:19
bsvI have a final playbook that restart all servers.11:19
*** fawadkhaliq has joined #openstack-dns11:19
bsvmight be the catch ;)11:19
kodokuokkk11:20
kodokuI don't have index.html in /usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains//usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains/11:20
kodokuoups11:20
kodokuin /usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains/11:20
bsvI like to see that everything is working after reboot.11:20
kodokuok git fail I guess because I don't have index.html11:21
bsvI still have no messages from nova... weird.11:22
kodokuarf11:23
kodokuI don't know why but when install, template is not use => designatedashboard/dashboards/project/dns_domains/templates/dns_domains11:24
kodokubsv do you have /usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains/index.html in your horizon node ?11:24
*** fawadkhaliq has quit IRC11:25
bsvno11:27
bsvno such file11:27
kodokuok11:27
bsvwhat do you use for notifications_driver and topic in designate.conf?11:27
kodokudriver default11:28
kodokuand topic same in nova.conf11:28
bsvdocumentation have the options located in section 'DEFAULT', i created the section [oslo_messaging_notifications] while debugging this issue.11:28
kodokubut don't use notifications11:28
kodokuI have #notification_driver =11:31
kodokuand #notification_topics =11:31
kodokuin default section11:31
kodokujust notification_topics = designate-notifications11:32
kodokucontrol_exchange = 'nova'11:32
kodokuin handler:nova_fixed11:32
kodokumugsie do you here ?11:32
kodokuAre you here*11:32
*** fawadkhaliq has joined #openstack-dns11:38
kodokuin babel-django.cfg you can see [django: **/templates/**.html]11:38
*** ducttape_ has joined #openstack-dns11:38
kodokuBut with python install, I guess no works :/11:38
kodokubsv with find / -name index.html -print11:39
kodokuDo you have index.html in a dns folder ?11:39
bsvback11:39
bsvphone >.<11:40
*** fawadkhaliq has quit IRC11:40
*** fawadkhaliq has joined #openstack-dns11:40
bsv# find / -name index.html -print |grep 'dns'11:41
bsv/usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains/templates/dns_domains/index.html11:41
bsv/opt/designate-dashboard/designatedashboard/dashboards/project/dns_domains/templates/dns_domains/index.html11:41
bsv/opt/designate-dashboard/build/lib/designatedashboard/dashboards/project/dns_domains/templates/dns_domains/index.html11:41
kodokuhum11:41
kodokuok I don't have template in /usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains/11:42
kodokuand in build11:43
kodokuhum11:43
kodokuso build fail11:43
*** fawadk has joined #openstack-dns11:43
*** fawadkhaliq has quit IRC11:44
*** fawadkhaliq has joined #openstack-dns11:44
kodokumy build http://paste.openstack.org/show/508902/11:44
kodokudoesn't use template folder ><11:45
*** fawadk has quit IRC11:48
*** ducttape_ has quit IRC11:50
*** ducttape_ has joined #openstack-dns11:51
*** ducttape_ has quit IRC11:55
*** abalutoiu_ has joined #openstack-dns11:57
*** abalutoiu has quit IRC12:00
*** fawadkhaliq has quit IRC12:03
*** abalutoiu has joined #openstack-dns12:06
*** abalutoiu_ has quit IRC12:07
*** aurelien__ has joined #openstack-dns12:20
*** aurelien__ has quit IRC12:21
bsvmugsie: can you post a working designate.conf ?12:22
*** fawadkhaliq has joined #openstack-dns12:22
*** fawadkhaliq has quit IRC12:26
*** sonuk has quit IRC12:27
*** fawadkhaliq has joined #openstack-dns12:33
*** abalutoiu_ has joined #openstack-dns12:35
*** leitan has joined #openstack-dns12:37
*** abalutoiu has quit IRC12:38
*** ducttape_ has joined #openstack-dns12:44
mugsiebsv: the one here works - http://docs.openstack.org/developer/designate/install/ubuntu-dev.html#configuring-designate12:49
mugsiewe use that as part of the vagrant env12:49
mugsiebut that does not use sink12:49
mugsiei think I will need to retest sink.12:49
bsvi'm not seeing any events on sink, and are having a hard time finding any documentation about the configuration needed.12:50
mugsieyeah, sink docs were never really written - we never thought people would use it that much12:52
bsvfrom what I hear/read, only a minor configuration change on the compute-node is required (/etc/nova/nova.conf).12:52
mugsiethe problem is most of us don't use it, so are not hugely familiar with iut12:52
bsv>.<12:52
mugsieso, I will need to dig in for a bit, and then write docs12:53
bsvWho wrote the code?12:53
mugsieI will add it to the list for today12:53
mugsieKiall did, at the start of the project12:53
mugsieit has not really changed since it was writen12:53
kodokumugsie hey, do you have idea why dashboard don't use template folder ?12:54
kodokumy build http://paste.openstack.org/show/508902/12:54
kodokudashboards/project/dns_domains/template is not add in buuild12:55
mugsiereally?12:55
mugsieweird12:55
mugsielet me look12:55
mugsiehow were you installing it?12:55
kodokuon horizon node12:56
kodokudefault path12:56
kodokuwith python setup.py install12:56
mugsiedesignate_dashboard-0.0.012:56
mugsiethat looks ... wrong12:57
mugsieis this a fresh clone?12:57
kodokuyes I don't have net on my node12:57
kodokuyes12:57
mugsieah, k12:57
kodokuI try to change version in __init.py12:57
kodokuwith12:58
kodoku__version__ = '2.0.0'12:58
kodokubut no works12:58
mugsiewhat happens?12:58
kodokualways 0.0.012:59
*** abalutoiu_ is now known as abalutoiu12:59
abalutoiuhello13:00
mugsiekodoku: try "pip install ." ?13:01
mugsieabalutoiu: o/13:01
kodokuI can use pip install but with what ?13:02
kodokudesigante dashboard is not on pypi13:02
kodokuha this is a command ^^13:03
mugsiekodoku: "." at the end tells pip to use this folder13:03
kodokuSuccessfully installed designate-dashboard-0.0.013:04
kodoku:D13:04
*** ducttape_ has quit IRC13:04
*** fawadkhaliq has quit IRC13:04
mugsieand, does horizon agree?13:04
kodokuno13:04
kodokubecause I don't have template folder in /usr/lib/python2.7/site-packages/designatedashboard/dashboards/project/dns_domains/13:05
kodokucan you send me the dist of dashboard ? :D13:06
mugsieeh, yeah. give me a sec13:06
kodokuthx13:06
mugsiekodoku: http://tarballs.openstack.org/designate-dashboard/designate-dashboard-stable-mitaka.tar.gz is it (i *think* )13:08
mugsiei am creating one right now anyway13:08
bsvmugsie: great if you would look at sink, I cannot use OpenStack without that feature :D13:08
kodokuthx13:09
kodokuI'll try13:09
kodokuok now I have templates folder13:11
kodokuthx13:11
kodokuI test horizon13:11
kodokubsv sink not work ?13:11
leitanguys, any specific change i need to do on powerDNS 4.0 to allow SOA updates from designate mdns ?13:12
bsvkodoku: no activity in sink13:12
bsvim not getting any events at all.13:13
kodokuleitan I guess designate mitaka no test with pdns 4.013:13
mugsiekodoku: https://shell.gra.ham.ie/designate-dashboard-2.0.1.dev10.tar.gz was just built from source as well13:13
mugsieleitan: I doubt it will work13:13
mugsiewe have done 0 testing13:13
bsvCorrect me if i'm wrong, but sink communicates with nova ONLY by rabbitmq... right?13:13
mugsiebsv: yes13:13
leitanmugsie, kodoku  lovely hahaha, ill try today to make it work, if not ill switch to another backend13:14
kodokubsv send your nova.conf on compute and designate.conf13:14
bsvIs there some resource on how to wrap your head around the notification system?13:14
mugsieleitan: why the need for 4.0 ?13:14
kodokuleiten I use pdns 3.4.813:14
leitanmugsie, no need, just was what 16.04 deployed on the server13:14
mugsiebsv: no. this is half the problem. across all openstack projects the notifications are a dark art13:15
mugsieleitan: oh, really?13:15
bsvmugsie: and the most critical :p13:15
mugsiebsv: yeah. can you see messages in any queue from nova?13:15
kodokumugsie horizon works ;)13:15
mugsieand is celiometer running?13:15
mugsiekodoku: \o/13:16
leitanmugsie, yes, so i was crush and burning till i realized today to check the powerdns version13:16
mugsieleitan: :(13:16
mugsieright13:16
mugsiefiling a bug13:16
kodokubsv you can turn on web mode on rabbitmq for see queue13:16
kodokuI use that for debug queue for sink13:17
leitanmugsie,  i had this working on kilo like a charm, that was surpsided me13:17
bsvjust a sec13:18
leitanbsv, maybe mugsie or kodoku can confirm, but i had a similar problem in the past, and it was that i had on vhost per service with password, and designate wasnt able to read from the vhost13:18
leitanso i have to create two shovels13:18
leitanon rabbit13:18
leitanone for nova, and one for neutron so the notifications.info messages get shoveled to dnsnotifications queue on designate13:18
mugsieleitan: pdns have debs they build for each OS, maybe a 3.x deb will be there for ubuntu 16.04 ?13:19
leitani dont know if designate is capable to read from multiple private vhost now13:19
mugsieleitan: nope13:19
mugsieits a limitation of oslo messaging afaik13:19
bsvdesignate.conf = http://paste.openstack.org/show/AIZyPynKEIlGYU10cnf6/13:19
*** richm has joined #openstack-dns13:20
bsvonly trying to use nova_fixed atm.13:20
leitanmugsie, its werid cause ceilometer allows to configure user:pwd@vhost , so should be allowerd13:20
leitanallowed13:20
bsvno neutron_floatingip13:20
leitanbsv, nova has its own vhost ?13:20
kodokubsv I don't have [oslo_messaging_notifications] in my designate.conf13:20
kodokutry to remove all13:21
mugsieleitan: does it?13:21
bsvI added that section manually, because the logfile kept shouting up about putting notification_drivers/topics under DEFAULT is deprecated.13:21
kodokuyes13:22
kodokuremove all13:22
kodokuI doesn't use  notification_drivers/topics in default too13:22
kodokuall comments13:22
kodokuuse default value13:22
leitanmugsie, that was gordon chung said to me when i was configuring gnocchi + ceilometer13:22
kodokusend your nova.conf too :)13:22
dasmo/13:25
bsvnova.conf = http://paste.openstack.org/show/Fh2Im4ePfySKkAy5rGtr/13:26
bsvleitan: its own vhost?13:27
mugsiebsv: a lot of people isolate services from each other using rmq vhosts13:27
mugsie(and really, you should)13:28
bsvah yeah, I tried openstack-ansible with lxc's... awfull performance.13:28
kodokubsv13:28
bsvthis is just a Poc, not production.13:28
bsvnot even a pilot.13:28
leitanbsv, its not your case, you have on the / guest13:28
kodokuadd notification_driver = messagingv213:28
kodokuin nova.conf13:28
mugsiehell, we ran entireley separate rmqs back in the public cloud days13:28
mugsieok. a few changes.13:29
kodokubsv and control_exchange=nova13:29
bsvim pretty sure its control_exchange=nova allready.13:29
kodokumaybe by default13:30
kodokuI force it in my nova.conf13:30
mugsieand in the [oslo_messaging_notifications] remove "notifications_designate"13:30
mugsiethat section is about where designate sends notifications13:30
kodokuyep13:30
bsvgone... :)13:30
bsvmugsie: in designate.conf right?13:30
kodokuok try now :)13:30
mugsiebsv: yeap13:30
bsvand control_exchange was in nova.conf?13:31
kodokudon't forget to add messagingv213:31
bsvdefault section?13:31
kodokuand remove messaging from nova.conf in your notification_driver13:31
bsvkodoku: dont you mean rename messaging to messagningv2 ?13:32
kodokuyes13:33
bsvhm no sink events.13:34
bsvkodoku: where did you want that control_exchange=nova entry?13:35
bsvI have it in my designate.conf under handler:nova_fixed13:35
kodokuyes13:35
kodokuthis is for designate and nova have same exchange name13:36
kodokureboot compute node and designate sink ?13:36
bsvi just restarted the service13:36
kodokuyes is good13:36
leitanmugsie, sadly 16.04 is shipped only with powerdns 4.0 -> oot@mgmt01:~# apt-cache madison pdns-server13:36
kodokuhum13:36
leitanpdns-server | 4.0.0~alpha2-3build1 | http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages13:36
leitan      pdns | 4.0.0~alpha2-3build1 | http://us.archive.ubuntu.com/ubuntu xenial/universe Sources13:36
kodokuon your rabbit node13:37
mugsieleitan: https://downloads.powerdns.com/releases/deb/pdns-static_3.4.9-1_amd64.deb13:37
kodokubsv launch => rabbitmq-plugins enable rabbitmq_management13:37
kodokuand restart rabbitmq server13:37
mugsiethat is built by pdns themselves13:37
kodokugo on http://rabbitmqnode:1567213:38
kodokudon't forget to open 15672 tcp port on rabbitmq13:38
leitanmugsie, yes, i was doing exactly that, just for you guys to know if someone has a similar issue, want me to fill a bug ?13:38
kodokubsv then go to queue and search notifications_designate13:38
*** johnbelamaric has joined #openstack-dns13:38
bsvkodoku: hmm port 15672 not listening13:40
mugsieleitan: I filed it13:40
kodokubsv you have restart rabbit ?13:40
leitanmugsie, great !13:40
bsvyes, just a sec, this is a vm so I'll just reboot it.13:40
kodokuyou can just restart service ;)13:41
bsvthe compute node is ~15 mins to reboot :)13:41
bsvI did, no luck13:41
bsvand its up13:42
kodokubsv  netstat -laputen | grep LISTEN | grep 15672  return nothing ?13:42
bsvtcp        0      0 0.0.0.0:15672           0.0.0.0:*               LISTEN      1392/beam.smp13:43
kodokugood13:43
kodokurabbitmq listen13:43
bsvyes, got http now13:43
kodokuok use guest/ guest for user/pass13:44
bsvim in13:44
kodokudo you see queue ?13:44
bsvim seeing pools, mdns13:45
bsvnoyigivsyiond<-frdihnsyr.ingo13:45
bsvwau13:45
bsvnotifications_designate.info13:45
kodokugreat13:45
kodokugo on13:45
bsvno events13:46
kodokuok13:46
kodokudo you have a bindings and a consummer ?13:46
bsvyes13:46
kodokuok consummer is your designate sink service13:46
kodokuand bind is nova-compute13:46
bsvdoes not look that way13:46
bsvnova13:47
kodokuyou have messagingv2 in nova.conf on compute node ?13:47
bsvyes13:47
bsvnotification_driver = nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier,messagingv213:47
kodokuok13:47
kodokuyou see a queued message graph ?13:48
bsvyes13:48
kodokuand Message rates  graph ?13:48
bsv0 ready, 0 unack, 0 total13:48
kodokufor messages rates ?13:48
bsvlet me check the mapping between consumer portnumber and the sink service...13:49
kodokuyes :)13:49
bsvstopped the sink service, the consumer was removed. So success on that part. Sink is connected.13:51
kodokuyes13:51
kodokunow start VM13:51
kodokuyou sould see activities in messages rate graph13:51
bsvnothing13:52
bsvspawned 4 instances13:52
kodokuyou have one compute ?13:53
mugsieok. that means nova is not spitting events out13:53
mugsieis there any logs on the instance?13:53
bsvI have 2 compute for testing avail. zones.13:53
bsvI spawned 2 instances on each compute node.13:53
kodokudo you have messagingV2 on each node ?13:53
bsvonly testing on one computenode atm.13:54
bsvyou think that could mess messagning up?13:54
leitanmugsie, kodoku , switched to powerdns 3.4, still seeing the same thing, when i add a new record, mdns wants to perform SOA update on pdns, and pdns answers with 0, or lower, but when full AXFR is performed the records got update13:54
kodokuleitan hey13:54
kodokuopen udp port on mdns server13:54
kodoku535413:54
kodokuand send your mdns log13:55
kodokubsv I test with one compute13:55
kodokuI paste my nova.conf13:55
leitankodoku, its open already13:56
leitanroot@mgmt00:~# netstat -aupna | grep 535413:56
leitanudp        0      0 0.0.0.0:5354            0.0.0.0:*                           28343/python13:56
kodokubsv http://paste.openstack.org/show/508937/13:57
kodokuleitan send log ;)13:58
kodokuand your pdns conf13:58
leitankodoku, http://paste.openstack.org/show/508938/14:00
bsvstuff is happening now14:01
kodokubsv when nova compute start I can see sr/lib/python2.7/site-packages/oslo_config/cfg.py:252114:02
*** kodoku_ has joined #openstack-dns14:02
kodoku_sorry client bug14:02
kodoku_bsv when compute start I can see in log sr/lib/python2.7/site-packages/oslo_config/cfg.py:2521 2016-06-08 16:00:03.731 18067 DEBUG oslo_service.service [req-78004a14-1ec4-46af-af7d-a9ef71dd70eb - - - - -] aggregate_image_properties_isolation_separator = . log_opt_values /usr/lib/python2.7/site-packages/oslo_config/cfg.py:2521 2016-06-08 16:00:03.731 18067 DEBUG oslo_service.service [req-78004a14-1ec4-46af-af7d-a9ef71dd70eb - -14:02
kodoku_arf14:03
kodoku_oslo_messaging_notifications.driver = ['nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier, nova.openstack.common.notifier.rpc_notifier', 'messagingv2']14:03
kodoku_check on oslo_messaging_notifications.driver14:03
*** kodoku has quit IRC14:03
leitankodoku_, http://paste.openstack.org/show/508939/14:03
bsvi'll be offline for a few hours, off work now. Working later again. Either that single line of notifications_driver did the trick. or that extra driver you used.14:03
bsvI will check details later and report bacl ;)14:04
bsvback;)14:04
kodoku_ok ;)14:04
kodoku_leitan I check log14:04
leitankodoku_, thanks14:04
*** bsv has quit IRC14:05
*** ducttape_ has joined #openstack-dns14:05
*** kodoku has joined #openstack-dns14:05
*** kodoku_ has quit IRC14:05
leitankodoku, here the designate.conf + pools.yml -> http://paste.openstack.org/show/0rNfxA3viBbygHzcNn2m/  if helps14:07
kodokuleitan I can see your paste logs14:08
kodokuhttp://paste.openstack.org/show/508939/ ??14:08
leitankodoku, yes http://paste.openstack.org/show/508938/14:09
*** ducttape_ has quit IRC14:09
kodokuOk yesterday I have same issue14:09
kodokucan you try with iptable stop on your mdns server14:10
kodokuand 10.100.0.101 is your pdns server ?14:10
kodokuyou send NOTIFY to localhost14:11
kodokuNOTIFY' for 'mycloud.com.' to '127.0.0.1:53'14:12
kodokuwrong config14:12
kodokuyou should send notify to pdns node14:12
leitanits sending to both, dont know why14:12
kodokuno14:12
kodokusending SOA to  10.100.0.10114:12
kodokubut sending NOTIFY to 127.0.0.114:12
kodokuif notify doesn't work, SOA can't work14:13
leitanok, how can i change that, here is the designate conf  http://paste.openstack.org/show/0rNfxA3viBbygHzcNn2m/14:13
leitanwhat im missing ?14:13
leitanalso the pool.yml is there14:13
kodokuwhat is IP of ns1.osscloud.com.14:14
kodoku?14:14
leitani added an A registry pointing to the 10.100.0.10114:14
mugsieleitan: https://etherpad.openstack.org/p/leitan-designate-pools14:14
leitanon the designate domains14:14
mugsiethe highlighted section14:14
mugsieyou need to add that to pools.yaml14:15
kodokuyes missing this option14:15
mugsie(the host and port in the options section)14:15
mugsieits the weird way our power dns driver works - it needs it redefined there14:15
mugsieso, add that, run designate-manage pool update, and restart pool-manager14:16
leitanmugsie, doing i14:16
leitant14:16
*** pglass has joined #openstack-dns14:17
kodokumugsie Can I copy policy.json (from /etc/designate/) to horizon policy folder ?14:17
leitanmugsie, syntax error maybe missing the "-" on the host ?14:18
*** EricGonczer_ has joined #openstack-dns14:19
kodokuleitan I add my pool.yaml if you want14:20
leitanfixed, seems some weird character going on14:21
leitanok pool updated14:21
*** jhfeng has joined #openstack-dns14:21
leitanrestarting pool-manager14:21
kodokuand mdns14:21
kodoku;)14:21
leitanrestaring mdns14:22
leitanim gonna try to add a new record14:22
leitankodoku, mugsie WORKING !14:24
leitanleitan@macuntu:~$ dig @10.100.0.101 kodoku.osscloud.com14:24
leitankodoku.osscloud.com.3600INA10.100.0.10114:24
leitan:D14:24
*** mlavalle has joined #openstack-dns14:25
leitanok, now its time to nova+neutron integration, im running mitaka, should my existing ips synchronize with the dns, or just the new ones ?14:26
kodokugood domain :)14:26
*** jmcbride has joined #openstack-dns14:27
leitankodoku, haha, just to be sure, are my fixed_ip and floating_ip sections ok on the designate conf file ?14:29
leitanhttp://paste.openstack.org/show/0rNfxA3viBbygHzcNn2m/14:30
kodokuI check14:30
kodokuyou use mitaka?14:30
leitanyes14:30
leitani not seeing any message on the notifications queue14:30
kodokuchange domain_id by zone_id14:30
leitanok14:30
kodokuand domain by zone in format14:31
kodokuand you need to conf nova.conf on your compute for nova14:31
mugsiekodoku: horizon policy - yes14:31
kodokusend your nova.conf (on compute node)14:31
kodokumugsie ok good :)14:31
leitankodoku, changed domain_id to zone and zone on format on both section14:32
leitanill send you the neutron.conf + nova.conf14:32
*** pglass has quit IRC14:32
kodokuyes14:33
kodokuand yes14:33
leitankodoku, http://paste.openstack.org/show/xHZh7g5HYOtstJVA3DTI/14:35
*** james_li has joined #openstack-dns14:35
kodokuadd notification_driver = messagingv2 in nova.conf14:37
leitanok, default section ?14:37
leitancomputes + controllers ? only compute ?14:37
kodokucompute14:37
kodokuand you have already a notification_driver14:37
kodokujust after this line14:37
kodokuand add14:37
kodokunotify_on_state_change=vm_and_task_state14:37
kodokuho sorry it's neutron.conf first14:38
kodokulook my nova.conf14:40
kodokuhttp://paste.openstack.org/show/508937/14:40
kodokunotification_topics must be same in your designate.conf14:40
kodokufor you it's dnsnotifications14:40
kodokuso notification_topics=notifications,dnsnotifications14:41
leitani have a shovel on notifications to reflects on the queue dnsnotifications on the designate vhost14:41
leitanso i should put notifications here14:42
leitanill add both, no harm here14:42
leitanok done14:43
leitanrestart nova-compute ?14:43
kodokunova and designate communicate by rabbit. So both need to have acces to same vhost14:43
kodokusame for neutron14:43
leitankodoku, i have the neutron vhost also, so i cant do it like that, i need to configure rabbit shovels14:43
kodokumugsie can you confirm ?14:43
kodokuI'am no pro with rabbit :/14:44
mugsiekodoku: sure - let me read the scrollback14:45
leitanhere /nova.notifications -> shovel > /designate.dnsnotifications14:45
leitanand /neutron.dnsnotifications -> shovel -> /designate.dnsnotifications14:45
leitani had this working on kilo :)14:45
*** Kdecherf has joined #openstack-dns14:45
mugsiekodoku: do you have separate vhosts?14:45
kodokunot me, it's for leitan :)14:45
mugsieah, yes14:45
Kdecherfhello there, i'm currently trying designate on mitaka14:45
mugsiebut, yeah, the shovel should work14:45
*** Alex_Stef has quit IRC14:45
mugsieKdecherf: hey14:45
Kdecherfis there a way to restrict clients that can make AXFR requests to designate-mdns?14:46
leitankodoku, ok, nova-compute restarted14:46
leitanwhat should i add on neutron ? same lines ? on neutron.conf where neutron-server is running ?14:46
leitanbasically the controllers14:46
mugsieyeah14:46
kodokumugsie on dns tab (horizon) I can see a message14:47
kodokuWarning: The quotas could not be retrieved.14:47
kodokudo you have quota for dns ?14:48
mugsiewe do14:48
mugsiebut that is usually due to nova issues14:48
kodokuok14:49
mugsieoh, wait14:49
mugsienope, someone added support14:49
kodokufor remove this warning ?14:49
mugsieif you add "quotas" to the v1_extentions list it should work14:49
kodokuok14:49
leitankodoku, added messagingv2 and notification topics on neutron14:49
leitanill restart neutron-server14:50
leitanok ?=14:50
kodokuy14:50
kodokuand nova compute14:50
kodokuservice14:50
kodokutail sink log and create a VM14:50
leitanyes already restart compute14:52
leitanok, ill create a vm now14:52
mugsiekodoku: or, in the copy of the policy.json on the horizon host set the "get_quota" policy to "!"14:52
mugsiethat will make horizon think it cannot get quotas, and skip it14:53
mugsieand not log the error14:53
kodokumugsie I have already enabled_extensions_v1 = diagnostics, quotas, reports, sync, touch14:54
mugsieweird  -is there any logs on the designate-api server to say what happened?14:55
kodokumugsie on API I have get_quotas: Calling central's get_quotas.14:58
kodokuon central => Policy check failed for rule 'all_tenants' on target {}14:58
kodokuafter Policy check succeeded for rule 'get_quotas' on target {'tenant_id': u'da4059ca3e324a7793fca6d3aaf613dc'}14:59
kodokuI try with ! in get_quota14:59
kodokuok no warning now :)15:00
*** fawadkhaliq has joined #openstack-dns15:00
kodokubut I have always request on api15:00
kodokuarf message again15:01
mugsiekodoku: and it is the policy file on the horizon node, right?15:03
kodokuy15:05
kodokuarf15:05
kodoku"get_quotas": "!",15:05
kodokubut "get_quota": "rule:admin_or_owner",15:05
kodoku-_-15:05
kodokuI guess the devil works for openstack foundation15:06
kodokuto have nightmares all OPK engineers15:07
*** pglass has joined #openstack-dns15:08
leitankodoku, no records are created, and vm creation, deletion, floating ip attachment are considerely SLOWER15:15
kodokuok first on nova15:16
leitanok tell me15:17
leitankodoku, hmmm im seeing an error of that the notification queue is set to durable=True15:18
kodokuleitan you see nothin in sink log ?15:22
leitannothing but i think i know why15:22
kodokumugsie ok no warning good :)15:22
*** james_li has quit IRC15:24
*** jschwarz has quit IRC15:26
*** james_li has joined #openstack-dns15:26
*** dmk0202 has quit IRC15:29
*** rudrajit has joined #openstack-dns15:30
leitankodoku, ok floating ips working15:32
leitandnsnotifications.info was getting redifined by the shovel, had to delete the shovel, recreate the queue restart neutron and create the shovel again15:33
leitanto make it durable=False15:33
leitanill try fixed_ips15:33
kodokugreat15:36
leitankodoku , okkkk fixed working too15:41
leitankodoku, mugsie thanks for the support guys !15:41
leitanyou rock15:41
mugsieleitan: np - though kodoku deserves most of the credit :)15:44
*** rudrajit has quit IRC15:47
kodokuleitan \o/15:47
kodokumugsie in 2 days, 3-4 users have same pb15:48
mugsieyeah15:48
kodokuMaybe need to ad docs15:48
kodokuadd*15:48
* mugsie needs to go write docs tomorrow15:48
kodoku:D15:48
mugsieand learn sink again today15:48
leitanmugsie, kodoku if you want guys i can help with the documentation15:49
leitani know it sucks15:49
leitanto document stuff15:49
kodokuI think dependency with other service ,like nova or neutron, missing on docs15:50
kodokufor sink15:50
kodokuand add a firewall section15:50
kodokuI go to home. bye15:52
mugsieleitan: I will do - thanks15:52
*** abalutoiu has quit IRC15:54
*** ivase has joined #openstack-dns15:54
leitanmugsie, ok no problem15:55
*** chlong has quit IRC15:58
*** ducttape_ has joined #openstack-dns16:06
*** fawadkhaliq has quit IRC16:07
*** ducttape_ has quit IRC16:10
*** dxu has joined #openstack-dns16:25
dxuHi all, I'm having some trouble with Designate. I was wondering if anyone could help16:26
dxuI've followed this guide (http://docs.openstack.org/developer/designate/install/ubuntu-kilo.html) and installed Designate alongside a DevStack instance16:27
dxuBut it looks like designate has trouble connecting to BIND916:27
dxuThe pool manager is giving me this error about `No targets for <Pool id:'.......c842' name:'default'> found.`16:28
dxuDoes anyone have any ideas?16:28
mugsiedxu: what version are you trying to install?16:37
mugsieit looks like mitaka16:37
Kdecherfis there any work in progress to add an experimental support of ALIAS record type? (non-standard)16:40
mugsieKdecherf: yes, - but it is failing gate16:41
mugsieelarson: was writing it16:41
dxumugsie: I'm installing from the master branch of designate16:41
mugsiedxu: Ah, ok. kilo is a much older version16:41
*** fawadkhaliq has joined #openstack-dns16:42
*** fawadkhaliq has quit IRC16:42
Kdecherfmugsie elarson what is the status of the work?16:42
*** fawadkhaliq has joined #openstack-dns16:42
mugsiedxu: http://docs.openstack.org/developer/designate/pools.html16:42
mugsiehttp://docs.openstack.org/developer/designate/backends/bind9.html has an example pools.yaml sample16:43
mugsieKdecherf: stalled, afaik16:43
dxumugsie, Thank you, I will take a look at that.16:43
mugsieit is a tough job16:43
Kdecherfmugsie: i could be interested to contribute :)16:44
*** rudrajit has joined #openstack-dns16:44
elarsonKdecherf: I have a branch that has had some trouble merging as it sat for a while. I need to redo it, but it was functional. unfortunatly, other priorities got in the way16:50
Kdecherfelarson: let me know if i can help (or/and if i can test it)16:51
elarsonKdecherf: here is the latest https://review.openstack.org/#/c/311204/16:52
Kdecherfelarson: thanks, i will check that16:55
*** james_li has quit IRC16:56
elarsonKdecherf: thanks! Let me know if you have any questions I can help answer!16:57
*** ducttape_ has joined #openstack-dns17:01
dxuHow do I reload any changes to designate.conf?17:02
*** ducttape_ has quit IRC17:03
*** ducttape_ has joined #openstack-dns17:04
elarsondxu: restarting the process should pick up the changes17:06
dxuelarson, Would that process be designate-central?17:08
*** bpokorny has joined #openstack-dns17:12
elarsondxu: whatever process that has changes you need to pick up :)17:14
dxuelarson, Makes sense. Thanks!17:14
dxuNow I'm getting designate-rootwrap not found. A quick search on the documentation/google hasn't turned up anything. Where does that command come from? I see the rootwrap.conf files in the etc/designate directory17:15
elarsondxu: the rootwrap is some configuration that determines how designate tries to call commands as root (ie like rndc)17:17
elarsondxu: not sure your use case, but you can try running processes as root17:17
elarsonI think pool manager is probably the only one that needs it17:17
dxuRight, it's pool manager that's giving me the rootwrap error. It looks like it's trying to do something like `sudo designate-rootwrap ....`17:19
dxuSo designate-rootwrap must be some kind of script, it's just I can't locate that script17:19
elarsondxu: exactly17:19
elarsondxu: there is a etc/designate/rootwrap.conf.sample in the repo17:20
* elarson just finished a taco so will hopefully be a little less curt with answers ;)17:22
elarsondxu: http://docs.openstack.org/developer/designate/install/ubuntu-dev.html provides a little more insight17:23
elarsonyou can see in the docs we run a script to copy all the *.sample files to get the basic configuration in place17:24
elarsonwhich includes the rootwrap bits17:24
dxuI uncommented the line `# root_helper = sudo` and restarted everything and it seemed to do the trick. Thanks again for all your help!17:24
elarsondxu: my pleasure!17:25
dxuIs it at all possible to run designate so that for every project that gets created in an openstack cluster, that project gets assigned its own isloated DNS server? The idea is that I want to run one DNS server instance and have multiple tenants inside that one server.17:42
mugsiedxu: right now, no.17:43
mugsieyou can multiple pools of servers, but they are shared by all users17:43
mugsiewait, re reading that17:44
mugsieyou want a single instace of bind / powerdns / what ever17:44
mugsieand have all projects share it?17:44
mugsiethat is what we do currently17:44
elarsondxu: the thing to remember is that designate doesn't mess with the actual dns server outside of administering the data. you still need to provision the actual dns servers (ie bind, powerdns, etc) yourself.17:47
dxumugsie, Yes, I just want a single instance of bind/powerdns/w.e and have all projects share it. But the caveat is that no one project can see entries from other projects17:47
dxuelarson, That's what I thought. I just wanted to double check17:48
mugsiedxu: well, they wont be able to see each others domains in the API17:49
mugsiebut they can query the DNS server17:49
mugsiewhen you say "see" do you mean in the API, or on the DNS server?17:50
dxuOn the DNS server17:50
mugsiewell, with the way DNS works anyone has to be able to query the dns server17:50
*** dxu has quit IRC17:50
*** dxu has joined #openstack-dns17:51
*** ChanServ changes topic to "OpenStack Designate - Logged @ http://eavesdrop.openstack.org/irclogs/%23openstack-dns | Review Dashboard @ http://graham.hayes.ie/designate/dashboard"17:52
mugsiedxu: well, with the way DNS works anyone has to be able to query the dns server17:52
dxuLet me back up and explain the scenario first. Right now we have a big openstack cluster where teams a provisioned projects. Some teams want to set up complex network topologies and test some network software. What they have to do right now is manually spin up instances with a manually configured DNS server17:54
dxuWhat I'd like to do is have some kind of setup where every project automatically gets assigned an isolated DNS server17:54
dxuThis is what I initially thought designate did to be honest17:55
mugsieah17:55
mugsieOK.17:56
mugsiewe are looking to do private DNS Servers, but at some popint in the future17:56
mugsiedesignate is mainly about service provider DNSaaS (like DynECT / Rackspace DNS / HP Cloud DNS )17:57
dxuRight, it took watching a few conference videos to figure that out haha17:57
dxuI think it would be helpful if this project had a "why choose designate" explanation somewhere17:57
mugsiedxu: noted - will add it ot the list of docs17:58
mugsiefor those teams, is there any reason the DNS Server has to be islolated>17:59
mugsie?*17:59
*** jhfeng has quit IRC17:59
dxuThe engineers get lazy and share the same heat templates, which means same instance names everywhere. They also make the DNS name of each host the same as the instance name, so we would see collisions if the DNS servers are not isolated18:02
*** jhfeng has joined #openstack-dns18:03
mugsieah, ok.18:04
mugsiein heat, you could just have a "prefix" input, that prepends to the zone name?18:05
dxuSo something like host1.PREFIXzone.domain.com?18:06
mugsieyeah18:08
dxuWell that would require a change made to the heat template every time, no?18:08
mugsieyou specifiy it as an inpout to the template18:09
mugsiethen it would have to supplied every time the stack is booted, wihtout changing the actual tempate18:09
-openstackstatus- NOTICE: Zuul has been restarted to correct an error condition. Events since 17:30 may have been missed; please 'recheck' your changes if they were uploaded since then, or have "NOT_REGISTERED" errors.18:10
elarsonmugsie: we should think about supporting service discovery like consul with designate18:10
elarsonseeing as there are two concepts of dns out there, the traditional mode, which designate does well and the service discovery bits which designate hasn't really explored18:11
elarsonit might be more of a client piece...18:12
dxumugsie, Ah, that makes sense. I'm not very familiar with the heat stuff yet. I'll look into that, but my initial concern is that the teams run the templates as part of continuous integration, and that this would be a breaking change or be even more work than just spinning up an image of a DNS server18:12
elarsonanyway thinking aloud!18:12
mugsieelarson: yeah, I have thought of that alright.18:12
mugsiemu concern is the propagation time18:12
mugsiefor service discovery that has to be *fast*18:12
mugsieas in, oh crap, my DB is on fire, swap hosts18:13
elarsonmugsie: that would really depend on name server. if the zone is mapped to a specific cluster local dns server, then that doesn't matter much18:13
mugsiedxu: yeah, it was just an idea from the top of my head.18:13
dxumugsie, :)18:16
*** jhfeng has quit IRC18:26
*** jhfeng has joined #openstack-dns18:32
*** bpokorny has quit IRC18:33
*** bpokorny has joined #openstack-dns18:33
*** AJaeger has joined #openstack-dns18:34
*** AJaeger has left #openstack-dns18:34
*** jmcbride has quit IRC18:35
*** bpokorny has quit IRC18:38
*** bpokorny has joined #openstack-dns18:40
*** jmcbride has joined #openstack-dns18:43
*** ducttape_ has quit IRC18:49
*** ducttape_ has joined #openstack-dns18:51
*** nyechiel has quit IRC18:58
*** nyechiel has joined #openstack-dns19:03
*** ducttape_ has quit IRC19:07
*** nyechiel has quit IRC19:11
*** ducttape_ has joined #openstack-dns19:22
*** bpokorny has quit IRC19:35
dxuWhere can I find some examples of sample notification handlers for sink?19:41
*** bpokorny has joined #openstack-dns19:42
mugsiedxu: https://github.com/openstack/designate/tree/master/contrib/designate-ext-samplehandler19:43
dxuThanks!19:44
*** kodoku has quit IRC19:56
*** fawadkhaliq has quit IRC20:01
*** fawadkhaliq has joined #openstack-dns20:01
*** fawadkhaliq has quit IRC20:05
*** EricGonczer_ has quit IRC20:06
*** bpokorny has quit IRC20:07
*** bpokorny has joined #openstack-dns20:13
*** EricGonczer_ has joined #openstack-dns20:14
*** bpokorny has quit IRC20:30
*** openstackgerrit has quit IRC20:48
*** openstackgerrit has joined #openstack-dns20:48
*** ChanServ sets mode: +v openstackgerrit20:48
*** nyechiel has joined #openstack-dns21:04
*** chlong has joined #openstack-dns21:06
*** ivase has quit IRC21:13
*** nyechiel has quit IRC21:15
*** jmcbride has quit IRC21:16
*** EricGonczer_ has quit IRC21:18
*** jmcbride has joined #openstack-dns21:26
openstackgerritBenjamin George proposed openstack/designate: Add etc/designate/*.yaml to .gitignore  https://review.openstack.org/32734421:27
*** sonuk has joined #openstack-dns21:29
*** sonuk has quit IRC21:36
*** johnbelamaric has quit IRC21:36
*** rudrajit_ has joined #openstack-dns21:38
elarsonour intern's first patch!!!!! ^^^^21:39
*** rudrajit has quit IRC21:41
dxuIs there documentation for writing neutron handlers? All I could find were conference videos that are slightly old21:43
openstackgerritBenjamin George proposed openstack/designate: Add etc/designate/*.yaml to .gitignore  https://review.openstack.org/32734421:56
openstackgerritOpenStack Proposal Bot proposed openstack/designate: Updated from global requirements  https://review.openstack.org/32736421:57
*** ducttape_ has quit IRC21:57
*** jmcbride has quit IRC21:59
*** ducttape_ has joined #openstack-dns22:04
*** pglass has quit IRC22:08
*** sonuk has joined #openstack-dns22:14
*** ducttape_ has quit IRC22:16
*** bpokorny has joined #openstack-dns22:19
*** ducttape_ has joined #openstack-dns22:20
*** sonuk has quit IRC22:22
*** leitan has quit IRC22:23
*** mlavalle has quit IRC22:38
*** fawadkhaliq has joined #openstack-dns22:44
*** jhfeng has quit IRC22:48
*** ducttape_ has quit IRC23:03
*** ducttape_ has joined #openstack-dns23:04
*** rudrajit_ has quit IRC23:13
*** fawadkhaliq has quit IRC23:17
*** fawadkhaliq has joined #openstack-dns23:18
*** fawadkhaliq has quit IRC23:21
*** Daviey has joined #openstack-dns23:34
*** kei_yama has joined #openstack-dns23:36
*** ducttape_ has quit IRC23:57
*** ducttape_ has joined #openstack-dns23:58

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