Hi Timur,
Here's the synopsis:
Gluster talks through the FUSE filesystem to a tcp socket (default 6996) to
other machines. If you think of the OSI model, it goes down the stack on one
machine and up the corresponding stack on the other. In other words, it hits
the tcp port (6996) on the other machine and to FUSE.
Now, here's the fun part: if you have a directory /a/tmp as a filesystem on
BOTH machines of EQUAL SIZE and you want to put something under gluster
control. You get gluster up and working on both sides.
I'll provide my file for example after this. (I got help from the gluster
people)
Start it with: glustfsd -f <file>.vol --debug on both machines.
(debug is to make sure everything is working.
Performing a df on both machines you should see:
/dev/ad0s1d # # % /tmp/a
/dev/fuse0 # # % /mnt/a
This will show you that both machines are up and running. In order for stuff
to now be put under gluster control (it's a filesystem so it has to have
extended attributes turned on), you have to cp the info from somewhere and put
it into /mnt/a (tar, cp, etc)
In your debug screen, you'll see it go wild as it puts everything under
glusterfs control. On both machines, you'll see /mnt/a and /tmp/a get
populated simultaneously.
Pretty darn slick. Also, ORDER of the layers is important. My file, afr.vol
is:
volume posix
type storage/posix
option directory /a/tmp
end-volume
volume brick
type features/locks
subvolumes posix
end-volume
volume server
type protocol/server
option transport-type tcp
subvolumes brick
option auth.addr.brick.allow *
end-volume
volume machine01
type protocol/client
option transport-type tcp
option remote-host 10.1.1.1
option remote-subvolume brick
end-volume
volume machine02
type protocol/client
option transport-type tcp
option remote-host 10.1.1.2
option remote-subvolume brick end-volume
volume home
type cluster/afr
option read-subvolume `hostname`
subvolumes machine01 machine02
Paul Pathiakis
UNIX/Linux Systems Engineer
Iron Mountain Digital
120 Turnpike Rd.
Southborough, MA 01772
Microsoft - Where do you want to go today?
Linux - Where do you want to go tomorrow?
FreeBSD - Will you guys come on already?
-----Original Message-----
From: ti...@bat.ru [mailto:ti...@bat.ru] On Behalf Of Timur I. Bakeyev
Sent: Sunday, March 15, 2009 8:16 PM
To: Pathiakis, Paul
Cc: Jim Riggs; David N; po...@freebsd.org; Steven Kreuzer
Subject: Re: Port Request: gluster
Hi, Paul!
I'm working on it for quite a while, but still there are some rough
edges. What is your user experience with it?
With regards,
Timur.
On Wed, Mar 11, 2009 at 10:12 PM, Pathiakis, Paul
<paul.pathia...@ironmountain.com> wrote:
> Hi to all!
>
> Has anything progressed on this?
>
> I'm actually building it by hand on a couple of 7.1 machines. I expect
> it will be interesting.
>
> I still look forward to the port. :-)
>
> Thank you!
>
> Paul Pathiakis
> UNIX/Linux Systems Engineer
> Iron Mountain Digital
> 120 Turnpike Rd.
> Southborough, MA 01772
>
>
> Microsoft - Where do you want to go today?
> Linux - Where do you want to go tomorrow?
> FreeBSD - Will you guys come on already?
>
>
> -----Original Message-----
> From: Jim Riggs [mailto:po...@christianserving.org]
> Sent: Friday, February 20, 2009 8:31 PM
> To: David N
> Cc: Pathiakis, Paul; po...@freebsd.org; Steven Kreuzer
> Subject: Re: Port Request: gluster
>
> On 02/20/2009 11:40, David N wrote:
>> 2009/2/21 Pathiakis, Paul<paul.pathia...@ironmountain.com>:
>>> Steven,
>>>
>>> I'm going to start testing it in a pre-production environment. It
> seems
>>> so straightforward, integrates with ZFS, it has simple configuration
>>> files, all around, I'm hoping that it garners more
>>> clustering/replication for FreeBSD. Many of the other solutions are
>>> quite tedious and setup complexity is quite annoying.
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Steven Kreuzer [mailto:ste...@hudson-trading.com] On Behalf Of
>>> Steven Kreuzer
>>> Sent: Friday, February 20, 2009 11:30 AM
>>> To: Pathiakis, Paul
>>> Cc: po...@freebsd.org
>>> Subject: Re: Port Request: gluster
>>>
>>>
>>> On Feb 20, 2009, at 9:51 AM, Pathiakis, Paul wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I'd like to request that the gluster clustering/filesystem software
> be
>>>> ported and supported. This looks to be a very simple,
> straightforward
>>>> and viable clustering solution which FreeBSD has always lacked.
>>> This looks like a very interesting project. I might be able to take
>>> some time
>>> over the weekend and create a port for this.
>>>
>>> Out of curiosity, have you been using it in production? If so, can
> you
>>> describe your setup
>>> and your experience with it?
>>>
>>> Steven Kreuzer
>>> http://www.exit2shell.com/~skreuzer
>>>
>> Looks promising
>> http://www.gluster.org/docs/index.php/GlusterFS_on_BSD
>
>
> Several weeks ago I actually created a port for glusterfs as I was
> hoping to implement it myself. I'll have to see if I saved any of my
> work. I actually had a working port, but I may have dumped it. I will
> be happy to submit it if I can find it. I just don't know that I will
> be able to maintain it.
>
> A couple of notes from what I found:
>
> 1. It does not yet integrate with FreeBSD's implementation of ZFS (at
> least not in 7.x) due to the lack of ACL support. You can use it with a
> UFS partition or a UFS zvol. (Using a zvol requires a patch pjd@
> recommended for performance improvements.)
>
> 2. Performance in my setup was not very good over 2x1Gb LAGG. It might
> be better over a faster, dedicated channel of some type.
>
> - Jim
>
>
> The information contained in this email message and its attachments
> is intended
> only for the private and confidential use of the recipient(s) named
> above, unless the sender expressly agrees otherwise. Transmission
> of email over the Internet
> is not a secure communications medium. If you are requesting or
> have requested
> the transmittal of personal data, as defined in applicable privacy
> laws by means
> of email or in an attachment to email you must select a more
> secure alternate means of transmittal that supports your
> obligations to protect such personal data. If the reader of this
> message is not the intended recipient and/or you have received this
> email in error, you must take no action based on the information in
> this email and you are hereby notified that any dissemination,
> misuse, copying, or disclosure of this communication is strictly
> prohibited. If you have received
> this communication in error, please notify us immediately by email
> and delete the original message.
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
