Power on Settings configuration
-
Hi,
In the XCP-ng admin (Xen Centre) there's the options to set power on settings for hosts and/or pools. Specifically iLO, iDRAC and/or generic WOL to cause a wake on LAN.
Is it possible to enable such a possibility to configure, if not already present in Xen Orchestra and/or XO: Lite?
Also this could be an XO Proxy feature by having a HTTPS translation for transmission outside of network.
The request gets converted into a XO proxy and XO compatible format. This request then gets executed by XO proxy and/or the host with XO proxy VM or software installed.The ports for WOL would remain closed to the internet, so not a security risk (vulnerability). However it would be handled through the passing of a text based request structured data in the XO and XO proxy format. Basically in a similar fashion to how XO proxy handles backups and other requests.
-
You can configure it via
xe
CLI for now (it's not a widely used features, we tend to prioritize). In theory, as soon we add it to XO, it will be entirely transparent to use it via a proxy, as long it's a XAPI call.Can you explain a bit more your use case however?
-
@olivierlambert A hypothetical use case for your large deployment customers. As well some parts would be useful for XO Lite users on a pool (depending on size).
There's remote servers but currently they aren't always fully powered on. Just powered up enough for iLO or iDRAC etc to work. Opening the ports for them directly to the Internet is a security risk though.
So being able configure them via XO (with XO Proxy) and/or XO Lite would really help. As the transmissions when done in an authenticated format in a similar fashion to how backups are handled on remote geographic locations.
The XO and/or XO Proxy would translate the calls for going over HTTPS. Either would execute the remote power calls depending on whether its connected to XO Proxy or XOA. Though the APIs or WOLs wouldn't be Internet accessible only with in the appropriate appliances location (on its network).
The ability to remotely power on servers would be helpful, load balancing features as servers could also potentially shutdown and powered off when not needed. Less electricity usage especially when combined with BIOS or UEFI energy efficiency settings to further reduce power wastage.
-
The issue is within pools: XCP-ng isn't meant to have pool members down (for various reasons), so the scenario is only limited to pools with one host only