Why was HE Install made OVA only?
Hi, What was the reasoning behind making Hosted Engine install OVA only? The PXEBoot feature always worked really well for me, and now I have a number of extra steps to achieve the same end result. Thanks, Alan
On Mon, Nov 20, 2017 at 4:39 PM, Alan Griffiths <apgriffiths79@gmail.com> wrote:
Hi,
What was the reasoning behind making Hosted Engine install OVA only? The PXEBoot feature always worked really well for me, and now I have a number of extra steps to achieve the same end result.
Do you mean that you were customizing the image shipped via PXE? Deploying from the OVA is pretty convenient, if you want just to forget about it, you have to install also ovirt-engine-appliance rpm when you install ovirt-hosted-engine-setup one. I don't see other additional steps.
Thanks,
Alan _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I was building my own image, using Foreman, Puppet and PXE. There's a specific partitioning schema I'm required to use in my environment and building my own image from Kickstart is by far the easiest way to achieve this. I can appreciate that in most scenarios the OVA install is the best/easiest option, but it would have been nice to keep PXE and ISO options. On 20 November 2017 at 17:24, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Mon, Nov 20, 2017 at 4:39 PM, Alan Griffiths <apgriffiths79@gmail.com> wrote:
Hi,
What was the reasoning behind making Hosted Engine install OVA only? The PXEBoot feature always worked really well for me, and now I have a number of extra steps to achieve the same end result.
Do you mean that you were customizing the image shipped via PXE? Deploying from the OVA is pretty convenient, if you want just to forget about it, you have to install also ovirt-engine-appliance rpm when you install ovirt-hosted-engine-setup one. I don't see other additional steps.
Thanks,
Alan _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, Nov 21, 2017 at 10:26 AM, Alan Griffiths <apgriffiths79@gmail.com> wrote:
I was building my own image, using Foreman, Puppet and PXE. There's a specific partitioning schema I'm required to use in my environment and building my own image from Kickstart is by far the easiest way to achieve this.
Also our default appliance is built from a kickstart file. You can simply customize it as you need and rebuild your custom appliance to be used with hosted-engine-setup. Look here to see how the ovirt engine appliance is built: https://github.com/oVirt/ovirt-appliance/tree/master/engine-appliance
I can appreciate that in most scenarios the OVA install is the best/easiest option, but it would have been nice to keep PXE and ISO options.
The point is that now hosted-engine-setup is strongly using cloud-init to automatically configure the appliance and execute engine-setup there. It's simply using the no-cloud datasource which is just a cloud-init specific iso file attached on the fly as a CDROM; doing it over a pxe boot will instead require a zero conf network to supply cloud init data and it's by far more complex.
On 20 November 2017 at 17:24, Simone Tiraboschi <stirabos@redhat.com> wrote:
On Mon, Nov 20, 2017 at 4:39 PM, Alan Griffiths <apgriffiths79@gmail.com
wrote:
Hi,
What was the reasoning behind making Hosted Engine install OVA only? The PXEBoot feature always worked really well for me, and now I have a number of extra steps to achieve the same end result.
Do you mean that you were customizing the image shipped via PXE? Deploying from the OVA is pretty convenient, if you want just to forget about it, you have to install also ovirt-engine-appliance rpm when you install ovirt-hosted-engine-setup one. I don't see other additional steps.
Thanks,
Alan _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Alan Griffiths -
Simone Tiraboschi