Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On 07/01/2015 03:03 PM, Deepak Shetty wrote: > On Wed, Jul 1, 2015 at 11:32 AM, Krishnan Parthasarathi > wrote: > >> >>> Yeah this followed by glusterd restart should help >>> >>> But frankly, i was hoping that 'rm' the file isn't a neat way to fix this >>> issue >> >> Why is rm not a neat way? Is it because the container deployment tool >> needs to >> know about gluster internals? But isn't a Dockerfile dealing with details >> of the service(s) that is being deployment in a container. >> > > IIUC post 'rm' we need to restart glusterd, but touching a file as part of > Dockerfile > would bringup glusterd with the new UUID. I haven't tried this tho' > > I guess like Humble said, fixing this in glusterd seems ideal > The above discussion was _if_ glusterd continues the current behavior > then either 'rm' or 'touch' methods could be considered. Here you go, http://review.gluster.org/11488 should fix it and yes the changes are in glusterD ;) > > thanx, > deepak > -- ~Atin ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On Wed, Jul 1, 2015 at 9:39 AM, Atin Mukherjee wrote: > > > On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote: > > Hi All, > > > > > > Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS (7) are now > > available at docker hub ( https://registry.hub.docker.com/u/gluster/ ). > > These images can be used to deploy GlusterFS containers. > > > > The blog entry at planet.gluster.org [1] have details about how these > > images can be used. > > > > Please let me know if you have any comments/feedback/questions. > > > > [1] Building GlusterFS in a docker container @ planet.gluster.org > > [2] http://humblec.com/building-glusterfs-in-a-docker-container/ > Hi Humble, > > As discussed yesterday, post daemon refactoring we generate UUID at the > the time of glusterD init and this has caused an issue in bringing > multiple docker containers as UUIDs will be same across different > containers since yum install brings up glusterd and persist the > information in /var/lib/glusterd.info. This also means we should add a testcase and QEs should cover this scenario as part of their testing to ensure we don't break gluster for common-image-base type scenarios (containers, ovirt, virtualization templates). thanx, deepak ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On Wed, Jul 1, 2015 at 11:32 AM, Krishnan Parthasarathi wrote: > > > Yeah this followed by glusterd restart should help > > > > But frankly, i was hoping that 'rm' the file isn't a neat way to fix this > > issue > > Why is rm not a neat way? Is it because the container deployment tool > needs to > know about gluster internals? But isn't a Dockerfile dealing with details > of the service(s) that is being deployment in a container. > IIUC post 'rm' we need to restart glusterd, but touching a file as part of Dockerfile would bringup glusterd with the new UUID. I haven't tried this tho' I guess like Humble said, fixing this in glusterd seems ideal The above discussion was _if_ glusterd continues the current behavior then either 'rm' or 'touch' methods could be considered. thanx, deepak ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
Hi Raghavendra Bhat, Yes, its "gluster system uuid reset" command and it can resolve this issue. --Humble On Wed, Jul 1, 2015 at 12:01 PM, Raghavendra Bhat wrote: > On 07/01/2015 11:51 AM, Krishnan Parthasarathi wrote: > >> We do have a way to tackle this situation from the code. Raghavendra >>> Talur will be sending a patch shortly. >>> >> We should fix it by undoing what daemon-refactoring did, that broke the >> lazy creation >> of uuid for a node. Fixing it elsewhere is just masking the real cause. >> Meanwhile 'rm' is the stop gap arrangement. >> > > I remember a cli command to reset the glusterd uuid. (I think it is > "gluster system uuid reset". Not sure if its the exact command. But > something similar.) Its main purpose is to generate a new uuid for that > node (thus discarding the existing uuid) and start using that new uuid. > > Regards, > Raghavendra Bhat > > > ___ >> Gluster-users mailing list >> Gluster-users@gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >> > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users > ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
> Yeah this followed by glusterd restart should help > > But frankly, i was hoping that 'rm' the file isn't a neat way to fix this > issue >>Why is rm not a neat way? Is it because the container deployment tool needs to >>know about gluster internals? But isn't a Dockerfile dealing with details >>of the service(s) that is being deployment in a container. I do think fixing the dockerfile is *not* the correct way. That said, the use case is not just containers. This issue can pop up in Ovirt or virtualization environments as well. The VM template may have pre configured glusterd in it and the pool created out of this template can show the same behaviour. I believe fixing it in gluster code base would be the right thing to do. Thanks Atin for the heads up! > AFAICT we have 2 scenarios: > > 1) Non-container scenario, where the current behaviour of glusterd persisting > the info in .info file makes sense > > 2) Container scenario, where the same image gets used as the base, hence all > containers gets the same UUID > For this we can have an option to tell glusterd that instructs it to refresh > the UUID during next start. > --Humble On Wed, Jul 1, 2015 at 11:32 AM, Krishnan Parthasarathi wrote: > > > Yeah this followed by glusterd restart should help > > > > But frankly, i was hoping that 'rm' the file isn't a neat way to fix this > > issue > > Why is rm not a neat way? Is it because the container deployment tool > needs to > know about gluster internals? But isn't a Dockerfile dealing with details > of the service(s) that is being deployment in a container. > > > AFAICT we have 2 scenarios: > > > > 1) Non-container scenario, where the current behaviour of glusterd > persisting > > the info in .info file makes sense > > > > 2) Container scenario, where the same image gets used as the base, hence > all > > containers gets the same UUID > > For this we can have an option to tell glusterd that instructs it to > refresh > > the UUID during next start. > > > > Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid > makes > > glusterd refresh the UUID in .info > > and then delete this file, that ways, Dockerfile can touch this file, > post > > gluster rpm install step and things should > > work as expected ? > > If container deployment needs are different it should should address > issues like > above. If we start addressing glusterd's configuration handling for every > new deployment technology it would quickly become unmaintainable. > ___ > Gluster-devel mailing list > gluster-de...@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On 07/01/2015 11:51 AM, Krishnan Parthasarathi wrote: We do have a way to tackle this situation from the code. Raghavendra Talur will be sending a patch shortly. We should fix it by undoing what daemon-refactoring did, that broke the lazy creation of uuid for a node. Fixing it elsewhere is just masking the real cause. Meanwhile 'rm' is the stop gap arrangement. I remember a cli command to reset the glusterd uuid. (I think it is "gluster system uuid reset". Not sure if its the exact command. But something similar.) Its main purpose is to generate a new uuid for that node (thus discarding the existing uuid) and start using that new uuid. Regards, Raghavendra Bhat ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On Wed, Jul 1, 2015 at 11:51 AM, Krishnan Parthasarathi wrote: > > > We do have a way to tackle this situation from the code. Raghavendra > > Talur will be sending a patch shortly. > > We should fix it by undoing what daemon-refactoring did, that broke the > lazy creation > of uuid for a node. Fixing it elsewhere is just masking the real cause. > Meanwhile 'rm' is the stop gap arrangement. > Agreed. The patch I was supposed to send may not solve this issue . Atin understands this code well better than I and I guess would be sending the patch to generate uuid on first volume creation or first peer probe instead of on first start of glusterd. > ___ > Gluster-devel mailing list > gluster-de...@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel > -- *Raghavendra Talur * ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
> We do have a way to tackle this situation from the code. Raghavendra > Talur will be sending a patch shortly. We should fix it by undoing what daemon-refactoring did, that broke the lazy creation of uuid for a node. Fixing it elsewhere is just masking the real cause. Meanwhile 'rm' is the stop gap arrangement. ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
> Yeah this followed by glusterd restart should help > > But frankly, i was hoping that 'rm' the file isn't a neat way to fix this > issue Why is rm not a neat way? Is it because the container deployment tool needs to know about gluster internals? But isn't a Dockerfile dealing with details of the service(s) that is being deployment in a container. > AFAICT we have 2 scenarios: > > 1) Non-container scenario, where the current behaviour of glusterd persisting > the info in .info file makes sense > > 2) Container scenario, where the same image gets used as the base, hence all > containers gets the same UUID > For this we can have an option to tell glusterd that instructs it to refresh > the UUID during next start. > > Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid makes > glusterd refresh the UUID in .info > and then delete this file, that ways, Dockerfile can touch this file, post > gluster rpm install step and things should > work as expected ? If container deployment needs are different it should should address issues like above. If we start addressing glusterd's configuration handling for every new deployment technology it would quickly become unmaintainable. ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On 07/01/2015 11:09 AM, Deepak Shetty wrote: > On Wed, Jul 1, 2015 at 9:39 AM, Atin Mukherjee wrote: > >> >> >> On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote: >>> Hi All, >>> >>> >>> Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS (7) are now >>> available at docker hub ( https://registry.hub.docker.com/u/gluster/ ). >>> These images can be used to deploy GlusterFS containers. >>> >>> The blog entry at planet.gluster.org [1] have details about how these >>> images can be used. >>> >>> Please let me know if you have any comments/feedback/questions. >>> >>> [1] Building GlusterFS in a docker container @ planet.gluster.org >>> [2] http://humblec.com/building-glusterfs-in-a-docker-container/ >> Hi Humble, >> >> As discussed yesterday, post daemon refactoring we generate UUID at the >> the time of glusterD init and this has caused an issue in bringing >> multiple docker containers as UUIDs will be same across different >> containers since yum install brings up glusterd and persist the >> information in /var/lib/glusterd.info. To make this work for docker >> containers could you add a line just after the installation steps in >> Dockerfile? >> > > Yeah I too faced this issued in recent past, fixing this will help users > running gluster in containers. > > >> >> rm -rf /var/lib/glusterd/glusterd.info >> > > Yeah this followed by glusterd restart should help > > But frankly, i was hoping that 'rm' the file isn't a neat way to fix this > issue > AFAICT we have 2 scenarios: > > 1) Non-container scenario, where the current behaviour of glusterd > persisting the info in .info file makes sense > > 2) Container scenario, where the same image gets used as the base, hence > all containers gets the same UUID > For this we can have an option to tell glusterd that instructs it to > refresh the UUID during next start. > > Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid > makes glusterd refresh the UUID in .info > and then delete this file, that ways, Dockerfile can touch this file, post > gluster rpm install step and things should > work as expected ? We do have a way to tackle this situation from the code. Raghavendra Talur will be sending a patch shortly. > > thanx, > deepak > > > >> >> I could not find a way to send a pull request on this. >> >> ~Atin >>> >>> --Humble >>> >>> >>> >>> ___ >>> Gluster-devel mailing list >>> gluster-de...@gluster.org >>> http://www.gluster.org/mailman/listinfo/gluster-devel >>> >> >> -- >> ~Atin >> ___ >> Gluster-users mailing list >> Gluster-users@gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >> > -- ~Atin ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On Wed, Jul 1, 2015 at 9:39 AM, Atin Mukherjee wrote: > > > On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote: > > Hi All, > > > > > > Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS (7) are now > > available at docker hub ( https://registry.hub.docker.com/u/gluster/ ). > > These images can be used to deploy GlusterFS containers. > > > > The blog entry at planet.gluster.org [1] have details about how these > > images can be used. > > > > Please let me know if you have any comments/feedback/questions. > > > > [1] Building GlusterFS in a docker container @ planet.gluster.org > > [2] http://humblec.com/building-glusterfs-in-a-docker-container/ > Hi Humble, > > As discussed yesterday, post daemon refactoring we generate UUID at the > the time of glusterD init and this has caused an issue in bringing > multiple docker containers as UUIDs will be same across different > containers since yum install brings up glusterd and persist the > information in /var/lib/glusterd.info. To make this work for docker > containers could you add a line just after the installation steps in > Dockerfile? > Yeah I too faced this issued in recent past, fixing this will help users running gluster in containers. > > rm -rf /var/lib/glusterd/glusterd.info > Yeah this followed by glusterd restart should help But frankly, i was hoping that 'rm' the file isn't a neat way to fix this issue AFAICT we have 2 scenarios: 1) Non-container scenario, where the current behaviour of glusterd persisting the info in .info file makes sense 2) Container scenario, where the same image gets used as the base, hence all containers gets the same UUID For this we can have an option to tell glusterd that instructs it to refresh the UUID during next start. Maybe somethign like presence of a file /var/lib/glusterd/refresh_uuid makes glusterd refresh the UUID in .info and then delete this file, that ways, Dockerfile can touch this file, post gluster rpm install step and things should work as expected ? thanx, deepak > > I could not find a way to send a pull request on this. > > ~Atin > > > > --Humble > > > > > > > > ___ > > Gluster-devel mailing list > > gluster-de...@gluster.org > > http://www.gluster.org/mailman/listinfo/gluster-devel > > > > -- > ~Atin > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users > ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] [Gluster-devel] Gluster Docker images are available at docker hub
On 05/06/2015 12:31 PM, Humble Devassy Chirammal wrote: > Hi All, > > > Docker images of GlusterFS 3.6 for Fedora ( 21) and CentOS (7) are now > available at docker hub ( https://registry.hub.docker.com/u/gluster/ ). > These images can be used to deploy GlusterFS containers. > > The blog entry at planet.gluster.org [1] have details about how these > images can be used. > > Please let me know if you have any comments/feedback/questions. > > [1] Building GlusterFS in a docker container @ planet.gluster.org > [2] http://humblec.com/building-glusterfs-in-a-docker-container/ Hi Humble, As discussed yesterday, post daemon refactoring we generate UUID at the the time of glusterD init and this has caused an issue in bringing multiple docker containers as UUIDs will be same across different containers since yum install brings up glusterd and persist the information in /var/lib/glusterd.info. To make this work for docker containers could you add a line just after the installation steps in Dockerfile? rm -rf /var/lib/glusterd/glusterd.info I could not find a way to send a pull request on this. ~Atin > > --Humble > > > > ___ > Gluster-devel mailing list > gluster-de...@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel > -- ~Atin ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users
