Comment 12 for bug 1467120

Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 1467120] Re: MAAS should provide an API to determine available ranges in a Subnet

On 09/09/15 05:33, Mike Pontillo wrote:
> Note: there is some discussion about modeling IP ranges as first-class
> citizens, so that we can support IPv6, and easily *un-reserving* a
> range. Without modeling ranges, to undo the command in (4) above would
> require num_addresses calls to the `release` API, which isn't good.

EXACTLY!

The whole reservation is "one range with one ID and one purpose for one
user".

Within that reservation, MAAS might in future observe that some
addresses are being used (visibly passing traffic) and others are not.
But at the end of the day, it has allocated that block of addresses as a
single entity to that user for a given purpose (text field that
Landscape or a human could type text in, mainly to help others find out
who to talk to).

> There is debate about whether or not this fits into 1.9, but it looks
> like we'll have to do it in order to do this the right way.

Yes, I think we're just papering over if we do it address by address.

> This may also help as we convert the concepts of dynamic and static
> ranges attached to a cluster interface to the more generic concept of
> DHCP-reserved ranges, and ranges reserved for some other reason.

Yes, exactly that :) In other words, think of a DHCP range as just "a
range MAAS allocated to itself for the purpose of DHCP".

So say I am an admin user. I just go and say "I want another range of 10
addresses for DHCP". This shows up as:

 start - end mark maas-dhcp

In a future version I can come along and release the range (though MAAS
would hold on to it till all the leases expire to be pedantic :)). But
certainly, Landscape could release a range it had reserved.

Mark