alexskysilk's latest activity

  • A
    alexskysilk replied to the thread Proxmox on aarch64 (arm64).
    Absence of evidence isnt evidence of absence. Searching for evidence after making a claim is backwards. your google searches arent even informative- the toms hardware is breathless marketing without ANY substance. the Unihost article discusses...
    • 1786037257916.png
  • A
    alexskysilk replied to the thread Proxmox on aarch64 (arm64).
    You might want to cite your sources. and see what they were comparing.
  • A
    alexskysilk replied to the thread Proxmox on aarch64 (arm64).
    While it is possible to install Trixie on Mac hardware, it is dependent on Asahi linux patches. I doubt the pve Kernel would even work. If this is something of specific interest to you, please try it and let us know :) this would be enlightening...
  • A
    alexskysilk replied to the thread CEPH Performance.
    and yet you asked all the right questions anyway, correctly unwinding the "ceph" part from the "storage" part.
  • A
    alexskysilk replied to the thread Proxmox on aarch64 (arm64).
    there are very few options for this. and because its all low volume, they are not at all cost or performance competitive with comparable x86. No. and even if it could run, it wouldnt support mac guests, support MLX either directly or indirectly...
  • A
    alexskysilk replied to the thread Proxmox & NVIDIA partnership - what to expect?.
    PVE isnt very good for/at multitenant applications. Since KVM works natively on these platforms, an operator for such usecase is more likely to just deploy them to a cloud native orchestrator, eg Openstack.
  • A
    alexskysilk replied to the thread Proxmox & NVIDIA partnership - what to expect?.
    Dont conflate Nvidia hardware support as "AI." All this means in practice that nvidia "incentivized" Proxmox GMBH (probably with an NRE paid with nvidia couch change) to port PVE to their ARM cpus. Not really sure what for since the majority of...
  • A
    alexskysilk reacted to t.lamprecht's post in the thread Proxmox Virtual Environment now available for 64-bit ARM (arm64)! with Like Like.
    We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only. Proxmox VE 9.2 for arm64...
  • A
    alexskysilk replied to the thread A sudden error in the cluster, 2 reasons and 2nd one me being an idiot :-).
    You dont need a qdevice for a 3 node cluster; it will just serve as a 4th vote that doesnt have any consequence since its not a tiebreaker anyway. The lessons here are well learned, namely: 1. your cluster is only as stable as its network design...
  • A
    alexskysilk replied to the thread Multiple osd for device fail.
    seems like you have some leftovers from whatever you tried earlier. begin with ceph-volume lvm disk zap /dev/nvme0n1 IF this completes successfully, check for the presence of ceph-osd@0.service and ceph-osd@1.service. if either exist, delete...
  • A
    alexskysilk replied to the thread Multiple osd for device fail.
    Here is the uncomfortable truth for people wanting to deploy ceph: Its not a black box. you WILL need to understand what it (and by extension, you) are doing. If a key file in the preconfigured location is missing, you need to either...
  • A
    alexskysilk 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...
  • A
    alexskysilk 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...
  • A
    alexskysilk 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/
  • A
    alexskysilk 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.
  • A
    alexskysilk 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...
  • A
    alexskysilk reacted to Johannes S's post in the thread LXC and Docker compatibility now with Like Like.
    It 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...
  • A
    alexskysilk replied to the thread LXC and Docker compatibility now.
    You might want to expound on that to make a cogent point.
  • A
    alexskysilk 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.
  • A
    alexskysilk 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...
Show older items
Top Bottom
Back