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 working, and start over.
Sent from my iPad
> On Jan 20, 2020, at 11:46 PM, Tony Brian Albers <tba(a)kb.dk> wrote:
>
>> On Tue, 2020-01-21 at 07:35 +0000, webmattr(a)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 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 of oVirt, and wanted to try it with a couple disposable
>> vm's (plex, and a docker instance I break often). My current best-
>> thought for how to make it work is to setup NFS on the server, and
>> then point the self-hosted engine at the (local) NFS share. Is there
>> a better way to do this that I might be overlooking?*
>>
>> *Factoring that I don't have the funds to build out a proper storage
>> environment, yet.
>>
>> (and if anyone asks, I did search for a solution to this, but didn't
>> find anything super helpful. Mostly I found 5+ year old articles on a
>> similar but different scenario).
>>
>
> Well, if you can live with a regular engine(not self-hosted), this
> works:
>
>
https://www.ovirt.org/documentation/install-guide/chap-Installing_oVirt.html
>
>
> HTH
>
> /tony
>
>
>
>
>
>
>