Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1955362

Summary:	[RFE] Designate communication changes from RHOSP 13 to RHOSP 16
Product:	Red Hat OpenStack	Reporter:	Cristian Muresanu <cmuresan>
Component:	openstack-designate	Assignee:	Nate Johnston <njohnston>
Status:	CLOSED NOTABUG	QA Contact:	Toni Freger <tfreger>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	cmuresan, njohnston, scohen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-12 14:40:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cristian Muresanu 2021-04-29 22:58:20 UTC

Description of problem:

In RHOSP16, Can Nova and Neutron be configured to communicate with Designate via the RabbitMQ message bus?

In OSP13, Nova and Neutron write messages to RabbitMQ and Designate reads those messages via the Designate-Sink process in order to take action.
Our understanding is that in OSP16.1, Nova and Neutron communicate with Designate via direct API calls.

We have customizations to Designate Sink that help us conform to our DNS naming standards, to restrict which addresses get FQDNs, and to add automatic PTR records.

We would like to know if Designate Sink can still be used in OSP16.1 by having Nova and Neutron write messages to the Rabbit Queues as was done previously.

Can Nova and Neutron be configured to communicate with Designate via the RabbitMQ message bus?  If so, great.  If not, then we cannot actually make use of the Designate-Sink feature.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Nate Johnston 2021-05-12 14:40:01 UTC

We confirmed that Nova and Neutron still send notifications through RabbitMQ, so any process depending on that should still work.  That is a functionality of the base ML2 Neutron plugin, not an aspect of the mech driver change from ML2/OVS to ML2/OVN.  So there should be no change needed here.