Unless I'm mistaken, when provisioning using an oVirt template no finish
provisioning templates are run. This means that it only really uses the
oVirt template as a hardware profile & the contents of the template's disk
is worthless.
I have patched our local instance running 1.3.2 so that you can use
templates like images, providing a password for the appropriate user for
SSH provisioning. This is all working fine & I would like to see it added
in to 1.4 or 1.5. If you think this is worth adding in, then should I aim
for 1.4 or 1.5 if 1.4's feature set is frozen?
Thanks,
Jimmi
> Unless I'm mistaken, when provisioning using an oVirt template no finish
> provisioning templates are run. This means that it only really uses the
> oVirt template as a hardware profile & the contents of the template's disk
> is worthless.
>
True, unless you change the boot order not to pxe, then it should boot from
the template, this partly comes because ovirt combine both hw spec + disk
under the template concept.
>
> I have patched our local instance running 1.3.2 so that you can use
> templates like images, providing a password for the appropriate user for
> SSH provisioning. This is all working fine & I would like to see it added
> in to 1.4 or 1.5. If you think this is worth adding in, then should I aim
> for 1.4 or 1.5 if 1.4's feature set is frozen?
>
1.4 is feature freeze, we would for a patch against the develop branch,
which would be next 1.5.
Thanks!
Ohad
···
On Tue, Jan 21, 2014 at 9:48 PM, Jimmi Dyson wrote:
Thanks,
Jimmi
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
