[ovirt-users] hosted_engine on gluster storage for all the same fqdn?

[Sahina Bose]

On Thu, Aug 4, 2016 at 9:21 PM, Florian Nolden <f.nolden at xilloc.com> wrote:

> Thank's allot Sahina,
>
> I wouldn't come up with that solution. Would be nice to have that info
> also in the Wiki.
>
> https://www.ovirt.org/develop/release-management/features/en
> gine/self-hosted-engine/
>


We're working on updating the docs and feature page for hyperconverged
deployment. Meanwhile, please fee free to contribute and update this info
in link


>
> 2016-08-04 17:36 GMT+02:00 Sahina Bose <sabose at redhat.com>:
>
>>
>>
>> On Thu, Aug 4, 2016 at 8:13 PM, Florian Nolden <f.nolden at xilloc.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I try to install the hosted_engine on 3 Servers which host also the
>>> gluster data storage.
>>> When I install now the hosted_engine, which storage path should I use?
>>>
>>> Setup 1:
>>> server1: server1.san:/hosted_engine
>>> server2: server1.san:/hosted_engine
>>> server3: server1.san:/hosted_engine
>>>
>>
>>
>> Use this along with an answers.conf file with following content
>> [environment:default]
>> OVEHOSTED_STORAGE/mntOptions=str:backup-volfile-servers=serv
>> er2.san:server3.san
>>
>> and deploy hosted engine using "hosted-engine --deploy
>> --config-append=answers.conf"
>>
>> This will ensure that hosted-engine domain can be mounted on other
>> servers even when server1 is not reachable.
>>
>>
>>
>>>
>>> Setup 2:
>>> server1: localhost:/hosted_engine
>>> server2: localhost:/hosted_engine
>>> server3: localhost:/hosted_engine
>>>
>>> Setup 3:
>>> /etc/hosts: 127.0.0.1 gluster
>>> server1: gluster:/hosted_engine
>>> server2: gluster:/hosted_engine
>>> server3: gluster:/hosted_engine
>>>
>>> Other Setup? What is the best practice there?
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160805/3193fd77/attachment-0001.html>