we got much closer to officially remove the specialty status of both
the domain and the VM in 4.2 with features like Node 0 deployment
(default since 4.2.1) and direct libvirtxml support in engine and HE
There are couple of outstanding issues:
- HE needs to know how to connect all storage domains necessary for HE
VM disks (not 100% related, but close)
- (live) storage migration is not supported yet - HE nodes need to
learn about the new connection details
- changes to gluster topology are not supported yet - same reason as above
- we have a bug with regards to block devices - will be fixed by
- fencing and SPM role need to be tested a bit more to make sure we
have no surprises there
- old deployments might not have some data in the engine DB
We will not be adding any additional limits as all seems to work in
the usual cases and we work on removing the remaining restrictions. I
am not 100% certain when it will be finished exactly, but you can use
it now if you are careful (basically do not use custom mount options
and do not add disks to the HE VM that would come from a different
We have two tracking bugs for the related work:
https://bugzilla.redhat.com/show_bug.cgi?id=1393902 - most of what was
needed was fixed already.
On Fri, Feb 9, 2018 at 11:06 AM, Gianluca Cecchi
> On Thu, Jun 22, 2017 at 11:37 AM, Martin Sivak <msi...@redhat.com> wrote:
>> Chris is right. We want to remove the specialty status from that
>> storage domain. It is one of the highest priority items for hosted
>> engine right now.
>> There is currently no way to hide it I am afraid.
>> Best regards
>> Martin Sivak
>> SLA / oVirt
> Hello Martin (and list),
> any update on this item to remove specialty of hosted_engine storage?
> Any bugzilla RFE or pointer? I think it didn't catch 4.2, correct?
Users mailing list