DNS should be an optional field in the network definition
Bug #1365619 reported by
Dean Henrichsmeyer
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
lp:~julian-edwards/maas/dns-in-networks
- Jeroen T. Vermeulen (community): Approve
-
Diff: 552 lines (+406/-4)9 files modifiedsrc/maasserver/api/networks.py (+2/-1)
src/maasserver/api/tests/test_network.py (+3/-0)
src/maasserver/api/tests/test_networks.py (+3/-1)
src/maasserver/forms.py (+1/-0)
src/maasserver/migrations/0109_networks_dns_servers.py (+377/-0)
src/maasserver/models/network.py (+5/-0)
src/maasserver/templates/maasserver/network_detail.html (+4/-0)
src/maasserver/testing/factory.py (+8/-2)
src/maasserver/views/tests/test_networks.py (+3/-0)
description: | updated |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
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 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?