Perhaps you can use this tools: https://aravindavk.in/blog/gluster-georep-tools/ I am using it with great success. Em qui., 22 de ago. de 2024 ?s 17:36, Karl Kleinpaste <karl at kleinpaste.org> escreveu:> On 8/22/24 14:08, Strahil Nikolov wrote: > > I can try to reproduce it if you could provide the gluster version, > operating system and volume options. > > > Most kind. > > Fedora39, Packages: > > $ grep gluster /var/log/rpmpkgs > gluster-block-0.5-11.fc39.x86_64.rpm > glusterfs-11.1-1.fc39.x86_64.rpm > glusterfs-cli-11.1-1.fc39.x86_64.rpm > glusterfs-client-xlators-11.1-1.fc39.x86_64.rpm > glusterfs-cloudsync-plugins-11.1-1.fc39.x86_64.rpm > glusterfs-coreutils-0.3.2-1.fc39.x86_64.rpm > glusterfs-events-11.1-1.fc39.x86_64.rpm > glusterfs-extra-xlators-11.1-1.fc39.x86_64.rpm > glusterfs-fuse-11.1-1.fc39.x86_64.rpm > glusterfs-geo-replication-11.1-1.fc39.x86_64.rpm > glusterfs-resource-agents-11.1-1.fc39.noarch.rpm > glusterfs-server-11.1-1.fc39.x86_64.rpm > glusterfs-thin-arbiter-11.1-1.fc39.x86_64.rpm > libglusterfs0-11.1-1.fc39.x86_64.rpm > libvirt-daemon-driver-storage-gluster-9.7.0-4.fc39.x86_64.rpm > python3-gluster-11.1-1.fc39.x86_64.rpm > qemu-block-gluster-8.1.3-5.fc39.x86_64.rpm > > (Somewhere along the way, I'm sure I just did "dnf install *gluster*".) > > The two volumes were created using the quick start guide: > https://docs.gluster.org/en/main/Quick-Start-Guide/Quickstart/ > which means that, after establishing peering, I used these simple commands: > > (on pjs) gluster volume create j pjs:/xx/brick > (on pms) gluster volume create n pms:/xx/brick > > where /xx on these 2 systems are small, spare, otherwise empty, identical > filesystems of about 40G, formatted ext4. No other options were used in > creation. > > As I said in my initial note, it seems that the underlying problem (from > logged complaints) is lack of a geo-rep template configuration from which > to set up, and I simply don't know where/how/when that should have been > created. But this is just a surmise on my part. > ________ > > > > Community Meeting Calendar: > > Schedule - > Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC > Bridge: https://meet.google.com/cpu-eiue-hvk > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20240822/23d8e53d/attachment.html>
On 8/22/24 21:54, Gilberto Ferreira wrote:> Perhaps you can use this tools: > https://aravindavk.in/blog/gluster-georep-tools/ > I am using it with great success.I'll try anything once. In fact, I tried twice. It can't set up. First, the code has port 22 baked in. I mentioned earlier that my sshd listens on a nonstandard port. Looking at the code (gluster_georep_tools/setup/cli.py, glustercli/cli/georep.py), there is provision within functions for a different port, but there is no way that I see to use that in command line args. Oddly shortsighted, or maybe I'm missing something. So second, I tweaked the code to use my nonstandard port as its default, replacing all "22" with mine, and tried again...nope. Geo-replication session will be established between j and geoacct at pms::n root at pms password is required to complete the setup. NOTE: Password will not be stored. root at pms's password: [??? OK] pms is Reachable(Port 6247) Traceback (most recent call last): ? File "/usr/local/bin/gluster-georep-setup", line 8, in <module> ??? sys.exit(main()) ???????????? ^^^^^^ ? File "/usr/local/lib/python3.12/site-packages/gluster_georep_tools/setup/cli.py", line 524, in main ??? setup_georep() ? File "/usr/local/lib/python3.12/site-packages/gluster_georep_tools/setup/cli.py", line 461, in setup_georep ??? ssh = ssh_initialize(secondary_host, args.secondary_user, passwd) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ? File "/usr/local/lib/python3.12/site-packages/gluster_georep_tools/setup/cli.py", line 212, in ssh_initialize ??? ssh.connect(secondary_host, username=username, password=passwd) ? File "/usr/lib/python3.12/site-packages/paramiko/client.py", line 409, in connect ??? raise NoValidConnectionsError(errors) paramiko.ssh_exception.NoValidConnectionsError: [Errno None] Unable to connect to port 22 on 172.17.4.3 It seems that paramiko is either still using 22 under the hood somewhere (cf. last line error), or 22 is misinfo but it's insisting on connection using a password, but my (otherwise pretty standard) sshd configuration requires keys-only root login, no password, which is already in place among all these machines. I'm open to other suggestions. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20240823/0f431a78/attachment.html>