[hosted-engine] Dedicated LUN for hosted_engine data domain?
Hi, I used to install oVirt hosted-engine 3.5 using fibre channel storage. It required a dedicated LUN, which can't be used by other VMs, to host the hosted engine VM. Therefore, I have to create a small LUN (50GB) for the engine VM in addition to the LUN that I used to host other VMs. Does this still apply in 3.6.x? I'm currently using 3.6.4 and notice that I can now choose to create a new domain using the LUN reserved for the hosted engine (I didn't choose that LUN, but when I create my first data domain, 'hosted_storage' domain was created automatically and that LUN can't be selected by new domains anymore), and am able to deploy a new disk to 'hosted_storage' like any other data domain. -- Wee
On Tue, Apr 26, 2016 at 8:55 AM, Wee Sritippho <wee.s@forest.go.th> wrote:
Hi,
I used to install oVirt hosted-engine 3.5 using fibre channel storage. It required a dedicated LUN, which can't be used by other VMs, to host the hosted engine VM. Therefore, I have to create a small LUN (50GB) for the engine VM in addition to the LUN that I used to host other VMs.
Does this still apply in 3.6.x?
Yes, absolutely.
I'm currently using 3.6.4 and notice that I can now choose to create a new domain using the LUN reserved for the hosted engine (I didn't choose that LUN, but when I create my first data domain, 'hosted_storage' domain was created automatically and that LUN can't be selected by new domains anymore), and am able to deploy a new disk to 'hosted_storage' like any other data domain.
This could be an issue, adding Roy here.
-- Wee
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Simone Tiraboschi -
Wee Sritippho