alexskysilk's latest activity
-
Aalexskysilk replied to the thread Multiple osd for device fail.Yes, for HARD DRIVES. here is a link for a more recent version of that document: https://docs.ceph.com/en/tentacle/start/hardware-recommendations/ note that OP is using NVMEs. --edit worth discussing when its actually desireable/advisable to do...
-
Aalexskysilk replied to the thread [SOLVED] Use the extra space available due to zfs compression.you're going to need to adjust your focus. you cant use the space IN THE GUEST, because the reservation is for used space, not on-disk. If you need more space, expand the disk. you can use the space IN THE POOL since the pool isnt concerned with...
-
Aalexskysilk replied to the thread [SOLVED] Use the extra space available due to zfs compression.https://klarasystems.com/articles/why-zfs-reports-less-available-space-space-accounting-explained/
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.crystal :) so @proxuser77 does not recommend using docker in lx, because the PVE devs are on record recommending against it. actually that one is easier. You can. known problems are addressed, either in code or in workflow.
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.Good. so for the purpose of conversation, Docker is promarily the container topology- since the manner by which you run them has options. With you so far. still dont quite get whats "not that simple." True. but this isnt actually a problem...
-
AIt not only supersedes docker but also the hypervisor. You don't necessarily need a hypervisor if you have a way to deploy Kubernetes clusters baremetal. A hypervisor might still make sense if you want to distribute resources between different...
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.You might want to expound on that to make a cogent point.
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.Docker=the mechanism for shipping a container Kubernetes=Orchestration tool for containers They're not in conflict or "better" then each other.
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.Is that so? I am not an expert. perhaps you can explain. there is nothing "fundamental" seperating docker from other userspace software. Because in a non production environment it is the sweet spot of application deployability with namespace...
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.You're memory is spot on- but, again, nothing specific to docker. The PVE philosophy seems to be move fast and break things- thats just the cost of doing business on a rolling platform- there will be changes.
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.Because PVE "supports" the hypervisor and base OS. they DONT SUPPORT USERSPACE APPLICATIONS. You might as well suggest you shouldnt use MySQL since the PVE devs dont support that either. The only times in recent memory where PVE updates "broke"...
-
Aalexskysilk replied to the thread LXC and Docker compatibility now.This is true, but also irrelevant. The devs made a hypervisor; they neither test nor care about any specific software that runs within it. A debian or alpine lxc container is fully "supported" as far as that goes. I've been running docker inside...
-
Aalexskysilk replied to the thread How do you enforce per-pool (tenant) resource quotas for CPU / RAM / disk in Proxmox?.Worth noting that neither of those storage options are valid for cluster use. If the scope is single host, just monitoring disk space ought to suffice. As far as I know, there is no storage solution that offers snapshot quotas regardless of...
-
Aalexskysilk replied to the thread How do you enforce per-pool (tenant) resource quotas for CPU / RAM / disk in Proxmox?.A couple of comments: 1. Since you're deploying client assets in a cluster, there are two components to consider- first, what is your target overprovision/overall host load threshold and second- when deploying a new asset, you have a choice of...
-
Aalexskysilk replied to the thread [SOLVED] NVIDIA 580.x + Kernel 7.0 incompatibility on Trixie.GRID is long eol. the functionality was bifurcated and separated into multiple licensed products. see https://docs.nvidia.com/vgpu/index.html
-
Aalexskysilk replied to the thread Mitel Connect and Proxmox.The only thing I can think of is vcpu configuration. on a modern windows guest you really want to set it to x86_64_V3 or better. Avoid host without tuning, and QEMU/earlier X86_64 variants can have missing cpu features.
-
ANo and propably never will be since they use the same features of the kernel ( namespaces, cgroups etc) and host system ( apparmor etc ) so any update might introduce a breaking change. This is more likely with major upgrades ( like PVE8 to...
-
Aalexskysilk replied to the thread [SOLVED] NVIDIA 580.x + Kernel 7.0 incompatibility on Trixie.https://download.nvidia.com/XFree86/Linux-x86_64/580.173.02/
-
Aalexskysilk replied to the thread [SOLVED] NVIDIA 580.x + Kernel 7.0 incompatibility on Trixie.I have 580.173 working fine. I dont use the apt packages as nvidia doesnt seem to care about Trixie support, but the NVIDIA*.run installer works without a hitch.
-
Aalexskysilk replied to the thread High Latency on a new HDD-disks (ceph).Latency in the 80-100 range is normal. Just means the drives are busy. are they currently rebalancing?
