Recent content by gurubert

AFAIK NetApp has one of the fastest and most stable NFS server implementation in the industry. If you already have that I would definitely run some benchmarks on it.

And RedHat already has a virtualization offering for their enterprise customers. I doubt that anybody really entrenched into the "Enterprise" RHEL ecosystem is looking elsewhere.

We also use cloud-init and have no issues. The hostname was always set to the name of the VM. But we use an FQDN as VM name.

But it will only be one Proxmox node? And you need to mount the same filesystem in multiple VMs? Then ZFS with NFS/SMB shares on Proxmox.

Then I would suggest to use ZFS locally. Ceph is a distributed storage system that works best with five nodes or more.

Just to be curious: This is a test setup?

Addendum: PBS needs really fast disks and does not work well on HDD.

No, as this is file storage and not block storage.

AFAIK 100% of the original volume will be used as capacity for the snapshot volume.

And the destination PVE thinks it just started a new VM.

Hi, to see how hook scripts work I created a very basic script and placed it on a storage available to each node: #!/bin/bash echo "$@" | logger -i -p local4.info -t snippet-test When migrating a VM between the nodes I only see log entries for "pre-start" and "post-start" hooks on the...

Which is not needed when you just want to reboot a node. An OSD is set to "out" when it should be removed with ceph osd purge.

What do you mean by this? What type of drives are used?

Losing data is something else than losing write access. In an erasure coded pool if you lose more than m OSDs in an affected PG you lose data. If you have less than min_size OSDs you lose write access to the placement group.

With size=min_size you cannot lose any OSDs without losing write access to the affected objects. And it has nothing to do with number of nodes or number of OSDs.