search for: hyperconverged

...ks: (links to recordings provided in May newsletter) Gluster Colonizer with Ansible: A hands-on workshop: https://agenda.summit.redhat.com/SessionDetail.aspx?id=154077 Container-native storage and Red Hat Gluster Storage roadmap: https://agenda.summit.redhat.com/SessionDetail.aspx?id=153766 Red Hat Hyperconverged Infrastructure: Your open hyperconverged solution https://agenda.summit.redhat.com/SessionDetail.aspx?id=153974 Red Hat Summit: Community Happy Hour Tuesday, May 8, 2018 (6:30pm - 7:30pm) https://rhsummithappyhour.eventbrite.com/ Want swag for your meetup? https://www.gluster.org/events/ has a co...

...The reason we are also looking into gluster is that we like that it uses standard components and that we can prevent forklift upgrades every 5,6,7 years by replacing a few bricks each year. Next to providing storage for home directories we would like to also use the hosts to run VM's in a hyperconverged setup (with their storage as an additional gluster volume on those bricks). Regards, Rik -- Rik Theys System Engineer KU Leuven - Dept. Elektrotechniek (ESAT) Kasteelpark Arenberg 10 bus 2440 - B-3001 Leuven-Heverlee +32(0)16/32.11.07 ---------------------------------------------------------...

...t4, so I cannot comment on XFS. We use the fuse mount, because we are lazy and haven't upgraded to libgfapi.? I hope to start a new cluster with to libfgapi shortly because of the better performance. Also we use a localhost mount for the gluster driveset on each compute node (i.e. so called hyperconverged). So the only 'gluster' only kit is the lightweight arb box. So those VMs in the gluster 'pool' have a local write and then only 1 off-server write (to the other gluster enabled compute host), which means pretty good performance. We use the gluster included 'virt' tuning...

[Adding gluster-users] On Wed, Jul 19, 2017 at 2:52 PM, yayo (j) <jaganz at gmail.com> wrote: > Hi all, > > We have an ovirt cluster hyperconverged with hosted engine on 3 full > replicated node . This cluster have 2 gluster volume: > > - data: volume for the Data (Master) Domain (For vm) > - engine: volume fro the hosted_storage Domain (for hosted engine) > > We have this problem: "engine" gluster volume have alwa...

Hi, Why do you need to replace your existing solution? If you don't need to scale out due to the capacity reasons, the async NFS server will always outperform GlusterFS Ondrej ----- The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use,

...such as Apache CloudStack, OpenStack, oVirt, OpenNebula, and Ganeti. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects an...

Hi, On Thu, Aug 24, 2017 at 2:13 AM, WK <wkmail at bneit.com> wrote: > The default timeout for most OS versions is 30 seconds and the Gluster > timeout is 42, so yes you can trigger an RO event. I get read-only mount within approximately 2 seconds after failed IO. > Though it is easy enough to raise as Pavel mentioned > > # echo 90 > /sys/block/sda/device/timeout AFAIK

...to docs I found/read, I needed only add the new repo, do a yum > update, reboot, and be good on my hosts (did the yum update, the > engine-setup on my hosted engine). Things seemed to work relatively well, > except for a gluster sync issue that showed up. > > My cluster is a 3 node hyperconverged cluster. I upgraded the hosted > engine first, then engine 3. When engine 3 came back up, for some reason > one of my gluster volumes would not sync. Here's sample output: > > [root at ovirt3 ~]# gluster volume heal data-hdd info > Brick 172.172.1.11:/gluster/brick3/data-hdd &...

...the new repo, do a yum >>> update, reboot, and be good on my hosts (did the yum update, the >>> engine-setup on my hosted engine). Things seemed to work relatively well, >>> except for a gluster sync issue that showed up. >>> >>> My cluster is a 3 node hyperconverged cluster. I upgraded the hosted >>> engine first, then engine 3. When engine 3 came back up, for some reason >>> one of my gluster volumes would not sync. Here's sample output: >>> >>> [root at ovirt3 ~]# gluster volume heal data-hdd info >>> Brick...

That really isnt an arbiter issue or for that matter a Gluster issue. We have seen that with vanilla NAS servers that had some issue or another. Arbiter simply makes it less likely to be an issue than replica 2 but in turn arbiter is less 'safe' than replica 3. However, in regards to Gluster and RO behaviour The default timeout for most OS versions is 30 seconds and the Gluster

...oot, and be good on my hosts (did the yum update, the >>>>>> engine-setup on my hosted engine). Things seemed to work relatively well, >>>>>> except for a gluster sync issue that showed up. >>>>>> >>>>>> My cluster is a 3 node hyperconverged cluster. I upgraded the hosted >>>>>> engine first, then engine 3. When engine 3 came back up, for some reason >>>>>> one of my gluster volumes would not sync. Here's sample output: >>>>>> >>>>>> [root at ovirt3 ~]# glus...

On 07/19/2017 08:02 PM, Sahina Bose wrote: > [Adding gluster-users] > > On Wed, Jul 19, 2017 at 2:52 PM, yayo (j) <jaganz at gmail.com > <mailto:jaganz at gmail.com>> wrote: > > Hi all, > > We have an ovirt cluster hyperconverged with hosted engine on 3 > full replicated node . This cluster have 2 gluster volume: > > - data: volume for the Data (Master) Domain (For vm) > - engine: volume fro the hosted_storage Domain (for hosted engine) > > We have this problem: "engine" gluster...

Hi, We are looking into replacing our current storage solution and are evaluating gluster for this purpose. Our current solution uses a SAN with two servers attached that serve samba and NFS 4. Clients connect to those servers using NFS or SMB. All users' home directories live on this server. I would like to have some insight in who else is using gluster for home directories for about 500

...volumes) > > According to the dooutput (otps://docs.gluster.org/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/) : > > Note:?Enabling the arbiter feature?automatically?configures?client-quorum to 'auto'. This setting is?not?to be changed. > > Here is my output (Hyperconverged Virtualization Cluster -> oVirt): > # gluster volume info engine |? grep quorum > cluster.quorum-type: auto > cluster.server-quorum-type: server > > Changing quorum is more 'riskier' than other options, so you need to take necessary measures.? I think , we all? know what w...

...ters are using in replica volumes) According to the dooutput (otps://docs.gluster.org/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/) : Note:?Enabling the arbiter feature?automatically?configures?client-quorum to 'auto'. This setting is?not?to be changed. Here is my output (Hyperconverged Virtualization Cluster -> oVirt): # gluster volume info engine | grep quorum cluster.quorum-type: auto cluster.server-quorum-type: server Changing quorum is more 'riskier' than other options, so you need to take necessary measures. I think , we all know what will happen , if the clus...

...t;>>>>>>> engine-setup on my hosted engine). Things seemed to work relatively well, >>>>>>>>>> except for a gluster sync issue that showed up. >>>>>>>>>> >>>>>>>>>> My cluster is a 3 node hyperconverged cluster. I upgraded the >>>>>>>>>> hosted engine first, then engine 3. When engine 3 came back up, for some >>>>>>>>>> reason one of my gluster volumes would not sync. Here's sample output: >>>>>>>>>> &...

...t;> engine-setup on my hosted engine). Things seemed to work relatively well, >>>>>>>>>>>> except for a gluster sync issue that showed up. >>>>>>>>>>>> >>>>>>>>>>>> My cluster is a 3 node hyperconverged cluster. I upgraded the >>>>>>>>>>>> hosted engine first, then engine 3. When engine 3 came back up, for some >>>>>>>>>>>> reason one of my gluster volumes would not sync. Here's sample output: >>>>>>&g...

...y hosted engine). Things seemed to work relatively well, >>>>>>>>>>>>>> except for a gluster sync issue that showed up. >>>>>>>>>>>>>> >>>>>>>>>>>>>> My cluster is a 3 node hyperconverged cluster. I upgraded >>>>>>>>>>>>>> the hosted engine first, then engine 3. When engine 3 came back up, for >>>>>>>>>>>>>> some reason one of my gluster volumes would not sync. Here's sample output: >>&g...

...e-setup on my hosted engine). Things seemed to work relatively well, >>>>>>>>>>>>> except for a gluster sync issue that showed up. >>>>>>>>>>>>> >>>>>>>>>>>>> My cluster is a 3 node hyperconverged cluster. I upgraded the >>>>>>>>>>>>> hosted engine first, then engine 3. When engine 3 came back up, for some >>>>>>>>>>>>> reason one of my gluster volumes would not sync. Here's sample output: >>>>&g...

...y hosted engine). Things seemed to work relatively well, >>>>>>>>>>>>>> except for a gluster sync issue that showed up. >>>>>>>>>>>>>> >>>>>>>>>>>>>> My cluster is a 3 node hyperconverged cluster. I upgraded >>>>>>>>>>>>>> the hosted engine first, then engine 3. When engine 3 came back up, for >>>>>>>>>>>>>> some reason one of my gluster volumes would not sync. Here's sample output: >>&g...