Designate Sink is no longer required

[Kyle Dean]

**Bug Report**
Whats happening
Fixed IPs were being registered in designate.

What i expected to happen
Floating IPs to be registered in designate.

How to reproduce it:
Deploy kolla

Follow instructions on https://docs.openstack.org/kolla-ansible/latest/reference/networking/designate-guide.html

**Environment**:
* OS Ubuntu
* Kernel 5.4.0-66
* Kolla-Ansible version: stable/victoria
* Docker image Install type: source
* Docker image distribution: ubuntu
* Are you using official images from Docker Hub or self built: self built
* Kolla version and environment used to build: stable/victoria

After spending quite a while on the designate IRC with @johnsom

the following bug was found. Designate-sink is no longer required and neutron now publishes DNS records directly in designate.

I had to make the following changes to the global designate config.

This was missing. when backend TLS set to true
[network_api:neutron]
ca_certificates_file = /etc/ssl/certs/ca-certificates.crt

Do not put zone ID in the following sections. I believe these two attributes can be removed since designate-sink no longer registers DNS entries.
[handler:nova_fixed]
zone_id =

[handler:neutron_floatingip]
zone_id =

Stop designate sink completely. as this clashes with neutron.

I made the following modification to. the ml2 conf in neutron.

[ml2]
extension_drivers = port_security,dns_domain_ports

in the neutron.conf the following attribute is only used for internal DNS according to the Docs.
https://docs.openstack.org/neutron/latest/admin/config-dns-int.html

[DEFAULT]
dns_domain = example.com

Hope this helps.

Kind regards,

K

[Mark Goddard (mgoddard)]

Hi Kyle, thanks for raising the bug. I looked through the Designate release notes and can't find anything about designate sink not being required. I wonder why the service still exists if it is not necessary (and even harmful)?

Can you or Michael provide some more information:

* should we stop deploying designate-sink entirely?
* in which release was this change introduced?
* should we update our documentation to avoid the configuration of the handlers?

[Mark Goddard (mgoddard)]

Could you raise a separate bug for the internal TLS issue?

[Kyle Dean (k.s-dean)]

Hi Mark, hopefully this specific sentence. will help.

hamalq johnsom: thanks, also no need to use sink when u enable the neutron external dns plugin

[John Garbutt (johngarbutt)]

I think it would be nice to make the designate sync optional, as you say, its not required when you use the neutron extrnal dns plugin. Moreover, I think it is best to only use one of those, either designate sync OR the external dns interation.

The case where I think sync still works nicely, is where you have a provider network shared with mulitple projects, so the dns_name on the shared network doesn't really map to zone's owned by each project using the shared network. You could override per port the domain_name, I think, but that seems like a special case.

[Gaël THEROND (gtherond)]

This was fixed within master, we need to backport changes to supported releases that would still be affected.

[Sven Kieske (s-kieske)]

is this the fix? https://review.opendev.org/c/openstack/kolla-ansible/+/861958 users are asking about it/what fix they need.

the above fix only enables the sink if designate is enabled, however in this bug it is discussed, to disable the sink when neutron external dns is used. is there something missing?

please always link bugfixes to bugreports, avoiding unneccessary repository archaeology for future users and devs, thank you very much in advance.