&os;/EC2

From owner-svn-doc-head@FreeBSD.ORG Sat Oct 5 06:16:15 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 38698BE4; Sat, 5 Oct 2013 06:16:15 +0000 (UTC) (envelope-from pgj@FreeBSD.org) 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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 154622E83; Sat, 5 Oct 2013 06:16:15 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r956GEs5075709; Sat, 5 Oct 2013 06:16:14 GMT (envelope-from pgj@svn.freebsd.org) Received: (from pgj@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r956GEUN075707; Sat, 5 Oct 2013 06:16:14 GMT (envelope-from pgj@svn.freebsd.org) Message-Id: <201310050616.r956GEUN075707@svn.freebsd.org> From: Gabor Pali Date: Sat, 5 Oct 2013 06:16:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42847 - 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.14 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: Sat, 05 Oct 2013 06:16:15 -0000 Author: pgj Date: Sat Oct 5 06:16:14 2013 New Revision: 42847 URL: http://svnweb.freebsd.org/changeset/doc/42847 Log: - Add Q3 entry on the EC2 port Submitted by: cperciva Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2013-07-2013-09.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2013-07-2013-09.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2013-07-2013-09.xml Sat Oct 5 06:01:01 2013 (r42846) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2013-07-2013-09.xml Sat Oct 5 06:16:14 2013 (r42847) @@ -19,7 +19,7 @@

Thanks to all the reporters for the excellent work! This report - contains 11 entries and we hope you enjoy reading it.

+ contains 12 entries and we hope you enjoy reading it.

The deadline for submissions covering between October and @@ -565,4 +565,59 @@ Add more drivers. + + + &os;/EC2 + + + + + Colin + Percival + + cperciva@freebsd.org + + + + + &os;/EC2 Status Page + AWS Marketplace Listing + + + +

&os; images are available for use in EC2 for 8.3-RELEASE, + 8.4-RELEASE, 9.0-RELEASE, 9.1-RELEASE, and 9.2-RELEASE. In + 9.2-RELEASE, &os; runs in EC2 using an unpatched source tree, + but it needs the XENHVM kernel configuration.

+ +

Starting from &os; 10.0-ALPHA3, the GENERIC kernel + configuration now contains all the XENHVM bits needed + to allow &os; to run in EC2 natively. Consequently, + &os; 10.0 will be the first release for which &os;/EC2 is + purely "bits off the ISO". This also means that starting with + 10.0 it will be possible to use freebsd-update(8) for + all base system updates — in earlier releases it was + necessary to recompile the XENHVM kernel manually.

+ +

Due to &os;'s use of HVM virtualization, running on "old" EC2 + instance types (m1, m2, c1, t1) requires that &os; pretends to + be Windows, which unfortunately results in paying the higher + "windows" EC2 instance prices. On "new" EC2 instances (cc1, + cc2, cg1, cr1, hi1, hs1, and m3) &os; can run as a "unix" image + at the lower rate.

+ + + + Test &os; 10.0-ALPHAs/BETAs/RCs as they become available. + Plenty of new Xen code has been committed recently and there are + probably bugs to find before the release. + + Keep nagging Amazon to provide more instance types which + &os; can run on without paying a "Windows tax". + + Provide some mechanism for instance configuration via EC2 + user-data. This might involve using + cloud-init, or it might be a new system. + +