Hi Sahina,I've tried to upgrade to Gluster 3.7.16, but it seems the yum repo https://download.gluster.org/pub/gluster/glusterfs/ 3.7/3.7.16/EPEL.repo/epel-7.2/x86_ 64/ is not working.... Two questions:1 - Should I switch to the following repo ? This one seems to be working.[centos-gluster37]
name=CentOS-$releasever - Gluster 3.7
baseurl=http://mirror.centos.
org/centos/$releasever/ 3.7/storage/$basearch/gluster- gpgcheck=1
enabled=1
gpgkey=file:///etc/pki/rpm-
gpg/RPM-GPG-KEY-CentOS-SIG- Storage
2 - I'm using Centos7.2 + oVirt 3.6.6 with external gluster replica 3 storage. Is safe to upgrade to gluster 3.7.16 my external gluster server's ? The plan is to upgrade to oVirt 3.6.7 after this gluster server's upgrade.
Thanks
-Luiz
2016-08-08 4:26 GMT-03:00 Sahina Bose <sabose@redhat.com>:On Mon, Aug 8, 2016 at 3:37 AM, Luiz Claudio Prazeres Goncalves <luizcpg@gmail.com> wrote:Hi, it seems the ovirt-3.6-dependencies.repo is pointing the yum repo to http://download.gluster.org/pub/gluster/glusterfs/LATEST/EP and http://download.gluster.org/puEL.repo/epel-$releasever/$base arch/ b/gluster/glusterfs/LATEST/EPE L.repo/epel-$releasever/noarch , however the "LATEST" is now pointing to gluster 3.8.x and not to 3.7.x anymore. I checked the ovirt-release project and the dependency points to CentOS SIG repo - http://mirror.centos.org/centos/7/storage/$basearch/gluster- 3.7/
So, in order to fix it I was forced to manually adjust the yum repo paths as you can see below. Is this procedure correct? I would say yes, but it's always good to double check :)The procedure is correct.
Also, It's currently running centos 7.2 + ovirt 3.6.6 + gluster 3.7.11 (client) and I'm planning to upgrade to ovirt 3.6.7 and gluster 3.7.14 (client).The oVirt Cluster is running on top of an external gluster replica 3 cluster, hosting the engine storage domain and vms storage domain, running the version 3.7.11 which I'm also planning to move to 3.7.14 as well. I'm using XFS and not ZFS, which seems to have issues with gluster 3.7.13Is this upgrade safe and recommended?Update the gluster servers first and then the clients.
Thanks-Luiz[ovirt-3.6-glusterfs-epel]
name=GlusterFS is a clustered file-system capable of scaling to several petabytes.
#baseurl=http://download.glust
er.org/pub/gluster/glusterfs/L ATEST/EPEL.repo/epel-$releasev er/$basearch/ baseurl=https://download.glust
er.org/pub/gluster/glusterfs/ 3.7 /3.7.14/EPEL.repo/epel-7.2/x86_64/ enabled=1
skip_if_unavailable=1
gpgcheck=1
gpgkey=https://download.gluste
r.org/pub/gluster/glusterfs/LA TEST/pub.key
[ovirt-3.6-glusterfs-noarch-ep
el] name=GlusterFS is a clustered file-system capable of scaling to several petabytes.
#baseurl=http://download.glust
er.org/pub/gluster/glusterfs/L ATEST/EPEL.repo/epel-$releasev er/noarch baseurl=https://download.glust
er.org/pub/gluster/glusterfs/ 3.7 /3.7.14/EPEL.repo/epel-7.2/noarch enabled=1
skip_if_unavailable=1
gpgcheck=1
gpgkey=https://download.gluste
r.org/pub/gluster/glusterfs/LA TEST/pub.key
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users