No need for default DNS

Bug #1367877 reported by Steve McLellan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Fix Released
High
Ekaterina Chernova

Bug Description

NeutronNetwork requires a dns nameserver when it deploys a subnet. I can't see any reason to require it, nor configure a server-wide default. IIRC, if no nameserver list is provided to a neutron subnet, it uses the DHCP (gateway) address which in turn forwards to dnsmasq.

Unless i'm wrong about that, i suggest removing the `[networking]/default_dns` config option, and the useDefaultDNS flag from NeutronNetwork. If an explicit dns nameserver list is given, it can be added to the template, but the dns_nameservers attribute can otherwise be an empty list (the heat default).

A mandatory default can do more harm than good, since it means duplicating configuration details from the cloud to the murano configuration.

Changed in murano:
status: New → Confirmed
importance: Undecided → High
milestone: none → juno-rc1
Changed in murano:
assignee: nobody → tcs_openstack_group (tcs-openstack-group)
Revision history for this message
bharaththiruveedula (bharath-ves) wrote :

Actually I feel we don't need to pass any dns value to Heat. So do you
want me to totally remove the "default_dns" parameter or make it
optional i.e., if that option is there we pass it to heat otherwise we
don't?

Revision history for this message
Serg Melikyan (smelikyan) wrote :

I think we should remove this option completely

Changed in murano:
assignee: tcs_openstack_group (tcs-openstack-group) → Akhila C (chetlapalle-akhila-b)
assignee: Akhila C (chetlapalle-akhila-b) → tcs_openstack_group (tcs-openstack-group)
Changed in murano:
assignee: tcs_openstack_group (tcs-openstack-group) → bharaththiruveedula (bharath-ves)
ruhe (ruhe)
Changed in murano:
milestone: juno-rc1 → none
Changed in murano:
assignee: bharaththiruveedula (bharath-ves) → nobody
Changed in murano:
milestone: none → kilo-1
Changed in murano:
milestone: kilo-1 → kilo-2
Changed in murano:
status: Confirmed → In Progress
assignee: nobody → Ekaterina Chernova (efedorova)
Changed in murano:
milestone: kilo-2 → kilo-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on murano (master)

Change abandoned by Ekaterina Chernova (<email address hidden>) on branch: master
Review: https://review.openstack.org/144327

Changed in murano:
milestone: kilo-3 → kilo-rc1
Changed in murano:
status: In Progress → Confirmed
Changed in murano:
milestone: kilo-rc1 → liberty-1
Changed in murano:
status: Confirmed → In Progress
Changed in murano:
status: In Progress → Fix Released
Changed in murano:
status: Fix Released → In Progress
Changed in murano:
milestone: liberty-1 → liberty-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (master)

Reviewed: https://review.openstack.org/155397
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=ff9c0c49eaa53a054d4e2a847221a7bc797ffb92
Submitter: Jenkins
Branch: master

commit ff9c0c49eaa53a054d4e2a847221a7bc797ffb92
Author: Ekaterina Chernova <email address hidden>
Date: Thu Feb 12 19:31:48 2015 +0300

    Remove hardcoded dns from config file

    If no nameserver list is provided to a neutron subnet,
    it uses the DHCP (gateway) address which in turn forwards to dnsmasq.

    So dns_nameservers will be set to emptylist in heat templete.

    In case user wants to set different dns from default,
    he may edit the config parameter, witch is not removed.
    The name of parameters is changes to dns_nameservers (with s at the end)
    to correspond the same name in heat template.

    Change-Id: Iba8b12b8bc78f821e11debb58f20cb713a9dc9c7
    Closes-Bug: #1367877

Changed in murano:
status: In Progress → Fix Committed
Changed in murano:
status: Fix Committed → Fix Released
Changed in murano:
milestone: liberty-2 → 1.0.0
Changed in murano:
milestone: 1.0.0 → 1.0.1
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.