Designate

Add support for binding mDNS and API to multiple IP:PORT pairs

Bug #1536304 reported by Kiall Mac Innes on 2016-01-20

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Designate	Fix Released	Medium	Kiall Mac Innes	Designate mitaka-3 "m3"

In some environments, it may be necessary to bind mDNS / the API to multiple IP:PORT pairs, rather than the the 1 we support today.

One example of this is where mDNS and API servers have both a public facing and internal NIC / address.

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-01-20: Fix proposed to designate (master)

Fix proposed to branch: master
Review: https://review.openstack.org/270359

Changed in designate:
status:	Triaged → In Progress

Revision history for this message

Change abandoned by Graham Hayes (<email address hidden>) on branch: master
Review: https://review.openstack.org/270359
Reason: message

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2016-05-04: Fix merged to designate (master)

commit 82fcd5438e8c1dcb95e3d83fe185857366070812
Author: Kiall Mac Innes <email address hidden>
Date: Wed Jan 20 17:56:56 2016 +0000

Support multiple API and mDNS listen address pairs

Change-Id: Ic672e0f693b8f63abb729b560753cc75fb3c7094
Closes-Bug: 1536304

Changed in designate:
status:	In Progress → Fix Released

Revision history for this message

This issue was fixed in the openstack/designate 3.0.0.0b1 development milestone.

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.