it should work in general, but there are couple of corner cases to be aware of.
Hosted engine VM should have its disks only on the HE storage domain.
The HE should be installed using the new Node 0 approach (default in
4.2.1+) or it must not use any custom mount options
For all those reasons we do not recommend using it in production, but
we are not aware about anything that would really block you from doing
it. It just hasn't been tested and polished enough yet.
On Fri, Feb 9, 2018 at 1:02 PM, Simone Tiraboschi <stira...@redhat.com> wrote:
> On Fri, Feb 9, 2018 at 10:20 AM, yayo (j) <jag...@gmail.com> wrote:
>> Is there any problem to use the "hosted_engine" data domain to put disk of
>> others VM?
> it will be the default in 4.3.
> It's tracked here:
> I'm not aware of any specific block on 4.2 so it should work on technical
> side although it's not the recommended architecture on production systems.
> For sure you can actually face some perforce degradation of block device
> storage domains (iSCSI and FC) if you have a lot of inactive VMs on the
> hosted-engine storage domain due to
>> I have created a "too big" "hosted_engine" data domain so I want to use
>> that space...
>> Thank you
>> Users mailing list
> Users mailing list
Users mailing list