I'm looking at using a script similar to
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/export_vm_as_ova.py
to
export VMs as OVA for backup purposes. I tested it out and it seems that
it does create a snapshot and allows me to export an OVA of a running VM.
I read in guides
Hello
>I hope you plan to add another brick or arbiter, as you are now prone to
>split-brain and
other issues.
Yes I will add an other one, but I think this is not a problem. I ve set
cluster.server-quorum-ratio to 51% to avid the split brain problem. of course I
know I just have failure
On January 21, 2020 7:11:19 AM GMT+02:00, Stefan Wolf wrote:
>Hi Strahil,
>
>yes it is a replica 4 set
>I ve tried to stop and stop every gluster server,
>and Ive rebooted every server.
>
>or should I remove the brick and add it again?
>
>bye
>stefan
Dear oVirt,
While investigating and DHCP & DDNS collision issues between two VM servers
from different oVirt clusters, I noticed that oVirt assigns same default MAC
range for each of it’s managed clusters.
Question1: Does oVirt-Engine keep separate place in DB or … for MAC addresses
assigned
That was my original configuration, but I found that it wouldn't let me add the
local machine as a host, and so I thought perhaps I needed to use the
self-hosted deployment methodology instead.
Would a regular engine be better for my deployment type? If so, I can
investigate why that isn't
On Tue, Jan 21, 2020 at 8:37 AM wrote:
> Hello,
>
> I can't seem to install the self-hosted engine onto local storage. It
> gives me glustefs, iscsi, fc, and nfs as the available options. I'm using
> this in a home-lab scenario, and don't have budget/etc. for building out a
> dedicated NAS for
In a small environment I think the easiest way would be to use the
local machine as a host and then run the engine as a vm on a laptop or
an older PC. As long as you have memory enough it runs on pretty much
anything.
Be careful when using local storage, it's got some special
requirements:
You can set up a localhost NFS server to serve out the local storage.
Just ensure you have enough RAM so you don't hit the potential NFS
dead-locking problem. I've been running in this configuration for several
years. I've got 256GB RAM on the host. Works great for me.
-derek
On Tue, January
I run a single server setup for my home needs / lab work - and did
exactly as you described, run NFS on the server and mount it locally.
Little bit of overhead at the top end of performance, but we talking a
home lab so over-all it runs fine.
On 2020-01-21 6:35 PM, webma...@hotmail.com
I dont think a bare-metal engine can be a compute node as well.
On 2020-01-21 6:46 PM, Tony Brian Albers wrote:
On Tue, 2020-01-21 at 07:35 +, webma...@hotmail.com wrote:
Hello,
I can't seem to install the self-hosted engine onto local storage. It
gives me glustefs, iscsi, fc, and nfs as
10 matches
Mail list logo
