[2.0b4] All dynamic range's configure PXE
Bug #1579909 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
I want to reserve a dynamic range that doesn't configure PXE boot. This may be for scenarios were I want MAAS to provide DHCP but not tell machines to PXE boot off network.
Changed in maas: | |
milestone: | none → 2.0.0 |
Changed in maas: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
milestone: | 2.0.0 → 2.1.0 |
Changed in maas: | |
milestone: | 2.0.1 → 2.1.0 |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
Changed in maas: | |
milestone: | 2.1.3 → 2.2.0 |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.x |
Changed in maas: | |
milestone: | 2.2.x → next |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
How do you propose we would tell the difference between a DHCP client that should be able to boot from the network, and a DHCP client that should not?