opensvc / opensvc

The OpenSVC node agent
https://www.opensvc.com
GNU General Public License v2.0
35 stars 10 forks source link

You guys are awesome, please do a bit more for opensvc #652

Open woodholly opened 3 months ago

woodholly commented 3 months ago

OMG I am so happy I came across this project, it is clearly underrated and deserves more attention! I was looking for a way to get rid of ZFS/BTRFS in KVM asynchronous geo replication setup (send - recieve), even started to think on how to do it using libvirt + Qcow2 + snapshot replication (in theory it is possible by "virsh blockcommit" incremental snapshots on both sides). But now I my search is over because of yours https://docs.opensvc.com/latest/storage.dds.html !

I see you guys actively develop opensvc, please make it more popular by these simple steps: 1) update year on opensvc.com website to 2024 and add LARGE link to github 2) make new release or at least new tag in 2024 3) add keywords "asynchronous geo replication for KVM virtual machines using LVM, get rid of ZFS and BTRFS send/receive" to https://docs.opensvc.com/latest/storage.dds.html so others can find it faster. Please also add these keywords and tags to the README https://github.com/opensvc/opensvc

Thank you!

cvaroqui commented 3 months ago

Thank you for your kind words.

We have now updated the copyright years on www.opensvc.com. Thank you for the heads-up.

The link to github is the 2nd icon in the doc navigation menu, out of 5. It is labelled "Sources". We are pondering simplifying the website layout and will consider this advice if we decide to go this road.

For the 2.1 branch of the opensvc agent (production) branch, every PR we merge produces packages and can be considered a minor release. For the next major version (in opensvc/om3) we will use a stricter semver approach and explicit github releases. But this version is still alpha for now.

Please feel free to submit "meta" patches for opensvc/docs.opensvc.com, or open the third item as a new issue there. Note, as we also support drivers for zfs and btrfs send/receive we won't trash-talk some tech ... they all have a different sweet spot, and our clients/users can decide what's best for them. For example, for your use-case, some may prefer to send/recv a zvol backing the kvm disk, or drbd.

For reference, here is a resource configuration for such a zfs send/recv replication:

[sync#1]
src = data/{fqdn}
dst = data/{fqdn}
type = zfs
target = nodes
recursive = true
schedule = @12h