Hi Bryan,
Not much luck with this I'm afraid. I followed the documentation to the letter
and I managed to add a 3-node primary storage in CS, I can see the random named
linstor resources created by CS, yet I cannot create any instances, there's
always error at startup, like the one bellow.
Unable to orchestrate start VM instance
{"id":18,"instanceName":"i-2-18-VM","type":"User","uuid":"867503d9-3912-47e4-85be-a30b3e088aa4"}
due to [Create volume from template (ID = 4) failed: Resource definition
'cs-null' not found.].
This is the method I used, except I didn't create a zfs pool, I created a
thin-lvm one:
https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-linstor-cloudstack-installing-linstor
Any idea why this is happening?
-----Original Message-----
From: Bryan Tiang <[email protected]>
Sent: Friday, March 29, 2024 4:38 PM
To: [email protected]; [email protected]
Subject: RE: Storage solution for Cloudstack
Hey Alexandru,
The architecture is not quite the same because Linstors secret sauce is that
they use DRBD, which is what allows them to get such high performance and low
latency.
You can check up more about it here:
https://linbit.com/blog/how-does-linstor-compare-to-ceph/#:~:text=Ceph's%20use%20of%20the%20CRUSH,Ceph%20isn't%20operating%20normally.
And some performance benchmarks with ceps, here:
https://blog.palark.com/kubernetes-storage-performance-linstor-ceph-mayastor-vitastor/
Regards,
Bryan
On 29 Mar 2024 at 4:11 PM +0800, Bryan Tiang <[email protected]>, wrote:
>
>
> Bryan
