MAAS

Boot "purpose" is in flux

Bug #1031406 reported by Gavin Panella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Low
Unassigned

Bug Description

In https://code.launchpad.net/~allenap/maas/kernel-initrd-parameters/+merge/117432 I'm introducing a new function, get_boot_purpose(), that tries to indicate (indirectly) what kernel+initrd we ought to be using for a given node. However, it's unclear what choices we /should/ be making here, or if there's more work do be done elsewhere. For example, we may want to render a local boot option in some PXE config files, and that doesn't need any kernel/initrd. This issue still needs some discussion before we can complete the implementation.

Related branches

lp:~julian-edwards/maas/fix-localboot
Jeroen T. Vermeulen (community): Approve
Diff: 65 lines (+34/-1)
3 files modified
src/provisioningserver/pxe/config.localboot.template (+9/-0)
src/provisioningserver/pxe/config.py (+11/-1)
src/provisioningserver/pxe/tests/test_config.py (+14/-0)
Julian Edwards (julian-edwards)
Changed in maas:
assignee: nobody → Julian Edwards (julian-edwards)
status: Triaged → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote :

I'm happy with the use of "local" - it can be used by render_pxe_config to generate a different pxeconfig to make a node boot off its own disk.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Nothing will break if this is left as-is, so marking low. Just the TODOs in the code need clearing up, and check out whether "poweroff" is useful.

Changed in maas:
status: In Progress → Triaged
assignee: Julian Edwards (julian-edwards) → nobody
importance: High → Low
Julian Edwards (julian-edwards)
Changed in maas:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.