- Add 2013Q4 report on FreeBSD/EC2

Submitted by:	cperciva
This commit is contained in:
Gabor Pali 2014-01-11 10:47:52 +00:00
parent a750aeeb18
commit 07d489fd3d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=43471

View file

@ -19,7 +19,7 @@
<!-- XXX: Keep updating the number of entries -->
<p>Thanks to all the reporters for the excellent work! This report
contains 11 entries and we hope you enjoy reading it.</p>
contains 12 entries and we hope you enjoy reading it.</p>
<p>The deadline for submissions covering between January and
March 2014 is April 7th, 2014.</p>
@ -608,4 +608,57 @@
threads.</task>
</help>
</project>
<project cat='arch'>
<title>&os;/EC2</title>
<contact>
<person>
<name>
<given>Colin</given>
<common>Percival</common>
</name>
<email>cperciva@freebsd.org</email>
</person>
</contact>
<links>
<url href="http://www.daemonology.net/freebsd-on-ec2/">&os;/EC2 status page</url>
<url href="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html">Configinit</url>
</links>
<body>
<p>An Amazon Machine Image (AMI) is a special type of virtual
appliance that is used to create a virtual machine within the
Amazon Elastic Compute Cloud ("EC2"). It serves as the basic
unit of deployment for services delivered using EC2. Such AMIs
are available for <tt>8.3-RELEASE</tt> and later &os; releases,
and every ALPHA, BETA, and RC of &os;&nbsp;10.0. Starting from
&os;&nbsp;<tt>10.0-BETA1</tt>, &os;/EC2 images are running
"fully supported" &os; binaries, and starting from
&os;&nbsp;<tt>10.0-RC1</tt>, &os;/EC2 images include a
<tt>"configinit"</tt> system for autoconfiguration using EC2
user-data.</p>
<p>Due to limitations of old (<tt>m1</tt>, <tt>m2</tt>,
<tt>c1</tt>, <tt>t1</tt>) instance types,
<tt>"Windows"</tt>-labelled images are required for those
instance types; however all of the recent instances types
&mdash; <tt>m3</tt> (general purpose), <tt>c3</tt> (high-CPU),
and <tt>i2</tt> (high-I/O) &mdash; support &os; at the
<tt>"unix"</tt> pricing rates.</p>
<p>The maintainer of this platform considers it to be ready for
production use.</p>
</body>
<help>
<task>Hand over the task of building &os; AMIs to the Release
Engineering Team.</task>
<task>Get Amazon to add <tt>"&os;"</tt> to the list of platforms
supported by EC2, so that it can stop showing up as <tt>"Other
Linux"</tt>.</task>
</help>
</project>
</report>