On Sun, Oct 4, 2020 at 6:09 PM Amit Bawer wrote:
>
>
>
> On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi
> wrote:
>>
>> On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
>>>
>>>
>>>
>>> Since there wasn't a filter set on the node, the 4.4.2 update added the
>>> default filter for the root-lv
>And of course I want Gluster to switch between single node, replication >and
>dispersion seemlessly and on the fly, as well as much better >diagnostic tools.
Actually Gluster can switch from distributed to
replicated/distributed-replicated on the fly.
Best Regards,
Strahil Nikolov
Hi Mike,
In order to add them to a single cluster , you should set them to Opteron_G5
(my FX-8350 is also there) , untill you replace the host with something more
modern.
Of course , you can have your hosts in separate clusters - but then you won't
be able to live migrate your VMs.
Best
Thanks a lot for this feed back!
I've never had any practical experience with Ceph, MooseFS, BeeGFS or Lustre:
GlusterFS to me mostly had the charme of running on 1/2/3 nodes and then
anything beyond at a balanced benefits in terms of resilience vs.
performance... in theory, of course.
And on
Thank you very much for your story!
It has very much confirmed a few suspicions that have been gathering over the
last... O my God! Has it two years already?
1. Don't expect plug-and-play, unless you're on SAN or NFS (even HCI doesn't
seem to be in the heart of the oVirt team)
2. Don't expect
Hello everybody,
for some days I upgrade our environment from ovirt 4.3 to 4.4.2 and now
I stuck on upgrading the host compatibility version. It show there a
compatibility until version 4.4. The VMs have a limit until version 4.5
and the cluster shows to that I can upgrade them until 4.5.
From what I observed (but it's not something I try often), if you try to enable
maintenance on a host and have VMs on it, it will try migrating the VMs first,
which is a copy-first, state-transfer-afterwards process. So if there is no
migration target available or if the copying and
On Sun, Oct 4, 2020 at 5:28 PM Gianluca Cecchi
wrote:
> On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
>
>>
>>
>> Since there wasn't a filter set on the node, the 4.4.2 update added the
>> default filter for the root-lv pv
>> if there was some filter set before the upgrade, it would not have
On Sun, Oct 4, 2020 at 10:21 AM Amit Bawer wrote:
>
>
> Since there wasn't a filter set on the node, the 4.4.2 update added the
> default filter for the root-lv pv
> if there was some filter set before the upgrade, it would not have been
> added by the 4.4.2 update.
>
>>
>>
Do you mean that I
On Sun, Oct 4, 2020 at 2:07 AM Gianluca Cecchi
wrote:
> On Sat, Oct 3, 2020 at 9:42 PM Amit Bawer wrote:
>
>>
>>
>> On Sat, Oct 3, 2020 at 10:24 PM Amit Bawer wrote:
>>
>>>
>>>
>>> For the gluster bricks being filtered out in 4.4.2, this seems like [1].
>>>
>>> [1]
10 matches
Mail list logo
