Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
On Wed, Feb 15, 2017 at 02:53:26PM +0100, Pavel Szalbot wrote: > Hi, tested it with 3.8.8 on client (CentOS) and server (Ubuntu) and > everything is OK now. Awesome, many thanks for testing and reporting back the results. Niels > > -ps > > On Wed, Feb 15, 2017 at 11:49 AM, Pavel Szalbot> wrote: > > > Hi Daryl, > > > > I must have missed your reply and found out about it when reading about > > 3.8.9 and searching in gluster-users history. > > > > I will test the same setup with gluster 3.8.8 i.e. libvirt > > 2.0.0-10.el7_3.4, glusterfs 3.8.8-1.el7 and gluster 3.8.8 on servers > > (Ubuntu) and let you know. > > > > This is libvirt log for instance that used gluster storage backend > > (libvirt 2.0.0, gluster client 3.8.5 and later 3.8.7, probably 3.8.5 on > > servers, not sure): > > > > [2017-01-03 17:10:58.155566] I [MSGID: 104045] [glfs-master.c:91:notify] > > 0-gfapi: New graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) coming up > > [2017-01-03 17:10:58.155615] I [MSGID: 114020] [client.c:2356:notify] > > 0-gv_openstack_0-client-6: parent translators are ready, attempting connect > > on transport > > [2017-01-03 17:10:58.186043] I [MSGID: 114020] [client.c:2356:notify] > > 0-gv_openstack_0-client-7: parent translators are ready, attempting connect > > on transport > > [2017-01-03 17:10:58.186518] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > > 0-gv_openstack_0-client-6: changing port to 49156 (from 0) > > [2017-01-03 17:10:58.215411] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > > 0-gv_openstack_0-client-7: changing port to 49153 (from 0) > > [2017-01-03 17:10:58.243706] I [MSGID: 114057] [client-handshake.c:1446: > > select_server_supported_programs] 0-gv_openstack_0-client-6: Using > > Program GlusterFS 3.3, Num (1298437), Version (330) > > [2017-01-03 17:10:58.244215] I [MSGID: 114046] > > [client-handshake.c:1222:client_setvolume_cbk] > > 0-gv_openstack_0-client-6: Connected to gv_openstack_0-client-6, attached > > to remote volume '/export/gfs_0/gv_openstack_0_brick'. > > [2017-01-03 17:10:58.244235] I [MSGID: 114047] > > [client-handshake.c:1233:client_setvolume_cbk] > > 0-gv_openstack_0-client-6: Server and Client lk-version numbers are not > > same, reopening the fds > > [2017-01-03 17:10:58.244318] I [MSGID: 108005] > > [afr-common.c:4301:afr_notify] 0-gv_openstack_0-replicate-0: Subvolume > > 'gv_openstack_0-client-6' came back up; going online. > > [2017-01-03 17:10:58.244437] I [MSGID: 114035] > > [client-handshake.c:201:client_set_lk_version_cbk] > > 0-gv_openstack_0-client-6: Server lk version = 1 > > [2017-01-03 17:10:58.246940] I [MSGID: 114057] [client-handshake.c:1446: > > select_server_supported_programs] 0-gv_openstack_0-client-7: Using > > Program GlusterFS 3.3, Num (1298437), Version (330) > > [2017-01-03 17:10:58.247252] I [MSGID: 114046] > > [client-handshake.c:1222:client_setvolume_cbk] > > 0-gv_openstack_0-client-7: Connected to gv_openstack_0-client-7, attached > > to remote volume '/export/gfs_0/gv_openstack_0_brick'. > > [2017-01-03 17:10:58.247273] I [MSGID: 114047] > > [client-handshake.c:1233:client_setvolume_cbk] > > 0-gv_openstack_0-client-7: Server and Client lk-version numbers are not > > same, reopening the fds > > [2017-01-03 17:10:58.257855] I [MSGID: 114035] > > [client-handshake.c:201:client_set_lk_version_cbk] > > 0-gv_openstack_0-client-7: Server lk version = 1 > > [2017-01-03 17:10:58.259641] I [MSGID: 104041] > > [glfs-resolve.c:885:__glfs_active_subvol] > > 0-gv_openstack_0: switched to graph 6e6f6465-342d-6d69-6372-6f312e707267 > > (0) > > [2017-01-03 17:10:58.439897] I [MSGID: 104045] [glfs-master.c:91:notify] > > 0-gfapi: New graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) coming up > > [2017-01-03 17:10:58.439929] I [MSGID: 114020] [client.c:2356:notify] > > 0-gv_openstack_0-client-6: parent translators are ready, attempting connect > > on transport > > [2017-01-03 17:10:58.519082] I [MSGID: 114020] [client.c:2356:notify] > > 0-gv_openstack_0-client-7: parent translators are ready, attempting connect > > on transport > > [2017-01-03 17:10:58.519527] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > > 0-gv_openstack_0-client-6: changing port to 49156 (from 0) > > [2017-01-03 17:10:58.550482] I [MSGID: 114057] [client-handshake.c:1446: > > select_server_supported_programs] 0-gv_openstack_0-client-6: Using > > Program GlusterFS 3.3, Num (1298437), Version (330) > > [2017-01-03 17:10:58.550997] I [MSGID: 114046] > > [client-handshake.c:1222:client_setvolume_cbk] > > 0-gv_openstack_0-client-6: Connected to gv_openstack_0-client-6, attached > > to remote volume '/export/gfs_0/gv_openstack_0_brick'. > > [2017-01-03 17:10:58.551021] I [MSGID: 114047] > > [client-handshake.c:1233:client_setvolume_cbk] > > 0-gv_openstack_0-client-6: Server and Client lk-version numbers are not > > same, reopening the fds > > [2017-01-03 17:10:58.551089] I [MSGID: 108005] > > [afr-common.c:4301:afr_notify] 0-gv_openstack_0-replicate-0: Subvolume > >
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Hi, tested it with 3.8.8 on client (CentOS) and server (Ubuntu) and everything is OK now. -ps On Wed, Feb 15, 2017 at 11:49 AM, Pavel Szalbotwrote: > Hi Daryl, > > I must have missed your reply and found out about it when reading about > 3.8.9 and searching in gluster-users history. > > I will test the same setup with gluster 3.8.8 i.e. libvirt > 2.0.0-10.el7_3.4, glusterfs 3.8.8-1.el7 and gluster 3.8.8 on servers > (Ubuntu) and let you know. > > This is libvirt log for instance that used gluster storage backend > (libvirt 2.0.0, gluster client 3.8.5 and later 3.8.7, probably 3.8.5 on > servers, not sure): > > [2017-01-03 17:10:58.155566] I [MSGID: 104045] [glfs-master.c:91:notify] > 0-gfapi: New graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) coming up > [2017-01-03 17:10:58.155615] I [MSGID: 114020] [client.c:2356:notify] > 0-gv_openstack_0-client-6: parent translators are ready, attempting connect > on transport > [2017-01-03 17:10:58.186043] I [MSGID: 114020] [client.c:2356:notify] > 0-gv_openstack_0-client-7: parent translators are ready, attempting connect > on transport > [2017-01-03 17:10:58.186518] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > 0-gv_openstack_0-client-6: changing port to 49156 (from 0) > [2017-01-03 17:10:58.215411] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > 0-gv_openstack_0-client-7: changing port to 49153 (from 0) > [2017-01-03 17:10:58.243706] I [MSGID: 114057] [client-handshake.c:1446: > select_server_supported_programs] 0-gv_openstack_0-client-6: Using > Program GlusterFS 3.3, Num (1298437), Version (330) > [2017-01-03 17:10:58.244215] I [MSGID: 114046] > [client-handshake.c:1222:client_setvolume_cbk] > 0-gv_openstack_0-client-6: Connected to gv_openstack_0-client-6, attached > to remote volume '/export/gfs_0/gv_openstack_0_brick'. > [2017-01-03 17:10:58.244235] I [MSGID: 114047] > [client-handshake.c:1233:client_setvolume_cbk] > 0-gv_openstack_0-client-6: Server and Client lk-version numbers are not > same, reopening the fds > [2017-01-03 17:10:58.244318] I [MSGID: 108005] > [afr-common.c:4301:afr_notify] 0-gv_openstack_0-replicate-0: Subvolume > 'gv_openstack_0-client-6' came back up; going online. > [2017-01-03 17:10:58.244437] I [MSGID: 114035] > [client-handshake.c:201:client_set_lk_version_cbk] > 0-gv_openstack_0-client-6: Server lk version = 1 > [2017-01-03 17:10:58.246940] I [MSGID: 114057] [client-handshake.c:1446: > select_server_supported_programs] 0-gv_openstack_0-client-7: Using > Program GlusterFS 3.3, Num (1298437), Version (330) > [2017-01-03 17:10:58.247252] I [MSGID: 114046] > [client-handshake.c:1222:client_setvolume_cbk] > 0-gv_openstack_0-client-7: Connected to gv_openstack_0-client-7, attached > to remote volume '/export/gfs_0/gv_openstack_0_brick'. > [2017-01-03 17:10:58.247273] I [MSGID: 114047] > [client-handshake.c:1233:client_setvolume_cbk] > 0-gv_openstack_0-client-7: Server and Client lk-version numbers are not > same, reopening the fds > [2017-01-03 17:10:58.257855] I [MSGID: 114035] > [client-handshake.c:201:client_set_lk_version_cbk] > 0-gv_openstack_0-client-7: Server lk version = 1 > [2017-01-03 17:10:58.259641] I [MSGID: 104041] > [glfs-resolve.c:885:__glfs_active_subvol] > 0-gv_openstack_0: switched to graph 6e6f6465-342d-6d69-6372-6f312e707267 > (0) > [2017-01-03 17:10:58.439897] I [MSGID: 104045] [glfs-master.c:91:notify] > 0-gfapi: New graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) coming up > [2017-01-03 17:10:58.439929] I [MSGID: 114020] [client.c:2356:notify] > 0-gv_openstack_0-client-6: parent translators are ready, attempting connect > on transport > [2017-01-03 17:10:58.519082] I [MSGID: 114020] [client.c:2356:notify] > 0-gv_openstack_0-client-7: parent translators are ready, attempting connect > on transport > [2017-01-03 17:10:58.519527] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > 0-gv_openstack_0-client-6: changing port to 49156 (from 0) > [2017-01-03 17:10:58.550482] I [MSGID: 114057] [client-handshake.c:1446: > select_server_supported_programs] 0-gv_openstack_0-client-6: Using > Program GlusterFS 3.3, Num (1298437), Version (330) > [2017-01-03 17:10:58.550997] I [MSGID: 114046] > [client-handshake.c:1222:client_setvolume_cbk] > 0-gv_openstack_0-client-6: Connected to gv_openstack_0-client-6, attached > to remote volume '/export/gfs_0/gv_openstack_0_brick'. > [2017-01-03 17:10:58.551021] I [MSGID: 114047] > [client-handshake.c:1233:client_setvolume_cbk] > 0-gv_openstack_0-client-6: Server and Client lk-version numbers are not > same, reopening the fds > [2017-01-03 17:10:58.551089] I [MSGID: 108005] > [afr-common.c:4301:afr_notify] 0-gv_openstack_0-replicate-0: Subvolume > 'gv_openstack_0-client-6' came back up; going online. > [2017-01-03 17:10:58.551199] I [MSGID: 114035] > [client-handshake.c:201:client_set_lk_version_cbk] > 0-gv_openstack_0-client-6: Server lk version = 1 > [2017-01-03 17:10:58.554413] I [rpc-clnt.c:1947:rpc_clnt_reconfig] > 0-gv_openstack_0-client-7: changing port to 49153 (from
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Hi Daryl, I must have missed your reply and found out about it when reading about 3.8.9 and searching in gluster-users history. I will test the same setup with gluster 3.8.8 i.e. libvirt 2.0.0-10.el7_3.4, glusterfs 3.8.8-1.el7 and gluster 3.8.8 on servers (Ubuntu) and let you know. This is libvirt log for instance that used gluster storage backend (libvirt 2.0.0, gluster client 3.8.5 and later 3.8.7, probably 3.8.5 on servers, not sure): [2017-01-03 17:10:58.155566] I [MSGID: 104045] [glfs-master.c:91:notify] 0-gfapi: New graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) coming up [2017-01-03 17:10:58.155615] I [MSGID: 114020] [client.c:2356:notify] 0-gv_openstack_0-client-6: parent translators are ready, attempting connect on transport [2017-01-03 17:10:58.186043] I [MSGID: 114020] [client.c:2356:notify] 0-gv_openstack_0-client-7: parent translators are ready, attempting connect on transport [2017-01-03 17:10:58.186518] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-gv_openstack_0-client-6: changing port to 49156 (from 0) [2017-01-03 17:10:58.215411] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-gv_openstack_0-client-7: changing port to 49153 (from 0) [2017-01-03 17:10:58.243706] I [MSGID: 114057] [client-handshake.c:1446:select_server_supported_programs] 0-gv_openstack_0-client-6: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2017-01-03 17:10:58.244215] I [MSGID: 114046] [client-handshake.c:1222:client_setvolume_cbk] 0-gv_openstack_0-client-6: Connected to gv_openstack_0-client-6, attached to remote volume '/export/gfs_0/gv_openstack_0_brick'. [2017-01-03 17:10:58.244235] I [MSGID: 114047] [client-handshake.c:1233:client_setvolume_cbk] 0-gv_openstack_0-client-6: Server and Client lk-version numbers are not same, reopening the fds [2017-01-03 17:10:58.244318] I [MSGID: 108005] [afr-common.c:4301:afr_notify] 0-gv_openstack_0-replicate-0: Subvolume 'gv_openstack_0-client-6' came back up; going online. [2017-01-03 17:10:58.244437] I [MSGID: 114035] [client-handshake.c:201:client_set_lk_version_cbk] 0-gv_openstack_0-client-6: Server lk version = 1 [2017-01-03 17:10:58.246940] I [MSGID: 114057] [client-handshake.c:1446:select_server_supported_programs] 0-gv_openstack_0-client-7: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2017-01-03 17:10:58.247252] I [MSGID: 114046] [client-handshake.c:1222:client_setvolume_cbk] 0-gv_openstack_0-client-7: Connected to gv_openstack_0-client-7, attached to remote volume '/export/gfs_0/gv_openstack_0_brick'. [2017-01-03 17:10:58.247273] I [MSGID: 114047] [client-handshake.c:1233:client_setvolume_cbk] 0-gv_openstack_0-client-7: Server and Client lk-version numbers are not same, reopening the fds [2017-01-03 17:10:58.257855] I [MSGID: 114035] [client-handshake.c:201:client_set_lk_version_cbk] 0-gv_openstack_0-client-7: Server lk version = 1 [2017-01-03 17:10:58.259641] I [MSGID: 104041] [glfs-resolve.c:885:__glfs_active_subvol] 0-gv_openstack_0: switched to graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) [2017-01-03 17:10:58.439897] I [MSGID: 104045] [glfs-master.c:91:notify] 0-gfapi: New graph 6e6f6465-342d-6d69-6372-6f312e707267 (0) coming up [2017-01-03 17:10:58.439929] I [MSGID: 114020] [client.c:2356:notify] 0-gv_openstack_0-client-6: parent translators are ready, attempting connect on transport [2017-01-03 17:10:58.519082] I [MSGID: 114020] [client.c:2356:notify] 0-gv_openstack_0-client-7: parent translators are ready, attempting connect on transport [2017-01-03 17:10:58.519527] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-gv_openstack_0-client-6: changing port to 49156 (from 0) [2017-01-03 17:10:58.550482] I [MSGID: 114057] [client-handshake.c:1446:select_server_supported_programs] 0-gv_openstack_0-client-6: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2017-01-03 17:10:58.550997] I [MSGID: 114046] [client-handshake.c:1222:client_setvolume_cbk] 0-gv_openstack_0-client-6: Connected to gv_openstack_0-client-6, attached to remote volume '/export/gfs_0/gv_openstack_0_brick'. [2017-01-03 17:10:58.551021] I [MSGID: 114047] [client-handshake.c:1233:client_setvolume_cbk] 0-gv_openstack_0-client-6: Server and Client lk-version numbers are not same, reopening the fds [2017-01-03 17:10:58.551089] I [MSGID: 108005] [afr-common.c:4301:afr_notify] 0-gv_openstack_0-replicate-0: Subvolume 'gv_openstack_0-client-6' came back up; going online. [2017-01-03 17:10:58.551199] I [MSGID: 114035] [client-handshake.c:201:client_set_lk_version_cbk] 0-gv_openstack_0-client-6: Server lk version = 1 [2017-01-03 17:10:58.554413] I [rpc-clnt.c:1947:rpc_clnt_reconfig] 0-gv_openstack_0-client-7: changing port to 49153 (from 0) [2017-01-03 17:10:58.600956] I [MSGID: 114057] [client-handshake.c:1446:select_server_supported_programs] 0-gv_openstack_0-client-7: Using Program GlusterFS 3.3, Num (1298437), Version (330) [2017-01-03 17:10:58.601276] I [MSGID: 114046] [client-handshake.c:1222:client_setvolume_cbk] 0-gv_openstack_0-client-7: Connected to gv_openstack_0-client-7, attached to
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
On Fri, Jan 13, 2017 at 11:01:38AM +0100, Pavel Szalbot wrote: > Hi, you can install 3.8.7 from centos-gluster38-test using: > > yum --enablerepo=centos-gluster38-test install glusterfs > > I am not sure how QA works for CentOS Storage SIG, but 3.8.7 works same as > 3.8.5 for me - libvirt gfapi is unfortunately broken, no other problems > detected. Could you explain a little more of how this is broken? You would probably do good to report a bug as well: https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS=3.8=gfapi If the bug contain steps that we can follow to reproduce the problem you are facing, it will be easier to investigate the cause and fix it. Thanks, Niels > > Btw 3.9 is short term maintenance release ( > https://lists.centos.org/pipermail/centos-devel/2016-September/015197.html). > > > -ps > > On Fri, Jan 13, 2017 at 1:18 AM, Daryl leewrote: > > > Hey Gluster Community, > > > > According to the community packages list I get the impression that 3.8 > > would be released to the CentOS Storage SIG Repo, but this seems to have > > stopped with 3.8.5 and 3.9 is still missing all together. However, 3.7 is > > still being updated and is at 3.7.8 so I am confused why the other two > > versions have stopped. > > > > > > > > I did some looking on the past posts to this list and found a conversation > > about 3.9 on the CentOS repo last year but it looks like it's still not up > > yet; possibly due to a lack of community involvement in the testing and > > reporting back to whoever the maintainer is (which we don’t know yet)? I > > might be in a position to help since I have a test environment that mirrors > > my production environment setup that I would use for testing the patch > > anyways, I might as well provide some good to the community.. At this > > point I know to do " yum install --enablerepo=centos-gluster38-test > > glusterfs-server" but I'm not sure who to tell if it works or not, and what > > kind of info they are looking for.If someone wanted to give me a little > > guidance that would be awesome, especially if it will save me from having > > to switch to manually downloading packages. > > > > > > > > I guess the basic question is do we expect releases to resume for 3.8 on > > the CentOS Storage SIG repo or should I be looking to move to manual > > patching for 3.8. Additionally, if the person who does the releases to the > > CentOS Storage SIG is waiting for someone to tell them it looks fine, who > > should I contact to do so? > > > > > > > > > > > > > > > > Thanks! > > > > > > > > Daryl > > > > ___ > > 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 signature.asc Description: PGP signature ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
On Fri, Jan 13, 2017 at 11:07:40AM -0800, Daryl lee wrote: > Thanks everyone for the information. I'm happy to help provide test repo > feedback on an ongoing basis to help things along which I'll do right now. > > Niels, > If you require more or less information please let me know, happy to help. > Thanks for doing the builds! Many thanks Daryl! Information like this is sufficient for me to mark packages for release. The 3.8.8 packages will be signed and pushed to the CentOS mirrors the next time the CentOS team runs the procedure (probably Monday morning). The announcement has also been sent out, and the blog post with the release notes should show up on http://planet.gluster.org/ any minute now. Cheers, Niels > > I deployed GlusterFS v3.8.8 successfully to 5 servers running CentOS Linux > release 7.3.1611 (Core) here are the results. > > 2 GlusterFS clients deployed the following packages: > --- > glusterfs x86_64 > 3.8.8-1.el7centos-gluster38-test > 509 k > glusterfs-api x86_64 3.8.8-1.el7 > centos-gluster38-test89 k > glusterfs-client-xlators x86_64 3.8.8-1.el7 >centos-gluster38-test 781 k > glusterfs-fuse x86_64 3.8.8-1.el7 > centos-gluster38-test 133 k > glusterfs-libsx86_64 3.8.8-1.el7 > centos-gluster38-test 378 k > > Tests: > --- > Package DOWNLOAD/UPDATE/CLEANUP from repo - SUCCESS > Basic FUSE mount RW test to remote GlusterFS volume - SUCCESS > Boot and basic functionality test of libvirt gfapi based KVM Virtual Machine > - SUCCESS > > > 3 GlusterFS Brick/Volume servers running REPLICA 3 ARBITER 1 updated the > following packages: > --- > glusterfsx86_64 > 3.8.8-1.el7 centos-gluster38-test > 509 k > glusterfs-apix86_64 > 3.8.8-1.el7 centos-gluster38-test > 89 k > glusterfs-cli x86_64 > 3.8.8-1.el7 centos-gluster38-test > 182 k > glusterfs-client-xlators x86_64 3.8.8-1.el7 > centos-gluster38-test 781 k > glusterfs-fusex86_64 3.8.8-1.el7 >centos-gluster38-test 133 k > glusterfs-libs x86_64 > 3.8.8-1.el7 centos-gluster38-test > 378 k > glusterfs-server x86_64 3.8.8-1.el7 > centos-gluster38-test 1.4 M > userspace-rcux86_64 0.7.16-3.el7 > centos-gluster38-test 72 k > > Tests: > --- > Package DOWNLOAD/UPDATE/CLEANUP from repo - SUCCESS w/ warnings > * warning during updating of glusterfs-server-3.8.8-1.el7.x86_64 backing > up gluster .vol files saved to rpmsave. This is expected. > Bricks on all 3 servers started - SUCCESS > Self Healing Daemon on all 3 servers started - SUCCESS > Bitrot Daemon on all 3 servers started - SUCCESS > Scrubber Daemon on all 3 servers started - SUCCESS > First replica self healing - success > Second replica self healing - success > Arbiter replica self healing - success > > > -Daryl > > > -Original Message- > From: Kaushal M [mailto:kshlms...@gmail.com] > Sent: Friday, January 13, 2017 5:03 AM > To: Daryl lee > Cc: Pavel Szalbot; gluster-users; Niels de Vos > Subject: Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 > versions (3.8.5). Is it still being used and can I help? > > Packages for 3.7, 3.8 and 3.9 are being built for the Storage SIG. > Niels is very punctual about building them. The packages first land in the > respective testing repositories. If someone verifies that the packages are > okay, and gives Niels a heads-up, he pushes the packages to be
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Thanks for doing this Daryl. The help is appreciated. On Sat, Jan 14, 2017 at 12:37 AM, Daryl leewrote: > Thanks everyone for the information. I'm happy to help provide test repo > feedback on an ongoing basis to help things along which I'll do right now. > > Niels, > If you require more or less information please let me know, happy to help. > Thanks for doing the builds! > > I deployed GlusterFS v3.8.8 successfully to 5 servers running CentOS Linux > release 7.3.1611 (Core) here are the results. > > 2 GlusterFS clients deployed the following packages: > --- > glusterfs x86_64 > 3.8.8-1.el7centos-gluster38-test > 509 k > glusterfs-api x86_64 3.8.8-1.el7 > centos-gluster38-test89 k > glusterfs-client-xlators x86_64 3.8.8-1.el7 >centos-gluster38-test 781 k > glusterfs-fuse x86_64 3.8.8-1.el7 > centos-gluster38-test 133 k > glusterfs-libsx86_64 3.8.8-1.el7 > centos-gluster38-test 378 k > > Tests: > --- > Package DOWNLOAD/UPDATE/CLEANUP from repo - SUCCESS > Basic FUSE mount RW test to remote GlusterFS volume - SUCCESS > Boot and basic functionality test of libvirt gfapi based KVM Virtual Machine > - SUCCESS > > > 3 GlusterFS Brick/Volume servers running REPLICA 3 ARBITER 1 updated the > following packages: > --- > glusterfsx86_64 > 3.8.8-1.el7 centos-gluster38-test > 509 k > glusterfs-apix86_64 > 3.8.8-1.el7 centos-gluster38-test > 89 k > glusterfs-cli x86_64 > 3.8.8-1.el7 centos-gluster38-test > 182 k > glusterfs-client-xlators x86_64 3.8.8-1.el7 > centos-gluster38-test 781 k > glusterfs-fusex86_64 3.8.8-1.el7 >centos-gluster38-test 133 k > glusterfs-libs x86_64 > 3.8.8-1.el7 centos-gluster38-test > 378 k > glusterfs-server x86_64 3.8.8-1.el7 > centos-gluster38-test 1.4 M > userspace-rcux86_64 0.7.16-3.el7 > centos-gluster38-test 72 k > > Tests: > --- > Package DOWNLOAD/UPDATE/CLEANUP from repo - SUCCESS w/ warnings > * warning during updating of glusterfs-server-3.8.8-1.el7.x86_64 backing > up gluster .vol files saved to rpmsave. This is expected. > Bricks on all 3 servers started - SUCCESS > Self Healing Daemon on all 3 servers started - SUCCESS > Bitrot Daemon on all 3 servers started - SUCCESS > Scrubber Daemon on all 3 servers started - SUCCESS > First replica self healing - success > Second replica self healing - success > Arbiter replica self healing - success > > > -Daryl > > > -Original Message- > From: Kaushal M [mailto:kshlms...@gmail.com] > Sent: Friday, January 13, 2017 5:03 AM > To: Daryl lee > Cc: Pavel Szalbot; gluster-users; Niels de Vos > Subject: Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 > versions (3.8.5). Is it still being used and can I help? > > Packages for 3.7, 3.8 and 3.9 are being built for the Storage SIG. > Niels is very punctual about building them. The packages first land in the > respective testing repositories. If someone verifies that the packages are > okay, and gives Niels a heads-up, he pushes the packages to be signed and > added to the release repositories. > > The only issue is that Niels doesn't get enough (or any) verifications. And > the packages linger in testing. > > On Fri, Jan 13, 2017 at 3:31 PM, Pavel Szalbot > wrote: >> Hi, you can install 3.8.7 from centos-gluster38-test using: >> >> yum
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Thanks everyone for the information. I'm happy to help provide test repo feedback on an ongoing basis to help things along which I'll do right now. Niels, If you require more or less information please let me know, happy to help. Thanks for doing the builds! I deployed GlusterFS v3.8.8 successfully to 5 servers running CentOS Linux release 7.3.1611 (Core) here are the results. 2 GlusterFS clients deployed the following packages: --- glusterfs x86_64 3.8.8-1.el7 centos-gluster38-test 509 k glusterfs-api x86_64 3.8.8-1.el7 centos-gluster38-test89 k glusterfs-client-xlators x86_64 3.8.8-1.el7 centos-gluster38-test 781 k glusterfs-fuse x86_64 3.8.8-1.el7 centos-gluster38-test 133 k glusterfs-libsx86_64 3.8.8-1.el7 centos-gluster38-test 378 k Tests: --- Package DOWNLOAD/UPDATE/CLEANUP from repo - SUCCESS Basic FUSE mount RW test to remote GlusterFS volume - SUCCESS Boot and basic functionality test of libvirt gfapi based KVM Virtual Machine - SUCCESS 3 GlusterFS Brick/Volume servers running REPLICA 3 ARBITER 1 updated the following packages: --- glusterfsx86_64 3.8.8-1.el7 centos-gluster38-test 509 k glusterfs-apix86_64 3.8.8-1.el7 centos-gluster38-test 89 k glusterfs-cli x86_64 3.8.8-1.el7 centos-gluster38-test 182 k glusterfs-client-xlators x86_64 3.8.8-1.el7 centos-gluster38-test 781 k glusterfs-fusex86_64 3.8.8-1.el7 centos-gluster38-test 133 k glusterfs-libs x86_64 3.8.8-1.el7 centos-gluster38-test 378 k glusterfs-server x86_64 3.8.8-1.el7 centos-gluster38-test 1.4 M userspace-rcux86_64 0.7.16-3.el7 centos-gluster38-test 72 k Tests: --- Package DOWNLOAD/UPDATE/CLEANUP from repo - SUCCESS w/ warnings * warning during updating of glusterfs-server-3.8.8-1.el7.x86_64 backing up gluster .vol files saved to rpmsave. This is expected. Bricks on all 3 servers started - SUCCESS Self Healing Daemon on all 3 servers started - SUCCESS Bitrot Daemon on all 3 servers started - SUCCESS Scrubber Daemon on all 3 servers started - SUCCESS First replica self healing - success Second replica self healing - success Arbiter replica self healing - success -Daryl -Original Message- From: Kaushal M [mailto:kshlms...@gmail.com] Sent: Friday, January 13, 2017 5:03 AM To: Daryl lee Cc: Pavel Szalbot; gluster-users; Niels de Vos Subject: Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help? Packages for 3.7, 3.8 and 3.9 are being built for the Storage SIG. Niels is very punctual about building them. The packages first land in the respective testing repositories. If someone verifies that the packages are okay, and gives Niels a heads-up, he pushes the packages to be signed and added to the release repositories. The only issue is that Niels doesn't get enough (or any) verifications. And the packages linger in testing. On Fri, Jan 13, 2017 at 3:31 PM, Pavel Szalbotwrote: > Hi, you can install 3.8.7 from centos-gluster38-test using: > > yum --enablerepo=centos-gluster38-test install glusterfs > > I am not sure how QA works for CentOS Storage SIG, but 3.8.7 works > same as > 3.8.5 for me - libvirt gfapi is unfortunately broken, no other > problems detected. > > Btw 3.9 is short term maintenance release >
Re: [Gluster-users] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Packages for 3.7, 3.8 and 3.9 are being built for the Storage SIG. Niels is very punctual about building them. The packages first land in the respective testing repositories. If someone verifies that the packages are okay, and gives Niels a heads-up, he pushes the packages to be signed and added to the release repositories. The only issue is that Niels doesn't get enough (or any) verifications. And the packages linger in testing. On Fri, Jan 13, 2017 at 3:31 PM, Pavel Szalbotwrote: > Hi, you can install 3.8.7 from centos-gluster38-test using: > > yum --enablerepo=centos-gluster38-test install glusterfs > > I am not sure how QA works for CentOS Storage SIG, but 3.8.7 works same as > 3.8.5 for me - libvirt gfapi is unfortunately broken, no other problems > detected. > > Btw 3.9 is short term maintenance release > (https://lists.centos.org/pipermail/centos-devel/2016-September/015197.html). > > > -ps > > On Fri, Jan 13, 2017 at 1:18 AM, Daryl lee wrote: >> >> Hey Gluster Community, >> >> According to the community packages list I get the impression that 3.8 >> would be released to the CentOS Storage SIG Repo, but this seems to have >> stopped with 3.8.5 and 3.9 is still missing all together. However, 3.7 is >> still being updated and is at 3.7.8 so I am confused why the other two >> versions have stopped. >> >> >> >> I did some looking on the past posts to this list and found a conversation >> about 3.9 on the CentOS repo last year but it looks like it's still not up >> yet; possibly due to a lack of community involvement in the testing and >> reporting back to whoever the maintainer is (which we don’t know yet)? I >> might be in a position to help since I have a test environment that mirrors >> my production environment setup that I would use for testing the patch >> anyways, I might as well provide some good to the community.. At this >> point I know to do " yum install --enablerepo=centos-gluster38-test >> glusterfs-server" but I'm not sure who to tell if it works or not, and what >> kind of info they are looking for.If someone wanted to give me a little >> guidance that would be awesome, especially if it will save me from having to >> switch to manually downloading packages. >> >> >> >> I guess the basic question is do we expect releases to resume for 3.8 on >> the CentOS Storage SIG repo or should I be looking to move to manual >> patching for 3.8. Additionally, if the person who does the releases to the >> CentOS Storage SIG is waiting for someone to tell them it looks fine, who >> should I contact to do so? >> >> >> >> >> >> >> >> Thanks! >> >> >> >> Daryl >> >> >> ___ >> 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] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Hi, you can install 3.8.7 from centos-gluster38-test using: yum --enablerepo=centos-gluster38-test install glusterfs I am not sure how QA works for CentOS Storage SIG, but 3.8.7 works same as 3.8.5 for me - libvirt gfapi is unfortunately broken, no other problems detected. Btw 3.9 is short term maintenance release ( https://lists.centos.org/pipermail/centos-devel/2016-September/015197.html). -ps On Fri, Jan 13, 2017 at 1:18 AM, Daryl leewrote: > Hey Gluster Community, > > According to the community packages list I get the impression that 3.8 > would be released to the CentOS Storage SIG Repo, but this seems to have > stopped with 3.8.5 and 3.9 is still missing all together. However, 3.7 is > still being updated and is at 3.7.8 so I am confused why the other two > versions have stopped. > > > > I did some looking on the past posts to this list and found a conversation > about 3.9 on the CentOS repo last year but it looks like it's still not up > yet; possibly due to a lack of community involvement in the testing and > reporting back to whoever the maintainer is (which we don’t know yet)? I > might be in a position to help since I have a test environment that mirrors > my production environment setup that I would use for testing the patch > anyways, I might as well provide some good to the community.. At this > point I know to do " yum install --enablerepo=centos-gluster38-test > glusterfs-server" but I'm not sure who to tell if it works or not, and what > kind of info they are looking for.If someone wanted to give me a little > guidance that would be awesome, especially if it will save me from having > to switch to manually downloading packages. > > > > I guess the basic question is do we expect releases to resume for 3.8 on > the CentOS Storage SIG repo or should I be looking to move to manual > patching for 3.8. Additionally, if the person who does the releases to the > CentOS Storage SIG is waiting for someone to tell them it looks fine, who > should I contact to do so? > > > > > > > > Thanks! > > > > Daryl > > ___ > 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] CentOS Storage SIG Repo for 3.8 is behind 3 versions (3.8.5). Is it still being used and can I help?
Hey Gluster Community, According to the community packages list I get the impression that 3.8 would be released to the CentOS Storage SIG Repo, but this seems to have stopped with 3.8.5 and 3.9 is still missing all together. However, 3.7 is still being updated and is at 3.7.8 so I am confused why the other two versions have stopped. I did some looking on the past posts to this list and found a conversation about 3.9 on the CentOS repo last year but it looks like it's still not up yet; possibly due to a lack of community involvement in the testing and reporting back to whoever the maintainer is (which we don't know yet)? I might be in a position to help since I have a test environment that mirrors my production environment setup that I would use for testing the patch anyways, I might as well provide some good to the community.. At this point I know to do " yum install --enablerepo=centos-gluster38-test glusterfs-server" but I'm not sure who to tell if it works or not, and what kind of info they are looking for.If someone wanted to give me a little guidance that would be awesome, especially if it will save me from having to switch to manually downloading packages. I guess the basic question is do we expect releases to resume for 3.8 on the CentOS Storage SIG repo or should I be looking to move to manual patching for 3.8. Additionally, if the person who does the releases to the CentOS Storage SIG is waiting for someone to tell them it looks fine, who should I contact to do so? Thanks! Daryl ___ Gluster-users mailing list Gluster-users@gluster.org http://www.gluster.org/mailman/listinfo/gluster-users