maas-devel team mailing list archive

[Andreas Hasenack <andreas@xxxxxxxxxxxxx>]

On Fri, May 2, 2014 at 10:50 AM, Gavin Panella
<gavin.panella@xxxxxxxxxxxxx>wrote:

> On 2 May 2014 14:42, Andres Rodriguez <andres.rodriguez@xxxxxxxxxxxxx>
> wrote:
> > Why not making the static the addresses that have already been assigned
> > during enlistment/commissioning ? It seems to me that when the
> commissioning
> > process happens, the node already know what's its IP address. Why not
> making
> > an static mapping at that stage?
>
> That's what happens now. However, it seems that dhcpd treats static
> assignments within a dynamic range as advisory only, and will give
> them out when it runs low of free addresses.
>
>

What else can you do with omshell? Delete a lease perhaps? Add ranges, so
that the static IP is skipped?

And I missed this bit: why don't we use ranges in dhcpd.conf to exclude the
new static ip, because we need to restart dhcpd for that to take effect? No
reload option? And why would a restart be particularly bad?