On 01.09.2017 11:21, Daniel P. Berrange wrote: > On Fri, Sep 01, 2017 at 04:39:38PM +0800, Fam Zheng wrote: >> On Thu, 08/31 12:59, Philippe Mathieu-Daudé wrote: >>> Hi Fam, >>> >>> On 08/31/2017 03:42 AM, Fam Zheng wrote: >>>> This is the common code to implement a "VM test" to >>>> >>>> 1) Download and initialize a pre-defined VM that has necessary >>>> dependencies to build QEMU and SSH access. >>> >>> Looking at this project: >>> >>> https://www.packer.io/docs/builders/qemu.html >>> >>> Maybe we can have another CI that prepare/upload those images (reproducible, >>> easy upgrade version...), and document the build process in the JSON instead >>> of the wiki (so the doc is up to date). >> >> Thanks for the pointer, looks interesting. The json files can be committed to >> QEMU if we go that way. Though I'm not very convinced by the "screen capture" >> style automation that is used by the *BSD user recipes I've found with >> google. >> It would be good if *BSD can have cloud-init or kickstart -alike automation, >> with those we don't even need Packer. > > FreeBSD at least supports automation of its installer. eg > > https://github.com/clalancette/oz/blob/master/oz/FreeBSD.py > > Haven't found info on other *BSDs though. > > Regards, > Daniel >
NetBSD installer does not have scripting as far as I can say, but I think it's waste of time and resources to do it for qemu CI. A single image with BSD images will be supported for at least few years for FreeBSD and NetBSD and one year for OpenBSD.
signature.asc
Description: OpenPGP digital signature
