Gluster users - Jun 2017 - Persistent storage for docker containers from a Gluster volume

On 28-Jun-2017 5:49 PM, "mabi" <mabi at protonmail.ch> wrote:

Anyone?



-------- Original Message --------
Subject: Persistent storage for docker containers from a Gluster volume
Local Time: June 25, 2017 6:38 PM
UTC Time: June 25, 2017 4:38 PM
From: mabi at protonmail.ch
To: Gluster Users <gluster-users at gluster.org>

Hello,
I have a two node replica 3.8 GlusterFS cluster and am trying to find out
the best way to use a GlusterFS volume as persistent storage for docker
containers to store their data (e.g. web assets).
I was thinking that the simplest method would be to mount my GlusterFS
volume for that purpose on all docker nodes using FUSE and then simply
start containers which require persistent storage with a mount of bind
type. For example here is how I would create my container requiring
persistent storage:

docker service create --name testcontainer --mount type=bind,source=/mnt/
gustervol/testcontainer,target=/mnt alpine



What do you think about that? Is this a good way? or is the even a better
way?



If you are using kubernetes, then please have a look at

https://github.com/gluster/gluster-kubernetes

Otherwise, what you are suggesting works.

Raghavendra Talur



Regards,
M.


_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170629/fda8ee25/attachment.html>

Hi,

glusterFS is working fine for large files (in most of the cases it's 
used for VM image store), with docker you'll generate bunch of small 
size files and if you want to have a good performance may be look in [1] 
and [2].

Also two node replica is a bit dangerous in case of high load with small 
files there is a good risk of split brain situation, therefore think 
about arbiter functionality of gluster [3], I think if you'll apply 
recommendations from [1] and [2] and deploy arbiter volume.

Cheers

Erekle


[1] 
http://blog.gluster.org/2016/10/gluster-tiering-and-small-file-performance/

[2] 
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Small_File_Performance_Enhancements.html

[3] 
http://events.linuxfoundation.org/sites/events/files/slides/glusterfs-arbiter-VAULT-2016.pdf


On 29.06.2017 11:55, Raghavendra Talur wrote:
>
>
> On 28-Jun-2017 5:49 PM, "mabi" <mabi at protonmail.ch 
> <mailto:mabi at protonmail.ch>> wrote:
>
>     Anyone?
>
>
>
>>     -------- Original Message --------
>>     Subject: Persistent storage for docker containers from a Gluster
>>     volume
>>     Local Time: June 25, 2017 6:38 PM
>>     UTC Time: June 25, 2017 4:38 PM
>>     From: mabi at protonmail.ch <mailto:mabi at protonmail.ch>
>>     To: Gluster Users <gluster-users at gluster.org
>>     <mailto:gluster-users at gluster.org>>
>>
>>     Hello,
>>     I have a two node replica 3.8 GlusterFS cluster and am trying to
>>     find out the best way to use a GlusterFS volume as persistent
>>     storage for docker containers to store their data (e.g. web
assets).
>>     I was thinking that the simplest method would be to mount my
>>     GlusterFS volume for that purpose on all docker nodes using FUSE
>>     and then simply start containers which require persistent storage
>>     with a mount of bind type. For example here is how I would create
>>     my container requiring persistent storage:
>>
>>     docker service create --name testcontainer --mount
>>     type=bind,source=/mnt/gustervol/testcontainer,target=/mnt alpine
>>
>>
>>
>>     What do you think about that? Is this a good way? or is the even
>>     a better way?
>
>
>
> If you are using kubernetes, then please have a look at
>
> https://github.com/gluster/gluster-kubernetes
>
> Otherwise, what you are suggesting works.
>
> Raghavendra Talur
>
>
>>
>>     Regards,
>>     M.
>
>     _______________________________________________
>     Gluster-users mailing list
>     Gluster-users at gluster.org <mailto:Gluster-users at
gluster.org>
>     http://lists.gluster.org/mailman/listinfo/gluster-users
>     <http://lists.gluster.org/mailman/listinfo/gluster-users>
>
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170629/100ed32c/attachment.html>

Thank you very much Erekle for your links, they are all relevant to me and very
interesting as as you mention I will be mostly serving a lot of rather smaller
files from my containers.
I will first consider upgrading my gluserfs from 3.8 to 3.10 to take advantage
of the small file performance improvements which is afaik newly available in
3.10.
Best regards,
M.
> -------- Original Message --------
> Subject: Re: [Gluster-users] Persistent storage for docker containers from
a Gluster volume
> Local Time: June 29, 2017 12:34 PM
> UTC Time: June 29, 2017 10:34 AM
> From: erekle.magradze at recogizer.de
> To: mabi at protonmail.ch, gluster-users at gluster.org
>
> Hi,
>
> glusterFS is working fine for large files (in most of the cases it's
used for VM image store), with docker you'll generate bunch of small size
files and if you want to have a good performance may be look in [1] and [2].
>
> Also two node replica is a bit dangerous in case of high load with small
files there is a good risk of split brain situation, therefore think about
arbiter functionality of gluster [3], I think if you'll apply
recommendations from [1] and [2] and deploy arbiter volume.
>
> Cheers
>
> Erekle
>
> [1]
http://blog.gluster.org/2016/10/gluster-tiering-and-small-file-performance/
>
> [2]
https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Small_File_Performance_Enhancements.html
>
> [3]
http://events.linuxfoundation.org/sites/events/files/slides/glusterfs-arbiter-VAULT-2016.pdf
>
> On 29.06.2017 11:55, Raghavendra Talur wrote:
>
>> On 28-Jun-2017 5:49 PM, "mabi" <mabi at protonmail.ch>
wrote:
>>
>>> Anyone?
>>>
>>>> -------- Original Message --------
>>>> Subject: Persistent storage for docker containers from a
Gluster volume
>>>> Local Time: June 25, 2017 6:38 PM
>>>> UTC Time: June 25, 2017 4:38 PM
>>>> From: mabi at protonmail.ch
>>>> To: Gluster Users <gluster-users at gluster.org>
>>>> Hello,
>>>> I have a two node replica 3.8 GlusterFS cluster and am trying
to find out the best way to use a GlusterFS volume as persistent storage for
docker containers to store their data (e.g. web assets).
>>>> I was thinking that the simplest method would be to mount my
GlusterFS volume for that purpose on all docker nodes using FUSE and then simply
start containers which require persistent storage with a mount of bind type. For
example here is how I would create my container requiring persistent storage:
>>>> docker service create --name testcontainer --mount
type=bind,source=/mnt/gustervol/testcontainer,target=/mnt alpine
>>>> What do you think about that? Is this a good way? or is the
even a better way?
>> If you are using kubernetes, then please have a look at
>> https://github.com/gluster/gluster-kubernetes
>> Otherwise, what you are suggesting works.
>> Raghavendra Talur
>>
>>>> Regards,
>>>> M.
>>> _______________________________________________
>>> Gluster-users mailing list
>>> Gluster-users at gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>>
>> http://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20170629/5a37cd1b/attachment.html>