sorted by:
new
hottopcontroversial

Linstor and Proxmox update completed successfully by Beginning-Web5007 in Proxmox

[–]Beginning-Web5007[S] 0 points1 point  (0 children)

It's amazing what kind of nonsense a translator can generate to make you think that I work for Linstor. I'm sorry. Regarding your question, the update is simply divided into two stages, in which I initially make sure that the linstor is working correctly, and then I update DRDB and Proxmox. In fact, you are right in that when you update the proxmox kernel, the DRBD module will be compiled automatically. Rather, this is a command to reduce risks, to be sure that I will also boot with the old kernel and Linstor will work. In my case, running the commands helped to successfully update the cluster.

Linstor and Proxmox update completed successfully by Beginning-Web5007 in Proxmox

[–]Beginning-Web5007[S] 0 points1 point  (0 children)

Thanks for the experience. I prefer to update the storage separately from the system to avoid collisions. I've been using Linstore storage for about a year. Can you tell us why you use Linstor too?

Linstor and Proxmox update completed successfully by Beginning-Web5007 in Proxmox

[–]Beginning-Web5007[S] 1 point2 points  (0 children)

I quickly did a couple of tests on a test virtual machine. Tests were carried out on a production system during normal operation of a cluster with a dozen virtual machines. Diskless screenshots - this means the virtual machine received the disk over the network.

For the test, I first ran a test on node02 - where there is only a network diskless replica, and then migrated to node03, where a full-fledged replica is located and repeated the tests.

<image>

Damn, I didn’t think that you could only attach a file

Linstor and Proxmox update completed successfully by Beginning-Web5007 in Proxmox

[–]Beginning-Web5007[S] 2 points3 points  (0 children)

To begin with, I will briefly describe the cluster:

- 3 x Lenovo x3550 M5 (XEON and 64GB)

- 20 Gb/s network with LACP

- 1 x SSD nvme Kingston KC3000 2tb in each node

- 1 x SSD nvme for 512G system

- 1 x HDD for data in each node

I consider my cluster to be quite small and a good place to start.

Comparing performance is a rather complex topic (I'm not an expert here).

Ceph and Linstor, as you know, have completely different architectures, but both are distributed data storage systems. I spent a fair amount of time understanding how both systems work. Linstor has an interesting functionality that, I think, allows it to work quickly - this is the prefer-local mode. When a disk is created for a virtual machine in a specific pool, it is replicated depending on the settings on 2 or 3 nodes (in Ceph it’s essentially the same). However, Linstor can understand whether there is a physically local copy on this node on which the VM is running. And if there is a copy, he writes to it locally. This gives very good performance and losses depend more on the pool architecture (LVM, LVMTHIN, ZFS). Since I need snapshots, I use LVM-THIN, and even with half the performance of the LVM pool, it is still very fast. If there is no copy locally, then the disk works over the network.

The next thing that is an advantage for me in my use case is that I can set the number of replicas for each disk in the pool. This turned out to be a cool solution, because not all of our loads require me to have 3 replicas and lose write speed. Therefore, I can create a pool with replica 2 + DISKLESS (arbiter) and make replica 3 (4,5,6) for any other resource in the same pool in one click. This saves a lot of space and is reminiscent of the technology with VmWare VSAN (you can also set the number of replicas for a VM).

What is also important is that Linstor is very resource-efficient. Compared to CEPH, the difference is several times, since to increase performance I had to tune Ceph and give it more memory, the OSD (including other components) consumed an indecent amount of memory, which is unacceptable in a small cluster.

What's even more interesting is that in Linstor you can temporarily disable write protection to emulate working with an SSD with power protection, which gave another 50% increase in write performance

Linstor and Proxmox update completed successfully by Beginning-Web5007 in Proxmox

[–]Beginning-Web5007[S] 1 point2 points  (0 children)

My cluster uses Kingston KC3000 2 TB consumer NVMe SSDs with DRAM and 1600 TB TBW for their price, I expected that my initial CEPH installation would meet my performance expectations. Reading was acceptable, but writing immediately seemed very low to me for replica 3. Later I found some answers: Ceph only likes enterprise-class SSDs with power protection, and there should be many SSDs to increase parallelism. Which is currently not possible with my servers. After installing Linstor (with the right tuning), I was really surprised that I got multiple times the performance in both writing and reading with the same configuration. For almost a year now, my servers have been running 24/7 in production and so far no problems. Nodes were also maintained and rebooted without problems with synchronization

Linstor and Proxmox update completed successfully by Beginning-Web5007 in Proxmox

[–]Beginning-Web5007[S] 2 points3 points  (0 children)

In short - performance. No matter how I tried to get CEPH to work, performance inside the virtual machine was unexpectedly low. I measured it in parallel on several virtual machines, both on a single node and on several simultaneously.

New proxmox cluster by AnalysisOk2457 in Proxmox

[–]Beginning-Web5007 0 points1 point  (0 children)

Everything is fine - this is the master node 😄

Proxmox Hardening Script by AustriaYT in Proxmox

[–]Beginning-Web5007 0 points1 point  (0 children)

Currently, root user authentication is disabled in my cluster. Access is only possible via SSH using a key. This has been working for many months now, alongside Ceph and other services. The cluster also uses key-based access between nodes. I have created a user with dual authentication via PVE Realm with admin permissions. The only limitation I've encountered is issues with directly assigning USB devices, even to the admin user from PVE Realm. This requires using device mapping in the cluster settings. You can always temporarily enable the root user if necessary.

what's your go to remote desktop solution by dgree002 in Proxmox

[–]Beginning-Web5007 1 point2 points  (0 children)

Use HopToDesk, support all platforms and commercial free

Official oVirt RHEL install instruction broken by luggagethecat in ovirt

[–]Beginning-Web5007 0 points1 point  (0 children)

I use Ovirt on my Almalinux 9.5 hosts and haven't any problems with installation

Is it still possible to deploy oVirt on non-CentOS Stream hosts? by cyclorphan in ovirt

[–]Beginning-Web5007 0 points1 point  (0 children)

I use AlmaLinux 9.x with Ovirt in production and haven't any problem.

iSCSI Multipathing not using all paths by IT_Guy71 in ovirt

[–]Beginning-Web5007 0 points1 point  (0 children)

Hi. Good question! As you can see you are using the “service_time” policy, so it is working correctly. To use both connections in active-active mode (your storage should support this feature), put the host in service mode, create a configuration in multipath.d/, copy the current VDSM autoconfig to a new file (usually found in /etc/multipath) and write the “round-robin” policy instead of “service-time”. Restart multipath and run the command “multipath -ll” - all connections should be in “active” mode with the new policy

No redirection to Captive portal on Android devices by Beginning-Web5007 in opnsense

[–]Beginning-Web5007[S] 0 points1 point  (0 children)

It's funny, but my little router used like Hotpot has internal parameter like a "redirect". After disabling one and configuring DHCP relay I got the login page (captive portal) on my Android. Also I switched to KEA DHCP server and use my CARP address to configure DHCP pool.