You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for client/server or Similar mixed ipmitool
Use Case is:
Proxmox VE Host (CPU Temperature Controller, SSD/NVME Boot Drives)
Debian VM NAS (with LSI 9211-8i / 9207-8i PCIe Passthrough and several HDDs)
As such, the Control needs to be done in a Master-Slave Configuration most likely.
In the Most General Sense, it's a Master - N x Slaves Configuration.
Host
a. Global Temperature Controller: set Fan Speeds
b. CPU(s) Temperature Controller
c. SSD/NVME Boot Drives Temperature Controller
Guest VM
a. HDDs Temperature Controller
b. HBA Temperature Controller ????
Essentially 2 Approaches are Possible:
a. Host does ALL the Control, Guest VM Communicates the Temperature Values
b. Split regulation as outlined above, Guest VM communicates the required Fan Speed
Probably a single Centralized Controller is easier.
In any Case, care shall be taken in case the Slave stops sending Temperatures/Fan Speed References, there shall be some kind of Interlocking (or "Default to 80% Fan Speed or something like that").
The text was updated successfully, but these errors were encountered:
Sockets Programming (probably limited to 1 Client & must do Splitting/Rebuilding of Strings Manually, compared to Flask API which simply Outputs JSON):
Add support for client/server or Similar mixed ipmitool
Use Case is:
As such, the Control needs to be done in a Master-Slave Configuration most likely.
In the Most General Sense, it's a Master - N x Slaves Configuration.
a. Global Temperature Controller: set Fan Speeds
b. CPU(s) Temperature Controller
c. SSD/NVME Boot Drives Temperature Controller
a. HDDs Temperature Controller
b. HBA Temperature Controller ????
Essentially 2 Approaches are Possible:
a. Host does ALL the Control, Guest VM Communicates the Temperature Values
b. Split regulation as outlined above, Guest VM communicates the required Fan Speed
Probably a single Centralized Controller is easier.
In any Case, care shall be taken in case the Slave stops sending Temperatures/Fan Speed References, there shall be some kind of Interlocking (or "Default to 80% Fan Speed or something like that").
The text was updated successfully, but these errors were encountered: