MAAS DHCP/DNS can't manage more than a /16 network
Bug #1299231 reported by
Rod Smith
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Low
|
Jeroen T. Vermeulen | ||
Bug Description
In attempting to work around bug #1297008, I tried to reconfigure my MAAS server to be on the 172.16.0.0/12 network, which is the only one of the three networks supported by squid-deb-proxy that's not in use either at Canonical or in my home. Unfortunately, MAAS complains that it won't manage anything bigger than a /16 network. (See screen shot.) Although I understand that managing tens of thousands of computers from a single MAAS server is unreasonable, sometimes (as in my case), using a bigger-than-/16 network is desirable. Unless there's a compelling technical reason for this limit, I recommend its removal.
Related branches
lp:~jtv/maas/bug-1299231
- Raphaël Badin (community): Approve
-
Diff: 103 lines (+1/-53)2 files modifiedsrc/maasserver/models/nodegroupinterface.py (+0/-21)
src/maasserver/models/tests/test_nodegroupinterface.py (+1/-32)
Revision history for this message
| Rod Smith (rodsmith) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Jeroen T. Vermeulen (jtv) wrote | #3 |
| Changed in maas: | |
| assignee: | nobody → Jeroen T. Vermeulen (jtv) |
| 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 is a technical restriction at the moment, because MAAS writes out a template zone file for DNS. Going beyond /16 results in huge files and a laggy celery process.