Bootdisk Provisioning

Hi there

We are very much looking forward to the 1.12 release because of the
bootdisk based provisioning feature.
We have no DHCP in our server subnets so up until now we had to manually
attach the iso file to the VMs.

I've been testing the new functionality with RC1 and it seems to just work©.
One thing we'd like to see in the final release is that the iso file gets
dismounted and deleted after the VM is deployed.

I think when the new VM calls back to foreman to inform it that it's built,
it should be possible to hook into this step?

Thanks for all the hard work!
Sandro

> Hi there
>
> We are very much looking forward to the 1.12 release because of the
> bootdisk based provisioning feature.

This was in foreman_bootdisk 7.0.0 too (compatible with and shipped in
Foreman 1.11's repositories).

> We have no DHCP in our server subnets so up until now we had to manually
> attach the iso file to the VMs.
>
> I've been testing the new functionality with RC1 and it seems to just work©.
> One thing we'd like to see in the final release is that the iso file
> gets dismounted and deleted after the VM is deployed.

Well this isn't a Foreman feature, it's not part of Foreman 1.12's
(final) release, you're talking about something for a future update of
the plugin.

The kickstart template has reboot --eject added to it, so check that's
set as it ought to eject the virtual CDROM:
https://github.com/theforeman/community-templates/commit/7f33169c. Other
OSes will need some more work to eject from the provisioning templates,
please send fixes to that repo.

> I think when the new VM calls back to foreman to inform it that it's
> built, it should be possible to hook into this step?

The issue tracker is the place to file a feature request, see
https://github.com/theforeman/foreman_bootdisk#issues.

··· On 10/06/16 09:43, Sandro Roth wrote:


Dominic Cleal
dominic@cleal.org

>
> > Hi there
> >
> > We are very much looking forward to the 1.12 release because of the
> > bootdisk based provisioning feature.
>
> This was in foreman_bootdisk 7.0.0 too (compatible with and shipped in
> Foreman 1.11's repositories).
>

Didn't notice that, thanks!

> > We have no DHCP in our server subnets so up until now we had to manually
> > attach the iso file to the VMs.
> >
> > I've been testing the new functionality with RC1 and it seems to just
> work©.
> > One thing we'd like to see in the final release is that the iso file
> > gets dismounted and deleted after the VM is deployed.
>
> Well this isn't a Foreman feature, it's not part of Foreman 1.12's
> (final) release, you're talking about something for a future update of
> the plugin.
>
> The kickstart template has reboot --eject added to it, so check that's
> set as it ought to eject the virtual CDROM:
> https://github.com/theforeman/community-templates/commit/7f33169c. Other
> OSes will need some more work to eject from the provisioning templates,
> please send fixes to that repo.
>

Yeah this doesn't work for RHEL yet as mentioned in the PR.
https://bugzilla.redhat.com/show_bug.cgi?id=1191386

>
> > I think when the new VM calls back to foreman to inform it that it's
> > built, it should be possible to hook into this step?
>
> The issue tracker is the place to file a feature request, see
> https://github.com/theforeman/foreman_bootdisk#issues.
>

Will do

··· On Friday, June 10, 2016 at 10:58:18 AM UTC+2, Dominic Cleal wrote: > On 10/06/16 09:43, Sandro Roth wrote:


Dominic Cleal
dom...@cleal.org <javascript:>