[feature] Auto-assign IPs from reserved ranges based on purpose

[Wojtek Rakoniewski]

It is a feature proposal, but in my opinion it will be pleasantly received by many administrators.

Please add third type of reserved range in subnet configuration named "reserve auto assign"
Editing "auto assign range" should work as for "reserved ranges" but should be possible to add single tag to range.
If "reserve auto assign" is defined it should be used when we configure auto assign in ip address configuration in machine network configuration. IP to the machine should be assigned from that "reserve auto assign" range during deploy, but if some tags are defined for machine first auto assign ip reserve should be used with the same tag defined.

Example of use:
I want to have order in ip dresses so I define one ip range 192.168.0.0/24 then I define two "reserve auto assign" ranges:
- 192.168.0.10-29 with tag "controller"
- 192.168.0.100-199 with tag "compute"

I want to use Maas to deploy OpenStack cluster.
Some machines to be used as controllers I'm marking by adding tag "controller"
Some other machines to be used as compute nodes I'm marking by adding tag "compute"
Each machine network is configured with autoassign IP address.

When Maas deploy machines it will assign ip addresses from range depending on machine use case (defined tags). First assigned controller will have ip 192.168.0.10, first assigned compute node will have ip 192.168.0.100.

Regards,
Wojtek

[Mike Pontillo (mpontillo)]

This is an interesting idea; I don't think you would need another type for this though. Part of the intent of a reserved range is that you can reserve it, and then use it for a particular purpose. I like the idea of adding tags; right now we just have a description field.

[Adam Collard (adam-collard)]

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