IP ranges documentation

[Mark Shuttleworth]

On 20/02/17 22:13, Lloyd Parkes wrote:
> Thanks for that. It's perfectly logical in a twisted and perverse kind
> of way. I can see the UI getting updated at some point in the future
> so that it calls the reserved range two different names depending on
> whether or not the subnet is managed by MAAS. e.g. you would define
> "Managed ranges" in unmanaged subnets and "Unmanaged ranges" in
> managed subnets.
>
> I have written an alternative description for Reserved ranges and
> created a github pull request.

Thank you! That's much clearer terminology.

Essentially, if MAAS is providing DHCP and DNS on a subnet then it can
allocate addresses freely. If it is not, then the assumption is it will
be given addresses explicitly which it can offer to machines/containers
for static configuration.

The typical use case is a MAAS-controlled network with some machines
that are *also* attahed to a non-MAAS controlled network, like a DMZ
where IP addresses are given out manually. In that case, a small range
of those addresses is given to MAAS and can be used for those machines
or containers as needed. Since MAAS is not providing DHCP on that
network, and container mac addresses are dynamically generated, these IP
addresses have to be written statically on the machines/containers when
they are started.

Mark