On 7/13/2019 6:28 AM, Strahil Nikolov wrote:

I still don't get why you need the OVA .

Are you trying to extract and put it into another virtualization. If this is your intention - better install it as if it was a standalone engine.

Yes, I am trying to build ova with different OS.

What do you mean install it as standalone engine?

install VM first then install as ovirt engine?

Thanks,

Jingjie

Best Regards,

Strahil Nikolov.

В петък, 12 юли 2019 г., 21:48:35 ч. Гринуич+3, Jingjie Jiang <jingjie.jiang@oracle.com> написа:

Hi Strahil,

Thanks for your reply.

Can you share the procedure of creating ovirt-engine-appliance ova?

Thanks,

Jingjie

On 7/12/19 12:52 AM, Strahil wrote:

Based on my experience - the OVA contains the xml and the actual disk of the hosted engine.
Then the deployment starts locally the VM and populates the necessary data in it
Once it's over , the deployment shuts down and copies the disk of that local VM, undefines it and then ovirt's ha agents are being configured - so they can mount the shared storage and power up the VM (special tar /OVMF/ file on shared storage has the agent  configuration file).

So , in the ova there should be a  template VM + the xml config (cpus, ram, devices, etc) .
I would be surprised if there is something else in it.

Best Regards,
Strahil Nikolov

On Jul 11, 2019 23:39, Jingjie Jiang <jingjie.jiang@oracle.com> wrote: