Comment 6 for bug 1690231
Revision history for this message
| Mike Pontillo (mpontillo) wrote Re: [Bug 1690231] Re: MAAS auto-assigned gateway IP, while not allowing to reserve IP's in subnets. | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
MAAS did not start pre-reserving IP addresses until MAAS 2.0. MAAS 1.9
expects the static range to be under the complete control of MAAS.
In MAAS 2.0, the concept of a "static range" was removed; without that
explicit knowledge of which IPs were intended for allocation by MAAS, MAAS
learned to cope by excluding "special" addresses such as gateway IPs, DNS
servers, and interfaces configured on the MAAS servers themselves.
There are a couple ways I can think of we could address this in MAAS 1.9:
(1) Validate when saving a cluster interface that the static range doesn't
include the gateway IP.
(2) Change the IP allocation code to mimic the behavior of MAAS 2.x.
Both potential changes might not solve the entire issue, which is that MAAS
does not have complete information about the network. That is, if the user
didn't fill in the default gateway on the cluster and interface definition
page, MAAS 1.x has no idea what address it should avoid.