> > Sounds pretty good to me. Just to check we're on the same page, the > > patch below is meant so that the discovery image accepts blocks, so that > > the discovery image can accept *another* image and boot from it? > > I was under the impression you could use image to dump to disk and boot it > (think reusing your vm templates / cloud images for bare metal too). > > this can open the usage case of cloud init for bare metal and ideally speed > up bare metal provisioning time.
Yes, today if you use the patch, you can dump the image using netcat or using udpcast (multicast) and reboot and it just works. My idea is to: - extend FDI API with partitioning endpoint (create volumes/LVM) - create a image "library" plugin that will serve images - provide some helper scripts to feed the library with some images (*) - create new provisioning workflow in discovery plugin Initial "library" could be very easy smart-proxy plugin with simple provider (raw files in a directory) but we could integrate with other technologies later on. (*) virt-builder is a nice tool that can easily create bunch of images for you with firstboot scripts, custom root passwords and stuff like that -- Later, Lukas #lzap Zapletal -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
