[2.2] Expire the DHCP lease after commissioning or make the default-lease-time configurable
Bug #1639332 reported by
Jorge Niedbalski
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Critical
|
Andres Rodriguez |
Bug Description
[Environment]
MAAS 2.0
Xenial
[Problem description]
It would be desirable for the dynamic IP addresses used during commissioning
to be released upon shutdown instead of waiting for the default lease time to be reached.
The use case example is a user that configured a small dynamic range of 5 IP addresses
then they started 10+ for enlisting, the results are 5 machines will correctly enlist while the other 5 will be stuck waiting for the original enlisting IP's to expire (10 minutes by default).
[Possible Solutions]
- Expire/Release the DHCP leases upon shutdown.
- Expose the default-lease-time configuration or make it configurable via DHCP snippets.
Changed in maas: | |
status: | Won't Fix → Incomplete |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
milestone: | none → 2.2.0 |
assignee: | Andres Rodriguez (andreserl) → nobody |
status: | Incomplete → Triaged |
importance: | Undecided → Wishlist |
tags: | added: sts |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.0rc1 |
summary: |
- Expire the DHCP lease after commissioning or make the default-lease- - time configurable + [2.2] Expire the DHCP lease after commissioning or make the default- + lease-time configurable |
tags: | added: trivial |
Changed in maas: | |
milestone: | 2.2.0rc1 → 2.2.0rc2 |
Changed in maas: | |
importance: | Wishlist → Critical |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
milestone: | 2.2.0rc2 → 2.2.1 |
milestone: | 2.2.1 → 2.2.0rc3 |
To post a comment you must log in.
Update:
It looks like MaaS doesn't release the "dynamic IP" assigned to a node until it is being deployed, so as soon as I deployed the existing 5 machines, the other 5 machines started booting.
To the 5 machines that were enlisted, and are now being deployed, it automatically created a new IP address and set it to "Automatic" in the network list. Thereby removing it from "Observed" which allowed the other nodes to enlist.
That means right now realistically you need an IP address space that is twice as large as the amount of machines in the network if you want to be able to have the machines standing by in the "Ready" state. 1 IP for the Dynamic range, and 1 IP for the host when it goes to "Deployed". This seems like a waste of IP space because if all the machines are deployed 50% of your IP space is no longer used...