On 2/19/16 10:24 PM, John Belamaric wrote:
Thanks for the quick response!
On Feb 19, 2016, at 6:03 PM, Andrew Bogott <[email protected]> wrote:
I'm running designate kilo with a pdns backend. I originally set things up
in Juno, with designate-central syncing directly to the pdns mysql backend.
Everything was stable until my upgrade to Kilo. During the upgrade to Kilo I
was advised to add the mdns service, which I did, and I got things mostly
working. Every once in a while my pdns service falls over, though, and the
pdns logs are VERY strange.
As best I can tell, I am now (accidentally) using two simultaneous pdns
backends: designate-central writes directly to the pdns mysql database, but
mdns also sends sync requests which causes pdns to grab records via AXFR and
write them to the database (even though they are already there, thanks to the
direct writing by central). As you can imagine, this allows for a host of
weird race conditions.
The docs for this are baffling -- designate design is changing rapidly and
most docs are unversioned, so it's hard for me to know what I'm looking at.
Here are my questions:
1) Is it still possible to have central write directly to mysql backend? Can
I, in that case, simply turn mdns off, switch my pdns service to master=false
slave=false and live happily and simply?
2) If, on the contrary, I'm meant to do this via AXFR, why do the docs still
tell me to configure designate with access to the pdns mysql backend?
As I understand it, in Kilo and later mdns must be primary and send data to
other backends via XFR.
OK -- I can think of reasons for that choice. Why then, does
http://docs.openstack.org/developer/designate/backends/powerdns.html
suggest that I specify this setting in the designate config?
connection sqlite:///$pystatepath/powerdns.sqlite Database connection
string
Is that still needed? If so... what does it do?
3) (meta-question) Is there a designate-specific list, or new IRC channel I
should be using? I have in the past gotten good support in
#openstack-designate on freenode, but that channel has been utterly silent for
several months.
Try #openstack-dns instead.
Ah! I now see that in addition to openstack-nova there is an
invite-only openstack-compute channel, and in addition to
openstack-keystone there is an invite-only openstack-identity, etc.
We're really committing to the "two names for everything" gag :)
-A
Thanks all!
-Andrew
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
