&os; on Google Cloud

From owner-svn-doc-head@FreeBSD.ORG Thu Jan 15 16:30:15 2015 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5BDFDCDF; Thu, 15 Jan 2015 16:30:15 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D8C0A88; Thu, 15 Jan 2015 16:30:15 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t0FGUFTc063561; Thu, 15 Jan 2015 16:30:15 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t0FGUFMO063560; Thu, 15 Jan 2015 16:30:15 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201501151630.t0FGUFMO063560@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Thu, 15 Jan 2015 16:30:15 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46207 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 16:30:15 -0000 Author: bjk Date: Thu Jan 15 16:30:14 2015 New Revision: 46207 URL: https://svnweb.freebsd.org/changeset/doc/46207 Log: Add gcloud report Approved by: hrs (mentor, blanket) Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Thu Jan 15 14:50:20 2015 (r46206) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Thu Jan 15 16:30:14 2015 (r46207) @@ -2604,4 +2604,153 @@ newsletter.

+ + + &os; on Google Cloud + + + + + Steve + Wills + + swills@FreeBSD.org + + + + + The script + used to create gcloud images + More + detail on how to create and use a gcloud image + + + +

Google Cloud is a cloud computing platform that allows users to + run hosted services and servers in a cloud maintained by + Google. The goal of this project is to provide an easy way to + create and manage &os; installations running on Google + Cloud.

+ +

The good news:

+ +

FreeBSD 10.1 runs fine. You can create an image and start it + up and login via standard ssh, via the gcloud command + or via the web console (ssh in a web browser window). More + details on how to do all this can be found in the links. + Basically, you should be able to gcutil addimage + freebsd-101-release-amd64-20150101032704 + gs://swills-test-bucket/FreeBSD-10.1-RELEASE-amd64-20150101032704.tar.gz

+ +

Then spin up an image using gcloud compute instances + create --zone us-central1-b --image + freebsd-101-release-amd64-20150101032704 --boot-disk-size 20GB + gtest1

+ +

These commands are part of the google-cloud-sdk port, which + contains all the commands to interact with Google Cloud. There + is also a google-daemon port which is used in running instances to + create users and set them up and a google-startup-scripts port which + handles running startup/shutdown scripts as specified in node + metadata.

+ +

Additionally, the firstboot-growfs port has been brought back so + that new instances will grow their root filesystem. (Thanks to Colin + Percival for having created that port initially.)

+ +

There is also a firstboot-freebsd-update port which can be used + to update a system on first boot but is currently disabled. See + below. Similarly, the firstboot-pkgs port/scripts will install + specified packages on first boot.

+ +

Overall, Google Cloud Compute is quite nice; instances spin up + in about 60 seconds and it is very reasonably priced with + automatic discounts for longer term usage. There is a $300 credit + for first time users that also makes it free to try out. That + credit covers quite a lot of time, and the instances are pretty + fast, as well, even the ones without SSDs.

+ +

The bad news:

+ +

Google does not make sharing non-official images as easy as + AWS, so you have to create your own using my public tar file. The + tar was created using the script in the links section. That + script can be used to produce customized images, even though there + are no official image (nor will there be any time soon).

+ +

There are some issues running FreeBSD on Google Cloud, + listed in the tasks section.

+ + + + + +

The 8 and 16 cpu instances seem to reboot randomly.

+ + + +

Repeated UFS panics that Google folks have reported, but + I do not think those are particular to Google Cloud. The panic + message is "ffs_valloc dup alloc".

+ + + +

Running freebsd-update causes the system to become + unbootable, so updates do not work. (Reboots work fine + otherwise.)

+ + + +

There is no gcimagebundle command in the Ports + Collectiong so you cannot easily create an image from a running + machine.

+ + + +

There are a few minor issue with the startup script + that is supposed to regenerate ssh keys (for when you + create an image from an existing system).

+ + + +

10.1 works, but 10.0 does not boot; other versions remain + untested.

+ + + +

The kern.vm_guest sysctl node does not detect that it is in a + guest.

+ + + +

The vtnet driver needs wq disabled on 16 cpu boxes, but + is just disabled everywhere for now since that is easier.

+ + + +

There is a work needed for the Google + safe_format_and_mount command which formats and + mounts newly attached disks, but this is just a nicety really.

+ + + +

I need to look into irq affinity for vtnet.

+ + + +

We need to support virtualized clocks; bryanv@ is + working on this. In fact, all his ongoing work in the virt area + would probably make things work better.

+ + + +

It would be nice if there as the ability to disable the + spinner before the loader, which clutters up the console log. The + ability to disable it is in HEAD; hopefully it will be MFCd to + 10-STABLE before 10.2.

+ + + +