This video was a life-saver. I've been dabbling in docker swarm for a while now but have been constraining services to single nodes due to lack of replicated storage. Thanks for the simple walkthrough, it made setup much less intimidating.
Followed both vids so far and they have been a HUGE help. We need a video now showing me how to install a docker or template via portainer ensure the Gluster volume is utilized.
Год назад
Big fan of docker swarm here, happy to see some refreshing videos about it.
Great video! I am going to keep playing with it and get used to creating and destroying volumes in GlusterFS. I also want to set it up with geo replication, so that's the next step, but the official documentation is so frustrating. Also, if you try to locate /test-volume … it does not exist in the original file system. It is in GlusterFS's own file system only, and that is what we are mounting to /mnt. That is the only way that it can make sense to me. And the link between the two file systems is that /glusterfs/volumes = /test-volume. But I might be very wrong here.
Great video I have everything setup and running. Im running a 12 pi cluster but I only see 23G that are being shared when each pi has 64G each. Can I add a SSD to this ?
In your next video are you going to cover the portainer plugin for glusterfs on raspberry pi? Here is a snippet to look into: docker plugin install --alias glusterfs mochoa/glusterfs-volume-plugin-aarch64 --grant-all-permissions In my case I was working with 64 bit pi400 with the 23.04 ubuntu server.
I'm new to linux, and my questions below may look immature. Sorry for that. 1) Can i use exisiting oracle block storage mounts as glousterfs volumes? 2) Does glousterfs nodes needs to be on the same cloud region or can this be from any cloud region as long as there is an active tunneling established acrossed the nodes? 3) What happens if one of the three nodes reboots or goes to a hung state, and will it affect the entire glusterfs system temporarily?
Thank you - all up and running on Bullseye 64bit. My only problem is after a restart the /mnt is not working. Master and nodes starting at the same time - so I think therfore I never get them mount over /etc/fstab - I am searching for a solution.
QQ. Do you recommend setting up each Ubuntu VMs, each with 2 separate disks, the first disk to run the OS, and the second as the GlusterFS replicated volume? Or could I provision the VMs to store OS and GlusterFS replicated volume configuration on one huge iSCSi LUN on my Proxmox hypervisor? Please let me know. Thanks.
Hey, great question! So, think of GlusterFS kind of like a smarter version of NFS. Instead of keeping all your data in just one spot, GlusterFS can spread it out or make copies across different machines in your swarm. This means you're not just pointing to where the data lives; you're actually sharing it around so that if one machine goes kaput, you're not left in the lurch. It's all about making sure your data is safe, sound, and readily accessible, no matter what happens. Hope that clears things up!
And... Where is the swarm setup? How to make 5 step guide is great, but mount local glusterfs, docker plug-in for this fs and other stuff is necessary. It is "zero level" tutorial 😢
Yeah, I'll be honest I was planning on creating more videos on swarm and making a series but it's run away from me a bit. This was to be part of a bigger implementation guide.
nearly at the end hit a snag... seeking to mount the GlusterFS volume to the /mnt. Got this exception. ERROR: Server name/volume name unspecified cannot proceed further.. Please specify correct format Usage: man 8 /usr/sbin/mount.glusterfs
@@Techdox I tried, but not thsi round. Perhaps it is a RPi issue, not sure. The share shows on each system but it ran into a road bump... needed to move on. Working on a startup self funded project so conserving time and resources pulled me off that till I get additional eyes on. I think it will need paired focus.
