© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
At this point, I have landed [in MAAS 1.9] APIs to view reserved (or unreserved) APIs in a particular subnet; basically what was described in (1) and (3) above, but see the MP for example output.[1]
In summary, the change I landed provides a good foundation to address the remainder of the user stories now under discussion. But it does not address the specific use cases mentioned in the follow-on comments. I've filed two additional bugs to track those against; see below. Let's continue the discussion on those new bugs, as needed.
I had already planned for another user story to land separately in 1.9:
- As an API user (and on the web UI), I want to see the following details about a subnet:
* number of used IP addresses
* number allocated IP addresses
* percentage utilization
* largest contiguous block of free addresses
It sounds like it would be useful to have the same information available on Space (as an aggregation of the same information for all the subnets), so per your comments, s/subnet/subnet or space/ above.
I have filed bug #1498221 to track this.[2]
I was uncertain about whether or not we wanted to address the following user story in 1.9, (pending implementation of IP ranges) but it sounds like we need it for Landscape's convenience either way:
- As a MAAS administrator, I want to ask MAAS to reserve N arbitrary addresses in a Subnet or Space.
* Note: for this operation, it seems like MAAS should prefer *smaller* blocks of free address space, in case larger blocks are needed for other purposes.
I've filed bug #1498224 to track this.[3]
For maas-next we can model IP ranges properly, so that they can be easily released once claimed. (this will require refactoring the way IP addresses are managed across the system, impact the way cluster interfaces are defined, etc)
[1]: https:/
[2]: https:/
[3]: https:/