Start another editing pass over the 2016Q4 report

svn path=/head/; revision=49949

en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml

@@ -99,11 +99,11 @@
       <p>The AWS Marketplace reports that approximately 800 users
 	are running roughly 2000 &os; EC2 instances.  This does not
 	count the likely significantly larger number of EC2 instances
-	launched &quot;directly&quot; through the EC2 API and Console, but at
+	launched directly through the EC2 API and Console, but at
 	least places a lower bound on usage.</p>
 
       <p>&os; 11.0-RELEASE shipped with support for the &quot;enhanced
-	networking&quot; support in EC2 C3, C4, R3, I2, D2, and M4
+	networking&quot; capabilities of EC2 C3, C4, R3, I2, D2, and M4
 	(excluding m4.16xlarge) instances.  This provides
 	significantly higher network performance than the virtual
 	networking available on older EC2 instances and with older
@@ -127,7 +127,7 @@
 	m4.16xlarge instances.</task>
 
       <task>Provide tools for improved functionality via the Simple
-	Systems Manager service: Listing installed packages, checking
+	Systems Manager service: listing installed packages, checking
 	for updates, adding/removing users, [your favourite sysadmin
 	task goes here].</task>
 
@@ -172,8 +172,8 @@
 	and specify alerting conditions.  Tools like Grafana can be
 	used to create fancy dashboards using such queries.</p>
 
-      <p>The Prometheus project provides a utility called the
+      <p>The Prometheus project provides a utility called
-	node_exporter that gathers basic system metrics and serves
+	<tt>node_exporter</tt> that gathers basic system metrics and serves
 	them over HTTP.  This utility tends to be rather complex, as
 	it has to extract metrics from many different sources.  On
 	Linux, files in <tt>/proc</tt> have no uniform format, meaning
@@ -204,7 +204,7 @@
 	exporter a try!</task>
 
       <task>It would be nice if we created a set of useful alerting
-	rules and placed those in /usr/share/examples.  For example,
+	rules and placed those in <tt>/usr/share/examples</tt>.  For example,
 	how can one use this exporter to monitor the state of
 	GEOM-based RAID arrays?  Is such information even exported
 	through <tt>sysctl</tt>?</task>
@@ -370,7 +370,7 @@
 
       <p>The &os; 11.0 image on Azure (<a
 	  href="https://azure.microsoft.com/en-us/marketplace/partners/microsoft/FreeBSD110/">https://azure.microsoft.com/en-us/marketplace/partners/microsoft/FreeBSD110/</a>)
-	is also available now, in addition to the existing 10.3
+	is now available, in addition to the existing 10.3
 	image.</p>
 
       <p>We fixed an issue where SCSI disks would sometimes fail to
@@ -477,44 +477,32 @@
 	to <tt>x11/qterminal</tt> 0.7.0):</p>
 
       <ul>
-	<li>
+	<li><tt>devel/lxqt-build-tools</tt></li>
-	  <tt>devel/lxqt-build-tools</tt>
+
-	</li>
+	<li><tt>devel/liblxqt</tt></li>
-	<li>
+
-	  <tt>devel/liblxqt</tt>
+	<li><tt>devel/qtxdg</tt></li>
-	</li>
+
-	<li>
+	<li><tt>x11/libfm-qt</tt></li>
-	  <tt>devel/qtxdg</tt>
-	</li>
-	<li>
-	  <tt>x11/libfm-qt</tt>
-	</li>
       </ul>
 
       <p>Standalone applications:</p>
 
       <ul>
-	<li>
+	<li><tt>graphics/lximage-qt</tt></li>
-	  <tt>graphics/lximage-qt</tt>
+
-	</li>
+	<li><tt>x11-fm/pcmanfm-qt</tt></li>
-	<li>
-	  <tt>x11-fm/pcmanfm-qt</tt>
-	</li>
       </ul>
 
       <p>We also have updates for:</p>
 
       <ul>
-	<li>
+	<li><tt>x11/qterminal</tt> 0.7.1</li>
-	  <tt>x11/qterminal</tt> 0.7.1
+
-	</li>
+	<li><tt>x11-toolkits/qtermwidget</tt> 0.7.1</li>
-	<li>
+
-	  <tt>x11-toolkits/qtermwidget</tt> 0.7.1
+	<li>Updating the Porter's Handbook for LXQt support
-	</li>
+	  (<a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650</a>)</li>
-	<li>
-	  Updating the Porter's Handbook for LXQt support
-	  (<a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650</a>)
-	</li>
       </ul>
     </body>
 
@@ -549,65 +537,47 @@
 	up-to-date:</p>
 
       <ul>
-	<li>
+	<li><tt>audio/xfce4-mpc-plugin</tt> 0.5.0 (committed in devel
-	  <tt>audio/xfce4-mpc-plugin</tt> 0.5.0 (committed in devel
+	    repository)</li>
-	    repository)
+
-	</li>
+	<li><tt>deskutils/xfce4-notifyd</tt> 0.3.4</li>
-	<li>
+
-	  <tt>deskutils/xfce4-notifyd</tt> 0.3.4
+	<li><tt>graphics/ristretto</tt> 0.8.1</li>
-	</li>
+
-	<li>
+	<li><tt>sysutils/xfce4-diskperf-plugin</tt> 2.6.0</li>
-	  <tt>graphics/ristretto</tt> 0.8.1
+
-	</li>
+	<li><tt>sysutils/xfce4-battery-plugin</tt> 1.1.0 (committed in
-	<li>
+	    devel repository)</li>
-	  <tt>sysutils/xfce4-diskperf-plugin</tt> 2.6.0
+
-	</li>
+	<li><tt>sysutils/xfce4-fsguard-plugin</tt> 1.1.0 (committed in
-	<li>
+	    devel repository)</li>
-	  <tt>sysutils/xfce4-battery-plugin</tt> 1.1.0 (committed in
+
-	    devel repository)
+	<li><tt>sysutils/xfce4-netload-plugin</tt> 1.3.0 (committed in
-	</li>
+	    devel repository)</li>
-	<li>
+
-	  <tt>sysutils/xfce4-fsguard-plugin</tt> 1.1.0 (committed in
+	<li><tt>sysutils/xfce4-systemload-plugin</tt> 1.2.0 (committed
-	    devel repository)
+	    in devel repository)</li>
-	</li>
+
-	<li>
+	<li><tt>sysutils/xfce4-wavelan-plugin</tt> 0.6.0 (committed in
-	  <tt>sysutils/xfce4-netload-plugin</tt> 1.3.0 (committed in
+	    devel repository)</li>
-	    devel repository)
+
-	</li>
+	<li><tt>x11/xfce4-clipman-plugin</tt> 1.4.1</li>
-	<li>
+
-	  <tt>sysutils/xfce4-systemload-plugin</tt> 1.2.0 (committed
+	<li><tt>x11/xfce4-conf</tt> 4.12.1</li>
-	    in devel repository)
+
-	</li>
+	<li><tt>x11/xfce4-dashboard</tt> 0.6.1</li>
-	<li>
+
-	  <tt>sysutils/xfce4-wavelan-plugin</tt> 0.6.0 (committed in
+	<li><tt>x11/xfce4-terminal</tt> 0.8.2</li>
-	    devel repository)
+
-	</li>
+	<li><tt>x11/xfce4-whiskermenu-plugin</tt> 1.6.2</li>
-	<li>
+
-	  <tt>x11/xfce4-clipman-plugin</tt> 1.4.1
+	<li><tt>x11-clocks/xfce4-datetime-plugin</tt> 0.7.0 (committed
-	</li>
+	    in devel repository)</li>
-	<li>
+
-	  <tt>x11/xfce4-conf</tt> 4.12.1
+	<li><tt>x11-wm/xfce4-panel</tt> 4.12.1</li>
-	</li>
+
-	<li>
+	<li><tt>www/xfce4-smartbookmark-plugin</tt> 0.5.0 (committed
-	  <tt>x11/xfce4-dashboard</tt> 0.6.1
+	    in devel repository)</li>
-	</li>
-	<li>
-	  <tt>x11/xfce4-terminal</tt> 0.8.2
-	</li>
-	<li>
-	  <tt>x11/xfce4-whiskermenu-plugin</tt> 1.6.2
-	</li>
-	<li>
-	  <tt>x11-clocks/xfce4-datetime-plugin</tt> 0.7.0 (committed
-	    in devel repository)
-	</li>
-	<li>
-	  <tt>x11-wm/xfce4-panel</tt> 4.12.1
-	</li>
-	<li>
-	  <tt>www/xfce4-smartbookmark-plugin</tt> 0.5.0 (committed
-	    in devel repository)
-	</li>
       </ul>
 
       <p>We also follow the unstable releases (available in our
@@ -616,7 +586,9 @@
       <ul>
 	<li><tt>sysutils/xfce4-settings</tt> 4.13.0 (it requires Gtk+
 	    &gt; 3.20)</li>
+
 	<li><tt>x11/libexo</tt> 0.11.2</li>
+
 	<li><tt>x11/xfce4-whiskermenu-plugin</tt> 2.0.3</li>
       </ul>
     </body>
@@ -884,7 +856,7 @@
 	10.2 also reached end-of-life, support for those versions was
 	removed from the Ports Tree.</p>
 
-      <p>Some major ports were updated to their latest versions: pkg
+      <p>Some major ports were updated to their latest versions: <tt>pkg</tt>
 	to 1.9.4, Firefox to 50.1.0, Firefox-esr to 45.6.0, Chromium
 	to 54.0.2840.100, and Ruby to 2.1.10 / 2.2.6 / 2.3.3.
 	<tt>www/node</tt> was updated to version 7; version 6 was
@@ -922,7 +894,7 @@
     </links>
 
     <body>
-      <p>The Minnowboard is an Atom-based x86 board (Intel E38xx
+      <p>The MinnowBoard is an Atom-based x86 board (Intel E38xx
 	Series SoC) in a maker-friendly form-factor: it provides
 	convenient access to pins that can be used to connect
 	peripherals using one of the standard buses: GPIO, SPI, or
@@ -930,7 +902,7 @@
 	x86, so while &os; was able to boot just fine, it lacked
 	support for these buses on the MinnowBoard.</p>
 
-      <p>As of r310645, HEAD support all three buses via
+      <p>As of r310645, HEAD support all three buses via the
 	<tt>ig4(4)</tt>, <tt>bytgpio(4)</tt>, and <tt>intelspi</tt>
 	drivers.  The <tt>ig4(4)</tt> and <tt>bytgpio(4)</tt> changes
 	were backported to 11-STABLE; <tt>intelspi</tt> will be MFCed
@@ -971,6 +943,7 @@
 	    compatible with applications written for S3 and
 	    Swift.</p>
 	</li>
+
 	<li>
 	  <p>Block Storage</p>
 
@@ -978,6 +951,7 @@
 	    device images that are striped and replicated across the
 	    entire storage cluster.</p>
 	</li>
+
 	<li>
 	  <p>File System</p>
 
@@ -993,49 +967,41 @@
 	that are running ZFS.  User stations would be running
 	<tt>bhyve</tt> on RBD disks that are stored in Ceph.</p>
 
-      <p>The &os; build includes most of the tools in Ceph.  Note
+      <p>The &os; build of Ceph includes most of the tools Ceph provides.  Note
 	that the RBD-dependent items will not work, since &os; does
 	not have RBD (yet).</p>
 
       <p>The most notable progress since the last report:</p>
 
       <ul>
-	<li>
+	<li>RBD is actually buildable and can be used to manage
-	  RBD is actually buildable and can be used to manage
+	  <tt>RADOS BLOCK DEVICE</tt>s.</li>
-	  <tt>RADOS BLOCK DEVICE</tt>s.
+
-	</li>
+	<li>All tests run to completion for the current selection of
-	<li>
-	  All tests run to completion for the current selection of
 	  tools, though the neded (minor) patches have yet to be
-	  pulled into HEAD.
+	  pulled into HEAD.</li>
-	</li>
+
-	<li>
+	<li>Cmake is now the only way of building Ceph.</li>
-	  Cmake is now the only way of building Ceph.
+
-	</li>
+	<li>The threading/polling code has been reworked for the simple
-	<li>
-	  The threading/polling code has been reworked for the simple
 	  socket code.  It now uses a self-pipe, instead of using an
-	  odd <tt>shutdown()</tt>-signaling Linux feature.
+	  odd <tt>shutdown()</tt>-signaling Linux feature.</li>
-	</li>
+
-	<li>
+	<li>The EventKqueue code was modified to work around the
-	  The EventKqueue code was modified to work around the
 	  &quot;feature&quot; that starting threads destroys the
 	  kqueue handles.  The code was just finshed, so it is not yet
-	  submitted to the main repository.
+	  submitted to the main repository.</li>
-	</li>
+
-	<li>
+	<li>We investigated differences between &os; and Linux for
-	  We investigated differences between &os; and Linux for
 	  <tt>SO_REUSEADDR</tt> and <tt>SO_REUSEPORT</tt>.
 	  Fortunately, the code is only used during testing, so
-	  disabling these features only delays progress in the tests.
+	  disabling these features only delays progress in the tests.</li>
-	</li>
+
-	<li>
+	<li>A jenkins instances is regularly testing both
-	  A jenkins instances is regularly testing both
 	  <tt>ceph/ceph/master</tt> and
 	  <tt>wjwithagen/ceph/wip.FreeBSD</tt>, so there is regular
 	  verification of buildability and the tests:
-	  <a href="http://cephdev.digiware.nl:8180/jenkins/">http://cephdev.digiware.nl:8180/jenkins/</a>.
+	  <a href="http://cephdev.digiware.nl:8180/jenkins/">http://cephdev.digiware.nl:8180/jenkins/</a>.</li>
-	</li>
       </ul>
 
 
@@ -1052,22 +1018,16 @@
       <p>The following setup will get things running for &os;:</p>
 
       <ol>
-	<li>
+	<li>Install bash and link it in <tt>/bin</tt></li>
-	  Install bash and link it in <tt>/bin</tt>
-	</li>
 
-	<li>
+	<li>It is no longer necessary to add a definition of
-	  It is no longer necessary to add a definition of
+	  <tt>ENODATA</tt> to <tt>/usr/include/errno.h</tt></li>
-	  <tt>ENODATA</tt> to <tt>/usr/include/errno.h</tt>
+
-	</li>
+	<li>Clone the github repo
-	<li>
-	  Clone the github repo
 	  (http://github.com/wjwithagen/ceph.git) and checkout the
-	  &quot;wip.FreeBSD&quot; branch
+	  &quot;wip.FreeBSD&quot; branch</li>
-	</li>
+
-	<li>
+	<li>Run <tt>./do_FreeBSD.sh</tt> to start the build.</li>
-	  Run <tt>./do_FreeBSD.sh</tt> to start the build.
-	</li>
       </ol>
 
       <p>The old build method using automake is no longer used; see
@@ -1076,27 +1036,23 @@
       <p>Parts not (yet) included:</p>
 
       <ul>
-	<li>
+	<li>KRBD: Kernel Rados Block Devices is implemented in the Linux
-	  KRBD: Kernel Rados Block Devices is implemented in the Linux
 	  kernel, but not in the &os; kernel.  Perhaps <tt>ggated</tt>
 	  could be used as a template since it does some of the same
 	  things as KRBD, just between 2 disks.  It also has a
 	  userspace counterpart, which could ease development.
 	</li>
-	<li>
+
-	  BlueStore: &os; and Linux have different AIO APIs, and
+	<li>BlueStore: &os; and Linux have different AIO APIs, and
 	  that incompatibility needs to be resolved somehow.
 	  Additionally, there is discussion in &os; about
-	  <tt>aio_cancel</tt> not working for all devicetypes.
+	  <tt>aio_cancel</tt> not working for all devicetypes.</li>
-	</li>
+
-	<li>
+	<li>CephFS: Cython tries to access an internal field in
-	  CephFS: Cython tries to access an internal field in
+	  <tt>struct dirent</tt>, which does not compile.</li>
-	  <tt>struct dirent</tt>, which does not compile.
+
-	</li>
+	<li>Tests that verify the correct working of the above are
-	<li>
+	  also excluded from the testset.</li>
-	  Tests that verify the correct working of the above are
-	  also excluded from the testset.
-	</li>
       </ul>
     </body>
 
@@ -1117,7 +1073,7 @@
 
       <task>Scheduler information is not used at the moment, because
 	the schedulers work rather differently between &os; and Linux.
-	But a certain point in time, this would need some attention
+	But at a certain point in time, this would need some attention
 	in <tt>src/common/Thread.cc</tt>.</task>
 
       <task>Integrate the &os; <tt>/etc/rc.d</tt> initscripts in the