Hi,
I am using these versions for my test :
- ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm
- ovirt-node-ng-installer-4.4.1-2020072310.el8.iso
A single HCI server using nested KVM.
The gluster part works now without error, but when I click the
hosted-engine deployment button I get :
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 it, or setting up multiple nodes. I like the look
I would suggest a local single brick gluster. This will probably be most
simple and you can have a scale out option in this way to replica 3.
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
On Tue, Sep 6, 2016 at 12:17 PM, Christophe TREFOIS <
christophe.tref...@uni.lu> wrote:
> Hi,
>
> No, I move VMs around with an Export Storage domain.
>
If you have enough disk and bandwidth, perhaps it makes more sense to set
up Gluster as a shared storage?
And then just pin VMs to specific
On Tue, Sep 6, 2016 at 12:17 PM, Christophe TREFOIS
wrote:
> Hi,
>
> No, I move VMs around with an Export Storage domain.
OK.
>
> All NFS is exported only to the local machine.
>
> Nothing is “shared” between hosts. But because I want to export VMs, we use
> “shared”
Hi,
No, I move VMs around with an Export Storage domain.
All NFS is exported only to the local machine.
Nothing is “shared” between hosts. But because I want to export VMs, we use
“shared” storage in oVirt instead of “local”.
Best,
--
Dr Christophe Trefois, Dipl.-Ing.
Technical
On Tue, Sep 6, 2016 at 9:53 AM, Christophe TREFOIS
wrote:
> Personally my use case is that I have 4 machines with different specs and
> storage sizing. So I setup four DC with 1 host each. Then I have hosted
> engine on one of the hosts. Storage is local shared via
On 6 September 2016 at 00:34, Christophe TREFOIS
wrote:
> So basically we need at least 2 nodes to enter the realm of testing and
> maintained?
>
> If we’re talking pure oVirt here.
The short answer is yes.
The longer answer is more complex, but first a disclaimer,
Personally my use case is that I have 4 machines with different specs and
storage sizing. So I setup four DC with 1 host each. Then I have hosted engine
on one of the hosts. Storage is local shared via NFS so that I can move VMs
around.
At this point we are not interested necessarily in HA.
On Tue, Sep 6, 2016 at 12:34 AM, Christophe TREFOIS
wrote:
> So basically we need at least 2 nodes to enter the realm of testing and
> maintained?
I think some people occasionally use hosted-engine with local
iSCSI storage on a single machine. AFAIK it's not tested by
So basically we need at least 2 nodes to enter the realm of testing and
maintained?
If we’re talking pure oVirt here.
--
Dr Christophe Trefois, Dipl.-Ing.
Technical Specialist / Post-Doc
UNIVERSITÉ DU LUXEMBOURG
LUXEMBOURG CENTRE FOR SYSTEMS BIOMEDICINE
Campus Belval | House of
Adding Kimchi to oVirt node perhaps may be the easiest option. It can be
pretty useful for many situations and doesn't need such thing like
mounting NFS in localhost.
It is not nice to not have a All-in-One stable solution anymore as this
can help with its adoption for later growth.
On 4 September 2016 at 23:45, zero four wrote:
...
> I understand and acknowledge that oVirt is not targeted towards homelab
> setups, or at least small homelab setups. However I believe that having a
> solid configuration for such use cases would be a benefit to the project
On Mon, Sep 5, 2016 at 9:37 AM, Nir Soffer wrote:
> On Mon, Sep 5, 2016 at 8:46 AM, Philip Lo wrote:
>> I'm running single node hosted engine 4.0.x with local NFS and it runs just
>> fine. Thanks
>>
>> Regards,
>> Philip Lo
>>
>> On 5 Sep 2016, at 5:45 AM,
Oh wow. Well then I guess we are in a bad situation now. Don't really have the
infra to move to shared storage...
Isn't this the same issue then with NFS over gluster?
Best,
Sent from my iPhone
> On 05 Sep 2016, at 08:37, Nir Soffer wrote:
>
>> On Mon, Sep 5, 2016 at
On Mon, Sep 5, 2016 at 8:46 AM, Philip Lo wrote:
> I'm running single node hosted engine 4.0.x with local NFS and it runs just
> fine. Thanks
>
> Regards,
> Philip Lo
>
> On 5 Sep 2016, at 5:45 AM, Christophe TREFOIS
> wrote:
>
> I’m running 3.6
; Sent: dimanche 4 septembre 2016 22:45
> To: users@ovirt.org
> Subject: [ovirt-users] oVirt on a single server
>
> My current understanding is that oVirt no longer supports any single-server
> configuration since the All-In-One install was removed in 3.6. While the
>
...@ovirt.org] On Behalf Of
zero four
Sent: dimanche 4 septembre 2016 22:45
To: users@ovirt.org
Subject: [ovirt-users] oVirt on a single server
My current understanding is that oVirt no longer supports any single-server
configuration since the All-In-One install was removed in 3.6. While the
hosted
On Sun, Sep 4, 2016 at 11:45 PM, zero four wrote:
> My current understanding is that oVirt no longer supports any single-server
> configuration since the All-In-One install was removed in 3.6. While the
> hosted-engine install was supposed to replace it, it requires either
>
My current understanding is that oVirt no longer supports any single-server
configuration since the All-In-One install was removed in 3.6. While the
hosted-engine install was supposed to replace it, it requires either
networked storage (nfs, iscsi) or Glusterfs. To my knowledge nfs/iscsi
20 matches
Mail list logo