DNS should be an optional field in the network definition

Bug #1365619 reported by Dean Henrichsmeyer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Julian Edwards

Bug Description

I realize we've gone back and forth on whether or not to include DNS in the network definition in MAAS. Based on today's meeting, we need to include it.

DNS Should be an optional parameter to the network definition.

Related branches

description: updated
Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

This honestly doesn't make any sense to me. DNS is not a network-specific setting, it can and does apply to many networks. Since I wasn't in the meeting, would you mind explaining the rationale please?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

For example, it might make sense to have a new database table called "DNS" which links Networks to a common DNS server.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

OK I've just spoken to Andres about this and understand this is a book-keeping exercise. I think we can just add an extra text field which would still work if we added a separate dns server table later.

Changed in maas:
assignee: nobody → Julian Edwards (julian-edwards)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: none → 1.7.0
Changed in maas:
status: Fix Committed → Fix Released
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.