When we manually construct a machine/node (i.e. put together the motherboard, CPU/RAM/storage, etc.), we also provision a UEFI-settings snapshot to all nodes. This also ensures that “Wake-on-LAN” (WoL) is enabled, uniformly, from the beginning.
- Before MAAS even knows of a node, we power it on manually and run a simple manufacturer’s diagnostic
- We then emit a WoL “magic packet” from the console of the MAAS-hosting VM - and it works
- After MAAS sees the node for the first time - Enlistment - it finishes that first touch by shutting down the node
- We then emit a WoL “magic packet” from the console of the MAAS-hosting VM - and it doesn’t work
In this outcome-condition, we have to then manually power on the node. When “Commissioning” a node, the same occurs: WoL is active/working (by virtue of having turned on the node by hand), MAAS begins “Commissioning” phase, MAAS finishes by shutting down the node - and WoL no longer works.
It’s understood that despite the UEFI/BIOS setting of having WoL enabled, Ubuntu itself must also be configured/enabled (
ethtool, etc.) to make WoL persist between reboots/shutdowns.
With the above in mind:
- What is MAAS doing as part of Enlistment/Commissioning such that WoL “doesn’t work” after the requisite “shutdown” when each phase completes?
- Akin to “need to configure Ubuntu to make WoL persist after reboot/shutdown” - does that opportunity already exist when MAAS is doing Enlistment/Commissioning? (read: “are we just missing something here on our end?”)
- Adding to the above: is Ubuntu “already on the node” at the point of Enlistment/Commissioning? We didn’t think so, but… maybe? (was under the impression that “making WoL persist, as a setting” required the OS - Ubuntu - to exist. Maybe not? Like, how else would WoL not persist only after MAAS has had its first touch on a node? mea culpa)
Essentially we’re just wondering if we’re oblivious to some obvious config/setup/setting we could be employing in MAAS (some… Enlistment/Commissioning-phase script?) that would allow pre-Deployment-OS-presence to allow WoL to… persist/stick/be “on”/not cease to be/not pine for the fjords.
Any help would be greatly appreciated. Figuring this out would allow MAAS to be, for us, finally “from-across the room”-able.