Skip to content

Conversation

@ares
Copy link
Member

@ares ares commented Jul 9, 2025

The feature adds the ability to wake suspended Host by Wake on LAN. It
requires a smart proxy with WOL feature.

Typically, when host has a network interface attached to a subnet where
we manage the DHCP, the broadcast in such network is available. That's
due to the core principle of DHCP protocol. In such network, it's
possible to perform WOL, which also relies on broadcast. This patch adds
WOL support for Host's primary interface as that's the one we run the
DHCP orchestration on. This could be extended in future if we see the
need to specify other host interface instead.

The Host's API loads the primary interface, checks the presence of the
DHCP proxy and it's WOL capability. If it is available, it triggers the
relevant API on the smart proxy and displays a toast notification.

This new action reuses the same permission we have for BMC (power
management of the host).

@ares
Copy link
Member Author

ares commented Jul 9, 2025

@ares ares force-pushed the fix/38549 branch 2 times, most recently from 3a48195 to 915ef05 Compare July 9, 2025 20:35
@ares
Copy link
Member Author

ares commented Jul 9, 2025

Ah, there are some test failures I missed locally, I'll need to fix those first. Think of it as a draft meanwhile.

@ares
Copy link
Member Author

ares commented Jul 10, 2025

Also adding the UI demonstration
wol_full.webm

ares added 3 commits July 11, 2025 16:29
The feature adds the ability to wake suspended Host by Wake on LAN. It
requires a smart proxy with WOL feature.

Typically, when host has a network interface attached to a subnet where
we manage the DHCP, the broadcast in such network is available. That's
due to the core principle of DHCP protocol. In such network, it's
possible to perform WOL, which also relies on broadcast. This patch adds
WOL support for Host's primary interface as that's the one we run the
DHCP orchestration on. This could be extended in future if we see the
need to specify other host interface instead.

The Host's API loads the primary interface, checks the presence of the
DHCP proxy and it's WOL capability. If it is available, it triggers the
relevant API on the smart proxy and displays a toast notification.

This new action reuses the same permission we have for BMC (power
management of the host).
@@ -0,0 +1,13 @@
import { testActionSnapshotWithFixtures } from '../../../../common/testHelpers';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are moving away from testActionSnapshotWithFixtures see https://github.com/theforeman/foreman/blob/develop/developer_docs/ui-testing-guidelines.asciidoc for ui test guidelines

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants