Hi!
Thanks for bringing attention to this, I took a quick look and the determined cause tracks and the fix also seems targeted and alright.
I forwarded this issue to the Debian bug tracker here...
Hi All,
While setting up automated testing for PVE 9, we observed that several udev properties were missing from SCSI block devices. After some investigation, we traced the issue to a regression in the sg_inq tool (part of sg3_utils). The bug...
ProxmoxOfflineMirror should cover this, I havn't use it myself (yet) though: https://pom.proxmox.com/
Something like aptly or apt-mirror might work too but I havn't used them together with Proxmox products or Ceph yet
That is not true for Proxmox VE though. It does not use libvirt at all and has its own tooling to manage and start VMs. All the functionality is exposed via the API (see https://pve.proxmox.com/wiki/Proxmox_VE_API and...
I moved the thread :)
According to the Apache Cloudstack website:
And when checking their documentation, I also don't see Proxmox VE mentioned anywhere. So I am afraid that they do not support Proxmox VE as an underlying hypervisor.
Using more than one OSD per drive allowed to workaround internal processing limits in the OSD services themselves. Your Intel P4610 aren't the fastest drives ever, so chances are that you won't hit those limits. With recent versions of Ceph this...
Any solution is use case dependent, which is why this is left for you (the operator) to define, and you can find multiple documents making what seem to be antagonistic recommendations.
more pgs/OSD mean more granularity, meaning better seek...
You're concerned with optimal PG count when your cluster is lopsided. you have two nodes with HDDs, two nodes with a lot of SSD and 2 nodes with too little. any HDD device class rule would not be able to have a replication:3 rule, and an SSD...
What version of Checkmk are you running?
Starting with 2.4 my extension was incorporated upstream and does not need to be installed separately any more.
The mk_ceph.py agent plugin (for Python 3) needs to be deployed to...
Dein Server heißt prox2 aber der Name in /etc/hosts lautet prox. Behebe das (nano /etc/hosts), starte neu und prüfe noch mal ob manche der Fehler nun weg sind.
Wenn möglich nutze Code blocks anstatt Bilder von Text.