right; so logically the body responsible for the decision is elsewhere (QEMU.)
directory support still works and requires no support from PVE anyway. If the QEMU storage backend serves no additional utility, then what is the actual request for?
In order for it to be a true quorum provider, it has to be accessible to all nodes but NOT PHYSICALLY LOCATED at either site. The whole point is should one of the sites drop, the quorum provider is not affected.
It means that this package is included in ubuntu distributions. Proxmox uses debian as its parent distribution, not ubuntu. it also means that its not an actual package, its a collection of applications which you can install by yourself, like...
I read through the chain, and I dont really understand what everyone is arguing about.
Yes. ceph requires a minimum configuration (network topology, OSD count, etc) before its performant.
this the is the wrong question to ask. whether someone...
Thats an observable fact :) but when you say
It is explicitly a different message; I believe you come from a genuine place and want to help people- please expound on WHAT you feel is the risk is here. I think that would settle both your point...
lets put things in perspective.
OP wants to run pve on a 15 year old server. it is clearly NOT for production use. what, exactly, do you suppose any such "risk" actually entails?! regardless of the NUMBER of kernels released since, NONE of them...
There are multiple documented issues with modern Kernels (>6.2) with LSI based controllers on older (pre Haswell) platforms, stemming from bios mapping issues- older kernels were much more foregiving. You can try to shoehorn their firmware into...
In that case, all you need is the lxc config files (/etc/pve/lxc/*.conf.) simply copy those to your destination hypervisor, make sure the storage is mounted and the store presented in pvesm using the same name and away you go.
Why is your root...
https://docs.netapp.com/us-en/netapp-solutions-virtualization/proxmox/proxmox-deploy-guidelines.html
--edit with video: https://docs.netapp.com/us-en/netapp-solutions-virtualization/proxmox/proxmox-ontap-nfs.html#storage-administrator-tasks
This is a great breakdown of your progress, and hitting that 90% threshold on CPU and network is a solid milestone. However, regarding the storage deficit (the 50% delta on Ceph vs. Bare Metal), I want to save you some cycles on the "further...
hmm.
yes, I see your point.
I am guilty of thinking of PVE as an infrastructure. I forget that many (most?) of its users are homelabbers. consider me chastised :)
True generally, untrue in the OPs testing matrix. LVM-thin introduces its own problems. Since it is of almost no benefit in a modern deployment (LVM thick for SAN, zfs/btrfs for local) I dont know why OP even bothered testing it.
Yes. For Kubernetes nodes to interact with Ceph directly (via RBD or CephFS), they need to be on the Ceph public network. Without that direct line of sight, the Kubernetes workers won't be able to map the block devices or mount the filesystems...
a container in zombie state would do what you experience. use ps to find the process (it would be in a permanent 'D' state.)
The good news is that the rest of your containers work normally and you can use pct commands to control them. the bad...
1. any storage back end should serve that stated requirement. be aware that meeting a performance spec defined as "decent" may have different meaning for different people.
2. 15k iops is doable. In your environment, lvm type will yield the best...