Hi Neils, Have started my contibutions on the CentOS Storage SIG with GlusterFS: ---------- Forwarded message ---------- From: Javier Romero <xavinux at gmail.com> Date: 2018-02-22 14:02 GMT-03:00 Subject: Re: [Gluster-devel] GlusterFS project contribution. To: Shyam Ranganathan <srangana at redhat.com> Cc: Amar Tumballi <atumball at redhat.com>, Gluster Devel < gluster-devel at gluster.org>, Humble Chirammal <hchiramm at redhat.com>, Raghavendra Talur <rtalur at redhat.com> Hi Shyam, Thanks for your answer. > Javier, where is the PR/commit for the same, wanted to understand this better. > Further, Humble maintains the docker images for Gluster (added him here). > @Humble can we know how this ties in with our Docker images? As Humble said, he has already merged two pull requests I've sent to the gluster-containers repo at Github: https://github.com/gluster/gluster-containers/pull/66 https://github.com/gluster/gluster-containers/pull/68 > Javier, I guess a good start to this is: > https://github.com/raghavendra-talur/vagrant-cluster-creator > rtalur maintains this, although the last commit is a bit old. Also, added him to the CC to enable further discussion on topic. Will use that repo as a start point to create a new Vagrant cluster running GlusterFS. Regards, Javier Javier Romero 2018-02-16 16:45 GMT-03:00 Javier Romero <xavinux at gmail.com>: > Have created a new Dockerfile for image creation to run containers on > CentOS 7 with GlusterFS 3.13 already installed. > Also sent a pull request on Github to merge a new branch named > gluster-3.13 with this new Dockerfile included. > Test on Centos 7 release 7.4.1708 (Core) with kernel > 3.10.0-693.17.1.el7.x86_64 and works ok: > > > # docker images > REPOSITORY TAG IMAGE ID > CREATED SIZE > dockerfile-gluster-3.13 latest 07931ac54c87 > About an hour ago 371.9 MB > docker.io/centos 7 ff426288ea90 5 > weeks ago 207.2 MB > > > # docker ps -a > CONTAINER ID IMAGE COMMAND > CREATED STATUS PORTS NAMES > 4e164d71256f dockerfile-gluster-3.13 "/usr/sbin/init" > About an hour ago Up About an hour > backstabbing_babbage > > > # docker exec -it 4e164d71256f sh > sh-4.2# systemctl status glusterd > ● glusterd.service - GlusterFS, a clustered file-system server > Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; > vendor preset: disabled) > Active: active (running) since Fri 2018-02-16 17:44:22 UTC; 1h 50min ago > Process: 63 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid > --log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, > status=0/SUCCESS) > Main PID: 64 (glusterd) > CGroup: /system.slice/docker-4e164d71256f306144b2e2cf0d6b9d > 7c369c9958d0017014ade17fbbdbadcf2e.scope/system.slice/glusterd.service > └─64 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level > INFO > > Feb 16 17:44:16 centos-7 systemd[1]: Starting GlusterFS, a clustered > file-system server... > Feb 16 17:44:22 centos-7 systemd[1]: Started GlusterFS, a clustered > file-system server. > > > sh-4.2# glusterd -V > glusterfs 3.13.2 > Repository revision: git://git.gluster.org/glusterfs.git > Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/> > GlusterFS comes with ABSOLUTELY NO WARRANTY. > It is licensed to you under your choice of the GNU Lesser > General Public License, version 3 or any later version (LGPLv3 > or later), or the GNU General Public License, version 2 (GPLv2), > in all cases as published by the Free Software Foundation. > > Regards, > Javier Romero > > > > > 2018-02-16 13:36 GMT-03:00 Javier Romero <xavinux at gmail.com>: > > There was just a Dockerfile on the gluster-3.10 branch for building > > GlusterFS 3.10. Have updated that Dockerfile and sent a pull rquest on > > Github. > > > > # docker images > > REPOSITORY TAG IMAGE ID > > CREATED SIZE > > dockerfile-gluster-3.10 latest fbedfea074f6 36 > > minutes ago 435.5 MB > > docker.io/centos 7 ff426288ea90 5 > > weeks ago 207.2 MB > > > > > > # docker ps -a > > CONTAINER ID IMAGE COMMAND > > CREATED STATUS PORTS NAMES > > 0269de7f42bd dockerfile-gluster-3.10 "/usr/sbin/init" 7 > > seconds ago Up 6 seconds high_jang > > > > > > # docker exec -it 0269de7f42bd sh > > sh-4.2# systemctl status glusterd > > ● glusterd.service - GlusterFS, a clustered file-system server > > Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; > > vendor preset: disabled) > > Active: active (running) since Fri 2018-02-16 16:03:46 UTC; 28s ago > > Process: 55 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid > > --log-level $LOG_LEVEL $GLUSTERD_OPTIONS (code=exited, > > status=0/SUCCESS) > > Main PID: 62 (glusterd) > > CGroup: /system.slice/docker-0269de7f42bd1104c769d1adc4b6b2 > 570d64fe7955e7c9634844d4570cd0a216.scope/system.slice/glusterd.service > > └─62 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level > INFO > > > > Feb 16 16:03:40 centos-7 systemd[1]: Starting GlusterFS, a clustered > > file-system server... > > Feb 16 16:03:46 centos-7 systemd[1]: Started GlusterFS, a clustered > > file-system server. > > > > sh-4.2# glusterd -V > > glusterfs 3.10.10 > > Repository revision: git://git.gluster.org/glusterfs.git > > Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/> > > GlusterFS comes with ABSOLUTELY NO WARRANTY. > > It is licensed to you under your choice of the GNU Lesser > > General Public License, version 3 or any later version (LGPLv3 > > or later), or the GNU General Public License, version 2 (GPLv2), > > in all cases as published by the Free Software Foundation. > > > > > > Regards, > > Javier Romero > > > > > > > > > > 2018-02-15 13:19 GMT-03:00 Javier Romero <xavinux at gmail.com>: > >> Hi Niels, > >> > >> Built GlusterFS image from Dockerfile: > >> > >> # docker images > >> REPOSITORY TAG IMAGE ID > >> CREATED SIZE > >> dockerfile-gluster-3.12 latest 4647c9d71843 53 > >> minutes ago 371.2 MB > >> docker.io/centos 7 ff426288ea90 5 > >> weeks ago 207.2 MB > >> > >> > >> # docker ps -a > >> CONTAINER ID IMAGE COMMAND > >> CREATED STATUS PORTS NAMES > >> 9afa8c0ab468 dockerfile-gluster-3.12 "/usr/sbin/init" 38 > >> minutes ago Up 38 minutes small_shannon > >> > >> > >> # docker exec -it 9afa8c0ab468 bash > >> > >> # glusterd -V > >> glusterfs 3.12.5 > >> Repository revision: git://git.gluster.org/glusterfs.git > >> Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/> > >> GlusterFS comes with ABSOLUTELY NO WARRANTY. > >> It is licensed to you under your choice of the GNU Lesser > >> General Public License, version 3 or any later version (LGPLv3 > >> or later), or the GNU General Public License, version 2 (GPLv2), > >> in all cases as published by the Free Software Foundation. > >> > >> Updated the Dockerfile and changed Gluster version and vendor, a pull > >> request has been sent on Github. > >> > >> Regards, > >> > >> > >> Javier Romero > >> E-mail: xavinux at gmail.com > >> Skype: xavinux > >> > >> > >> > >> 2018-02-14 9:51 GMT-03:00 Javier Romero <xavinux at gmail.com>: > >>> Niels, > >>> > >>> Thanks for your answer. I'll be looking at the container you have > >>> suggested and will let you know how things are going. > >>> > >>> Regards, > >>> Javier Romero > >>> E-mail: xavinux at gmail.com > >>> Skype: xavinux > >>> > >>> > >>> > >>> 2018-02-14 6:48 GMT-03:00 Niels de Vos <ndevos at redhat.com>: > >>>> On Tue, Feb 13, 2018 at 09:55:02PM -0300, Javier Romero wrote: > >>>>> 2018-02-13 13:07 GMT-03:00 Niels de Vos <ndevos at redhat.com>: > >>>>> > >>>>> > On Mon, Feb 12, 2018 at 07:32:40PM -0300, Javier Romero wrote: > >>>> ... > >>>>> > > Have also been working with KVM virtual machines in the ISP > Datacenter > >>>>> > > for the last eight years, and with Docker since 2015, so think > that > >>>>> > > can also help with container and VM images if this can be useful. > >>>>> > > >>>>> > We do have a Gluster container in the CentOS Container Index [3], > but > >>>>> > would like to have different versions. At the moment, we actively > >>>>> > maintain Gluster versions 3.10, 3.12, 3.13 and are preparing for > 4.0. > >>>>> > Ideally we should have a container for each version. > >>>>> > > >>>>> > For which version of Gluster would you like me to start creating a > >>>>> container image first? > >>>> > >>>> Have a look at > >>>> https://github.com/gluster/gluster-containers/tree/master/CentOS. > This > >>>> is the container that is currently built for the CentOS Registry and > >>>> available at > >>>> https://registry.centos.org/repo/gluster/storagesig-gluster-centos. > >>>> > >>>> This container seems incorrect as well, the centos-release-gluster > >>>> package will install the latest Long-Term-Maintenance version, > currently > >>>> 3.12, but the version mentioned in the container is 3.10. In addition > to > >>>> that, the Vendor should either be CentOS or Gluster Community. There > >>>> might be more things that can be improved. > >>>> > >>>> I suggest to have a go at making sure the current container is > correct. > >>>> Once done, add a container for 3.10 (by installing > >>>> centos-release-gluster-310). Maybe place the Dockerfile in a different > >>>> directory, or just name it Dockerfile.3.10 or such. After that is > >>>> merged, it can be added to > >>>> https://github.com/CentOS/container-index/blob/master/ > index.d/gluster.yml > >>>> > >>>> Both Humble and Jose have been looking at the container images before. > >>>> They are on CC of this email and can help with any PullRequest reviews > >>>> or further guidance. > >>>> > >>>> Thanks! > >>>> Niels > >>>> > >>>> > >>>> ... > >>>>> > 0. http://lists.gluster.org/mailman/listinfo/packaging > >>>>> > 1. https://github.com/CentOS-Storage-SIG > >>>>> > 2. https://github.com/CentOS-Storage-SIG/glusterfs > >>>>> > 3. https://github.com/CentOS/container-index > >>>>> > 4. https://app.vagrantup.com/centos > >>>>> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20180223/7a355eae/attachment-0008.html>