| 10 Mar 2024 |
 adamcstephens | mkg20001 if you update the UI package will you make it a full package instead of overriding the lxd one? | 17:42:01 |
 mkg20001 | In reply to @adam:robins.wtf
mkg20001 if you update the UI package will you make it a full package instead of overriding the lxd one? why? is there any issue with the override? | 18:15:56 |
| adamcstephens | Don’t we want to ensure we update any patches/scripts from zabbly when we update the source package? | 18:17:22 |
| adamcstephens | I’m also still hoping to deprecate lxd. I’ve just been waiting for incus LTS | 18:17:51 |
 hexa | after reading alot of the docs; does incus support online migration with anything but ceph? | 18:22:56 |
| hexa | I feel they're not being clear on what is possible with what | 18:23:27 |
| adamcstephens | maybe the new lvmlock support? | 18:39:17 |
| adamcstephens | i don't have shared storage so i haven't explored it myself | 18:40:42 |
| hexa | Yeah, but lvm means having shared central storage | 18:49:55 |
| hexa | Which blows | 18:49:59 |
| adamcstephens | don't you already run ceph? | 19:00:53 |
| hexa | I do | 19:02:58 |
| hexa | was just trying to understand the alternatives | 19:03:12 |
| adamcstephens | https://github.com/lxc/incus/issues/564 | 19:03:48 |
| adamcstephens | https://github.com/lxc/incus/issues/344 | 19:04:05 |
| hexa | glusterfs is some weird distributed filesystem 😄 | 19:05:09 |
| hexa | linstor is iirc the firm behind drbd | 19:05:19 |
| adamcstephens | yep | 19:05:26 |
| hexa | or linbit is | 19:05:31 |
| hexa | I don't want to go back to drbd 😄 | 19:05:45 |
| hexa | so what is linstor | 19:05:53 |
| hexa |
LINSTOR has multiple uses, but it is typically used to manage a large number of DRBD replicated storage resources
| 19:06:53 |
| adamcstephens | i've never used drbd 🤷♂️ | 19:07:16 |
| hexa | way back, when we had two node hypervisor clusters over 10y ago | 19:07:30 |
| adamcstephens | yeah, gluster is also an old filesystem. but it's dying | 19:10:00 |
| adamcstephens | i think the real problem is clustered/distributed filesystems are hard and RH is probably the only one making any serious money with them | 19:12:24 |
| adamcstephens | (in the open source space) | 19:12:40 |
| hexa | so what clusterlvm does is make sure that in a clustered lvm setup that only one node can write metadata | 19:16:09 |
| hexa | they share the same block device, which can be attached by any means, but most likely iscsi | 19:16:27 |
| hexa | that only makes sense if you have a chonky multihead storage cluster | 19:16:41 |
