[2.0rc3] the term "reserve" in IP Ranges is misleading

[Nobuto Murata]

Although MAAS release notes[1] clearly describe subnet control has been changed from 1.9 behavior, the term "reserve" is confusing to me.

See the screenshot:
https://bugs.launchpad.net/maas/+bug/1607638/+attachment/4709252/+files/ip_from_unreserved.png

There are two buttons, "Reserve range" and "Reserve dynamic range". Those two "Reserve" for different targets.

"Reserve range": Reserve range *to be excluded from* MAAS
"Reserve dynamic range": Reserve dynamic range *for* MAAS

From those two buttons, it's hard to guess the new behavior in MAAS 2.0.

[1]
http://maas.ubuntu.com/docs/changelog.html#id19
> Because static ranges have been removed from MAAS, each static range has been migrated to one or more reserved ranges, which represent the opposite of the previous static range. (MAAS now assumes it has full control of each managed subnet, and is free to assign IP addresses as it sees fit, unless told otherwise.)

[Nobuto Murata (nobuto)]

"Reserve exclusion range" or something might be better than "Reserve range".

[Peter Matulis (petermatulis)]

IMO, the section should be renamed to "IP ranges". The "Reserve range" button is fine with me but the other button should be renamed to "Dynamic range". It would be great if the window that opens for the latter would have a line that made it clear that the range is for enlistment and commission only.

[Andres Rodriguez (andreserl)]

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the report date of this, we are currently marking it as Invalid. If you believe this bug report still valid against the latest release of MAAS, or if you are still interested in this, please re-open this bug report.

Thanks