[2.3, UX, enhancement] provide IP statistics per range and not just subnet.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Low
|
Unassigned |
Bug Description
I have 6 /21 subnets defined in a brand new MAAS 2.3.1, and nothing yet deployed. No dhcp leases are assigned.
All 6 networks show "6%" available IPs.
At first, this seemed like it had to be inaccurate. But I found that it is accurate by the measure of the current MAAS logic.
This appears to represent the portion of IP addresses which are not part of the static or dynamic ranges. In other words: addresses which will likely never be used by the MAAS cluster or its machines.
I find that metric to be not-at-all useful in production.
As cluster operator, what I care more about is: How much is available from the ranges that I've declared?
In other words: am I about to exhaust the IP space?
Please consider a re-think on the user experience in communicating IP allocation on the "Subnets" main page. Thank you.
Changed in maas: | |
importance: | Undecided → Low |
milestone: | none → next |
status: | New → Triaged |
summary: |
- 'available ips' percentage is confusing + [enhancement] provide IP statistics per range and not just subnet. |
summary: |
- [enhancement] provide IP statistics per range and not just subnet. + [2.3, enhancement] provide IP statistics per range and not just subnet. |
summary: |
- [2.3, enhancement] provide IP statistics per range and not just subnet. + [2.3, UX, enhancement] provide IP statistics per range and not just + subnet. |
tags: | added: ux |
Changed in maas: | |
milestone: | next → none |
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
MAAS Team