Can anyone share their experience on deploying hosted-engine with GlusterFS
I managed to setup a GlusterFS cluster and started to deploy hosted engine.
At first stage I was beaten by firewall rules - the deployment process
interrupted at GlusterFS config stage.
After fixing the
cockpit is enabled by default when you use ovirt-node. You will
probably have to install the necessary cockpit packages yourself on
pure CentOS - you will need cockpit and ovirt + gdeploy cockpit
plugins (sadly I do not recall the exact package names).
With regards to arbiter and the
Thanks for an article, Martin!
Any chance to configure a third cost to act as GlusterFS Arbitr only using
And stupid question - how to make this wizard up and running? I've
everything installed and nothing is runnin on port 9090 :)
On Fri, Nov 3, 2017 at 12:49 PM,
you should take a look at the hyper converged way of installing oVirt.
We have a cockpit wizard that does almost everything for you:
It uses three hosts and collocates the VMs together with Gluster
Nevertheless you could end up with a split brain situation because
you've no quorum.
So it doesn't matter which kind of cluster you want to build, but you'll
need a third node as a tiebreaker.
I know that a 2 node cluster with drbd would work, but not in all cases,
so do yourself a favor and get
Exporting the VMs to an export storage domain on the first server,
copying the files to another export storage domain on the second server
and importing it should work. What kind of problem did you find?
As for the order of doing things, my first oVirt lab was a 3-node setup
with gluster (oVirt
On drbd you have one master and use iscsi to share the storage. If the
master fails it will fail over to the other.
You have one up that will act as the iscsi storage and jump between the hosts.
If you run drbd master master ... Then you might get split brain and that
is not fun :)
Good point! Need to focus on this first
On Fri, Nov 3, 2017 at 10:50 AM, Karli Sjöberg wrote:
> On fre, 2017-11-03 at 10:39 +0300, Artem Tambovskiy wrote:
> > Thanks Eduardo!
> > I think I can find a third server to build a glusterFS storage. So
> > the
Just genuinely curious, how do you avoid split-brain situations with a
2-node setup (be it drbd, gluster or anything else)?
Eduardo Mayoral Jimeno (emayo...@arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
On 03/11/17 08:40, Johan
On fre, 2017-11-03 at 10:39 +0300, Artem Tambovskiy wrote:
> Thanks Eduardo!
> I think I can find a third server to build a glusterFS storage. So
> the first step will be to install a self-hosted engine on the new
> server and start building a glusterFS storage.
You´ll need to build the
Check on drbd. I have used that to build a cluster for two servers. It need
some more work than a three node gluster conf but works well.
I even think they have a white paper on how to do it for virtualization.
On November 3, 2017 08:11:04 Artem Tambovskiy
I think I can find a third server to build a glusterFS storage. So the
first step will be to install a self-hosted engine on the new server and
start building a glusterFS storage. IS there any easy way to migrate
existing 5 VM's running on the second bare-metal oVirt host, right?
For HA you will need some kind of storage available to all the compute
nodes in the cluster. If you have no external storage and few nodes, I
think your best option for storage is gluster , and the minimum number
of nodes you will need for HA is 3 (the third gluster node can be
Mail list logo