Recent content by alexskysilk

you may not want to look at a killawatt then. a 1L box will provide roughly equivalent performance at 1/5th the power draw- and thats not even brand new. 15 year old server = 150W+ at idle.

good question- I dont know. you COULD just edit the vmid.conf directly (eg, /etc/pve/qemu-server/100.conf) and add the disk directly- find the line that starts with unused0: and change it to efidisk0: might need other variables for pre-enrolled-keys, etc.

Not screwed at all, but you will have downtime. The way forward depends on whether the payload (virtual disks) are located on the same disk as your system or not. IF the virtual disks are on a seperate filesystem you're home free- just reinstall proxmox and use the method @Maximiliano presented...

I think he means license per storage bearing node, not pve cluster node.

thats aggregate- not to a single initiator. important distinction. and you dont fix latency with any OSD count.

ceph and zfs serve different purposes. ceph is a cluster store. zfs is host attached. while you can make a zfs filer act as cluster storage that still leave it as a SPOF in a HA environment. If you actually want to shortcut the lab you might want to ask specific questions, eg, what client...

Ask a subjective question, get subjective answers. its either terrible if you're looking for 500kIOPS, or great if you're looking for 100IOPs.

I think you're asking the wrong question. what is the workload in vm count and minimum required iops/vm? how much capacity do you need? ceph works fine with hard drives. its just slow.

ok, then that forces me to ground 0. Without resorting to screencaps, what is the actual issue? the screencap in OP does not lend itself to any actual issue; the screencaps you had showing various "red" items dont necessarily correlate to problems (although you will probably need to tweak your...

Thats quite an elitist perspective. the code is well documented and published; if it doesnt serve YOUR purposes or YOUR quality requirements, so be it, but in the spirit of open source if the project overlaps with something you value shitting on its shortcomings isnt constructive. maybe...

thank you! that answers the question perfectly. While it wouldnt occur to me to do this (clearly,) wouldnt this be a prime candidate for *claw? dont get me wrong, having actual working guardrails would be great, just trying to wrap my head around the project conceptually.

I've run into this issue multiple times in the past. IF you have linux kernel 6.1 in your available kernels to boot, you can live with it and just pin that kernel. Going forward, you should consider upgrading your motherboard to something from this decade ;)

It depends on your performance expectations, but ceph is quite capable to deal with this kind of mixed hardware- as long as you make sure that you have EQUIVALENT CAPACITY PER OSD TYPE on each osd server. In your case, assuming you want all 6 nodes to be OSD bearing, you'd want to divide your...

Some of the bigger names in the European list provide follow the sun support and can be engaged adhoc with 4 hour minimum charges. Not really familiar with any US based vendors but they probably exist; you'll need to reach out to a bunch of them and evaluate as you'd do for any other vendor.

Lets ignore safety for the moment (thats a constraint, not the use case.) I'm just having a hard time imagining how would one use this.