This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
start:cockpit [2023/03/06 13:11] – allebone | start:cockpit [2023/03/06 13:43] – allebone | ||
---|---|---|---|
Line 4: | Line 4: | ||
< | < | ||
- | sudo apt-get install cockpit cockpit-machines cockpit-pcp | + | sudo apt-get install cockpit cockpit-machines cockpit-pcp |
</ | </ | ||
(For just monitoring a remote linux machine you dont need the cockpit-machines package) | (For just monitoring a remote linux machine you dont need the cockpit-machines package) | ||
Line 25: | Line 25: | ||
Regarding ovirt - its is a full stack so there is not just the web interface - there is the hypervisor, guest additions and other bits and bobs etc. It is possible to run the ovirt-engine as a VM on one of the KVM hosts which could be your only RHEL VM. This would give a more pure debian style KVM host/one vm acting as a controller type setup. An alternative might be Proxmox (which is better imho). If ovirt ever runs on debian this VM would also not be needed. | Regarding ovirt - its is a full stack so there is not just the web interface - there is the hypervisor, guest additions and other bits and bobs etc. It is possible to run the ovirt-engine as a VM on one of the KVM hosts which could be your only RHEL VM. This would give a more pure debian style KVM host/one vm acting as a controller type setup. An alternative might be Proxmox (which is better imho). If ovirt ever runs on debian this VM would also not be needed. | ||
- | ***I dont personally reccomend | + | One nice thing about cockpit is it can provide basic trends of servers over a period |
+ | {{: | ||
+ | |||
+ | This can help with trends of servers over time. |