![]() This is certainly a hack and if your system supports anything better than Wake on LAN, or you’re willing to buy a supported PDU just for that one system, then you should do that instead.īut if the inability to turn a system on is all that stands in your way from adding it to your MAAS, as was the case for me, then that patch may help you. The new file won’t be removed during an upgrade, but the two modified files will get reverted and need patching again. The patch modifies two files and adds a new one. Note that you’ll have to re-apply part of the patch whenever MAAS is updated. For everything else, this power type behaves like the “Manual” type, asking the user to manually go shutdown or reboot the system as you can’t do that through Wake on LAN. MAAS will then be able to turn the system on, allowing for the normal commissioning and deployment stages. Once done, you’ll now see this in the web UI:Īfter selecting the new “Wake on LAN” power type, enter the MAC address of the network interface that you have WOL enabled on and save the change. Sudo patch -p1 -d /usr/lib/python3/dist-packages/provisioningserver/ < maas-wakeonlan.diff To apply it to your MAAS, do: sudo apt install wakeonlan The code change needed to re-implement a wake-on-lan power type is pretty simple and only took me a few minutes to sort out. I instead had to resort to modifying MAAS directly to add the extra power type. MAAS doesn’t provide a plugin system for power types, so I unfortunately couldn’t just write a plugin and distribute that as an unofficial power type for those who need WOL. I am, however not particularly willing to install an old Ubuntu release and an old version of MAAS just for that one trivial feature, so I instead spent a bit of time to just implement the bits I needed and keep a patch around to be re-applied whenever MAAS changes. This feature was however removed from MAAS 2.x (see LP: #1589140) and the development team suggests that users who want the old wake-on-lan feature, instead install Ubuntu 14.04 and the old MAAS 1.x branch. ![]() That machine does however have a good PCIe network card which provides reliable wake-on-lan.īack in the days (MAAS 1.x), there was a wake-on-lan power type that would have covered my use case. The trouble is that this being a desktop computer, it’s lacking any kind of remote management that MAAS supports. That machine also has a Fiber Channel HBA and Infiniband card for even less common setups. ![]() That machine is a desktop computer but with a server grade SAS controller and internal and external arrays. Another set of systems are virtual machines that MAAS drives through libvirt.īut I’ve long had another system I wanted to get in there. I use MAAS to track who’s using what and to have the machines deployed with whatever version of Ubuntu or Centos is needed to reproduce a given bug.Ī number of those systems are proper servers with hardware BMCs on a management network that MAAS can drive using IPMI. Link detected: help would be appreciated.Ĭode: Select all systemctl enable to enable unit: File Invalid lsī rvice ĭbus-fi.w1.wpa_rvice ĭ ĭ ĭ ĭ rviceĭ rvice ĭ maintain a number of development systems that are used as throw away machines to reproduce LXC and LXD bugs by the upstream developers. Link partner advertised FEC modes: Not reportedĬannot get wake-on-lan settings: Operation not permitted Link partner advertised auto-negotiation: Yes ![]() Link partner advertised pause frame use: Symmetric Link partner advertised link modes: 10baseT/Half 10baseT/Full Supported link modes: 10baseT/Half 10baseT/FullĪdvertised link modes: 10baseT/Half 10baseT/Full TX errors 0 dropped 0 overruns 0 carrier 0 collisions ethtool enp8s8 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ![]()
0 Comments
Leave a Reply. |