designate mdns should be at network nodes

Bug #1693918 reported by Eduardo Gonzalez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Eduardo Gonzalez
Ocata
New
Undecided
Unassigned
Pike
Fix Released
Undecided
Eduardo Gonzalez

Bug Description

Designate mDNS service publish DNS service to public network to be accessible by instances and external networks.

External published networks should only be in network nodes.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/468534
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=1f1d91b960ad8bc2b18e60ce1dd7ee0a16f46a3f
Submitter: Jenkins
Branch: master

commit 1f1d91b960ad8bc2b18e60ce1dd7ee0a16f46a3f
Author: Eduardo Gonzalez <email address hidden>
Date: Fri May 26 21:19:07 2017 +0100

    Move mDNS to network nodes

    mDNS publish DNS services to designate service customers.
    Only network node should be reachable by public networks.

    Change-Id: Id2947df89d2d831d67e006a581ac88b4ecf8ce04
    Closes-Bug: #1693918

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.0.0b3

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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