Dragonfly on GCE

Brad Fitzpatrick bradfitz at golang.org
Fri Dec 8 18:03:23 PST 2017


Thanks, Tim.

I was just about to post here about this.

As background, I run https://build.golang.org/ and manage its 55+ build
configurations (various OSes, architectures, versions). We run almost
everything in VMs (almost all GCE, but VMWare for Macs), and other stuff in
zones or Docker or other container things.

The Dragonfly builder is one of our inelastic non-VM configs. I believe it
runs on a single machine in a loop? We're prefer to run it on GCE where we
can spin up thousands of cores as needed.

GCE is KVM (but not qemu) and uses virtio.

I see Dragonfly supports virtio now, so I suspect it'd run on GCE. Usually
if something runs under qemu's virtio, it also runs on GCE. (GCE doesn't
use qemu, though)

We have an open bug to automate the creation of a bootable GCE image for
Dragonfly, if people can help:

     https://github.com/golang/go/issues/23060

For OpenBSD, NetBSD, and FreeBSD, we have bash scripts (linked from that
bug) that we run on Linux that runs curl to fetch the install ISOs, the
runs qemu + expect to run through the installer and crap out a tarball at
the end we can copy to Google Cloud Storage and then boot VMs off. Then
every few months we refresh or create new builder template VMs for each OS.
(each build+test runs in a single-use VM) We'd love to include Dragonfly in
this set. It also enables us to create ephemeral debugging VMs when
developers break an operating system they don't have locally.

Has anybody scripted the Dragonfly installer already?

Or is there a mode to do automated installs from a config file?

Thanks!
Brad



On Fri, Dec 8, 2017 at 1:37 PM, Tim Darby <t+dfbsd at timdarby.net> wrote:

> Has anyone run Dragonfly in a VM on Google Compute Engine? The Go team
> would like to try that for the builder.
>
> Tim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20171208/81c58a4b/attachment-0003.htm>


More information about the Users mailing list