Merge lp:~rodsmith/maas-cert-server/remove-redundant-documentation into lp:~hardware-certification/maas-cert-server/trunk

[Rod Smith]

Replaced documentation with a dependency on the certification-docs package. Made related changes in maniacs-setup and elsewhere.

[Jeff Lane  (bladernr)]

Wheee, here it goes

review: Approve

=== modified file 'debian/changelog'
--- debian/changelog	2015-11-10 20:19:05 +0000
+++ debian/changelog	2015-11-12 21:04:52 +0000
@@ -1,3 +1,10 @@
+maas-cert-server (0.2.11-0ppa1) trusty; urgency=medium
+
+  * Replace documentation with dependency on certification-docs
+    package; make related changes to maniacs-setup and other files.
+
+ -- Rod Smith <[e-mail]>  Thu, 12 Nov 2015 15:35:57 -0500
+
 maas-cert-server (0.2.10-0ppa1) trusty; urgency=medium
 
   * Give maniacs-setup the ability to detect what Ubuntu point-release

=== modified file 'debian/control'
--- debian/control	2015-07-30 23:08:57 +0000
+++ debian/control	2015-11-12 21:04:52 +0000
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Rod Smith <[e-mail]>
-Build-Depends: debhelper (>= 9.0.0), rst2pdf, ttf-ubuntu-font-family, python-pil
+Build-Depends: debhelper (>= 9.0.0), python-pil
 Standards-Version: 3.9.5
 Homepage: https://launchpad.net/maas-cert-server
 #Vcs-Bzr: lp:maas-cert-server
@@ -10,7 +10,7 @@
 
 Package: maas-cert-server
 Architecture: all
-Depends: ${misc:Depends}, python3, maas (>= 1.7), amtterm, iperf, apt-mirror, ipcalc
+Depends: ${misc:Depends}, python3, maas (>= 1.7), amtterm, iperf, apt-mirror, ipcalc, certification-docs
 Description: Ubuntu certification support files for MAAS server
  Support files used on a MAAS server configured for use in Ubuntu server
  certification tasks.

=== modified file 'debian/debinstall'
--- debian/debinstall	2015-07-17 19:42:06 +0000
+++ debian/debinstall	2015-11-12 21:04:52 +0000
@@ -9,7 +9,6 @@
 rm -rf $BUILD_ROOT
 
 mkdir -p "$BUILD_ROOT/usr/sbin"
-mkdir -p "$BUILD_ROOT/usr/share/doc/maas-cert-server"
 mkdir -p "$BUILD_ROOT/usr/share/man/man8"
 mkdir -p "$BUILD_ROOT/usr/share/maas-cert-server"
 mkdir -p "$BUILD_ROOT/usr/share/maas-cert-server/etc/apt"
@@ -24,12 +23,3 @@
 cp -a etc/maas-cert-server/config "$BUILD_ROOT/etc/maas-cert-server/"
 cp -a usr/share/man/man8/maniacs-setup.8 "$BUILD_ROOT/usr/share/man/man8/"
 gzip -9 "$BUILD_ROOT/usr/share/man/man8/maniacs-setup.8"
-
-make -C documentation
-cp -a "documentation/MAAS_Advanced_NUC_Installation_And_Configuration.pdf" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"
-cp -a "documentation/MAAS_Advanced_NUC_Installation_And_Configuration.html" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"
-cp -a "documentation/MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.pdf" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"
-cp -a "documentation/MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.html" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"
-cp -a "documentation/Self-Test_Guide.pdf" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"
-cp -a "documentation/Self-Test_Guide.html" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"
-cp -a "documentation/images" "$BUILD_ROOT/usr/share/doc/maas-cert-server/"

=== removed directory 'documentation'
=== removed file 'documentation/MAAS_Advanced_NUC_Installation_And_Configuration.rst'
--- documentation/MAAS_Advanced_NUC_Installation_And_Configuration.rst	2015-08-20 15:46:56 +0000
+++ documentation/MAAS_Advanced_NUC_Installation_And_Configuration.rst	1970-01-01 00:00:00 +0000
@@ -1,1132 +0,0 @@
-==================================================
- MAAS Advanced NUC Installation and Configuration
-==================================================
------------------------
- (The MANIAC Document)
------------------------
-
-.. include:: <isonum.txt>
-
-.. header:: |ubuntu_logo|
-
-.. |ubuntu_logo| image:: images/logo-ubuntu_su-white_orange-hex.png
-   :scale: 20%
-
-.. footer:: |canonical_logo|
-
-.. |canonical_logo| image:: images/logo-canonical_no-tm-white-hex.png
-   :scale: 10%
-
-.. raw:: pdf
-
-   PageBreak oneColumn
-
-.. contents::
-
-.. raw:: pdf
-
-   PageBreak
-
-Purpose
-=======
-
-This document describes how to install MAAS on a portable computer (such as
-an Intel NUC or laptop) so that you can deploy systems in a test
-environment as well as install the certification tools and perform
-certification testing. Consult the Ubuntu Certified Hardware Self-Testing
-Guide (available from https://certification.canonical.com) for detailed
-information on running the certification tests themselves.
-
-Note that this document is based on using the Ubuntu Desktop image for
-ease of use, and thus some bits, the Network Manager bits especially,
-may not apply if you're using Server without a desktop.
-
-A device (referred to generically as a "portable computer") configured
-as described here is not intended for general Internet use. Some
-settings relax security in the interest of ease of use, so you should
-limit use of the portable computer on the Internet at large.
-
-This document begins with information on the required hardware and then
-moves on to details about Ubuntu's network configuration and then the
-procedures for installing MAAS. (This document assumes that you know how
-to install Ubuntu.) Because the purpose of this document is to help you
-bring up a MAAS server for certification purposes, it then describes how
-to install additional software and configure MAAS to automatically
-install the certification packages on the system under test (SUT).
-
-Figure 1 illustrates the overall configuration that this document will
-help you create. This document describes configuration of the Portable
-Computer device in the figure. It presupposes the existence of a local
-LAN that the portable computer can use for external connections, as well
-as the availability of at least one SUT for testing at the end of the
-process. (Note that the Internet connection is required for initial
-setup, but a properly-configured MAAS server does not need this
-connection to bring up SUTs.) Once configured, you will be able to move
-the portable computer from one site to another, repopulating the MAAS
-LAN at each site.
-
-.. figure:: images/maniac-network.png
-   :alt: This document describes configuring a server that manages its own
-         subnet and connects to a wider network on another interface.
-   :width: 100%
-
-   Figure 1: Network structure in which the portable computer will reside
-
-Hardware Required
-=================
-
-Before beginning, you should ensure that you have the following
-hardware:
-
-*  Portable computer
-
-   -  Ensure that the portable computer has two network interfaces. A
-      laptop with both Ethernet and wi-fi should suffice; or you can use a
-      USB network dongle to provide a second interface, particularly for a
-      NUC.
-
-   -  Because testing sessions can last for hours, ensure that you have a
-      power brick; you should *not* run on battery power!
-
-   -  You can install on a virtual machine in a more general-purpose
-      computer, but you'll have to pay careful attention to the network and
-      disk settings.
-
-*  System Under Test (SUT) that supports one of the power types MAAS
-   supports:
-
-   -  IPMI
-   -  AMT
-   -  WOL
-   -  Sentry PDU
-   -  SeaMicro 15000
-   -  HP Moonshot
-   -  Cisco UCS manager
-
-*  Small gigabit switch (8 ports should be enough)
-
-   -  For laptop with Wi-Fi: one Ethernet cable
-
-   -  For NUC or laptop with dongle: two Ethernet cables
-
-   -  For each SUT: one Ethernet cable for each NIC port including the BMC
-
-*  Monitor and keyboard for SUT (helpful, but not strictly required)
-
-*  Monitor, keyboard, and mouse for the MAAS system (a laptop's built-in
-   devices should be sufficient)
-
-*  Video cable for NUC (HDMI, Mini DisplayPort, or a converter like a
-   MiniDP to VGA)
-
-*  At least 1TB of disk space with which to mirror the Ubuntu archives,
-   if desired. (An external USB3 hard disk may be used for this, if
-   necessary.)
-
-Note that these hardware requirements are geared toward a typical
-testing environment. You may need to expand this list in some cases. For
-instance, if you test multiple servers simultaneously, you may need
-additional Ethernet ports.
-
-Installing and Configuring Ubuntu
-=================================
-
-Once you've assembled the basic hardware for your portable system, you can
-begin preparing it. The initial steps involve installing Ubuntu and setting
-up its most basic network settings:
-
-#. Install Ubuntu 14.04 (Trusty Tahr) to the portable system
-
-   -  The Desktop version of Ubuntu is recommended because it allows you to
-      easily access the MAAS Dashboard locally without needing a third
-      system.
-
-   -  If you choose to use the Server version, you will probably want to
-      install the desktop on top of that as it simplifies MAAS access.
-
-   -  This guide assumes the use of Ubuntu 14.04. Although another version
-      may work, some details will differ.
-
-2. Boot the portable computer and log in.
-
-3. Configure your portable computer's ``eth0`` as the *internal* port. This
-   guide assumes a static IP address of 192.168.0.2/16 on this port.
-
-   -  If possible, configure the computer's built-in Ethernet port, rather
-      than a plug-in dongle, as ``eth0``. (You can edit
-      ``/etc/udev/rules.d/70-persistent-net.rules`` to adjust network port
-      identifiers.)
-
-   -  You can either edit ``/etc/network/interfaces`` or use the GUI Network
-      tool in the System Settings panel to configure ``eth0``. An example
-      ``/etc/network/interfaces`` configuration resembles the following::
-
-         auto eth0
-         iface eth0 inet static
-             address 192.168.0.2
-             broadcast 192.168.255.255
-             netmask 255.255.0.0
-             dns-nameservers 192.168.0.2
-             dns-search example.org
-
-      The final two lines are necessary if you want to use the names that
-      MAAS assigns to the SUTs on the command line (for instance, when
-      using ``ssh`` to log in to them). You must adjust the values for your
-      network, of course.
-
-   -  If necessary or desired, you may use a different IP address on the
-      *internal* port.
-
-   -  Do not specify a gateway for the private internal LAN; doing so will
-      create confusion when trying to access the Internet via the external
-      port.
-
-   -  If you have issues installing packages, check ``route -n`` and make
-      sure you don't have a gateway route to the private LAN.
-
-   -  Once you've finished configuring this network port, be sure to
-      activate it. If you configured it by editing
-      ``/etc/network/interfaces``, type ``sudo ifup eth0`` to activate it.
-      (Depending on your starting configuration, you might need to type
-      ``sudo ifdown eth0`` or bring it down via your GUI tools before
-      bringing it up with its changed configuration.)
-
-4. Configure your *external* network port:
-
-   -  On a laptop, you can use the Wi-Fi (usually ``wlan0``) port as the
-      external port.
-
-   -  In theory, you can configure the external network either via
-      ``/etc/network/interfaces`` or by using the Desktop's Network Manager
-      tool. In practice, the latter sometimes causes problems with name
-      resolution, so if at all possible, you should use
-      ``/etc/network/interfaces`` for this task.
-
-   -  On a NUC or laptop with an Ethernet dongle, set ``eth1`` as the external
-      port.
-
-   -  *This ordering is important,* as you want to make sure that
-      ``resolvconf`` processes the DNS services of the internal network
-      (``eth0``) before the external one (``eth1`` or ``wlan0``). This
-      shows itself in ``/etc/resolv.conf``. ``resolvconf``'s order of
-      processing is in ``/etc/resolvconf/interface-order``.
-
-   -  In most cases, no explicit configuration of the external port is
-      necessary because the Ubuntu Desktop system will have set it up to
-      use DHCP, which is appropriate. You can adjust it if necessary,
-      though.
-
-.. _`Installing and Configuring MAAS`:
-
-Installing and Configuring MAAS
-===============================
-
-Installing MAAS on the computer is quite straightforward; you simply use
-APT. Configuring MAAS, though, takes more effort, because you must
-customize it for your environment. You must also download Ubuntu images
-that MAAS will ultimately deliver to your SUTs. For the network to function
-as desired, you must also set up NAT on your MAAS server. In many cases,
-you may need to mirror the Ubuntu archives, which is a time-consuming
-process. If you do this, you must also tweak you Apache configuration
-appropriately.  The following procedure is therefore rather lengthy.
-
-Installing MAAS
----------------
-
-Configuring MAAS is described in generic terms at
-`http://maas.ubuntu.com/docs/install.html <http://maas.ubuntu.com/docs/install.html>`_.
-The more specific procedure for using MAAS in certification testing is:
-
-#. Install the MAAS stable PPA
-   (`https://launchpad.net/~maas/+archive/ubuntu/stable <https://launchpad.net/~maas/+archive/ubuntu/stable>`_)::
-
-      $ sudo add-apt-repository ppa:maas/stable
-
-   Currently (late June, 2015), Ubuntu 14.04 installs MAAS 1.7 by default.
-   This PPA holds version 1.8 of MAAS, which is the recommended version for
-   certification testing, although MAAS 1.7 is also acceptable. This
-   document describes MAAS 1.8, so if you skip this step, some details will
-   differ.
-
-#. Several scripts and configuration files, some of which are quite
-   lengthy, are available in the ``maas-cert-server`` package in the
-   hardware certification PPA. You can install the scripts and configuration files
-   as follows::
-
-      $ sudo apt-add-repository ppa:hardware-certification/public
-      $ sudo apt-get update
-      $ sudo apt-get install maas-cert-server
-
-   As of version 0.1.2, the ``maas-cert-server`` package includes a
-   dependency on MAAS, so installing ``maas-cert-server`` will also install
-   MAAS, as well as all of MAAS's dependencies.
-
-   Most of the ``maas-cert-server`` files will be installed in
-   subdirectories of  ``/usr/share/maas-cert-server``, although a few
-   appear outside of that directory tree. (Subsequent steps describe how to
-   use these files.)
-
-#. Verify that you've installed MAAS 1.8 from the PPA, rather than MAAS
-   1.5 or some other version::
-
-      $ dpkg -p maas | grep Version
-
-   If the wrong version is installed, fixing the problem (presumably a
-   misconfigured PPA) and upgrading may work. If you upgrade from an
-   earlier version of MAAS, be sure to select the option to upgrade all the
-   configuration files when the package manager asks about this.
-
-#. Reconfigure the region controller with the IP address of ``eth0``::
-
-      $ sudo dpkg-reconfigure maas-region-controller
-
-   Give it the static IP for ``eth0``, e.g. 192.168.0.2. Note that Apache
-   may complain that it "could not reliably determine the server's fully
-   qualified domain name." You can safely ignore this message, both here
-   and in the next step.
-
-#. Reconfigure the cluster controller with the URL for MAAS::
-
-      $ sudo dpkg-reconfigure maas-cluster-controller
-
-   Give it the URL (in the prompt) with the IP of ``eth0`` -- (e.g.
-   \http://192.168.0.2/MAAS).
-
-#. Create the MAAS superuser::
-
-      $ sudo maas-region-admin createsuperuser
-
-   You can use any name you like for the superuser. Your login name is
-   likely to be easy to remember.
-
-Configure SSH
--------------
-
-Installing ``maas-cert-server`` should also install the ``openssh-client``
-and ``openssh-server`` packages. You should make some configuration changes
-for these packages, though:
-
-#. Edit ``/etc/ssh/ssh_config``:
-
-   -  Uncomment the line reading ``StrictHostKeyChecking ask`` and change
-      ``ask`` to ``no``.
-
-   -  This change eliminates the issues with reinstalling a SUT multiple
-      times and having to deal with the ``Incorrect Host Key`` warning
-      messages. You'll still see the message if there's a conflicting key
-      in ``~/.ssh/known_hosts`` but SSH will ignore that.
-
-   -  This change is *very* insecure, but since this is a test machine and
-      not something meant to sit on the Internet or connect to much outside
-      via SSH, it's an acceptable compromise.
-
-   -  If you want to completely eliminate the issue, add this to the
-      ``ssh_config`` file::
-
-         UserKnownHostsFile /dev/null/
-
-      Note that this is *very very* insecure
-
-#. Create an SSH key for MAAS::
-
-      $ ssh-keygen
-
-   Leave the filename as-is for the ID file or change it. If you change the
-   filename (say, to ``maas.id_rsa``), you can have both non-MAAS and
-   MAAS-only keys.
-
-Setting Up NAT and Routing
---------------------------
-
-The Ubuntu configuration at this point is a good start, but it won't
-provide your SUTs with access to the Internet. To correct this problem, you
-can use the ``startnat.sh`` script, which is installed as part of the
-``maas-cert-server`` package, in the ``/usr/sbin`` directory.
-
-As the name implies, ``startnat.sh`` will start NAT on the portable
-computer, which will enable the SUTs to access the Internet. (This is
-required for submitting certification results directly from the SUTs and is
-also necessary to fully install and upgrade the SUTs *if* the portable
-computer lacks a full Ubuntu archive mirror.)
-
-Note that this script reads ``/etc/maas-cert-server/config`` to determine
-which network ports connect to the internal and external networks. By
-default, ``eth0`` is assumed to be the *internal* port and ``eth1`` the
-*external* port. If these are not the correct assignments, edit
-``/etc/maas-cert-server/config`` appropriately.
-
-You can launch ``startnat.sh`` automatically when you boot by adding a
-reference to it to the ``/etc/rc.local`` startup script; or you can launch
-it manually on an as-needed basis. (If local security policies forbid use
-of NAT, you'll have to disable this script, use a local archive mirror, and
-bring server test suite results out via sneakernet.)
-
-If you need to disable NAT, the ``flushnat.sh`` script should do the job.
-
-On some networks, you may need to perform additional configuration
-steps. Keep this fact in mind when moving your portable computer between
-networks; you may need to reconfigure it to meet the needs of specific
-networks.
-
-Mirroring the Ubuntu Archives
------------------------------
-
-Mirroring the Ubuntu archives is *optional*. It is helpful as a means to
-reduce network traffic and speed up installations and updates,
-particularly at sites with slow Internet connections. It is required
-only if you must run certifications at sites that are completely
-disconnected from the Internet. If you want or need to create a local
-mirror for these purposes, follow these steps:
-
-#. Ensure that you have sufficient disk space (a little over 50GB per
-   version and architecture of Ubuntu to be supported -- 1TB total
-   should be plenty) available at ``/srv`` on the portable MAAS server. You
-   can do this in various ways:
-
-   -  Use an internal hard disk that's big enough to hold all the files you
-      need.
-
-   -  Prepare a USB3 hard disk with ext4fs and add a line to ``/etc/fstab`` so
-      that it will mount to ``/srv``.
-
-2. Install the ``apt-mirror`` package::
-
-   $ sudo apt-get install apt-mirror
-
-3. Copy the ``/var/spool/apt-mirror`` directory tree to ``/srv``::
-
-   $ sudo cp -a /var/spool/apt-mirror/* /srv
-
-4. Edit the ``/etc/apt/mirror.list`` file to include a convenient mirror
-   site and the PPAs used by the certification software
-   (``ppa:hardware-certification/public`` and
-   ``ppa:firmware-testing-team/ppa-fwts-stable``). Also be sure to set the
-   ``base_path`` option to ``/srv``.
-
-   - The ``maas-cert-server`` package includes a sample ``mirror.list``
-     file; it should be in the ``/usr/share/maas-cert-server/etc/apt/``
-     directory.
-
-   - This example file pulls down source, AMD64, and i386 architectures
-     for both 12.04 (Precise) and 14.04 (Trusty). The total disk space
-     (and network bandwidth consumed) is on the order of 300GiB.
-
-   - For comparison, HD video consumes 1-8GiB per hour -- usually on the
-     low end of that range for video streaming services. As should be
-     clear, the result will be significant network demand that will
-     *degrade a typical residential DSL or cable connection for hours,*
-     and possibly exceed your monthly bandwidth allocation.
-
-   - You may want to adjust your file to support additional versions, if
-     you have sufficient disk space and network bandwidth. If you're
-     running on a residential network connection, you can mirror just one
-     architecture and one Ubuntu version to reduce bandwidth consumption.
-
-   - You can adjust the source site from ``archive.ubuntu.com`` to a
-     closer site to speed up the mirror process. If you do so, you may
-     need to adjust some of the paths later in this document.
-
-5. Copy the ``postmirror.sh`` script from ``/usr/share/maas-cert-server/`` to
-   ``/srv/var/``. Edit the local path and URL as necessary for your
-   installation and the archive site from which you're mirroring your
-   system.
-
-6. Mirror the archives::
-
-      $ sudo apt-mirror
-
-   Note that this process is likely to take several hours, depending on the
-   quality of your network connection.
-
-In addition to mirroring the main Ubuntu archives, you may
-*optionally* mirror the MAAS archives. Ordinarily, you download these
-files just once for the architectures you need on the MAAS server, but
-having a backup may be useful in case you need to install an unexpected
-architecture or restore files should they be damaged. Mirroring these
-files requires using a different tool from ``apt-mirror``:
-
-#. Install the ``simplestreams`` and ``ubuntu-cloud-keyring packages``::
-
-   $ sudo apt-get install simplestreams ubuntu-cloudimage-keyring
-
-2. Change to the ``/srv/mirror`` directory.
-
-3. Mirror the site with the following command::
-
-      $ sudo sstream-mirror --keyring \\
-        usr/share/keyrings/ubuntu-cloudimage-keyring.gpg --max=1 \\
-        http://maas.ubuntu.com/images/ephemeral/releases/ \\
-        -v maas.ubuntu.com
-
-   -  You can test this process without actually downloading files by
-      specifying ``\-\-no-item-download`` among the options.
-
-   -  Note that the ``simplestreams`` package is not part of Ubuntu 12.04.
-
-If you are planning to operate in locations with bad or no outside
-network access, you will also need to obtain and bring a copy of a
-bootable Ubuntu Cloud Image for the virtualization portion of the
-certification test. You can obtain that here:
-
-`http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-i386-disk1.img <http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-i386-disk1.img>`_
-
-You can use another release of Ubuntu if this is convenient. An i386 image
-is used even when you're testing 64-bit hardware. You can place this file
-on the ``/srv`` volume and copy it to the SUTs before running the server
-test suite.
-
-Configuring Apache
-------------------
-
-Apache is used both for accessing the MAAS web UI and for delivering
-archive mirrors, if you've created them. It should have already been
-installed as a dependency of MAAS. If you've mirrored an Ubuntu archive
-site, you must create symbolic links of the mirror archives to the default
-Apache directory:
-
-#. Create symbolic links for the main Ubuntu mirror, for the PPA
-   mirrors, and for the MAAS mirror::
-
-      $ sudo ln -s /srv/mirror/archive.ubuntu.com/ubuntu /var/www/html/ubuntu
-      $ sudo ln -s /srv/mirror/ppa.launchpad.net/\* /var/www/html/
-      $ sudo ln -s /srv/mirror/maas.ubuntu.com /var/www/html/
-
-   Note that if you altered ``/etc/apt/mirror.list`` to mirror from a
-   regional repository (such as ``us.archive.ubuntu.com``) rather than from
-   the main Ubuntu repository (``archive.ubuntu.com``), you must adjust the
-   first command appropriately.
-
-2. Ensure that the mirrors are readable by Apache users::
-
-      $ sudo chown -R www-data:www-data /srv/mirror/\*
-
-Of course, you should keep your mirrors up-to-date. You can do this
-manually or by creating a ``cron`` job. In fact, the ``apt-mirror`` package
-installs a suitable ``cron`` file, ``/etc/cron.d/apt-mirror``. Remove the
-leading hash (``#``) from the following line in that file to activate it::
-
-   #0 4 \* \* \* apt-mirror /usr/bin/apt-mirror > /var/spool/apt-mirror/var/cron.log
-
-Once activated, this job will run every day at 4:00 AM, provided the
-computer is powered on at that time. If that won't be the case, you can
-run it manually by typing ``sudo apt-mirror`` whenever is convenient. Runs
-after the initial one should take much less time and bandwidth than the
-original one.
-
-Similarly, you can re-run the ``sstream-mirror`` command (from the
-``/srv/mirror`` directory) to update the MAAS files. As with
-``apt-mirror``, you can do this manually or create a ``cron`` job.
-
-You can save a little time and network bandwidth in the following steps by
-configuring your portable computer to use the archives you've just
-downloaded. To do so, edit ``/etc/apt/sources.list`` and edit the lines
-that are equivalent to those you entered in ``/etc/apt/mirror.list`` to
-refer to ``localhost`` rather than ``archive.ubuntu.com`` (or whatever
-mirror site your computer is set up to use by default). For instance, your
-original file might include a line like the following::
-
-   deb http://archive.ubuntu.com/ubuntu precise main restricted universe multiverse
-
-You would change that to read::
-
-   deb http://localhost/ubuntu precise main restricted universe multiverse
-
-Be sure to change all the references to the standard archives that
-you've mirrored. To test these changes, type::
-
-   $ sudo apt-get update
-   $ sudo apt-get dist-upgrade
-
-You should see normal output for these commands, although chances are
-the ``dist-upgrade`` command will report no need to update any files.
-
-Configuring the MAAS Web UI
----------------------------
-
-With MAAS installed and (if desired) the Ubuntu archives mirrored, you can
-proceed with further MAAS configuration via its web-based user interface.
-To do so, follow these steps:
-
-#. Verify you can access the MAAS Dashboard:
-
-   -  Launch a browser and point it to \http://192.168.0.2/MAAS (your
-      internal port).
-
-   -  You should also be able to access this by default on the
-      external port, too.
-
-   -  If you provide the computer with a hostname in DNS or ``/etc/hosts``,
-      you should be able to access it via that name, as well.
-
-   -  You should see a login prompt.
-
-#. Log in to the Dashboard using the username and password you added
-   above for the superuser.
-
-#. Click on the down arrow next to the user name in the top right
-   corner. A drop-down menu will appear, as shown here:
-
-   .. image:: images/maas-dropdown.png
-      :width: 100%
-
-#. Select Account (Preferences in MAAS 1.7) in this drop-down menu. A user
-   preferences screen will appear.
-
-#. Add your SSH key
-
-   -  Click on "+ Add SSH key"
-
-   -  Copy and paste the entire contents of your ``~/.ssh/id_rsa.pub`` (or
-      MAAS-specific public key) in the "Public key" box
-
-   -  click on "+ Add key"
-
-   -  You may optionally add more keys in the same way.
-
-#. Click Images near the top of the MAAS web page. This will bring you
-   to a page in which you can select the architectures and Ubuntu
-   versions to support. For certification, you should import a minimum
-   of Ubuntu 14.04 LTS for AMD64; however, you may want to add 12.04
-   LTS and i386 or other CPU types, depending on your anticipated
-   needs. (Note that custom point-release images are imported later, but
-   you must import at least one image for each CPU architecture hereJ.)
-
-#. In the Images page, select the images you want MAAS to support and
-   then click Import Images. A spinner will appear as the download
-   progresses. This process can take minutes to hours depending on your
-   Internet connection. MAAS needs to download PXE images for all
-   supported releases as well as ephemeral images for commissioning and
-   deployment.
-
-#. Check the Clusters page to verify the status of your image downloads. A
-   successful image import will show Synced under Images.
-
-#. Edit the ``/etc/maas/templates/dhcp/dhcpd.conf.template`` file. You can
-   customize your DHCP options here. Most defaults are fine for most
-   installations, but you might want to add entries for servers that are
-   not MAAS nodes and should have fixed IP addresses or customize certain
-   options. (Many values can be set via the MAAS web UI, as described
-   shortly.) A pair of options you may want to adjust are the default and
-   maximum lease times, which both default to 30 seconds. Such low settings
-   can create excessive DHCP traffic, so increasing them is advisable. A
-   value of 3600 (1 hour) works well for certification testing purposes.
-
-#. Click the Clusters link near the top of the web page so you can set
-   the DHCP options:
-
-   #.  Click the cluster name for the cluster controller (Cluster Master in
-       this example):
-
-       .. image:: images/clusters-page.png
-          :width: 98%
-
-   #.  Mouse over the *internal* (normally ``eth0``) network
-       interface. (If you don't see your internal interface listed, click
-       the "Add Interface" button to add it.) You should see a pair of
-       icons appear, one to edit the interface and one to delete it. Click
-       the former, then change the following items:
-
-       - Interface = ``eth0`` (or your *internal* port)
-
-       - Management = *DHCP and DNS*
-
-       - IP (required) = the IP address of the *internal* port
-
-       - Subnet mask = appropriate mask (such as 255.255.0.0)
-
-       - Broadcast IP = network IP (such as 192.168.255.255)
-
-       - Router IP = IP of ``eth0`` (the *internal* port, such as
-         192.168.0.2)
-
-       - DHCP dynamic IP range low value = Start of the DHCP IP address
-         range used for enlistment, commissioning, and unknown devices
-         (such as 192.168.0.50)
-
-       - DHCP dynamic IP range high value = end of the DHCP dynamic IP
-         address range (such as 192.168.0.99)
-
-       - Static IP range low value = Start of the static IP address range
-         used for servers (SUTs) managed by MAAS (such as 192.168.0.100)
-
-       - Static IP range high value = end of the static IP address range
-         (such as 192.168.0.200)
-
-       - Click Save Interface
-
-#. If desired, change the DNS zone name field on the "Edit Cluster
-   Controller" page to some convenient value, such as ``example.org``. If
-   you set a search domain in ``/etc/network/interfaces``, using that value
-   is desirable. Click "Save Cluster Controller" when you're finished.
-
-#. Click Settings near the top of the page to load the MAAS Settings page,
-   where you set several miscellaneous MAAS details:
-
-   -  Click the associated "save" button for *each* of the following
-      sections you change. Unfortunately, each save button is
-      section-specific and won't save changes made in other sections of
-      that page.
-
-   -  There should be at least one MAAS Admin listed in Users and
-      Keys.
-
-   -  Scroll down to Commissioning and verify that the "Default Ubuntu
-      release used for commissioning" is set to what you need. This will
-      normally be Ubuntu 14.04 LTS "Trusty Tahr." (If MAAS claims there is
-      no usable release, you will need to wait for the ephemeral image
-      downloading step to complete and then refresh the page to see the
-      options.)
-
-   -  Set the options under "Deploy" to suitable values.
-
-      - For Trusty certification, you should set the options to Ubuntu 14.04
-        LTS "Trusty Tahr."
-
-      - If you must also certify 12.04, you can override this option on a
-        boot-by-boot basis. Set the default for whichever version you use
-        most frequently.
-
-   -  If you're using a local APT mirror or if you want to change the
-      mirror used by your SUTs from the default, change the URLs for Main
-      archive and Ports archive to the correct URLs for your
-      environment. If you mirrored your archives as described earlier, you
-      can adjust these values to obviate the need for Internet access by
-      the SUTs:
-
-      - The Main Archive should refer to \http://192.168.0.2/ubuntu.
-
-      - The Ports Archive can remain unchanged from the default.
-
-      - Adjust 192.168.0.2 as appropriate for your network settings; the
-	reference should be to your portable computer's *internal* network
-	address.
-
-   -  Under *Network Configuration*, you may want to make some changes,
-      such as an HTTP proxy, an upstream DNS server, and an NTP server.
-      These settings help you deal with strict local firewalls. These
-      settings are most likely to be necessary if you did not mirror the
-      Ubuntu archives.
-
-   -  Under *Third Party Drivers Configuration*, ensure that *Enable the
-      installation of proprietary drivers (i.e. HPVSA)* is checked.
-
-Testing the MAAS Server
-=======================
-
-At this point, your MAAS server should be set up and configured
-correctly. If you continued preparing MAAS as your images downloaded,
-though, wait until that process has finished before proceeding. To test
-it, follow these steps:
-
-#. Prepare a computer by configuring it to boot via PXE. This computer
-   need not be a computer you plan to certify; anything that can
-   PXE-boot should work, although to fully test the MAAS server, the
-   test system should provide IPMI or some other power-control tool that
-   MAAS supports.
-
-#. Connect the test computer to the portable computer's *internal* network
-   and power it on.
-
-   - The test computer should PXE-boot from the portable MAAS computer.
-
-   - This first boot should be to the enlistment image, which provides
-     some very basic information to the MAAS server. Once the node powers
-     itself off you should see it listed in the MAAS nodes list
-     (\http://localhost/MAAS/#/nodes/ or, on MAAS 1.7,
-     \http://localhost/MAAS/nodes/) with a Status field of "New."
-
-   - Note that you will have to refresh the nodes list as it does not
-     refresh itself to list new data.
-
-#. Click on the node's hostname to view the node's summary page.
-
-#. If desired, click the node's hostname near the upper-left corner of the
-   page. This will enable you to change the hostname to something
-   descriptive, such as the computer's model number. Click "Save" when
-   you've made your changes.
-
-#. If necessary, click "Edit" in the Machine Summary section to change the
-   architecture of the machine. Click "Save Changes" when you're done.
-
-#. If necessary, change the Power Type in the Power section of the page.
-   This may necessitate setting an IP address, MAC address, password, or
-   other information, depending on the power control technology in use.
-   Click "Save Changes" when you're done.
-
-#. Click "Take Action" near the top-right corner of the page, followed by
-   "Commission Node" from the resulting drop-down menu. You must then click
-   "Go."
-
-   - The node should power on again. This time you'll see it PXE-boot the
-     commissioning image. Note that if your test system lacks a BMC or
-     other means to remotely control its power, you must manually power it
-     on.
-
-   - The node should do a bit more work this time before powering off
-     again.
-
-   - Once it's done, the UI will show a Status of "Ready."
-
-#. Once the system powers off after commissioning, click "Take Action"
-   followed by "Deploy." You must then click "Go" to confirm this action.
-
-   - The node should power on again (or you will have to control it
-     manually if it lacks a BMC). This time it will take longer to finish
-     working, as MAAS will install Ubuntu on the system.
-
-   - Once it's done, the computer will reboot into its installed image.
-
-   - You could install and run certification software on the test system
-     at this point. The next section, `Installing Certification Packages
-     Automatically via MAAS`_, describes additional changes to MAAS to
-     simplify this task.
-
-If any of these steps fail, you may have run into a MAAS bug; your test
-computer may have a buggy PXE, IPMI, or other subsystem; or you may have
-misconfigured something in the MAAS setup. You may want to review the
-preceding sections to verify that you configured everything correctly.
-To help in debugging problems, the node status page includes a section
-entitled Latest Node Events with a summary of the last few events
-related to the node. (You must refresh the page to see new events.)
-
-Note that there are two methods of installing nodes:
-
--  **Standard** -- aka Debian or d-i, this installation method installs
-   Ubuntu using the same installation program used by an Ubuntu ISO file
-   that you might download from the Internet.
-
--  **Fastpath** -- aka curtin, this installation method places a pre-built
-   Ubuntu image onto the node's hard disk.
-
-A fastpath install is, as the name implies, faster than a standard
-install. In MAAS 1.5, the standard install was the default, but in MAAS
-1.7, the default has changed to the fastpath method. The fastpath method
-is also preferred for certification testing because it permits the
-certification suite to detect and report the MAAS version, whereas the
-d-i method does not currently support this feature. The method to
-deliver fixed point releases, described next, uses the fastpath install
-procedures.
-
-Configuring MAAS to Deliver Fixed Point Releases
-================================================
-
-By default, MAAS delivers whatever version of Ubuntu was packaged by the
-MAAS team when you downloaded your MAAS installation images. This
-version is likely to correspond to the current point release, possibly
-plus some updates. For certification work, it's far better to install a
-fixed point release, such as 14.04 GA or 14.04.1. This can be
-accomplished with MAAS 1.7 by installing custom images:
-
-#. Download the custom images. They are currently hosted at
-   http://certification-static.canonical.com/fixed-point-releases/.
-   Retrieve whichever images you need and store them somewhere
-   convenient, such as your user's home directory on the portable
-   computer. Images are about 250-300MiB in size.
-
-#. Return to the terminal and login to the API using maas-cli::
-
-      $ maas login <PROFILE_NAME> <API_URL> <KEY>
-
-   -  ``<PROFILE_NAME>`` is anything you wish. This guide uses ``maas`` for
-      simplicity.
-
-   -  ``<API_URL>`` refers to a URL on the MAAS server, as in
-      \http://192.168.0.2/MAAS/api/1.0.
-
-   -  ``<KEY>`` is a key displayed in the Dashboard
-      (\http://localhost/MAAS/account/prefs/) in the MAAS Keys section or
-      can be obtained by typing ``sudo maas-region-admin apikey
-      \-\-username {user}`` in a shell (substitute your MAAS username for
-      ``{user}``).
-
-   -  You should get a message saying "You are now logged in to the MAAS
-      server at ``<URL>`` with the profile name ``'<PROFILE_NAME>'``"
-
-   -  If you've previously run the maas command using sudo, you may need to
-      either use sudo with this command or change the ownership of
-      ``~/.maascli.db``.
-
-3. Tell MAAS about each image you want to import::
-
-      $ maas maas boot-resources create name=custom_14041_amd64 \\
-        title="Ubuntu 14.04.1 (AMD64)" architecture=amd64/generic \\
-        content@=/home/ubuntu/ubuntu-14.04.1-server-amd64-curtin.tar.gz
-
-   -  Repeat this step once for each image.
-
-   -  Give each image a unique ``name``. The name *must not exceed 20
-      characters!*
-
-   -  Adjust the ``title`` to the value you want to see in the MAAS web UI.
-      Each image must have a unique ``title``.
-
-   -  Point ``content@=`` to the image you want to add.
-
-4. Check the MAAS boot images page (\http://localhost/MAAS/images/) to
-   see that the images have imported correctly. They should appear in
-   the Custom Images section. If an image has an active spinner next to
-   it, MAAS hasn't finished importing it. If the spinner becomes a
-   hollow pink circle, the import failed.
-
-5. You may optionally change the default OS to deploy on the MAAS
-   settings page (\http://localhost/MAAS/settings/) to point to one of
-   your custom images. Note that whenever you release a node, the OS
-   changes back to the default, so you may need to alter that setting
-   whenever you release and redeploy a node.
-
-Once the images have been imported, you can select them as you would any
-other OS version in the MAAS web UI. Instead of appearing as an OS Type
-of "Ubuntu," though, these images will appear with an OS Type of
-"Custom."
-
-Once the images have been imported, you can select them as you would any
-other OS version in the MAAS web UI:
-
-#. If a node is already running, select "Take Action" followed by "Release"
-   in its node summary page. Confirm this action by clicking "Go." It may
-   take a few seconds for MAAS to fully release the node.
-
-#. Select "Take Action" followed by "Deploy." An option to choose the
-   image you want to deploy should appear.
-
-#. Select the image. It will be a Custom image with the name you
-   specified when you loaded it, as shown here:
-
-   .. image:: images/custom-image-selection.png
-      :width: 100%
-
-#. Click "Go" to deploy the image. Your node should start up and install
-   the point-release image you selected.
-
-In MAAS 1.7.0 and earlier, it was possible to set the OS prior to acquiring
-a node, which enabled a streamlined process of setting the OS and then
-using the "Acquire and Start" button; but as of version 1.7.1, you must set
-the OS between acquiring and starting the node, as just described. If you
-want to switch the OS of an already-running node, you must first release
-it, then re-acquire it, set its OS, and finally start it. You can also set
-a fixed point release to be your default OS on the Settings page
-(\http://localhost/MAAS/settings/).
-
-Note that before you can install a custom image for any given architecture,
-you must have first imported at least one image for that architecture via
-the conventional means, as described earlier, in "Installing and
-Configuring MAAS."
-
-.. _`Installing Certification Packages Automatically via MAAS`:
-
-Installing Certification Packages Automatically via MAAS
-========================================================
-
-MAAS can automatically install the certification packages every time you
-"Start" a node. This is how to do it:
-
-#. On the MAAS server, enter the ``/etc/maas/preseeds`` subdirectory::
-
-   $ cd /etc/maas/preseeds
-
-2. Back up the ``generic`` file::
-
-   $ sudo cp generic generic-orig
-
-3. Copy the ``stable-preseed-generic`` file from
-   ``/usr/share/maas-cert-server/preseed/`` to
-   ``/etc/maas/preseeds/generic``::
-
-    $ sudo cp /usr/share/maas-cert-server/preseed/stable-preseed-generic \
-      ./generic
-
-   .. Note to self: Documentation on finer-grained naming is at
-      https://www.google.com/url?q=https%3A%2F%2Fmaas.ubuntu.com%2Fdocs%2Fdevelopment%2Fpreseeds.html&sa=D&sntz=1&usg=AFQjCNFARkFbhKDIyF6L8uyJvJUPqJ_6Ng
-      This is currently delicate and I suspect the documentation is faulty.
-      Not worth covering here, but maybe revisit in the future....
-
-   This action creates a configuration file that causes nodes to install
-   the certification suite after a standard/d-i install.
-
-4. Back up the original ``curtin_userdata`` and
-   ``curtin_userdata_custom`` files::
-
-   $ sudo cp curtin_userdata curtin_userdata-orig
-   $ sudo cp curtin_userdata_custom curtin_userdata_custom-orig
-
-5. Copy ``curtin_userdata`` from ``/usr/share/maas-cert-server/preseed/`` to
-   ``/etc/maas/preseeds``, as both ``cutin_userdata`` and as
-   ``curtin_userdata_custom``::
-
-      $ sudo cp /usr/share/maas-cert-server/preseed/curtin_userdata ./
-      $ sudo cp /usr/share/maas-cert-server/preseed/curtin_userdata \
-        ./curtin_userdata_custom
-
-   The modified ``curtin_userdata`` file causes nodes started via the
-   fastpath/curtin method to install the certification software. This file
-   affects nodes of all architectures. The ``curtin_userdata_custom`` file
-   does the same thing for the custom images used for testing with specific
-   point releases.
-
-6. The preseed files each include two or three lines that refer to the
-   ``ppa.launchpad.net`` repository. If you are relying on a mirrored
-   archive, change these references to your own local repository (at
-   192.168.0.2, or whatever IP address you're using). Note that if you
-   leave this file as-is, the SUT will attempt to access the Internet,
-   and so will require Internet access to fully provision itself.
-
-7. Using the MAAS web user interface, enlist and commission a new node.
-   Alternatively, you can click "Release Node" on the node you tested
-   earlier, then wait a few seconds and refresh the page.
-
-8. Go back to the Node View and deploy a node, as described earlier. Your
-   SUT should turn on, do an installation, and then install the
-   certification tools.
-
-9. You can observe the installation process by connecting a monitor to the
-   node and viewing the messages in real-time as they're being produced.
-
-10. Once the machine finishes installation and reboots, you can SSH into
-    its ``ubuntu`` account from the MAAS server and you should be able to
-    run the command::
-
-       $ canonical-certification-server
-
-    Note, however, that this works only on 14.04 (GA and point release)
-    versions. If you are certifying a 12.04 release, you must manually
-    install the certification suite.
-
-For more on the  certification process itself, see the Ubuntu Server
-Hardware Self-Testing Guide, which is available from
-https://certification.canonical.com.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix A: Performing a Partial Restore
-========================================
-
-If the MAAS server's support files (the PXE boot images and related
-files) become damaged, PXE-booting SUTs may fail. The SUT may fail to
-retrieve PXE boot images or the boot may fail with any number of
-symptoms later in the process. If you're unable to discover a cause and
-solution through less drastic means, one possible recovery procedure is
-to restore those files to a fresh state; however, be aware that this
-procedure will *destroy all existing node definitions.* Thus (and because
-the solution involves downloading new boot images, which can be
-time-consuming), you should attempt this solution only as a last resort.
-Steps 1 and 6 of the following procedure are the minimum required;
-steps 2-5 make for a more thorough cleansing of the system. The overall
-procedure is:
-
-#. Click the Clusters link in the MAAS server's web interface (to reach
-   the server's ``/MAAS/clusters/`` page).
-
-#. Click the small trash can icon that appear near the right side of the
-   page associated with your malfunctioning cluster when you mouse over it,
-   and then confirm the operation. This will delete the cluster
-   controller's definition.
-
-#. Delete the contents, including all subdirectories, of the
-   ``/var/lib/maas/boot-resources`` directory on the portable server.
-
-#. In a shell, reconfigure the ``maas-cluster-controller`` and
-   ``maas-region-controller`` packages::
-
-      $ sudo dpkg-reconfigure maas-cluster-controller
-      $ sudo dpkg-reconfigure maas-region-controller
-
-   You should not need to adjust the default values.
-
-5. Reset the cluster controller's DHCP and DNS options, as described in
-   step #10 under `Configuring the MAAS Web UI`_,
-   earlier.
-
-6. If necessary or desired, adjust the images you want to import, as
-   described in steps #6 and #7 under `Configuring the MAAS Web UI`_,
-   earlier.
-
-This procedure should restore your ability to PXE-boot your SUTs.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix B: Glossary
-====================
-
-The following definitions apply to terms used in this document.
-
-1Gbps
-  1 Gigabit - Network speed for Gigabit Ethernet (1000Mbps).
-
-10Gbps
-  10 Gigabit - Network speed for 10 Gigabit Ethernet (10,000Mbps).
-
-BMC
-  Baseboard Management Controller - A device in many server models
-  that allows remote in and out of band management of hardware.
-
-DHCP
-  Dynamic Host Control Protocol - method for providing IP addresses
-  to the SUT and Targets.
-
-Greylist test
-  A test that must be performed but will not affect the
-  granting of a certified status.
-
-KVM
-  Kernel Virtual Machine - A system for running virtual machines on
-  Ubuntu Server.
-
-IPMI
-  Intelligent Platform Management Interface - A technology for
-  remotely connecting to a system to perform management functions.
-
-LAN
-  Local Area Network - the network to which your SUT and Targets are
-  connected. The LAN does not need to be Internet accessible (though that
-  is preferable if possible).
-
-MAAS
-  Metal as a Service - a Canonical product for provisioning systems
-  quickly and easily.
-
-NIC
-  Network Interface Card - the network device(s).
-
-NUC
-  A small form-factor PC product from Intel.
-
-.. raw:: pdf
-
-   PageBreak
-
-PXE
-  Pre-boot Execution Environment - A technology that allows you to
-  boot a system using remote images for easy deployment or network-based
-  installation.
-
-RAID
-  Redundant Array of Independent Disks - multiple disk storage
-  providing redundancy, parity checking and data integrity.
-
-RAM
-  Random Access Memory - System Memory.
-
-SAN
-  Storage Area Network - Usually FibreChannel.
-
-SUT
-  System Under Test - The machine you are testing for certification.
-
-Target
-  A system or systems on the test LAN that the SUT can use for
-  network testing. The Target must be running an iperf server, but
-  otherwise does not need any special configuration. The MAAS server may
-  double as the Target.
-
-Test case
-  A test to be executed as part of the certification test
-  suite. Test cases include things such as "CPU Stress" and "CPU
-  Topology."
-
-Whitelist test
-  A test that MUST pass for the SUT to be granted a
-  certified status.

=== removed file 'documentation/MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.rst'
--- documentation/MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.rst	2015-11-10 20:19:05 +0000
+++ documentation/MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.rst	1970-01-01 00:00:00 +0000
@@ -1,870 +0,0 @@
-=============================================================
- MAAS Advanced NUC Installation and Configuration -- Scripted
-=============================================================
------------------------
- (The MANIACS Document)
------------------------
-
-.. include:: <isonum.txt>
-
-.. header:: |ubuntu_logo|
-
-.. |ubuntu_logo| image:: images/logo-ubuntu_su-white_orange-hex.png
-   :scale: 20%
-
-.. footer:: |canonical_logo|
-
-.. |canonical_logo| image:: images/logo-canonical_no-tm-white-hex.png
-   :scale: 10%
-
-.. raw:: pdf
-
-   PageBreak oneColumn
-
-.. contents::
-
-.. raw:: pdf
-
-   PageBreak
-
-Purpose
-=======
-
-This document describes how to install MAAS on a portable computer (such as
-an Intel NUC or laptop) so that you can deploy systems in a test
-environment as well as install the certification tools and perform
-certification testing. Consult the Ubuntu Certified Hardware Self-Testing
-Guide (available from https://certification.canonical.com) for detailed
-information on running the certification tests themselves.
-
-Note that this document is based on using the Ubuntu Desktop image for
-ease of use, and thus some bits, the Network Manager bits especially,
-may not apply if you're using Server without a desktop.
-
-A device (referred to generically as a "portable computer") configured
-as described here is not intended for general Internet use. Some
-settings relax security in the interest of ease of use, so you should
-limit use of the portable computer on the Internet at large.
-
-This document begins with information on the required hardware and then
-moves on to details about Ubuntu's network configuration and then the
-procedures for installing MAAS. (This document assumes that you know how
-to install Ubuntu.) Because the purpose of this document is to help you
-bring up a MAAS server for certification purposes, it then describes how
-to install additional software and configure MAAS to automatically
-install the certification packages on the system under test (SUT).
-
-Figure 1 illustrates the overall configuration that this document will
-help you create. This document describes configuration of the Portable
-Computer device in the figure. It presupposes the existence of a local
-LAN that the portable computer can use for external connections, as well
-as the availability of at least one SUT for testing at the end of the
-process. (Note that the Internet connection is required for initial
-setup, but a properly-configured MAAS server does not need this
-connection to bring up SUTs.) Once configured, you will be able to move
-the portable computer from one site to another, repopulating the MAAS
-LAN at each site.
-
-.. figure:: images/maniac-network.png
-   :alt: This document describes configuring a server that manages its own
-         subnet and connects to a wider network on another interface.
-   :width: 100%
-
-   Figure 1: Network structure in which the portable computer will reside
-
-Hardware Required
-=================
-
-Before beginning, you should ensure that you have the following
-hardware:
-
-*  Portable computer
-
-   -  Ensure that the portable computer has two network interfaces. A
-      laptop with both Ethernet and wi-fi should suffice; or you can use a
-      USB network dongle to provide a second interface, particularly for a
-      NUC.
-
-   -  Because testing sessions can last for hours, ensure that you have a
-      power brick; you should *not* run on battery power!
-
-   -  You can install on a virtual machine in a more general-purpose
-      computer, but you'll have to pay careful attention to the network and
-      disk settings.
-
-*  System Under Test (SUT) that supports one of the power types MAAS
-   supports:
-
-   - American Power Conversion (APC) PDU
-   - Cisco UCS Manager 
-   - Digital Loggers, Inc. PDU
-   - HP Moonshot - iLO Chassis Manager
-   - HP Moonshot - iLO (IPMI)
-   - IPMI
-   - Intel AMT
-   - Microsoft OCS - Chassis Manager
-   - SeaMicro 15000
-   - Sentry Switch CDU
-   - VMWare
-   - Virsh (virtual systems)
-
-*  Small gigabit switch (8 ports should be enough)
-
-   -  For laptop with Wi-Fi: one Ethernet cable
-
-   -  For NUC or laptop with dongle: two Ethernet cables
-
-   -  For each SUT: one Ethernet cable for each NIC port including the BMC
-
-*  Monitor and keyboard for SUT (helpful, but not strictly required)
-
-*  Monitor, keyboard, and mouse for the MAAS system (a laptop's built-in
-   devices should be sufficient)
-
-*  Video cable for NUC (HDMI, Mini DisplayPort, or a converter like a
-   MiniDP to VGA)
-
-*  At least 1TB of disk space with which to mirror the Ubuntu archives,
-   if desired (an external USB3 hard disk may be used for this, if
-   necessary)
-
-Note that these hardware requirements are geared toward a typical
-testing environment. You may need to expand this list in some cases. For
-instance, if you test multiple servers simultaneously, you may need
-additional Ethernet ports.
-
-Installing and Configuring Ubuntu
-=================================
-
-Once you've assembled the basic hardware for your portable system, you can
-begin preparing it. The initial steps involve installing Ubuntu and setting
-up its most basic network settings:
-
-1. Install Ubuntu 14.04 (Trusty Tahr) to the portable system
-
-   -  The Desktop version of Ubuntu is recommended because it enables you
-      to easily access the MAAS Dashboard locally without needing a third
-      system.
-
-   -  If you choose to use the Server version, you will probably want to
-      install the desktop on top of that as it simplifies MAAS access.
-
-   -  This guide assumes the use of Ubuntu 14.04. Although another version
-      may work, some details will differ.
-
-#. Boot the portable computer and log in.
-
-#. Configure your *external* network port:
-
-   -  On a laptop, you can use the Wi-Fi (usually ``wlan0``) port as the
-      external port.
-
-   -  If you need to use both a built-in Ethernet port and an Ethernet
-      dongle, it's best to use the latter as your external port.
-
-   -  In most cases, no explicit configuration of the external port is
-      necessary because the Ubuntu Desktop system will have set it up to
-      use DHCP, which is appropriate. You can adjust it if necessary,
-      though.
-
-   -  In theory, you can configure the external network either via
-      ``/etc/network/interfaces`` or by using the Desktop's Network Manager
-      tool.
-
-#. Configure your portable computer's *internal* port. This guide assumes
-   use of ``eth0`` and a static IP address of 172.16.0.1/22 on this port.
-
-   -  If possible, configure the computer's built-in Ethernet port, rather
-      than a plug-in dongle, as the internal port.
-
-   -  You can either edit ``/etc/network/interfaces`` or use the GUI
-      Network tool in the System Settings panel to configure the internal
-      port. An example ``/etc/network/interfaces`` configuration resembles
-      the following::
-
-         auto eth0
-         iface eth0 inet static
-             address 172.16.0.1
-             broadcast 172.16.3.255
-             netmask 255.255.252.0
-
-   -  If necessary or desired, you may use a different IP address on the
-      *internal* port. If your portable computer will move from one
-      *external* network to another, be sure to consider all its likely
-      *external* addresses when deciding on its *internal* address and
-      netmask.
-
-   -  Do not specify a gateway for the private internal LAN; doing so will
-      create confusion when trying to access the Internet via the external
-      port.
-
-   -  If you have issues installing packages, check ``route -n`` and make
-      sure you don't have a gateway route to the private LAN.
-
-   -  Using a /22 or wider network is advisable for the internal network.
-      When so configured, the setup script will use the final two of the
-      four resulting octet ranges (for instance, 172.16.2.x and 172.16.3.x
-      from 172.16.0.0/22) for DHCP addresses, leaving the first two ranges
-      (for instance, 172.16.0.x and 172.16.1.x) for static addresses -- for
-      instance, for the MAAS server itself, as well as anything else you
-      want to assign a static IP address (perhaps your BMCs).
-
-   -  If you use a /22 or wider network, the MAAS server's address can be
-      anything within the first two ranges (for instance, 172.16.0.x or
-      172.16.1.x), which are not handled by the computer's own DHCP server.
-      If you use a /23 or /24 network, the MAAS server must be within the
-      first nine addresses of that range (for instance, 172.16.0.1 through
-      172.16.0.9), since the rest of the range is assigned by MAAS's DHCP
-      server.
-
-   -  Once you've finished configuring this network port, be sure to
-      activate it. If you configured it by editing
-      ``/etc/network/interfaces``, type ``sudo ifup eth0`` to activate it.
-      (Depending on your starting configuration, you might need to type
-      ``sudo ifdown eth0`` or bring it down via your GUI tools before
-      bringing it up with its changed configuration.)
-
-#. If you plan to mirror the Ubuntu archives locally, ensure you have
-   enough space in the ``/srv`` directory to hold your mirrors. As a
-   general rule of thumb, you should set aside about 150GB per release. If
-   necessary, mount an extra disk at ``/srv`` to hold your repository
-   mirror.
-
-#. Update the software on your system to the latest versions available::
-
-    $ sudo apt-get update
-    $ sudo apt-get dist-upgrade
-
-#. Reboot the computer. This enables you to begin using your updated kernel
-   (if it was updated) and ensures that your network settings will survive a
-   reboot.
-
-.. _`Installing and Configuring MAAS`:
-
-Installing and Configuring MAAS
-===============================
-
-Installing MAAS on the computer is quite straightforward; you simply use
-APT. With MAAS installed, you can run the ``maniacs-setup`` script to
-configure MAAS for use in an Ubuntu certification environment.
-
-Installing MAAS
----------------
-
-Configuring MAAS is described in generic terms at
-`http://maas.ubuntu.com/docs/install.html <http://maas.ubuntu.com/docs/install.html>`_.
-The more specific procedure for using MAAS in certification testing is:
-
-#. Install the MAAS stable PPA
-   (`https://launchpad.net/~maas/+archive/ubuntu/stable <https://launchpad.net/~maas/+archive/ubuntu/stable>`_)::
-
-      $ sudo apt-add-repository ppa:maas/stable
-
-   Currently (July, 2015), Ubuntu 14.04 installs MAAS 1.5 by default. This
-   PPA holds version 1.8 of MAAS, which is the recommended version for
-   certification testing. (MAAS 1.7 is also acceptable.) Version 1.8 will
-   eventually become standard for Ubuntu 14.04, at which point this step
-   will become unnecessary.
-
-#. Several scripts and configuration files, some of which are quite
-   lengthy, are available in the ``maas-cert-server`` package in the
-   hardware certification PPA. You can install the scripts and configuration files
-   as follows::
-
-      $ sudo apt-add-repository ppa:hardware-certification/public
-      $ sudo apt-get update
-      $ sudo apt-get install maas-cert-server
-
-   As of version 0.1.2, the ``maas-cert-server`` package includes a
-   dependency on MAAS, so installing ``maas-cert-server`` will also install
-   MAAS, as well as all of MAAS's dependencies.
-
-   Most of the ``maas-cert-server`` files will be installed in
-   subdirectories of  ``/usr/share/maas-cert-server``, although a few
-   appear outside of that directory tree. (Subsequent steps describe how to
-   use these files.)
-
-#. Verify that you've installed MAAS 1.8 from the PPA, rather than MAAS
-   1.5 or some other version::
-
-      $ dpkg -p maas | grep Version
-
-   If the wrong version is installed, fixing the problem (presumably a
-   misconfigured PPA) and upgrading may work. If you upgrade from an
-   earlier version of MAAS, be sure to select the option to upgrade all the
-   configuration files when the package manager asks about this.
-
-#. Edit the ``/etc/maas-cert-server/config`` file to be sure that the
-   variables it contains are correct. Specifically:
-
-   - ``INTERNAL_NET`` must point to your *internal* network device
-     (``eth0`` in this document).
-
-   - ``EXTERNAL_NET`` must point to your *external* network device
-     (``eth1`` in this documnt, but this might be ``wlan0`` if you're
-     using a laptop).
-
-   - Do not adjust other values without consulting with the Server
-     Certification Team.
-
-   - Note that there must *not* be spaces surrounding the equal signs
-     (``=``) in the assignments!
-
-Running the Setup Script
-------------------------
-
-The certification script is called ``maniacs-setup``, and was installed as part
-of the ``maas-cert-server`` package. Running this script will set up the MAAS
-server with reasonable defaults for certification work; however, the script
-will also ask you a few questions along the way::
-
-    $ sudo maniacs-setup
-    
-    ***************************************************************************
-    * Identified networks:
-    *   INTERNAL: 172.16.0.1 on eth0
-    *   EXTERNAL: 192.168.25.143 on eth1
-    *
-    * Is this correct (Y/n)?
-
-Be sure your network assignments are correct at this point! If the script
-complains about a problem, such as an inability to identify an IP address
-or a default route being present on your internal network, go back and
-review both your network settings and the contents of your
-``/etc/maas-cert-server/config`` file to identify the cause and correct the
-problem.
-
-If you approve the settings, the script will display additional messages as
-it begins to configure the MAAS server. Some of these messages are the
-output of the programs it calls. For the most part this output can be
-ignored, but if a problem occurs, be sure to report it in detail, including
-the script's output.
-
-Note that at all prompts for a "Y/N" response, the default value is
-capitalized; if you press Enter, that default will be used.
-
-The next question acquires a password for the administrative account, which
-will have the same name as your default login name::
-
-    ***************************************************************************
-    * A MAAS administrative account with a name of ubuntu is being
-    * created.
-    *
-    * Please enter a password for this account:
-    * Please re-enter the password for verification:
-
-In most cases, you should enable NAT on your MAAS server; however, if
-official policy at the site where the server will be used forbids the use
-of NAT, you may opt to leave it disabled::
-
-    ***************************************************************************
-    * NAT enables this computer to connect the nodes it controls to the Internet
-    * for direct downloads of package updates and to submit certification results
-    * to C3.
-    *
-    * You can configure this computer to automatically start NAT. If you do so, you
-    * can disable it temporarily by using the 'flushnat.sh' script or permanently
-    * by removing the reference to /usr/sbin/startnat.sh from /etc/rc.local.
-    *
-    * Do you want to set up this computer to automatically enable NAT (Y/n)?
-
-Note that you can enable NAT on a one-time basis by running the
-``startnat.sh`` script and disable it by running the ``flushnat.sh``
-script. Both of these scripts come with the ``maas-cert-server`` package.
-
-If your work site has poor Internet connectivity or forbids outgoing
-connections, you must create a local mirror of the Ubuntu archives on your
-MAAS server. These archives will be stored in the ``/srv`` directory, but
-creating them takes a long time because of the amount of data to be
-downloaded -- about 150 GB per release. For comparison, HD video consumes
-1-8GiB per hour -- usually on the low end of that range for video streaming
-services. As should be clear, the result will be significant network demand
-that will degrade a typical residential DSL or cable connection for hours,
-and possibly exceed your monthly bandwidth allocation. If you want to defer
-creating a mirror, you should respond ``N`` to the following prompt, then
-re-launch ``maniacs-setup`` with the ``\-\-mirror-archives`` (or ``-m``)
-option later. In any event, you make your selection at the following
-prompt::
-
-    ***************************************************************************
-    * Mirroring an archive site is necessary if you'll be doing testing while
-    * disconnected from the Internet, and is desirable if your test site has
-    * poor Internet connectivity. Performing the mirroring operation takes
-    * time and disk space, though -- about 150 GiB per release mirrored.
-    * To defer this task, respond 'N' to the following question.
-    *
-    * Do you want to mirror an archive site for local use (y/N)? Y
-
-If you opt to mirror the archive, the script will ask you to verify the
-upstream mirror site::
-
-    * Identified upstream archive is:
-    *  http://us.archive.ubuntu.com/ubuntu/
-    *
-    * Is this correct (Y/n)? y
-
-If you respond ``n`` to this question, the script asks you to specify
-another archive site. The script then asks you which Ubuntu releases to
-mirror::
-
-    * Do you want to mirror precise (Y/n)? n
-    * Do you want to mirror trusty (Y/n)? y
-    * Do you want to mirror vivid (Y/n)? n
-    * Do you want to mirror wily (Y/N)? n
-
-The list of releases changes as new versions become available and as old
-ones drop out of supported status.
-When the mirror process is done, you'll be asked if you want to configure
-the computer to
-automatically update its mirror every day, by modifying the
-``/etc/cron.d/apt-mirror`` file. If you do not opt for automatic daily
-updates, you can update your mirror at any time by typing ``sudo
-apt-mirror``.
-
-::
-
-    * Set up cron to keep your mirror up-to-date (Y/n)? y
-    * Cron should update your mirror every morning at 4 AM.
-    * You can adjust /etc/cron.d/apt-mirror manually, if you like.
-
-Note that ``maniacs-setup`` configures the system to mirror AMD64, i386,
-and source repositories because all three are required by the default APT
-configuration. If you want to tweak the mirror configuration, you can do so
-by editing the ``/etc/apt/mirror.list`` file -- but do so *after* finishing
-with the ``maniacs-setup`` script, and then type ``sudo apt-mirror`` to
-pull in any new directories you've specified. You can also configure the
-computer to use its own local mirror, if you like::
-
-    * Adjust this computer to use the local mirror (Y/n)? y
-
-The script then gives you the option to retrieve an image used for
-virtualization testing. If your site has good Internet connectivity, you
-may not need this image; but it's not a bad idea to have it on hand
-just in case. Note that the script skips this prompt if it detects an image
-already exists in ``/srv``. Although downloading the cloud image isn't
-nearly as time-consuming as mirroring the archives, it can take long
-enough that you may want to defer this action. You can download the
-cloud image later by launching ``maniacs-setup`` with the
-``\-\-download-virtualization-image`` (or ``-d``) option.
-
-::
-
-    ***************************************************************************
-    * An Ubuntu cloud image is required for virtualization tests. Having such an
-    * image on your MAAS server can be convenient, but downloading it can take
-    * a while (it's about 250MiB).
-    *
-    * To defer this task, respond 'N' to the following question.
-    *
-    * Do you want to copy a cloud image for the vitualization tests (Y/n)?
-
-You can customize the site that MAAS tells nodes to use for their
-repositories. If you mirrored a repository, the script points nodes to
-itself (via its internal IP address); but if you did not mirror a
-repository, the script should point your nodes to the same site used by the
-MAAS server itself. In either case, you can press the Enter key to accept
-the default or enter a new value::
-
-    ***************************************************************************
-    * MAAS tells nodes to look to an Ubuntu repository on the Internet. You
-    * can customize that site by entering it here, or leave this field blank
-    * to use the default value of http://172.16.0.1/ubuntu.
-    *
-    * Type your repository's URL, or press the Enter key:
-
-At this point, the script gives you the option of telling MAAS to begin
-importing its boot resources -- images it uses to enlist, commission, and
-start nodes. This process can take several minutes to over an hour to
-complete, so the script gives you the option of deferring this process::
-
-    ***************************************************************************
-    * MAAS requires boot resource images to be useful; however, importing them
-    * can take a LONG time. You can perform this task now or defer it until
-    * later (or do it manually with the MAAS web UI).
-    *
-    * Do you want to import boot resources now? (Y/n)
-
-If you choose to defer this process, MAAS may begin it automatically in the
-background. If this fails and you want to initiate it manually later, you
-can use the MAAS web UI or launch ``maniacs-setup`` with the
-``\-\-import-boot-resources`` (or ``-i``) option.
-
-When MAAS has finished importing boot resources, the
-script helps you import the point-release images used for certification;
-however, you are first asked which series you want to import::
-
-    ***************************************************************************
-    * Ubuntu hardware certification is done using point-release images. These
-    * can take a LONG time to download. You can do so now or defer this task.
-    *
-    * Do you want to import point-release images now (Y/n)? y
-    *
-    * Do you want to import 15.10 (1 image) (y/N)? n
-    * Do you want to import the 14.04 series (4 images) (Y/n)? y
-    * Do you want to import the 12.04 series (6 images) (y/N)? y
-
-Whenever you respond ``Y`` to a question about a particular version or
-series, the script proceeds to download and register the images. (The
-relevant output has been omitted from the preceding example.) If an image
-is already installed, ``maniacs-setup`` skips that image. Certification
-uses only LTS images; however, non-LTS images, such as 15.10, may be made
-available for testing and as a way to "preview" the features of
-future LTS series.
-
-If you're running MAAS 1.8.2 or later, ``maniacs-setup`` registers the most
-recent point-release image in any series you download as the default OS for
-deployments.
-
-Again, this process can take a while, especially if you opt to import the
-12.04 images. If you want to skip this step for now and return to it, you
-can; you should re-launch ``maniacs-setup`` with its
-``\-\-update-point-releases`` (or ``-u``) option when you're ready to
-download these images.
-
-Finally, the script announces it's finished its work::
-
-    ***************************************************************************
-    * The maniacs-setup script has finished!
-
-In addition to setting the options for which it prompts, ``maniacs-setup``
-adjusts some other details of which you should be aware:
-
-- SSH keys are generated for your user account and added to the MAAS
-  server. These keys enable you to log in to nodes that MAAS deploys from
-  your regular account on the MAAS server.
-
-- Any keys in your ``~/.ssh/authorized_keys`` file on the portable are also
-  added to the MAAS setup. Again, this simplifies login.
-
-- The portable computer's SSH server configuration is relaxed so that
-  changed host keys do not block outgoing connections. This change is
-  *insecure*, but is a practical necessity because your internal network's
-  nodes will be redeployed regularly. You should keep this setting in mind
-  and minimize your use of this computer to SSH to external sites.
-
-- MAAS is configured to tell nodes to install the Canonical Certification
-  Suite whenever they're deployed. This detail increases deployment time
-  compared to a generic MAAS installation.
-
-Checking the MAAS Configuration
--------------------------------
-
-At this point, MAAS should be installed and configured; however, it's worth
-verifying the most important options in the MAAS Web UI. You may also want
-to modify a few settings. To do so, follow these steps:
-
-#. Verify you can access the MAAS Dashboard:
-
-   -  Launch a browser and point it to \http://172.16.0.1/MAAS (your
-      internal port).
-
-   -  You should also be able to access this by default on the
-      external port, too.
-
-   -  If you provide the computer with a hostname in DNS or ``/etc/hosts``,
-      you should be able to access it via that name, as well.
-
-   -  You should see a login prompt.
-
-#. Log in to the Dashboard using your regular username and the password you
-   gave to the setup script.
-
-#. Click Images near the top of the MAAS web page. This page will show the Ubuntu images that are available on the server. The setup script imports a 14.04 image for AMD64, as well as custom images for every 14.04 point release. You may need to take additional actions in some cases:
-
-   - If you see a blue circle next to an image, it did not import
-     correctly. You can also check the Clusters page to verify the status
-     of your image downloads. A successful image import will show Synced
-     under Images.
-
-   - If you need to support architectures other than AMD64, you must check
-     that architecture and click Apply Changes. This process will probably
-     take several minutes to complete.
-
-   - If you need to import i386 point-release images, you must import them
-     manually, as described in Appendix B.
-
-#. Click the Clusters link near the top of the web page so you can review
-   the DHCP options:
-
-   #.  Click the cluster name for the cluster controller (Cluster Master in
-       this example):
-
-       .. image:: images/clusters-page.png
-          :width: 98%
-
-   #.  Mouse over the *internal* (normally ``eth0``) network
-       interface. (If you don't see your internal interface listed, click
-       the "Add Interface" button to add it.) You should see a pair of
-       icons appear, one to edit the interface and one to delete it. Click
-       the former, then review the following items:
-
-       - Be sure that "Interface" is set to your internal port and that
-         "Management" is set to "DHCP and DNS."
-
-       - Review the various IP addresses and netmasks.
-
-       - Click "Save Interface" if you made any changes.
-
-#. Click Settings near the top of the page to load the MAAS Settings page,
-   where you review several miscellaneous MAAS details. If you change any
-   settings, be sure to click the associated "Save" button within that
-   section. Unfortunately, each save button is section-specific and won't
-   save changes made in other sections of that page.
-
-Testing the MAAS Server
-=======================
-
-At this point, your MAAS server should be set up and configured correctly.
-To test it, follow these steps:
-
-#. Prepare a computer by configuring it to boot via PXE. This computer
-   need not be a computer you plan to certify; anything that can
-   PXE-boot should work, although to fully test the MAAS server, the
-   test system should provide IPMI or some other power-control tool that
-   MAAS supports.
-
-#. Connect the test computer to the portable computer's *internal* network
-   and power it on.
-
-   - The test computer should PXE-boot from the portable MAAS computer.
-
-   - This first boot should be to the enlistment image, which provides
-     some very basic information to the MAAS server. Once the node powers
-     itself off you should see it listed in the MAAS nodes list
-     (\http://localhost/MAAS/#/nodes/ or, on MAAS 1.7,
-     \http://localhost/MAAS/nodes/) with a Status field of "New."
-
-   - Note that you will have to refresh the nodes list as it does not
-     refresh itself to list new data.
-
-#. Click on the node's hostname to view the node's summary page.
-
-#. If desired, click the node's hostname near the upper-left corner of the
-   page. This will enable you to change the hostname to something
-   descriptive, such as the computer's model number. Click "Save" when
-   you've made your changes.
-
-#. If necessary, click "Edit" in the Machine Summary section to change the
-   architecture of the machine. Click "Save Changes" when you're done.
-
-#. If necessary, change the Power Type in the Power section of the page.
-   This may necessitate setting an IP address, MAC address, password, or
-   other information, depending on the power control technology in use.
-   Click "Save Changes" when you're done.
-
-#. Click "Take Action" near the top-right corner of the page, followed by
-   "Commission Node" from the resulting drop-down menu. You must then click
-   "Go."
-
-   - The node should power on again. This time you'll see it PXE-boot the
-     commissioning image. Note that if your test system lacks a BMC or
-     other means to remotely control its power, you must manually power it
-     on.
-
-   - The node should do a bit more work this time before powering off
-     again.
-
-   - Once it's done, the UI will show a Status of "Ready."
-
-#. Once the system powers off after commissioning, click "Take Action"
-   followed by "Deploy." You must then click "Go" to confirm this action.
-
-   - The node should power on again (or you will have to control it
-     manually if it lacks a BMC). This time it will take longer to finish
-     working, as MAAS will install Ubuntu and the certification suite on
-     the system.
-
-   - Once it's done, the computer will reboot into its installed image.
-
-   - Log into the node from the MAAS server by using SSH, as in ``ssh
-     testnode`` if you've given the node the name ``testnode``.
-
-   - In the node, type ``canonical-certification-server``. The
-     certification suite software should run. You can type Ctrl+C to exit;
-     at this point, it's sufficient to know that it installed correctly.
-
-If any of these steps fail, you may have run into a MAAS bug; your test
-computer may have a buggy PXE, IPMI, or other subsystem; or you may have
-misconfigured something in the MAAS setup. You may want to review the
-preceding sections to verify that you configured everything correctly.
-To help in debugging problems, the node status page includes a section
-entitled Latest Node Events with a summary of the last few events
-related to the node. (You must refresh the page to see new events.)
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix A: Updating Fixed Point Release Images
-===============================================
-
-From time to time, Canonical updates the LTS versions of Ubuntu with new
-point releases, such as 14.04.1, 14.04.2, and so on. Because you must run
-the certification tests on the latest point release, updating your MAAS
-server with the latest point releases will become necessary, sooner or
-later. This task can be accomplished with MAAS 1.7 or 1.8 by installing
-custom images.
-
-The ``maniacs-setup`` script automatically downloads and installs all the
-available point-release images at the time you first run it. After a new
-point release is made, you can re-run the script with the
-``\-\-update-point-releases`` (or ``-u``) option to have the script install
-the new release::
-
-    $ sudo apt-get install maas-cert-server
-    $ sudo maniacs-setup --update-point-releases
-
-The script will skip most of the setup steps and proceed to asking you
-which point-release images to download and install. When you select a
-series, only those point-release images that have not yet been installed
-from that series will be downloaded. Note that if you're running
-``maas-cert-server`` version 0.2.9 or earlier, you should update to the
-latest version before updating your point releases. Version 0.2.10
-introduced the ability to dynamically determine what Ubuntu point-release
-images are available for download; earlier versions used a hard-coded list,
-and so will miss updates beyond Ubuntu 14.04.3.
-
-If a particular point release is giving you problems, you can delete it
-using the MAAS web UI and then update your point-release images as just
-described; this will refresh the image to the latest available version.
-Similarly, if the Server Certification Team releases new images, you should
-first delete the old ones using the web UI and then update your point
-releases.
-
-Note that before you can install a custom image for any given architecture,
-you must have first imported at least one image for that architecture via
-the conventional means. The ``maniacs-setup`` script detects whether you've
-installed the standard i386 images and will install i386 point-release
-images if and only if the standard i386 images are already installed.
-Currently, only AMD64 and i386 point-release images are available.
-
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix B: Adding i386 Support
-===============================
-
-By default, the ``maniacs-setup`` script supports only AMD64 (64-bit,
-x86-64) nodes. (If you created a local mirror, it includes i386/x86
-binaries because they're needed by some 64-bit packages.) If you expect to
-run certification tests on i386 (32-bit, x86) computers, though, you must
-add support for such systems in MAAS:
-
-#. In the MAAS web UI, click the Images tab.
-
-#. Select "i386" in the "Architecture" column.
-
-#. Click "Apply changes." The standard MAAS i386 images will download. This
-   process can take several minutes, and perhaps over an hour on a slow
-   Internet connection.
-
-#. Re-run the ``maniacs-setup`` script, but add the
-   ``\-\-update-point-releases`` option to the script, as described in
-   Appendix A. This will cause the script to download and add the
-   point-release images for i386 systems.
-
-That's it. You can add support for ppc64el, ARM64, or other architectures
-in a similar way; however, there are currently no point-release images for
-these architectures. Please consult the Server Certification Team if you
-need to certify systems using these CPUs.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix C: Performing a Partial Restore
-========================================
-
-If the MAAS server's support files (the PXE boot images and related
-files) become damaged, PXE-booting SUTs may fail. The SUT may fail to
-retrieve PXE boot images or the boot may fail with any number of
-symptoms later in the process. If you're unable to discover a cause and
-solution through less drastic means, one possible recovery procedure is
-to restore those files to a fresh state; however, be aware that this
-procedure will *destroy all existing node definitions.* Thus (and because
-the solution involves downloading new boot images, which can be
-time-consuming), you should attempt this solution only as a last resort.
-Steps 1 and 6-7 of the following procedure are the minimum required;
-steps 2-5 make for a more thorough cleansing of the system. The overall
-procedure is:
-
-#. Click the Clusters link in the MAAS server's web interface (to reach
-   the server's ``/MAAS/clusters/`` page).
-
-#. Click the small trash can icon that appear near the right side of the
-   page associated with your malfunctioning cluster when you mouse over it,
-   and then confirm the operation. This will delete the cluster
-   controller's definition.
-
-#. Delete the contents, including all subdirectories, of the
-   ``/var/lib/maas/boot-resources`` directory on the portable server.
-
-#. In a shell, reconfigure the ``maas-cluster-controller`` and
-   ``maas-region-controller`` packages::
-
-      $ sudo dpkg-reconfigure maas-cluster-controller
-      $ sudo dpkg-reconfigure maas-region-controller
-
-   You should not need to adjust the default values.
-
-5. Reset the cluster controller's DHCP and DNS options.
-
-6. If necessary or desired, adjust the images you want to import.
-
-7. Re-run the ``maniacs-setup`` script with the
-   ``\-\-update-point-releases`` option, as described in Appendix A, to
-   refresh your point-release images.
-
-This procedure should restore your ability to PXE-boot your SUTs.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix D: Glossary
-====================
-
-The following definitions apply to terms used in this document.
-
-1Gbps
-  1 Gigabit - Network speed for Gigabit Ethernet (1000Mbps).
-
-10Gbps
-  10 Gigabit - Network speed for 10 Gigabit Ethernet (10,000Mbps).
-
-BMC
-  Baseboard Management Controller -- A device in many server models
-  that allows remote in- and out-of-band management of hardware.
-
-DHCP
-  Dynamic Host Control Protocol -- method for providing IP addresses
-  to the SUTs.
-
-IPMI
-  Intelligent Platform Management Interface -- A technology for
-  remotely connecting to a system to perform management functions.
-
-LAN
-  Local Area Network -- the network to which your SUTs are connected. The
-  LAN does not need to be Internet accessible (though that is preferable if
-  possible).
-
-MAAS
-  Metal as a Service -- a Canonical product for provisioning systems
-  quickly and easily.
-
-NIC
-  Network Interface Card -- the network device(s).
-
-NUC
-  A small form-factor PC product from Intel.
-
-PXE
-  Pre-boot Execution Environment -- A technology that allows you to
-  boot a system using remote images for easy deployment or network-based
-  installation.
-
-SUT
-  System Under Test -- The machine you are testing for certification.

=== removed file 'documentation/Makefile'
--- documentation/Makefile	2015-07-17 19:42:06 +0000
+++ documentation/Makefile	1970-01-01 00:00:00 +0000
@@ -1,36 +0,0 @@
-SHELL = /bin/sh
-RST2PDF=rst2pdf
-RST2HTML=rst2html
-DOC_NAMES=Self-Test_Guide MAAS_Advanced_NUC_Installation_And_Configuration MAAS_Advanced_NUC_Installation_And_Configuration_Scripted
-HTML_NAMES=$(DOC_NAMES:=.html)
-PDF_NAMES=$(DOC_NAMES:=.pdf)
-
-.SUFFIXES:
-.SUFFIXES: .pdf .rst
-
-all:	html pdf
-
-html:	$(HTML_NAMES)
-
-pdf:	$(PDF_NAMES)
-
-%.pdf: %.rst
-	$(RST2PDF) --smart-quotes 1 -s styles/cert-doc.style $< -o $@
-
-%.html: %.rst
-	$(RST2HTML) --smart-quotes=yes $< $@
-
-maniac: MAAS_Advanced_NUC_Installation_And_Configuration.pdf
-
-maniacs: MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.pdf
-
-stg: Self-Test_Guide.pdf
-
-maniach: MAAS_Advanced_NUC_Installation_And_Configuration.html
-
-maniacsh: MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.html
-
-stgh: Self-Test_Guide.html
-
-clean:
-	rm -f *.pdf *.html

=== removed file 'documentation/README'
--- documentation/README	2015-07-17 19:42:06 +0000
+++ documentation/README	1970-01-01 00:00:00 +0000
@@ -1,86 +0,0 @@
-=========================================
- Server Certification Team Documentation
-=========================================
-
-Overview
-========
-
-This directory contains documentation for the Server Certification team in
-reStructuredText format. Specific documents are:
-
-* MAAS_Advanced_NUC_Installation_And_Configuration.rst -- The MANIAC
-  document
-* MAAS_Advanced_NUC_Installation_And_Configuration_Scripted.rst -- The
-  MANIACS (MANIAC - Scripted) document
-* Self-Test_Guide.rst -- The Server Self-Test Guide
-
-Support files and directories are:
-
-* Makefile -- A Makefile to generate .pdf and .html files from the .rst
-  files.
-* images/ -- A subdirectory holding images. Note that some images are
-  stored in both source form (.fig, .xcf, etc.) and the .png files that are
-  mostly referenced in the .rst files.
-* styles/ -- Style files used in generating PDFs. Currently has just one
-  style.
-
-Converting from .rst to .pdf form requires the ``rst2pdf`` package::
-
-  sudo apt-get install rst2pdf
-
-Creating HTML and PDF Files
-===========================
-
-PDFs and HTML files can be generated by way of the ``make`` utility, as
-in::
-
-    make stg
-
-This example builds the Self-Test Guide in PDF form. The complete set of
-targets are:
-
-* ``stg`` -- Builds the Self-Test Guide as a PDF
-* ``maniac`` -- Builds the MANIAC document as a PDF
-* ``maniacs`` -- Builds the MANIACS document as a PDF
-* ``stgh`` -- Builds the Self-Test Guide as an HTML file
-* ``maniach`` -- Builds the MANIAC document as an HTML file
-* ``maniacsh`` -- Builds the MANIACS document as an HTML file
-* ``pdf`` -- Builds all three documents as PDFs
-* ``html`` -- Builds all three documents as HTML files
-* ``all`` (default) -- Builds all three documents as both PDFs and as
-  HTML files
-* ``clean`` -- Removes all ``.pdf`` and ``.html`` files
-
-Note that the primary intended output format is PDF; HTML output is rough
-at this time (July, 2015).
-
-Styles and Formatting
-=====================
-
-The general style for the document is based on the Canonical whitepaper
-template provided by Magdalena Mirowicz ([e-mail])
-in March of 2015. This template was not directly usable because it was in
-ODF format and used a two-column layout. I've tried to stick close to the
-ODF template in reStructuredText, but there are some differences:
-
-* We're using a single-column layout.
-* Our default font is a darker shade of gray.
-* Our document uses letter-size paper rather than A4, since most of our
-  readers are in the US.
-* Headers and footers were replicated "by eye" and so are not precise
-  conversions.
-* The rst2pdf program creates a Contents list that is NOT capitalized
-  (as in the sample template) and that provides hyperlinks to the
-  referenced sections.
-
-Editing Tips
-============
-
-Some tips when editing the .rst files:
-
-* Use your favorite text editor.
-* If necessary, you can insert page breaks manually; but use this feature
-  only if absolutely necessary.
-* Once a year, the images/cover-background.xcf file must be edited and
-  re-exported to cover-background.png to update the copyright date that
-  appears on the cover page.

=== removed file 'documentation/Self-Test_Guide.rst'
--- documentation/Self-Test_Guide.rst	2015-07-17 19:42:06 +0000
+++ documentation/Self-Test_Guide.rst	1970-01-01 00:00:00 +0000
@@ -1,1255 +0,0 @@
-=================================================================
- Ubuntu Server Certified Hardware Self-Testing Guide (14.04 LTS)
-=================================================================
-
-.. header:: |ubuntu_logo|
-
-.. |ubuntu_logo| image:: images/logo-ubuntu_su-white_orange-hex.png
-   :scale: 20%
-
-.. footer:: |canonical_logo|
-
-.. |canonical_logo| image:: images/logo-canonical_no-tm-white-hex.png
-   :scale: 10%
-
-.. raw:: pdf
-
-   PageBreak oneColumn
-
-.. contents::
-
-.. raw:: pdf
-
-   PageBreak
-
-Introduction
-============
-
-The aim of this document is to provide the information needed to certify
-a server on-site using the Canonical Server Test Suite without requiring
-an Internet connection.
-
-Glossary
-========
-
-The following definitions apply to terms used in this document.
-
-1Gbps
-  1 Gigabit per second -- Network speed for Gigabit Ethernet (1000Mbps).
-
-10Gbps
-  10 Gigabits per second -- Network speed for 10 Gigabit Ethernet
-  (10,000Mbps).
-
-BMC
-  Baseboard Management Controller -- A device in many server models
-  that enables remote in- and out-of-band management of hardware.
-
-DHCP
-  Dynamic Host Control Protocol -- A method for providing IP
-  addresses to the SUT and Targets.
-
-Greylist test
-  A test that must be performed but will not affect the
-  granting of a certified status.
-
-KVM
-  Kernel Virtual Machine -- A system for running virtual machines on
-  Ubuntu Server.
-
-IPMI
-  Intelligent Platform Management Interface -- A technology for
-  remotely connecting to a computer to perform management functions.
-
-JBOD
-  Just a bunch of disks -- A non-RAID disk configuration.
-
-LAN
-  Local Area Network -- The network to which your SUT and Targets are
-  connected. The LAN does not need to be Internet accessible (though that
-  is preferable if possible).
-
-.. raw:: pdf
-
-   PageBreak
-
-MAAS
-  Metal as a Service -- A Canonical product for provisioning systems
-  quickly and easily.
-
-NIC
-  Network Interface Card -- The network device(s).
-
-PXE
-  Pre-boot Execution Environment -- A technology that enables you to
-  boot a computer using remote images for easy deployment or network-based
-  installation.
-
-RAID
-  Redundant Array of Independent Disks - Multi-disk storage
-  providing redundancy, parity checking, and data integrity.
-
-RAM
-  Random Access Memory -- System memory.
-
-SAN
-  Storage Area Network -- Usually FibreChannel.
-
-SUT
-  System Under Test -- The machine you are testing for certification.
-
-Target
-  A computer on the test LAN that the SUT can use for network testing. The
-  Target must be running an ``iperf`` server, but otherwise does not need
-  any special configuration. The MAAS server may double as the Target.
-
-Test case
-  A test to be executed as part of the certification test
-  suite. Test cases include things such as "CPU Stress" and "CPU
-  Topology."
-
-Whitelist test
-  A test that *must* pass for the SUT to be granted a certified status.
-
-Overview of the Certification Process
-=====================================
-
-The certification process has certain prerequisites and procedures with
-which you should be familiar before beginning. Specifically, you should
-be aware of hardware requirements and the needs of the network test
-environment. There are steps you should perform before running the
-certification tests and before uploading the results. The following
-sub-sections briefly describe these requirements. Detailed descriptions
-appear later in this document.
-
-Hardware Requirements
----------------------
-
--  SUTs must contain at least 4GiB of RAM and one hard disk, but using
-   the maximum amount of RAM and the maximum number of disks is
-   preferable. Likewise, if configurable, using the maximum number of
-   CPUs is desirable.
-
--  CPUs should support virtualization (VMX/SVM), when supported by CPU
-   architecture.
-
--  All firmware (BIOS/UEFI, NIC, storage controller, etc) should be
-   shipping level, *not* development level.
-
--  A monitor and keyboard for the SUT are helpful because they will
-   enable you to monitor its activities. If necessary, however,
-   certification can be done without these items.
-
-Network Test Environment
-------------------------
-
--  In addition to the SUT, the network must contain at least one other
-   machine, which will run MAAS and an ``iperf`` server. The MAAS Advanced
-   NUC Installation and Configuration (MANIAC) document (available from
-   https://certification.canonical.com) describes how to configure a MAAS
-   server. This server may be a standard part of the testing network or
-   something you bring with you for testing purposes alone. A laptop or a
-   small portable computer such as an Intel NUC is sufficient. MAAS version
-   1.7 or later is strongly preferred for certification work; the older
-   MAAS 1.5 lacks certain features that are becoming increasingly
-   important. This document describes use of MAAS 1.8. If you use MAAS 1.7,
-   some procedures will differ slightly.
-
--  The MAAS server computer should run Ubuntu 14.04 (Trusty Tahr), and
-   should be configured to deliver Ubuntu 14.04 images to its clients.
-   Testing with fixed point releases, as described in the "Configuring
-   MAAS to Deliver Fixed Point Releases" section of the MANIAC document,
-   is required.
-
--  Ideally, the network should have few or no other computers;
-   extraneous network traffic can negatively impact the network tests.
-
--  Ideally, the MAAS server system should handle DNS and DHCP for the
-   network. If other computers manage these tasks, be sure that they're
-   configured to work with the MAAS server so that the SUT obtains its
-   PXE-boot images from the MAAS server.
-
--  Network cabling, switches, and the ``iperf`` server should be capable of
-   at least the SUT's best speed. For instance, if the SUT has 1Gbps
-   Ethernet, the other network components should be capable of 1Gbps or
-   faster speeds. If the local network used for testing is less capable
-   than the best network interfaces on the SUT, those interfaces must be
-   tested later on a more-capable network.
-
--  If desired, the MAAS server may be run inside a virtual machine;
-   however, it is advisable to run the ``iperf`` server on "real" hardware
-   so as to minimize the risk of network tests failing because of
-   virtualization issues.
-
-Before Running Test Cases
--------------------------
-
--  The SUT must be properly configured and cabled.
-
--  The SUT must have Ubuntu 14.04 installed on it. (This must be done via
-   MAAS.) See the `Installing Ubuntu on the System`_ section below for
-   details on how to do this.
-
--  The ``canonical-certification-server`` package must be installed on the
-   SUT together with all its dependencies. (This will normally be done via
-   MAAS.) For more information about how to get all the packages, please
-   refer to the `Installing the Server Test Suite Packages`_ section below.
-
--  Be sure to have all the items described in the `Equipment to
-   Bring`_ section below.
-
--  Some manual configuration will be necessary to perform
-   network testing. See the `Installing Ubuntu on the
-   System`_ section below.
-
-Before Uploading Test Case Results
-----------------------------------
-
-Prior to uploading results to Canonical's certification site, you must
-handle some preliminary tasks:
-
--  You will need an account at the certification web site,
-   https://certification.canonical.com.
-
-   -  The certification web site is the location where all the test case
-      results will be uploaded once your testing session has finished.
-
-   -  *If you do not have an account for your company on the private
-      certification web site, please contact your account manager who will
-      work with the Server Certification Team to establish the account.*
-
--  You must create a hardware entry (unless one already exists for the
-   SUT) at the certification web site with a secure ID.
-
-   -  The secure ID is a string made from 15 alphanumeric characters that
-      is used to make sure that only authorized parties upload results to
-      the site and also to associate the results to the hardware being
-      tested. This can be found on the hardware entry page on the
-      Certification web site:
-
-      .. image:: images/secure_id.png
-         :alt: The Secure ID can be obtained from the Ceritification web site.
-         :align: left
-         :width: 50%
-
-   -  For more information on creating the hardware entry, please see
-      `Creating a Hardware Entry on C3` below.
-
--  If the SUT lacks Internet access, the package
-   ``canonical-certification-submit`` should be installed on the system
-   from which you plan to submit results. Please see the section below
-   titled `Manually Uploading Test Results to the Certification Site`_ for
-   more information on this topic.
-
-Initial Setup
-=============
-
-Before you certify the hardware, you must perform some initial setup
-steps. These steps are preparing the hardware you'll bring, configuring
-the SUT for testing, installing Ubuntu, and installing the Server Test
-Suite.
-
-Equipment to Bring
-------------------
-
-The requirements for running the tests for a server are minimal. Ensure
-that you have:
-
--  A writable USB stick with enough free space (> 256MB). It must contain a
-   *single partition* with a *writable FAT* filesystem on it. If you need
-   to test more than one computer then *bring one USB stick per system*. 
-   Note that a USB stick with multiple partitions may cause problems, so if
-   necessary you should repartitition your device to have a single
-   partition.
-
--  A data CD with some files written to it. This is required to test the
-   system's optical drive read capabilities. Note that a movie DVD or an
-   audio CD won't be useful in this case, as they are not in the right
-   format for the test. If you need to test more than one computer then
-   *bring one medium per system*.
-
--  A computer to function as a MAAS server and ``iperf`` target on the test
-   LAN. This server will provision the SUT. The MAAS server can be a normal
-   part of the test LAN or can be brought in specifically for testing SUTs
-   on the test LAN. (Note, however, that the MAAS server for certification
-   testing should ideally be configured to automatically install the Server
-   Test Suite on the SUT, which will not be the case for a "generic" MAAS
-   server.)
-
--  A USB flash drive that holds the Server Test Suite software. (This is a
-   precautionary measure in case MAAS can't install the Server Test Suite
-   packages and your LAN lacks Internet access.) The `Bringing the Server
-   Test Suite Packages With You`_ section of Appendix A describes how to
-   obtain the software.
-
-Hardware Setup
---------------
-
-The following should be considered the minimum requirements for setting
-up the SUT and test environment:
-
--  Minimum loadout
-
-   -  Minimum of 4GiB RAM
-
-   -  1 HDD (2 with minimal RAID)
-
-   -  1 CPU of a supported type
-
--  Recommended (preferred) loadout
-
-   -  Maximum supported number of HDDs or SSDs, especially if you can
-      configure multiple RAID levels (e.g. 2 for RAID 0, 3 for RAID 5, and
-      6 for RAID 50)
-
-   -  Maximum amount of supported RAM
-
-   -  Maximum number of supported CPUs
-
--  The SUT should not contain any extraneous PCI devices that are not
-   part of the certification.
-
-   -  This includes things like network, SAN and iSCSI cards.
-
-   -  Hardware RAID cards are allowed if they are used to provide RAID
-      services to the SUT's onboard storage.
-
--  The SUT should be running a release level BIOS/UEFI configured using
-   factory default settings, with the following exceptions:
-
-   -  If the hardware virtualization options in the BIOS/UEFI are not
-      enabled, enable them, save the settings and allow the SUT to reboot.
-
-   -  The SUT must be configured to PXE-boot by default.
-
--  Storage should be properly configured.
-
-   -  If the SUT is to be tested using RAID, then the proper hardware RAID
-      configuration should be set up prior to testing.
-
-   -  Software RAID, including firmware-supported software RAID (aka "fake
-      RAID") should *not* be used. If hardware RAID is not available,
-      configure the server for JBOD.
-
-   -  Any additional HDDs or logical drives should be partitioned and
-      mounted prior to testing. Partitions on those additional HDDs should,
-      preferably, be a single partition that spans the entire disk.
-
-   -  Some computers may have problems booting from disks over 2TiB in
-      size. If the SUT fails for this reason, it may pass with smaller
-      disks (or a smaller RAID array). In some cases, configuring the SUT
-      to boot in UEFI mode may also solve this problem; but consult the
-      Canonical Certification Team before changing firmware settings to
-      overcome such a problem.
-
--  If possible, as many processors as the SUT will support should be
-   installed.
-
-   -  Note that systems that ship with processors from different families
-      (e.g Sandy Bridge vs. Haswell) will require extra testing.
-
-   -  CPU speed bumps and die shrinks do not require extra testing.
-
--  Disks with 4,096-byte *logical* sector sizes may require booting in
-   EFI/UEFI mode, and MAAS's support for this is still new, so be alert to
-   potential problems. For instance, some computers support EFI-mode
-   booting but not EFI-mode PXE-booting. Note that disks with 4,096-byte
-   *physical* sector sizes are fine, so long as the disk's firmware
-   translates those sectors into 512-byte logical sectors.
-
--  The test environment should have a working network setup. Internet
-   access is not required, and testing should work on any private or
-   segregated LAN.
-
-   -  If possible, the test LAN's speed should match or exceed the network
-      speed of the SUT. For instance, a SUT with 1Gbps onboard Ethernet
-      should be connected to a LAN capable of at least 1Gbps and a system
-      with 10Gbps Ethernet should be connected to a LAN capable of at least
-      10Gbps. Connecting a SUT to a network with greater network speed is
-      acceptable.
-
-   -  If the primary test network cannot meet these requirements,
-      re-running the network tests in an environment that does match these
-      requirements will be necessary.
-
-   -  Every network port must be cabled to the LAN and properly configured
-      with either DHCP or static addressing. If a SUT has 4 NIC ports, then
-      all 4 must be connected to the LAN.
-
-   -  It is very strongly recommended that SUT and Target machines be on a
-      clean network (that is, one that is not full of other traffic), as
-      extraneous network traffic could impact the network testing results.
-
--  The test LAN must have a working MAAS server that can provision and run
-   the tests on the SUT. The MAAS Advanced NUC Installation and
-   Configuration (MANIAC) document, available at
-   https://certification.canonical.com, describes the basics of the MAAS
-   setup, but you may need to refer to additional documentation to complete
-   the task if you're not already familiar with MAAS.
-
--  The test LAN must have one system available to act as a Target for
-   network testing with ``iperf``. Note that accessing an ``iperf`` server
-   that's reachable only via a router may not work, because routing tables
-   are temporarily lost during network testing. The ``iperf`` server is
-   normally the same as the MAAS server, but this does not need to be the
-   case. If the SUT has a faster network interface than the MAAS server,
-   you should set up another computer that matches the SUT's network
-   interface speed to function as an ``iperf`` server.
-
--  The SUT's BMC, if present, may be configured via DHCP or with a static
-   IP address. MAAS will set up its own BMC user account (``maas``) when
-   enlisting the SUT.
-
-Installing Ubuntu on the System
--------------------------------
-
-Beginning with Ubuntu 14.04 (Trusty Tahr), server certification requires
-that the SUT be installable via MAAS. Therefore, the following procedure
-assumes the presence of a properly-configured MAAS server. The MAAS
-Advanced NUC Installation and Configuration (MANIAC) document describes how
-to set up a MAAS server for certification testing purposes. This document
-describes use of MAAS 1.8. Using MAAS 1.7 is also acceptable, but some user
-interface details differ.
-
-Once the SUT and MAAS server are both connected to the network, you can
-install Ubuntu on the SUT as follows:
-
-#. Unplug any USB flash drives or external hard disks from the SUT.
-   (MAAS will attempt to install to a USB flash drive if it's detected
-   before the hard disk. This is obviously undesirable.)
-
-#. Power on the SUT and allow it to PXE-boot.
-
-   -  The SUT should boot the MAAS enlistment image and then power off.
-
-   -  You should see the SUT appear as a newly-enlisted computer in your
-      MAAS server's node list. (You may need to refresh your browser to see
-      the new entry.)
-
-#. Check and verify the following items in the MAAS server's node details
-   page:
-
-   -  If desired, set a node name for the SUT.
-
-   -  Check the SUT's power type and ensure it's set correctly (IPMI, AMT,
-      etc.). If the SUT has no BMC, you can leave this section blank or
-      enter "dummy" data. If the power control information was detected
-      incorrectly or incompletely, you should consult the Canonical
-      Certification Team for advice.
-
-#. Commission the node by clicking Take Action followed by Commission
-   and then Go.
-
-   -  If the SUT has a BMC, the computer should power up, pass more
-      information about itself to the MAAS server, and then power down
-      again.
-
-   -  If the SUT does not have a BMC, you should manually power on the SUT
-      after clicking the Commission Node button. The SUT should power up,
-      pass more information about itself to the MAAS server, and then power
-      down again.
-
-   -  Note that manual power control is acceptable only on low-end servers
-      that lack BMCs. If MAAS fails to detect a BMC that is present or if
-      MAAS cannot control a BMC that is present, please consult the
-      Canonical Certification Team.
-
-#. On the MAAS server, verify that the SUT's Status is listed as Ready
-   in the node list or on the node's details page. You may need to
-   refresh the page to see the status update.
-
-#. Click Take Action followed by Deploy. Options to select the OS version
-   to deploy should appear.
-
-#. Select the Ubuntu release you want to deploy. Normally, you'll pick a
-   point release that you installed as described in the MANIAC document.
-   This image will appear as an OS type of Custom" and a description that
-   you gave it. The normal procedure is to test with 14.04 GA followed by
-   the latest point release. `Appendix D - Point Release Testing`_,
-   elaborates on this policy.
-
-#. Click Go to begin deployment.
-
-   -  If the SUT has a BMC, it should power up and install Ubuntu. This
-      process can take several minutes.
-
-   -  If the SUT does not have a BMC, you should power it on manually after
-      clicking Acquire and Start Node. The SUT should then boot and install
-      Ubuntu. This process can take several minutes.
-
-If MAAS has problems in any of the preceding steps, the SUT might not
-pass certification. For instance, certification requires that MAAS be
-able to detect the SUT and set its power type information automatically.
-If you have problems with any of these steps, contact the
-Canonical Server Certification Team to learn how to proceed; you might
-have run into a simple misconfiguration, or the server might need
-enablement work.
-
-Logging Into the SUT
---------------------
-
-Once the SUT is installed, you should be able to log into it using SSH from
-the MAAS server. Check the node details page to learn its primary IP
-address. (Using a hostname will also work if DNS is properly configured,
-but this can be fragile.) The username on the node is ``ubuntu``, and you
-should require no password when logging in from the MAAS server or from any
-other computer and account whose SSH key you've registered with the MAAS
-server.
-
-You should keep some details in mind as you continue to access the SUT:
-
--  You should *not* install updates to the SUT unless they are absolutely
-   necessary to pass the certification. In that case, the Canonical
-   Certification Team will make the determination of what updates should be
-   applied.
-
--  You should verify your SUT's version by typing ``lsb_release -a``. The
-   result includes both the main release version (such as 14.04) and the
-   point release version (such as 14.04.2, on the *Description* line). You
-   can also check your kernel version by typing ``uname -r``. The kernel
-   version changes with the Ubuntu release. Both 14.04 and 14.04.1 ship
-   with 3.13-series kernels, while 14.04.2 ships with a 3.16-series kernel.
-
--  By default, MAAS provides a DHCP server, and the SUT should use it to
-   obtain an IP address. If necessary for your environment, you may
-   manually change these settings on the SUT to use a static IP address.
-
--  If you want to log in at the console or from another computer, you
-   must set a password::
-
-    $ sudo passwd ubuntu
-
-   After prompting, this command changes the password for the user called
-   ``ubuntu``, which is the default user created by MAAS. Testing at the
-   console has certain advantages (described shortly).
-
--  A MAAS installation configured for certification testing should
-   provision the SUT with the Server Test Suite and related packages. If
-   you're using a more "generic" MAAS setup, you'll have to install the
-   certification software yourself, as described in `Appendix A -
-   Installing the Server Test Suite Manually`_.
-
-Ensure all network devices are configured in the file
-``/etc/network/interfaces``:
-
-.. figure:: images/interfaces.png
-   :alt: The /etc/network/interfaces file must be properly configured
-         for your system's interfaces.
-   :width: 100%
-
-Be sure to start networking on all the interfaces. (The network tests will
-*not* bring up a network interface, even if it's defined in
-``/etc/network/interfaces``.) In most cases, typing ``sudo ifup eth1``, and
-so on for additional entries, will do the job. (The ``eth0`` interface is
-normally enabled by default on the first boot and so need not be explicitly
-brought up, but this isn't always the case.) Once you've done this, typing
-``ifconfig`` should show that all the interfaces have IP addresses.
-
-Installing the Server Test Suite Packages
------------------------------------------
-
-Three methods of installing the Server Test Suite exist:
-
--  Automatically by the MAAS server
-
--  Using APT to retrieve the Server Test Suite packages on a SUT with
-   full Internet access
-
--  By loading the Server Test Suite Debian packages from a USB flash
-   drive or other medium you bring with you to the test site
-
-If MAAS is fully configured as described in the `MAAS Advanced NUC
-Installation and Configuration (MANIAC)` document, it should deploy the
-Server Test Suite automatically. If MAAS doesn't deploy the Server Test
-Suite properly, you can do so manually, as described in `Appendix A -
-Installing the Server Test Suite Manually`_.
-
-Creating a Hardware Entry on C3
-===============================
-
-In order to upload test results to the certification web site
-(http://certification.canonical.com, or C3 for short) you need to create a
-hardware entry for the system which you will be certifying. If the SUT has
-no direct Internet connection, you can put off creating the C3 entry until
-after the test (although doing it before testing is fine, too). If you
-don't plan to submit the results, you should not create a C3 entry for the
-machine. To create an entry you can go directly to:
-
-https://certification.canonical.com/hardware/create-system
-
-If you have problems accessing this site, contact your account manager.
-
-When creating an entry, you must enter assorted pieces of information:
-
-#. Fill in the details:
-
-   * **Account** -- The name of your account. If the account is incorrect
-     or can't be set, please contact your account manager for assistance.
-     This field is never published; it is for internal use only.
-
-   * **Make** -- The manufacturer of the system, e.g. Dell, HP, as you
-     would like it to appear on the public web site.
-
-   * **Model** -- The name of the system itself, e.g ProLiant DL630 or
-     PowerEdge R210, as you would like it to appear on the public web site.
-
-   * **Aliases** -- This is used for alternate marketing names for a
-     server. This field is only accessible to the Canonical Server
-     Certification Team.  If you need to add items to this field, please
-     contact your account manager. These do appear publicly as separate
-     entries in the database (e.g. Server1000, Alias1001 and Alias1002 all
-     point to the same system, but appear as three separate entries on the
-     public web site).
-
-   * **Codenames** -- This is for your internal reference and use and is
-     for the internal code name associated with the SUT. This data is
-     *never* published and is visible only to you and to Canonical.
-
-   * **Web site** -- Optional, link to the system info on the
-     manufacturer's web site. This field is published publicly and is a way
-     for potential customers to directly access information about your
-     hardware on your own web site.
-
-   * **Comment** -- Optional, any comment you want to make about the
-     hardware, including things like tester name, test location, etc. 
-     These comments are never made public, they are for internal use only.
-
-   * **Form factor** -- The type of system: Laptop, Server, etc. This is
-     not published directly, but determines where your system is displayed
-     on the public site.  Client form factors appear in one place while
-     server form factors appear elsewhere on the public certification site.
-     You may select any of the Server form factors you like except for
-     Server SoC, which is reserved for System on Chip certifications.
-
-   * **Architecture** -- The CPU architecture of the SUT. This is used
-     internally and is not published.
-
-   * **Confidential** -- Defaults to False (unchecked). Check the box if
-     the system has not been publicly announced yet or should remain
-     unpublished for any reason. This will cause the entire entry to *not*
-     be published to the public web site.
-
-#. Click Submit.
-
-#. Note the "Secure ID for testing purposes" value. You'll need this
-   when submitting the test results. (Note that this value is unique for
-   each machine.)
-
-Running the Certification Tests
-===============================
-
-To initiate a testing session in a server:
-
-#. Connect to the server via SSH or log in at the console. A standard MAAS
-   installation creates a user called ``ubuntu``, as noted earlier. You can
-   test using either a direct console login or SSH, but an SSH login may be
-   disconnected by the network tests or for other reasons.
-
-#. Before testing you must ensure that all network ports are cabled to a
-   working LAN and configured in ``/etc/network/interfaces`` using the
-   appropriate configuration (static or DHCP) for your test environment.
-   If you edit this file, either reboot or bring up the interfaces you
-   add with ``ifup`` before running tests.
-
-#. If the SUT provides the suitable ports and drives, plug in a USB 2
-   stick, plug in a USB 3 stick, and insert a suitable data CD in the
-   optical drive. Note that USB testing is not required for blades that
-   provide USB ports only via specialized dongles. These media must remain
-   inserted *throughout the test run*, because the media tests will be
-   kicked off partway through the run.
-
-#. If the system doesn't have Internet access:
-
-   * Copy the image you downloaded from
-     http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-i386-disk1.img (as
-     noted in `Appendix A`) to any directory of the SUT.
-
-   * Supply the full path under the section labeled "environment" in
-     ``/etc/xdg/canonical-certification.conf``. For example::
-
-       [environment]
-       KVM_TIMEOUT:
-       KVM_IMAGE: /home/ubuntu/trusty-server-cloudimg-i386-disk1.img
-
-#. If necessary, edit the ``/etc/xdg/canonical-certification.conf`` file on
-   the SUT so as to specify your ``iperf`` server. For example::
-
-    TEST_TARGET_FTP = your-ftp-server.example.com
-    TEST_USER = anonymous
-    TEST_PASS =
-    TEST_TARGET_IPERF =  192.168.0.2
-
-   If you configured your MAAS server as described in the MANIAC document,
-   the ``TEST_TARGET_IPERF`` line should point to your SUT's gateway address,
-   which is normally also your MAAS server; but if your network
-   configuration deviates from the one described in MANIAC, you may need to
-   adjust this value. The Server Test Suite does not currently use FTP, but
-   these lines must be uncommented. They may be left at their default
-   values.
-
-#. While editing ``/etc/xdg/canonical-certification.conf``, you may
-   optionally enter the SUT's Secure ID in the ``[sru]`` section. This can
-   simplify submission of results at the end of the test; however, this
-   will work only if the SUT has full Internet access.
-
-#. Launch ``iperf`` on the server identified in the SUT's
-   ``/etc/xdg/canonical-certification.conf`` file by typing::
-
-    $ iperf -s
-
-#. If you're running the test via SSH, type screen on the SUT to ensure
-   that you can reconnect to your session should your link to the SUT go
-   down, as may happen when running the network tests. If you're
-   disconnected, you can reconnect to your session by logging in and
-   typing ``screen -r``. This step is not important if you're running the
-   Server Test Suite at the console.
-
-#. Run::
-
-    $ canonical-certification-server
-
-#. A welcome message will be displayed. Make sure to read the message
-   and follow its instructions.
-
-#. Press the Enter key. The system will display a Suite Selection
-   screen:
-
-   .. figure:: images/some_tests.png
-      :alt: The suite selection screen enables you to pick which
-            tests to run
-      :width: 100%
-
-#. Select the *Server-full-14.04* item and deselect the other items.
-   (These other suites exist to enable easy re-running of subsets of
-   tests that often fail in some environments.)
-
-#. Use the arrow keys to highlight the *<OK>* option and then press
-   Enter.
-
-#. After a few seconds, a test selection screen will appear, as shown
-   below. You should ordinarily leave all the tests selected. (Tests that
-   are irrelevant for a given computer, such as tests of the optical drive
-   on computers that lack this hardware, are automatically ignored.) If a
-   test is hanging or otherwise causing problems, please contact the
-   Canonical Server Certification Team for advice on how to proceed. Using
-   this screen is fairly straightforward, but `Appendix C - Using the Test
-   Selection Screen`_ covers the details.
-
-   .. figure:: images/ccs_tests.png
-      :alt: The suite selection screen enables you to pick which
-            tests to run
-      :width: 100%
-
-#. Press the *T* key to start testing. The screen will begin displaying a
-   scrolling set of technical details about the tests as they are
-   performed.
-
-#. The full test suite can take several hours to complete, depending on
-   the hardware configuration (amount of RAM, disk space, etc). During
-   this time the computer may be unresponsive. This is due to the
-   inclusion of some stress test cases. These are deliberately
-   intensive and produce high load on the system's resources.
-
-#. If at any time during the execution you are *sure* the computer has
-   crashed (or it reboots spontaneously) then after the system comes back
-   up you should run the ``canonical-certification-server`` command again
-   and respond `y` when asked if you want to resume the previous session.
-
-#. When the test run is complete, you should see a summary of tests run, a
-   note about where the ``submission.xml``, ``results.html``, and
-   ``results.xlsx`` files have been stored, and a prompt to submit the
-   results to ``certification.canonical.com``. If you're connected to the
-   Internet, typing ``y`` at this query should cause the results to be
-   submitted. You will need either a Secure ID value or to have already
-   entered this value in the ``/etc/xdg/canonical-certification.conf``
-   file.
-
-#. Copying the results files off of the SUT is advisable. This is most
-   important if the automatic submission of results fails; however,
-   having the results available as a backup can be useful because it
-   enables you to review the results off-line or in case of submission
-   problems that aren't immediately obvious. The results are stored in
-   the ``~/.local/share/plainbox`` directory.
-
-#. Copy the whole directory to an external medium and bring it with you
-   after certifying the system. It contains a file called
-   ``submission.xml`` which is the results of the testing as well as a file
-   called ``results.html`` that, if loaded in a web browser, will show you
-   the results.
-
-If you review your results by loading ``results.html`` in a web browser,
-you can quickly spot failed tests because they're highlighted in red with a
-"FAILED" notation in the Result column, whereas passed tests acquire a
-green color, with the word "PASSED." Note, however, that *a failed test
-does not necessarily denote a failed certification*. Reasons a test might
-fail but still enable a certification to pass include the following:
-
--  A test may be a greylist test, as described in the `Ubuntu Server
-   Hardware Certification Coverage` document, available from
-   https://certification.canonical.com.
-
--  Some tests are known to produce occasional false positives -- that
-   is, they claim that problems exist when in fact they don't.
-
--  Some test environments are sub-optimal, necessitating that specific
-   tests be re-run. This can happen with network tests or if the tester
-   forgot to insert a removable medium. In such cases, the specific test
-   can be re-run rather than the entire test suite.
-
-Consult your account manager if you have questions about specific test
-results.
-
-Manually Uploading Test Results to the Certification Site
-=========================================================
-
-If you can't upload test results to the certification site from the
-certification program itself, you must do so manually, perhaps from
-another computer. To upload the results, you should have the Server Test
-Suite and ``canonical-certification-submit`` installed on the system from
-which you plan to submit results. The Server Test Suite is part of the
-default install on all Ubuntu Desktop systems. At this time, there is no
-mechanism for submitting results from an OS other than Ubuntu.
-
-To add the Hardware Certification PPA, install
-``canonical-certification-submit``, and submit the results, follow these
-instructions:
-
-#. Add the Hardware Certification PPA::
-
-   $ sudo apt-add-repository ppa:hardware-certification/public
-   $ sudo apt-get update
-
-#. Install the package::
-
-   $ sudo apt-get install canonical-certification-submit
-
-#. Run the following command::
-
-    $ canonical-certification-submit --secure_id <SUT_SECURE_ID> \
-      <PATH_TO>/submission.xml
-
-   where:
-
-   -  ``<SUT_SECURE_ID>`` can be found on your system's page on the
-      certification web site (http://certification.canonical.com) by
-      looking next to "Secure ID for testing purposes":
-
-      .. image:: images/secure_id.png
-         :alt: The Secure ID can be obtained from the Ceritification web site.
-         :align: left
-         :width: 50%
-
-   -  ``<PATH_TO>`` refers to the location of the ``submission.xml file``
-      (which should be contained in the ``~/.local/share/plainbox``
-      directory you copied to the USB key).
-
-   -  Older versions of this tool used ``\-\-hwid`` rather than
-      ``\-\-secure_id``.
-
-You should see output similar to the following for a successful
-submission::
-
-  $ canonical-certification-submit --hwid a00D000000LU9Ji \
-     ~/.local/share/plainbox/submission.xml
-   2012-03-28 11:05:30,575 INFO     Preparing to submit results using Hardware
-                                    ID: a00D000000LU9Ji
-   2012-03-28 11:05:30,576 INFO     Getting messages
-   2012-03-28 11:05:56,726 INFO     Exchanged 8 of 8 messages
-   2012-03-28 11:05:56,726 INFO     Results have been successfully submitted.
-                                    To review your test results now, please
-                                    go to the following URL:
-               https://certification.canonical.com/submission/eFXnst3rVbBvdu2
-  
-Once results submission is complete, use the provided link in the output
-to review the results and confirm that they are correct.
-
-Requesting a Certificate
-========================
-
-Once you've uploaded the data to the certification site, you should
-review it in the web interface. If you're satisfied that there are no
-problems, you can request a certificate:
-
-#. Click the date link under the Created column in the Submissions
-   section. The result should be a page showing most of the same
-   information as the previous page, but in a different format, and
-   restricted to that one test run.
-
-#. Click the Request Certificate link. The result should be a page with
-   a few radio buttons in which you can enter information:
-
-   -  Status is fixed at In Progress.
-
-   -  Release indicates the Ubuntu release used for testing, and for which
-      the certificate will be issued.
-
-   -  Level indicates the type of certification:
-
-      -  Certified is for for hardware that's ready to be deployed with
-         Ubuntu.
-
-      -  Certified Pre-installed is for hardware that ships with a (possibly
-         customized) version of Ubuntu.
-
-   -  Is Private should be checked if the certification should be kept
-      private. Note that this check box affects the certificate only, not
-      the entry for the computer as a whole on
-      http://certification.canonical.com. Other public pre-existing
-      certificates, or those issued in the future, will remain public.
-
-#. Click Submit. You'll see a new screen in which you can (and in one
-   case *must*) enter more information. In particular, you can click:
-
-   -  Link Bug to link to a bug on https://bugs.launchpad.net.
-      This option is available only to Canonical engineers.
-
-   -  Create Note or Create Note from Template to create a note. Most
-      systems will have at least two notes:
-
-      -  *A note titled "Tester" with the name of the person who did the
-         testing is required.*
-
-      -  A note titled "Test Notes" is usually present. It describes
-         test-specific quirks, such as why a failure should be ignored
-         (say, if a network test failed because of local network problems
-         but succeeded on re-testing). If the
-         *miscellanea/get-maas-version* test fails, be sure to specify the
-         version of MAAS used to deploy the SUT.
-
-      In most cases, the "Private" check box should be checked for your
-      notes.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix A - Installing the Server Test Suite Manually
-======================================================
-
-Ordinarily, MAAS will install the Server Test Suite onto the SUT as part
-of the provisioning process, as described in the main body of this
-document. If the MAAS server is not configured to do this, though, you
-have two additional options for installing the Server Test Suite: You
-may use APT if the SUT has full Internet access or you may install
-the Server Test Suite from a tarball that you bring with you.
-
-Installing the Server Test Suite via APT
-----------------------------------------
-
-If your lab setup has Internet access, getting the testing tools is a
-pretty straightforward process, because you can install the necessary
-tools from the Ubuntu Hardware Certification PPA.
-
-Log in to the server locally or via SSH or KVM and run the following
-commands::
-
-  $ sudo apt-add-repository ppa:hardware-certification/public
-  $ sudo apt-add-repository ppa:firmware-testing-team/ppa-fwts-stable
-  $ sudo apt-get update
-  $ sudo apt-get install canonical-certification-server
-
-.. The ppa:hardware-certification/public should be stable. For
-   the development PPA, instead use ppa:checkbox-dev/ppa.
-
-If for some reason you want to  run the test suite from an Ubuntu live
-medium, you must also enable the universe repository::
-
-  $ sudo apt-add-repository universe
-
-Note that running the test suite from a live medium is not accepted for any
-certification attempt; this information is provided to help in unusual
-situations or when debugging problems that necessitate booting in this way.
-
-During the installation, you may be prompted for a password for ``mysql``.
-This can be set to anything you wish; it will not be used during testing.
-
-At this point, you should have the test suite and dependencies installed
-and be ready to begin testing.
-
-Bringing the Server Test Suite Packages With You
-------------------------------------------------
-
-If you do not have Internet access from your LAN, you can find the
-pre-built tarball including the Server Test Suite packages under:
-
-https://certification.canonical.com/offline
-
-Note that you will be asked for your account credentials when you access
-that URL.
-
-Copy the appropriate ``.tar.gz`` file to a USB stick and bring this with
-you when testing the system. You will also need to obtain and bring a copy
-of a bootable Ubuntu Cloud Image for the virtualization portion of the
-certification test.  You can obtain that here:
-
-http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-i386-disk1.img
-
-You can use another release of Ubuntu if this is convenient. An i386
-image is used even when you're testing 64-bit hardware. The point is to
-test that virtualization features work, not that a specific Ubuntu
-version or architecture is supported. Because the i386 image is more
-general, it's the one that we use in testing.
-
-To install the server certification packages from the copied tarball,
-perform the following steps on the SUT:
-
-#. Insert the USB drive on which you placed the tarball.
-
-#. Extract the contents of the ``.tar.gz`` file from the USB stick to a
-   temporary directory (such as ``/tmp/``)::
-
-    $ tar -C /tmp -xzf ubuntu-14.04-server-amd64.tar.gz
-    $ cd /tmp
-
-#. Look for a directory whose name begins with ``apt-repo`` and switch to
-   it (note this is just an example, your exact directory name may be
-   different)::
-
-    $ cd apt-repo-ubuntu-14.04.1-server-amd64.iso-20140901-canonical-certification-ser
-
-4. Use a provided helper script to add a local package repository::
-
-    $ sudo ./add_offline_repository -u
-
-5. Install the Server Test Suite::
-
-    $ sudo apt-get install canonical-certification-server
-
-During the installation, you may be prompted for a password for ``mysql``.
-This can be set to anything you wish; it will not be used during testing.
-If you're asked about mail server configuration, respond that the mail
-server should not be configured.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix B - Re-Testing and Installing Updated Tests
-====================================================
-
-Occasionally, a test will fail, necessitating re-testing a feature. For
-instance, if you forget to insert a USB flash drive, the relevant USB
-tests will fail. The same thing will happen if a USB flash drive is
-defective or improperly prepared. Another common source of problems is
-network tests, which can fail because of busy LANs, flaky switches, bad
-cables, and so on. When this happens, you must re-run the relevant
-test(s).
-
-Although it's often possible to re-run a test by directly executing a
-single test script, the preferred method is:
-
-#. Re-run ``canonical-certification-server``.
-
-#. Use one of the abbreviated testing whitelists (such as *Network-only*)
-   or adjust the set of tests to be run (as described in `Appendix C`).
-
-#. Submit the resulting ``submission.xml`` file to the C3 site.
-
-You can then request a certificate based on the main results (the one with
-the most passed tests) and refer to the secondary set of results in the
-certificate notes. This procedure ensures that all the necessary data will
-be present on C3. It also ensures that (sometimes subtle) problems will be
-avoided; for instance, network tests may not be valid if network ports that
-are not being tested are active. The ``canonical-certification-server``
-framework ensures that such potential problems are avoided.
-
-From time to time, a test will be found to contain a bug or need to be
-updated to deal with a problem. In such cases, it is often impractical
-to wait for the fix to work its way down through Ubuntu's packaging
-system, or even through the PPAs in which some of the relevant tools are
-distributed. In such cases, the usual procedure for replacing the script
-or file is as follows:
-
-#. Consult with the Server Certification Team about the problem; *do
-   not* install an updated script from some other source!
-
-#. Obtain the updated file (typically a script) from the Server
-   Certification Team. Store it on the SUT in the home directory of the
-   test account. For instance, the new script might be
-   ``/home/ubuntu/newscript``. If necessary, give the new file execute
-   permissions.
-
-#. On the SUT, rename or delete the original file, as in::
-
-    $ sudo rm /usr/lib/2013.canonical.com\:checkbox/bin/oldscript
-
-#. Create a symbolic link from the new script to the original name, as
-   in::
-
-     $ sudo ln -s /home/ubuntu/newscript \
-       /usr/lib/2013.canonical.com\:checkbox/bin/oldscript
-
-#. Run the tests again, using the ``canonical-certification-server`` user
-   interface.
-
-In some cases, another procedure might be necessary; for instance, a bug
-fix might require installing a new Debian package with the dpkg command,
-or you might need to edit a configuration file. The Canonical Server
-Certification Team can advise you about such requirements.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix C - Using the Test Selection Screen
-============================================
-
-It may be necessary for you to deselect some of the tests which are to
-be run for certification. This is unlikely, though, and you should only
-do it when so instructed.
-
-The test selection screen looks like this:
-
-.. figure:: images/ccs_tests2.png
-   :alt: The test selection screen enables you to select the tests
-         you want to run.
-   :width: 100%
-
-Every test suite name is preceded by a brackets that contain either an
-*X* character or nothing to identify whether the test suite has been
-selected or not.
-
-Tests are arranged hierarchically. When a top-level test is highlighted,
-you can hide or reveal the details by pressing the Enter key; or you can
-select or deselect all the tests in that category by pressing the
-Spacebar. For instance, with *Benchmark tests* highlighted, as in the
-figure, pressing Enter will hide the lines up to *CPU tests*; and pressing
-the Spacebar will deactivate (or re-activate) all of the benchmark
-tests. You can select or de-select an individual test, such as the
-*hdparm-read_sda* test, by highlighting it and pressing the Spacebar.
-
-Once you've selected all the tests, press the *T* key to begin the testing
-process.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix D - Point Release Testing
-==================================
-
-Ordinarily, 14.04 certification requires testing two releases:
-
--  Ubuntu 14.04 GA -- That is, the version that was released in April of
-   2014.
-
--  The current point release -- That is, version 14.04.2 or whatever is
-   the latest release in the 14.04 series.
-
-In theory, compatibility will only improve with time, so a server might
-fail testing with 14.04 GA because it uses new hardware that had not
-been supported in April of 2014, but pass with the latest version. Such
-a server would be certified for that latest version, but not for the
-original GA release. If such a situation arises, testing should also be
-done with intervening releases so as to determine the earliest working
-version of Ubuntu.
-
-If a server fails certification with a more recent release but works
-with an earlier one, this situation is treated as a regression; a bug
-report should be filed and note made of the problem in the certificate
-request. Please notify your TPM about such problems to facilitate their
-resolution.
-
-Because Ubuntu 14.04.1 uses the same 3.13 kernel series as 14.04 GA,
-testing 14.04.1 is required only if 14.04 GA fails. (Although 14.04 GA
-and 14.04.1 use the same kernel series, 14.04.1 ships with a later
-kernel within that series, so it might fix a bug that blocks 14.04 GA
-certification.)
-
-If the procedure for installing point releases, as described in
-the MANIAC document (available from https://certification.canonical.com),
-fails, then you should consult the Server Certification Team.
-
-.. raw:: pdf
-
-   PageBreak
-
-Appendix E - Troubleshooting Tips
-=================================
-
-Submitting Results
-------------------
-
-If submitting results from the Server Test Suite itself fails, you can use
-the ``canonical-certification-submit`` program, as described earlier, in
-`Manually Uploading Test Results to the Certification Site`. You can try
-this on the SUT, but if network problems prevented a successful submission,
-you may need to bring the files out on a USB flash drive or other removable
-medium and submit them from a computer with better Internet connectivity.
-
-Inconsistent Message when Submitting Results
---------------------------------------------
-
-If you receive a message that looks like the following when using
-``canonical-certification-submit``, please be sure to save the
-``submission.xml`` file and contact your account manager::
-
-  2014-04-28 10:55:33,894 CRITICAL Error: Inconsistent message
-
-Network Problems
-----------------
-
-Network problems are common in testing. These problems can manifest as
-complete failures of all network tests or as failures of just some
-tests. Specific suggestions for fixing these problems include:
-
--  **Check cables and other hardware** -- Yes, this is very basic; but bad
-   cables can cause problems. For instance, one bad cable at Canonical
-   resulted in connections at 100Mbps rather than 1Gbps, and therefore
-   failures. Some of these failures were identified in the output as the
-   lack of a route to the host. Similarly, if a switch connecting the SUT
-   to the ``iperf`` server is deficient, it will affect the network test
-   results.
-
--  **Use the simplest possible network** -- Complex network setups and those
-   with heavy traffic from computers uninvolved in the testing or those
-   with multiple switches, bridges, etc., can create problems for
-   network testing. Simplifying the network in whatever way is practical
-   can improve matters.
-
--  **Check the iperf server** -- Ensure that the server computer is up and
-   that the ``iperf`` server program is running on it. Also ensure that the
-   computer has no issues. For instance, some versions of ``iperf``, when
-   run in daemon mode, cause the load average to go up every time a client
-   disconnects. This can bring even a powerful computer to its knees quite
-   quickly!
-
--  **Ensure the iperf server is on the SUT's local network** -- The
-   network tests temporarily remove the default route from the routing
-   table, so the ``iperf`` server must be on the same network segment as
-   the SUT.
-
--  **Check the SUT's network configuration** -- A failure to configure the
-   network ports in ``/etc/network/interfaces`` will cause a failure of the
-   network tests. Likewise, a failure to bring up a network interface
-   before testing will cause the test to fail, even if
-   ``canonical-certification-server`` detects the interface.
-
--  **Check your DHCP server** -- A sluggish or otherwise malfunctioning
-   DHCP server can delay bringing up the SUT's network interfaces (which
-   repeatedly go down and come up during testing). This in turn can cause
-   network testing failures.
-
-If you end up having to re-run the network tests, either do so from within
-``canonical-certification-server`` or be sure to bring down all the network
-interfaces except the one you're testing before using ``iperf`` manually.
-The way Linux manages network interfaces makes it difficult to ensure that
-network traffic will be restricted to a single network port if more than
-one is active.
-
-Issues During Testing
----------------------
-
-The testing process should be straightforward and complete without issue.
-Should you encounter issues during testing, please contact your account
-manager. Be sure to save the ``~/.local/share/plainbox`` and
-``~/.cache/plainbox`` directory trees as they will contain logs and other
-data that will help the Server Certification Team determine if the issue is
-a testing issue or a hardware issue that will affect the certification
-outcome.
-
-If possible, please also save a copy of any terminal output or
-tracebacks you notice to a text file and save that along with the
-previously-noted directories. (Feel free to send us a photo of the
-screen taken with a digital camera.)
-

=== removed directory 'documentation/images'
=== removed file 'documentation/images/ccs_tests.png'
Binary files documentation/images/ccs_tests.png	2015-07-17 19:42:06 +0000 and documentation/images/ccs_tests.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/ccs_tests2.png'
Binary files documentation/images/ccs_tests2.png	2015-07-17 19:42:06 +0000 and documentation/images/ccs_tests2.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/clusters-page.png'
Binary files documentation/images/clusters-page.png	2015-07-17 19:42:06 +0000 and documentation/images/clusters-page.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/cover-background.png'
Binary files documentation/images/cover-background.png	2015-07-17 19:42:06 +0000 and documentation/images/cover-background.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/cover-background.xcf'
Binary files documentation/images/cover-background.xcf	2015-07-17 19:42:06 +0000 and documentation/images/cover-background.xcf	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/custom-image-selection.png'
Binary files documentation/images/custom-image-selection.png	2015-07-17 19:42:06 +0000 and documentation/images/custom-image-selection.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/interfaces.png'
Binary files documentation/images/interfaces.png	2015-07-17 19:42:06 +0000 and documentation/images/interfaces.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/logo-canonical_no-tm-white-hex.png'
Binary files documentation/images/logo-canonical_no-tm-white-hex.png	2015-07-17 19:42:06 +0000 and documentation/images/logo-canonical_no-tm-white-hex.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/logo-ubuntu_su-white_orange-hex.png'
Binary files documentation/images/logo-ubuntu_su-white_orange-hex.png	2015-07-17 19:42:06 +0000 and documentation/images/logo-ubuntu_su-white_orange-hex.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/logo-ubuntu_su-white_orange-hex.svg'
--- documentation/images/logo-ubuntu_su-white_orange-hex.svg	2015-07-17 19:42:06 +0000
+++ documentation/images/logo-ubuntu_su-white_orange-hex.svg	1970-01-01 00:00:00 +0000
@@ -1,25 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- Generator: Adobe Illustrator 15.0.2, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
-<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
-<svg version="1.1" id="ubuntu__x5F__white_x26_orange" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="425.197px" height="209.764px" viewBox="0 0 425.197 209.764" enable-background="new 0 0 425.197 209.764" xml:space="preserve">
-<g>
-</g>
-<g>
-</g>
-<g>
-</g>
-<g>
-</g>
-<g>
-	<circle fill="#DD4814" cx="337.365" cy="90.017" r="16.966"/>
-	<path fill="#FFFFFF" d="M326.783,87.978c-1.127,0-2.036,0.912-2.036,2.039c0,1.123,0.909,2.037,2.036,2.037   c1.128,0,2.039-0.914,2.039-2.037C328.822,88.89,327.911,87.978,326.783,87.978z M341.338,97.244   c-0.976,0.559-1.308,1.807-0.747,2.779c0.563,0.977,1.809,1.309,2.784,0.748c0.975-0.562,1.31-1.809,0.747-2.783   C343.559,97.013,342.312,96.679,341.338,97.244z M331.213,90.017c0-2.016,0.998-3.797,2.529-4.873l-1.488-2.498   c-1.784,1.191-3.112,3.014-3.664,5.148c0.646,0.525,1.055,1.324,1.055,2.223c0,0.893-0.408,1.691-1.055,2.219   c0.552,2.133,1.88,3.955,3.664,5.146l1.488-2.496C332.211,93.81,331.213,92.031,331.213,90.017z M337.165,84.06   c3.112,0,5.663,2.385,5.931,5.43l2.905-0.047c-0.144-2.244-1.124-4.26-2.631-5.742c-0.776,0.291-1.672,0.25-2.445-0.199   c-0.773-0.447-1.26-1.199-1.394-2.02c-0.754-0.207-1.547-0.322-2.366-0.322c-1.408,0-2.741,0.332-3.922,0.918l1.415,2.537   C335.42,84.259,336.271,84.06,337.165,84.06z M337.165,95.968c-0.895,0-1.745-0.197-2.507-0.553l-1.415,2.537   c1.181,0.588,2.514,0.916,3.922,0.916c0.819,0,1.612-0.111,2.366-0.32c0.134-0.82,0.62-1.572,1.394-2.021   c0.775-0.447,1.669-0.49,2.445-0.195c1.507-1.484,2.487-3.5,2.631-5.746l-2.905-0.041   C342.828,93.585,340.277,95.968,337.165,95.968z M341.338,82.789c0.974,0.561,2.221,0.229,2.782-0.748   c0.563-0.971,0.229-2.219-0.745-2.781c-0.976-0.562-2.221-0.229-2.784,0.746C340.03,80.98,340.362,82.226,341.338,82.789z"/>
-	<g>
-		<path fill="#FFFFFF" d="M104.798,134.53c-1.725,0.432-3.999,0.889-6.826,1.374c-2.83,0.483-6.102,0.726-9.817,0.726    c-3.23,0-5.952-0.472-8.159-1.413c-2.209-0.941-3.986-2.274-5.332-3.998c-1.348-1.724-2.316-3.757-2.908-6.101    c-0.594-2.341-0.889-4.939-0.889-7.795V93.734h7.513v21.973c0,5.117,0.808,8.779,2.424,10.986    c1.616,2.211,4.334,3.314,8.159,3.314c0.809,0,1.642-0.029,2.505-0.083c0.86-0.053,1.67-0.122,2.425-0.202    c0.752-0.081,1.439-0.161,2.059-0.242c0.619-0.08,1.064-0.173,1.334-0.283V93.734h7.514V134.53z"/>
-		<path fill="#FFFFFF" d="M123.134,95.591c0.915-0.592,2.304-1.211,4.161-1.857s3.999-0.969,6.422-0.969    c3.016,0,5.696,0.539,8.039,1.615c2.342,1.078,4.322,2.584,5.938,4.523c1.614,1.939,2.839,4.256,3.675,6.947    c0.834,2.695,1.253,5.656,1.253,8.888c0,3.392-0.5,6.45-1.494,9.168c-0.999,2.72-2.412,5.021-4.242,6.907    c-1.832,1.885-4.039,3.34-6.625,4.362c-2.584,1.023-5.493,1.535-8.725,1.535c-3.502,0-6.598-0.244-9.289-0.728    c-2.693-0.485-4.902-0.97-6.625-1.454V74.347l7.513-1.293V95.591z M123.134,129.197c0.755,0.216,1.818,0.42,3.192,0.605    c1.373,0.191,3.082,0.284,5.129,0.284c4.039,0,7.271-1.334,9.693-3.999c2.425-2.666,3.637-6.45,3.637-11.349    c0-2.153-0.216-4.173-0.646-6.062c-0.432-1.883-1.132-3.514-2.102-4.885c-0.969-1.375-2.222-2.451-3.756-3.232    s-3.38-1.172-5.533-1.172c-2.049,0-3.932,0.352-5.654,1.051c-1.727,0.701-3.045,1.428-3.96,2.182V129.197z"/>
-		<path fill="#FFFFFF" d="M194.546,134.53c-1.725,0.432-4,0.889-6.826,1.374c-2.827,0.483-6.1,0.726-9.816,0.726    c-3.23,0-5.95-0.472-8.158-1.413c-2.209-0.941-3.986-2.274-5.331-3.998c-1.348-1.724-2.315-3.757-2.909-6.101    c-0.593-2.341-0.889-4.939-0.889-7.795V93.734h7.512v21.973c0,5.117,0.809,8.779,2.424,10.986    c1.617,2.211,4.336,3.314,8.159,3.314c0.81,0,1.644-0.029,2.505-0.083c0.859-0.053,1.668-0.122,2.424-0.202    c0.754-0.081,1.44-0.161,2.061-0.242c0.618-0.08,1.062-0.173,1.331-0.283V93.734h7.514V134.53z"/>
-		<path fill="#FFFFFF" d="M205.37,94.947c1.723-0.432,4.01-0.889,6.867-1.375c2.852-0.484,6.138-0.727,9.854-0.727    c3.34,0,6.113,0.473,8.32,1.414c2.208,0.943,3.972,2.262,5.293,3.959c1.317,1.695,2.246,3.729,2.786,6.098    c0.538,2.373,0.808,4.984,0.808,7.837v23.588h-7.513v-21.973c0-2.584-0.176-4.791-0.525-6.624    c-0.351-1.833-0.929-3.313-1.737-4.442c-0.808-1.133-1.885-1.953-3.231-2.465c-1.346-0.514-3.018-0.768-5.007-0.768    c-0.811,0-1.645,0.027-2.504,0.08c-0.862,0.055-1.686,0.121-2.464,0.203c-0.784,0.08-1.481,0.176-2.102,0.281    c-0.62,0.109-1.063,0.189-1.333,0.242v35.464h-7.512V94.947z"/>
-		<path fill="#FFFFFF" d="M256.665,93.734h15.914v6.301h-15.914v19.388c0,2.1,0.161,3.84,0.485,5.212s0.809,2.451,1.454,3.229    c0.646,0.781,1.452,1.333,2.423,1.656c0.97,0.324,2.1,0.487,3.392,0.487c2.314,0,4.147-0.258,5.494-0.771    c1.345-0.511,2.262-0.874,2.748-1.09l1.614,6.141c-0.755,0.378-2.088,0.863-3.999,1.453c-1.912,0.593-4.078,0.889-6.502,0.889    c-2.856,0-5.212-0.362-7.07-1.089c-1.856-0.729-3.351-1.817-4.482-3.273c-1.131-1.453-1.925-3.243-2.382-5.372    c-0.46-2.126-0.688-4.59-0.688-7.391V82.021l7.513-1.293V93.734z"/>
-		<path fill="#FFFFFF" d="M313.455,134.53c-1.726,0.432-3.999,0.889-6.826,1.374c-2.827,0.483-6.101,0.726-9.814,0.726    c-3.232,0-5.952-0.472-8.161-1.413s-3.986-2.274-5.33-3.998c-1.348-1.724-2.316-3.757-2.91-6.101    c-0.592-2.341-0.889-4.939-0.889-7.795V93.734h7.515v21.973c0,5.117,0.808,8.779,2.424,10.986    c1.614,2.211,4.334,3.314,8.159,3.314c0.807,0,1.641-0.029,2.504-0.083c0.859-0.053,1.667-0.122,2.422-0.202    c0.754-0.081,1.441-0.161,2.061-0.242c0.617-0.08,1.063-0.173,1.334-0.283V93.734h7.513V134.53z"/>
-	</g>
-</g>
-</svg>
\ No newline at end of file

=== removed file 'documentation/images/maas-dropdown.png'
Binary files documentation/images/maas-dropdown.png	2015-07-17 19:42:06 +0000 and documentation/images/maas-dropdown.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/maniac-network.fig'
--- documentation/images/maniac-network.fig	2015-07-17 19:42:06 +0000
+++ documentation/images/maniac-network.fig	1970-01-01 00:00:00 +0000
@@ -1,1157 +0,0 @@
-#FIG 3.2  Produced by xfig version 3.2.5c
-Landscape
-Center
-Metric
-A4      
-70.00
-Single
--2
-1200 2
-0 32 #c6b797
-0 33 #eff8ff
-0 34 #dccba6
-0 35 #404040
-0 36 #808080
-0 37 #c0c0c0
-0 38 #e0e0e0
-0 39 #8e8f8e
-0 40 #aaaaaa
-0 41 #555555
-0 42 #c7c3c7
-0 43 #565151
-0 44 #8e8e8e
-0 45 #d7d7d7
-0 46 #85807d
-0 47 #d2d2d2
-0 48 #3a3a3a
-0 49 #4573aa
-0 50 #aeaeae
-0 51 #7b79a5
-0 52 #444444
-0 53 #73758c
-0 54 #f7f7f7
-0 55 #414541
-0 56 #635dce
-0 57 #bebebe
-0 58 #515151
-0 59 #e7e3e7
-0 60 #000049
-0 61 #797979
-0 62 #303430
-0 63 #414141
-0 64 #c7b696
-0 65 #9e9e9e
-0 66 #868286
-0 67 #717571
-0 68 #aeaaae
-0 69 #c7c7c7
-0 70 #757575
-0 71 #f3f3f3
-# Drawn by Markus Laner 2010 March
-6 180 2520 2205 3735
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 999 2810 1343 2596 1728 2939
-	 0.000 -1.000 0.000
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 1684 2853 2071 2853 2114 3281
-	 0.000 -1.000 0.000
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 1170 3581 828 3710 657 3496
-	 0.000 -1.000 0.000
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 657 3496 228 3281 571 3024
-	 0.000 -1.000 0.000
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 2068 3248 2156 3410 1939 3462
-	 0.000 -1.000 0.000
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 1942 3453 1684 3710 1128 3539
-	 0.000 -1.000 0.000
-3 2 0 2 0 7 50 -1 -1 0.000 0 0 0 3
-	 486 3068 574 2714 1088 2842
-	 0.000 -1.000 0.000
--6
-# Laptop computer
-6 3629 2475 4905 3870
-1 1 0 1 0 7 50 0 -1 0.000 1 0.0000 4202 3830 30 18 4202 3830 4232 3849
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 8
-	 3717 2483 3711 3191 3879 3191 3879 3123 4592 3123 4592 3198
-	 4754 3198 4768 2479
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 16
-	 3715 3194 3636 3767 3910 3814 3916 3803 4619 3794 4640 3805
-	 4688 3804 4891 3767 4903 3757 4900 3744 4744 3198 4648 3198
-	 4648 3210 3808 3208 3808 3190 3715 3190
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 9
-	 3638 3769 3644 3820 3913 3863 3924 3856 4610 3849 4629 3858
-	 4662 3858 4870 3811 4902 3760
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4767 2479 3721 2483 3719 2482
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3752 2521 4722 2517 4716 3090 3745 3095 3752 2519
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3760 3348 3760 3363 3840 3363 3841 3350
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3763 3345 3835 3345 3836 3358 3762 3358 3763 3344
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3774 3232 4105 3233 4105 3257 3773 3257 3775 3232
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3700 3394 4782 3395 4872 3732 3661 3747 3700 3395
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4180 3799 4182 3760 4375 3759 4377 3795
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4207 3775 4350 3775 4350 3787 4207 3787 4207 3775
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3711 3375 3731 3375 3731 3389 3711 3388 3711 3375
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3974 3686 3974 3719 4331 3718 4332 3684 3974 3686
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 3973 3719 3953 3742 3954 3680 4351 3677 4351 3739 4331 3719
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3865 3686 3865 3717 3937 3717 3937 3685 3865 3685
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 3865 3686 3849 3680 3849 3744 3950 3744 3950 3679 3849 3679
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3849 3744 3865 3717
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3949 3743 3937 3718
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3938 3684 3949 3680
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3769 3741 3769 3679 3850 3679
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3769 3743 3848 3743
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3787 3686 3769 3679
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3834 3687 3848 3680
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3833 3714 3848 3743
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3788 3714 3770 3742
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3772 3293 3837 3293 3837 3320 3772 3320 3772 3293
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3787 3686 3834 3686 3834 3714 3787 3714 3787 3686
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3686 3688 3754 3688 3754 3720 3686 3720 3686 3688
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3673 3679 3769 3679 3769 3742 3673 3742 3673 3679
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3673 3742 3686 3720
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 3686 3718
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3673 3679 3686 3688
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3769 3680 3754 3688
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3768 3742 3754 3719
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3954 3682 3973 3686
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4352 3678 4427 3678 4427 3737 4352 3737 4352 3678
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4427 3678 4514 3678 4514 3737 4427 3737 4427 3678
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4515 3677 4579 3677 4590 3735
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4590 3735
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4584 3677 4595 3735 4632 3735 4620 3678 4584 3678
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4367 3686 4419 3686 4419 3718 4367 3718 4367 3686
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4444 3686 4503 3686 4503 3719 4444 3719 4444 3686
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4534 3689 4579 3689 4579 3723 4534 3723 4534 3689
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4352 3738 4366 3717
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4351 3679 4367 3686
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4368 3686
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4428 3678 4418 3686
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4428 3738 4418 3718
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4429 3737 4444 3719
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4427 3678 4445 3686
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4515 3678 4503 3686
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4514 3737 4503 3719
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4516 3737 4535 3722
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4515 3678 4535 3689
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4579 3678 4578 3690
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4588 3734 4578 3722
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4592 3619 4607 3675 4693 3673 4676 3614 4590 3615 4592 3619
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4614 3627 4621 3659 4678 3659 4670 3624 4613 3625 4614 3627
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4626 3681 4639 3735 4709 3733 4696 3678 4626 3679 4626 3681
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4652 3689 4659 3719 4698 3719 4691 3686 4652 3687 4652 3689
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4687 3614 4702 3671 4767 3670 4754 3612 4687 3613 4687 3614
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4705 3679 4718 3733 4788 3732 4771 3675 4705 3675 4705 3679
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4709 3624 4716 3654 4756 3653 4749 3621 4710 3621 4709 3624
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4727 3685 4734 3711 4775 3711 4766 3681 4727 3681 4727 3685
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4778 3675 4793 3733 4864 3732 4848 3669 4777 3671 4778 3675
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4799 3684 4805 3711 4847 3711 4841 3681 4799 3682 4799 3684
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4762 3614 4775 3668 4845 3666 4831 3612 4762 3613 4762 3614
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4781 3627 4787 3649 4832 3649 4827 3623 4781 3624 4781 3627
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4515 3621 4525 3671 4600 3671 4587 3616 4517 3616 4515 3621
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4442 3615 4449 3670 4520 3669 4509 3616 4442 3616 4442 3615
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4460 3627 4463 3653 4504 3652 4500 3624 4460 3626 4460 3627
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4535 3627 4540 3647 4584 3647 4577 3622 4533 3623 4535 3627
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4618 3565 4631 3607 4752 3607 4739 3558 4617 3556 4618 3565
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4639 3566 4646 3588 4738 3588 4732 3566 4639 3565 4639 3566
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4749 3564 4759 3607 4828 3604 4818 3560 4749 3560 4749 3564
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4735 3508 4746 3556 4816 3555 4802 3500 4734 3501 4735 3508
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4722 3457 4730 3497 4801 3497 4789 3453 4721 3452 4722 3457
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4663 3503 4727 3503 4738 3552 4674 3552 4663 3503
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4591 3501 4653 3503 4666 3549 4601 3550 4590 3503 4591 3501
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4764 3570 4769 3592 4818 3592 4813 3568 4764 3570
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4755 3514 4759 3537 4806 3537 4800 3509 4754 3511 4755 3514
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4743 3462 4745 3482 4791 3482 4787 3460 4743 3460 4743 3462
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4450 3670 4463 3653
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4442 3616 4460 3626
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4509 3616 4499 3625
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4521 3669 4503 3651
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4527 3673 4540 3646
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4516 3616 4535 3624
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4588 3616 4577 3623
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4599 3673 4584 3647
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4608 3675 4621 3659
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4590 3616 4614 3626
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4676 3615 4671 3626
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4694 3674 4677 3658
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4704 3672 4717 3654
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4689 3614 4710 3623
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4755 3614 4749 3621
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4766 3671 4756 3653
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4776 3668 4788 3648
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4764 3614 4782 3624
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4832 3614 4828 3624
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4846 3667 4833 3648
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4759 3607 4769 3591
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4750 3561 4765 3570
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4819 3561 4813 3569
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4829 3605 4819 3591
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4638 3734 4659 3719
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4625 3680 4653 3688
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4710 3732 4699 3719
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4697 3680 4692 3685
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4705 3676 4728 3683
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4718 3734 4735 3711
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4788 3732 4774 3711
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4772 3676 4766 3682
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4777 3672 4800 3683
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4795 3733 4806 3711
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4863 3732 4847 3711
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4848 3671 4842 3682
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4608 3512 4650 3512 4655 3538 4612 3539 4607 3512 4608 3512
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4678 3513 4722 3512 4726 3541 4686 3542 4678 3514 4678 3513
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 8
-	 4612 3455 4622 3497 4723 3497 4719 3470 4714 3449 4629 3449
-	 4613 3454 4612 3455
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4629 3451 4633 3472 4718 3470
-2 3 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 7
-	 4540 3452 4549 3501 4618 3499 4609 3456 4602 3449 4550 3451
-	 4540 3452
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4551 3450 4557 3478 4603 3476 4602 3450
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4634 3473 4623 3496
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4557 3479 4551 3499
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4605 3477 4617 3497
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4515 3506 4525 3555 4592 3553 4580 3503 4516 3502
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4532 3509 4535 3535 4578 3534 4573 3510 4533 3510
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4533 3512 4515 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4537 3535 4526 3555
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4578 3535 4591 3552
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4574 3510 4578 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4543 3561 4554 3612 4625 3611 4611 3558 4543 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4555 3612 4567 3588 4607 3587 4625 3610
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4567 3587 4562 3565 4608 3563 4608 3586
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4561 3565 4545 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4608 3565 4611 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4472 3452 4480 3500 4547 3500 4538 3449 4471 3450
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4481 3499 4493 3482 4536 3483 4545 3499
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4493 3482 4486 3454 4472 3451
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4488 3455 4533 3454 4539 3451
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4533 3456 4535 3482
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4445 3505 4452 3558 4525 3556 4512 3503 4444 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4453 3557 4466 3533 4508 3532 4524 3556
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4467 3532 4461 3510 4446 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4462 3510 4509 3510 4513 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4509 3510 4509 3532
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4470 3562 4478 3612 4552 3613 4538 3560 4470 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4478 3612 4493 3591 4533 3589 4552 3612
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4494 3589 4493 3572 4472 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4494 3571 4533 3571 4538 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4534 3572 4534 3589
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4364 3621 4369 3675 4446 3675 4437 3620 4363 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4366 3627
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4369 3675 4387 3652 4429 3652 4446 3676
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4389 3651 4385 3633 4365 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4385 3632 4426 3631 4437 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4429 3651 4426 3630
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4426 3633
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4395 3562 4400 3615 4472 3612 4465 3558 4394 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4400 3614 4418 3596 4457 3596 4472 3612 4470 3612
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4395 3559 4418 3571 4418 3596
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4418 3571 4456 3570 4465 3558
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4457 3570 4456 3595
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4399 3449 4406 3500 4473 3499 4467 3449 4398 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4408 3501 4420 3477 4459 3476 4473 3500
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4400 3450 4419 3461 4421 3478
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4419 3461 4460 3461 4460 3477
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4460 3461 4468 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4369 3506 4376 3558 4450 3557 4442 3504 4369 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4377 3558 4392 3535 4434 3535 4451 3557
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4393 3535 4391 3517 4369 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4391 3516 4432 3516 4443 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4433 3516 4433 3535
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4633 3608 4647 3588
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4601 3551 4613 3540
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4617 3558 4640 3566
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4739 3558 4731 3566
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4666 3549 4655 3538
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4654 3502 4651 3513
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4591 3503 4608 3512
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4664 3502 4678 3512
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4674 3552 4686 3542
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4739 3551 4726 3542
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4727 3502 4722 3512
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4724 3512
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4730 3497 4745 3481
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4722 3453 4744 3461
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4791 3453 4787 3460
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4802 3497 4792 3481
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4752 3606 4738 3588
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4749 3557 4760 3536
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4736 3502 4756 3511
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4804 3500 4801 3510
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4817 3555 4806 3536
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4321 3562 4325 3614 4398 3615 4391 3560 4321 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4326 3614 4339 3596 4383 3595 4398 3614
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4339 3596 4339 3571 4323 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4339 3572 4382 3572 4390 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4382 3572 4383 3596
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4286 3618 4291 3678 4367 3676 4362 3619 4285 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4290 3677 4305 3658 4350 3659 4367 3676
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4351 3658 4350 3632 4362 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4350 3631 4303 3632 4304 3658
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4303 3632 4287 3619
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4246 3560 4248 3614 4322 3614 4316 3560 4246 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4249 3614 4264 3596 4304 3595 4323 3614
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4264 3596 4263 3571 4246 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4265 3571 4304 3570 4316 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4304 3571 4304 3596
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4210 3618 4210 3675 4288 3675 4283 3619 4210 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4210 3675 4227 3655 4273 3655 4286 3675 4285 3675
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4228 3654 4225 3633 4210 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4224 3632 4273 3632 4283 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4273 3632 4273 3655
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4296 3505 4301 3557 4373 3556 4364 3503 4295 3505
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4303 3556 4315 3537 4359 3537 4372 3556
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4315 3537 4313 3516 4297 3505
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4314 3514 4360 3513 4364 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4360 3515 4359 3537
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 4327 3452 4332 3499 4400 3499 4393 3449 4327 3449 4327 3452
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4333 3499 4344 3483 4388 3482 4401 3498
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4388 3482 4386 3459 4392 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4385 3459 4340 3459 4344 3482
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4339 3458 4327 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4254 3445 4259 3498 4327 3498 4318 3446 4254 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4258 3498 4272 3483 4311 3482 4326 3497
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4254 3447 4269 3454 4272 3483
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4271 3454 4311 3454 4320 3445
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4313 3454 4313 3482
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4220 3504 4223 3557 4299 3556 4290 3504 4221 3505
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4224 3557 4239 3538 4283 3538 4299 3555
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4239 3538 4237 3517 4221 3505
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4239 3517 4283 3518 4290 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4283 3519 4282 3538
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4182 3450 4183 3498 4254 3497 4248 3448 4182 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4183 3497 4195 3483 4242 3482 4253 3497
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4195 3484 4193 3456 4182 3448
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4195 3456 4242 3456 4248 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4242 3458 4244 3482
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4147 3505 4149 3556 4219 3556 4215 3504 4147 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4149 3556 4161 3543 4208 3542 4219 3556
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4162 3542 4159 3516 4149 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4159 3515 4208 3515 4214 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4208 3516 4207 3542
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4165 3561 4165 3610 4244 3612 4239 3560 4165 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4165 3612 4180 3599 4232 3598 4243 3611
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4180 3599 4180 3571 4166 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4177 3569 4233 3569 4239 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4239 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4233 3571 4233 3598
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4128 3618 4132 3675 4205 3674 4201 3617 4128 3617
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4133 3674 4146 3659 4193 3659 4203 3673
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4146 3659 4144 3629 4128 3617
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4146 3629 4191 3629 4201 3617
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4191 3630 4193 3659
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4107 3451 4111 3496 4178 3496 4172 3449 4106 3449
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4111 3494 4122 3482 4167 3482 4177 3495
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4123 3482 4121 3460 4108 3450
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4122 3460 4165 3460 4172 3450
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4167 3460 4167 3482
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4071 3502 4073 3555 4146 3556 4140 3504 4071 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4074 3555 4087 3537 4131 3536 4146 3555
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4088 3535 4087 3516 4072 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4088 3516 4131 3516 4140 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4131 3516 4131 3536
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4089 3561 4090 3613 4161 3612 4160 3561 4089 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4091 3614 4104 3599 4151 3599 4161 3612
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4105 3598 4105 3571 4089 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4105 3571 4153 3571 4160 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4154 3571 4152 3599
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4051 3618 4053 3676 4127 3675 4124 3618 4051 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4053 3676 4070 3658 4115 3657 4127 3675
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4072 3658 4069 3631 4051 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4070 3630 4115 3630 4124 3617
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4115 3630 4115 3658
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4036 3447 4036 3499 4102 3499 4098 3446 4036 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4035 3499 4048 3483 4089 3483 4102 3498
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4050 3483 4050 3456 4036 3445
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4050 3455 4090 3455 4098 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4090 3455 4089 3484
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3998 3503 3997 3555 4068 3555 4065 3503 3998 3502
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3997 3555 4012 3538 4056 3538 4068 3555
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4013 3538 4013 3513 3999 3502
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4016 3512 4056 3512 4066 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4057 3513 4056 3538
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4013 3559 4013 3614 4083 3614 4084 3560 4014 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4013 3613 4026 3599 4074 3599 4084 3613
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4028 3599 4027 3573 4014 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 4028 3573 4074 3573 4084 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4074 3573 4074 3599
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 3975 3618 3975 3676 4047 3676 4047 3618 3975 3618 3976 3617
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3976 3674 3990 3651 4036 3651 4047 3676
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3990 3651 3991 3630 3976 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3991 3630 4033 3630 4047 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4034 3630 4035 3651
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3956 3498 4031 3498 4028 3448 3957 3447 3958 3497
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3958 3498 3976 3479 4015 3478 4031 3497
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3976 3479 3975 3451 3957 3447
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3976 3451 4020 3452 4029 3448
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4029 3450
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4020 3453 4016 3479
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3894 3616 3895 3676 3969 3676 3969 3617 3894 3615
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3896 3676 3911 3658 3952 3658 3969 3675
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3952 3658 3952 3624 3969 3616
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3951 3623 3909 3624 3895 3616
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3910 3625 3912 3659
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3936 3561 3936 3612 4010 3612 4006 3559 3936 3558
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3937 3612 3949 3596 3997 3596 4010 3612
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3997 3595 3998 3563 4006 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3949 3595 3948 3563 3936 3559
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3949 3564 3997 3564
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3922 3507 3922 3553 3993 3553 3993 3504 3921 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3921 3552 3933 3536 3982 3536 3994 3552
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3982 3535 3982 3509 3993 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3982 3509 3933 3508 3921 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3933 3535 3933 3508
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3885 3445 3885 3499 3955 3499 3952 3446 3887 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3885 3499 3900 3479 3940 3479 3954 3499
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3940 3479 3941 3450 3953 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3941 3449 3900 3449 3885 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3899 3450 3900 3479
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3815 3448 3814 3498 3880 3498 3879 3446 3815 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3815 3497 3826 3479 3868 3478 3880 3498
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3868 3478 3868 3449 3879 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3868 3450 3828 3449 3828 3478
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3828 3449 3814 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3847 3503 3845 3558 3915 3558 3917 3503 3847 3501
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3844 3557 3859 3537 3903 3537 3915 3558
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3903 3537 3903 3510 3917 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3903 3510 3857 3510 3858 3536
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3858 3510 3846 3502
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3861 3561 3861 3611 3932 3611 3932 3560 3861 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3862 3611 3876 3594 3921 3594 3931 3610
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3922 3594 3921 3564 3931 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3923 3564 3873 3564 3876 3595
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3874 3564 3861 3560
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 3819 3621 3819 3674 3891 3673 3891 3619 3819 3618 3819 3623
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 3819 3630
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3819 3674 3832 3654 3878 3654 3890 3672
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 3887 3669
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3878 3655 3879 3624 3891 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3880 3625 3829 3624 3831 3654
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3831 3625 3819 3618
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3781 3562 3782 3614 3859 3615 3855 3561 3781 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3783 3615 3796 3594 3845 3594 3859 3614
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3845 3594 3845 3567 3856 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3845 3567 3793 3567 3796 3593
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3794 3567 3781 3562
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 6
-	 3770 3507 3769 3559 3844 3558 3843 3502 3770 3502 3770 3507
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3771 3558 3781 3538 3827 3538 3845 3558
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3827 3538 3827 3510 3843 3503
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3827 3510 3781 3510 3782 3538
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3783 3510 3770 3501
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3740 3448 3737 3497 3808 3497 3806 3447 3740 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3738 3496 3752 3479 3791 3479 3808 3497
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3791 3479 3791 3454 3807 3446
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3791 3454 3753 3454 3753 3479
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3753 3455 3740 3447
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 3740 3445
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3682 3621 3674 3676 3812 3674 3814 3620 3682 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3675 3675 3689 3655 3789 3654 3812 3673
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3789 3654 3792 3628 3814 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 3814 3620
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3793 3628 3691 3628 3689 3655
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3691 3629 3683 3621
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3687 3561 3683 3615 3779 3615 3776 3561 3686 3561
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3685 3615 3701 3600 3765 3600 3779 3614
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3765 3601 3765 3571 3776 3562
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3765 3572 3700 3572 3701 3601
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3701 3572 3688 3562
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3690 3556 3767 3556 3765 3503 3699 3502 3688 3557
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3691 3556 3705 3533 3739 3531 3768 3556
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3704 3533 3709 3509 3699 3502
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 3
-	 3710 3509 3739 3509 3739 3531
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3739 3509 3763 3504
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3703 3442 3738 3442 3734 3500 3699 3500 3704 3441
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3709 3404 3705 3438 3776 3440 3780 3406 3710 3405
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3707 3437 3714 3420 3764 3420 3776 3439
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3765 3420 3766 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3715 3420 3720 3406
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3792 3407 3789 3440 3862 3440 3866 3408 3794 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3789 3441 3800 3430 3854 3428 3864 3440
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3801 3428 3801 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3854 3430 3856 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3874 3410 3872 3439 3930 3440 3932 3409 3873 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3872 3440 3884 3427 3917 3427 3930 3440
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3918 3427 3919 3411
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3884 3427 3886 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 3938 3410 3938 3442 3998 3443 3999 3410 3939 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 3940 3442 3947 3430 3987 3430 3999 3442
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3948 3430 3949 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 3987 3430 3987 3411
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4005 3410 4005 3442 4064 3442 4065 3409 4005 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4007 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4005 3442 4018 3428 4055 3429 4065 3442
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4018 3429 4017 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4055 3429 4055 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4078 3409 4077 3442 4135 3442 4135 3409 4077 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4077 3442 4086 3428 4123 3428 4135 3442
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4086 3428 4086 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4122 3428 4122 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4139 3409 4139 3444 4199 3444 4199 3409 4140 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 1
-	 4139 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4139 3444 4146 3433 4189 3433 4199 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4189 3432 4189 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4146 3433 4146 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4204 3410 4204 3444 4260 3444 4259 3409 4203 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4204 3444 4212 3433 4249 3433 4260 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4213 3433 4213 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4249 3433 4249 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4266 3409 4265 3443 4326 3444 4326 3409 4266 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4267 3444 4276 3432 4318 3432 4325 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4333 3409 4333 3444 4395 3444 4395 3408 4333 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4333 3444 4340 3433 4389 3433 4394 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4341 3433 4340 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4389 3432 4389 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4276 3433 4276 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4320 3432 4320 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4401 3408 4401 3444 4464 3444 4463 3408 4401 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4401 3444 4411 3433 4454 3432 4464 3443
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4412 3432 4412 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4455 3433 4455 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4468 3409 4468 3444 4533 3444 4532 3407 4468 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4469 3445 4477 3435 4523 3435 4534 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4479 3434 4479 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4524 3435 4524 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4537 3406 4538 3445 4597 3444 4595 3406 4537 3406
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4538 3444 4548 3433 4587 3433 4597 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4587 3433 4587 3406
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4550 3433 4549 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4603 3406 4603 3445 4662 3445 4662 3406 4603 3406
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4603 3445 4614 3432 4653 3432 4662 3444
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4615 3432 4615 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4654 3432 4654 3407
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4666 3407 4666 3445 4719 3445 4719 3408 4666 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4667 3445 4676 3432 4713 3432 4718 3445
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4678 3432 4678 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4714 3433 4714 3408
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4725 3410 4725 3446 4789 3446 4781 3407 4725 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4727 3446 4736 3434 4782 3434 4790 3445
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4782 3434 4776 3409
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4738 3433 4736 3409
-2 2 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 5
-	 4760 3375 4784 3375 4784 3387 4760 3387 4760 3375
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 4
-	 4081 2482 4085 2510 4409 2507 4410 2480
-2 1 0 1 0 7 50 0 -1 0.000 0 0 -1 0 0 2
-	 4331 3685 4352 3678
--6
-6 7065 2430 11430 3510
-6 10752 2603 10922 2754
-6 10752 2603 10922 2678
-1 3 0 1 0 4 50 0 25 0.000 1 0.0000 10790 2641 27 27 10790 2641 10809 2660
-1 3 0 1 0 4 50 0 25 0.000 1 0.0000 10884 2641 27 27 10884 2641 10904 2660
--6
-6 10752 2678 10922 2754
-1 3 0 1 0 14 50 0 25 0.000 1 0.0000 10790 2715 27 27 10790 2715 10809 2735
-1 3 0 1 0 14 50 0 25 0.000 1 0.0000 10884 2715 27 27 10884 2715 10904 2735
--6
--6
-6 7517 2623 8894 3297
-6 7517 2623 8894 2869
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 8194.000 1223.581 7517 2623 8216 2778 8871 2623
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 7517 2623 8894 2623 8894 2869 7517 2869 7517 2623
--6
-6 7517 3050 8894 3297
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 8194.000 1670.395 7517 3050 8216 3207 8871 3050
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 7517 3050 8894 3050 8894 3297 7517 3297 7517 3050
--6
--6
-6 9073 2623 10453 3297
-6 9073 2623 10453 2869
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 9751.000 1219.355 9073 2623 9774 2778 10429 2623
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 9073 2623 10453 2623 10453 2869 9073 2869 9073 2623
--6
-6 9073 3050 10453 3297
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 9751.000 1666.223 9073 3050 9774 3207 10429 3050
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 9073 3050 10453 3050 10453 3297 9073 3297 9073 3050
--6
--6
-2 2 0 1 0 7 49 -1 20 0.000 0 0 -1 0 0 5
-	 7065 2475 7965 2475 7965 2970 7065 2970 7065 2475
-2 4 0 1 0 7 50 0 -1 0.000 0 0 3 0 0 5
-	 10959 3373 10959 2565 10734 2565 10734 3373 10959 3373
-2 4 0 1 0 43 50 0 9 0.000 0 0 3 0 0 5
-	 11354 3410 11354 2490 11053 2490 11053 3410 11354 3410
-2 4 0 1 0 43 50 0 27 0.000 0 0 3 0 0 5
-	 10922 3317 10922 3053 10771 3053 10771 3317 10922 3317
-2 2 0 1 0 42 53 0 15 0.000 0 0 7 0 0 5
-	 7065 2453 11411 2453 11411 3467 7065 3467 7065 2453
-2 4 0 1 0 43 50 0 9 0.000 0 0 3 0 0 5
-	 7442 3410 7442 2490 7141 2490 7141 3410 7442 3410
-4 0 0 40 -1 16 20 0.0000 4 240 735 7155 2835 BMC\001
--6
-6 7065 3870 11430 4995
-# Rack mounted PC
-# Drawn by Andre Esser
-6 7065 3870 11430 4961
-6 10752 4043 10922 4194
-6 10752 4043 10922 4118
-1 3 0 1 0 4 50 0 25 0.000 1 0.0000 10790 4081 27 27 10790 4081 10809 4100
-1 3 0 1 0 4 50 0 25 0.000 1 0.0000 10884 4081 27 27 10884 4081 10904 4100
--6
-6 10752 4118 10922 4194
-1 3 0 1 0 14 50 0 25 0.000 1 0.0000 10790 4155 27 27 10790 4155 10809 4175
-1 3 0 1 0 14 50 0 25 0.000 1 0.0000 10884 4155 27 27 10884 4155 10904 4175
--6
--6
-6 7517 4063 8894 4737
-6 7517 4063 8894 4309
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 8194.000 2663.581 7517 4063 8216 4218 8871 4063
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 7517 4063 8894 4063 8894 4309 7517 4309 7517 4063
--6
-6 7517 4490 8894 4737
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 8194.000 3110.395 7517 4490 8216 4647 8871 4490
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 7517 4490 8894 4490 8894 4737 7517 4737 7517 4490
--6
--6
-6 9073 4063 10453 4737
-6 9073 4063 10453 4309
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 9751.000 2659.355 9073 4063 9774 4218 10429 4063
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 9073 4063 10453 4063 10453 4309 9073 4309 9073 4063
--6
-6 9073 4490 10453 4737
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 9751.000 3106.223 9073 4490 9774 4647 10429 4490
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 9073 4490 10453 4490 10453 4737 9073 4737 9073 4490
--6
--6
-2 4 0 1 0 7 50 0 -1 0.000 0 0 3 0 0 5
-	 10959 4813 10959 4005 10734 4005 10734 4813 10959 4813
-2 4 0 1 0 43 50 0 9 0.000 0 0 3 0 0 5
-	 7442 4850 7442 3930 7141 3930 7141 4850 7442 4850
-2 4 0 1 0 43 50 0 9 0.000 0 0 3 0 0 5
-	 11354 4850 11354 3930 11053 3930 11053 4850 11354 4850
-2 4 0 1 0 43 50 0 27 0.000 0 0 3 0 0 5
-	 10922 4757 10922 4493 10771 4493 10771 4757 10922 4757
-2 2 0 1 0 42 53 0 15 0.000 0 0 7 0 0 5
-	 7065 3893 11411 3893 11411 4907 7065 4907 7065 3893
--6
-2 2 0 1 0 7 49 -1 20 0.000 0 0 -1 0 0 5
-	 7065 3915 7965 3915 7965 4410 7065 4410 7065 3915
-4 0 0 40 -1 16 20 0.0000 4 240 735 7155 4275 BMC\001
--6
-6 7065 900 11430 2025
-# Rack mounted PC
-# Drawn by Andre Esser
-6 7065 900 11430 1991
-6 10752 1073 10922 1224
-6 10752 1073 10922 1148
-1 3 0 1 0 4 50 0 25 0.000 1 0.0000 10790 1111 27 27 10790 1111 10809 1130
-1 3 0 1 0 4 50 0 25 0.000 1 0.0000 10884 1111 27 27 10884 1111 10904 1130
--6
-6 10752 1148 10922 1224
-1 3 0 1 0 14 50 0 25 0.000 1 0.0000 10790 1185 27 27 10790 1185 10809 1205
-1 3 0 1 0 14 50 0 25 0.000 1 0.0000 10884 1185 27 27 10884 1185 10904 1205
--6
--6
-6 7517 1093 8894 1767
-6 7517 1093 8894 1339
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 8194.000 -306.419 7517 1093 8216 1248 8871 1093
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 7517 1093 8894 1093 8894 1339 7517 1339 7517 1093
--6
-6 7517 1520 8894 1767
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 8194.000 140.395 7517 1520 8216 1677 8871 1520
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 7517 1520 8894 1520 8894 1767 7517 1767 7517 1520
--6
--6
-6 9073 1093 10453 1767
-6 9073 1093 10453 1339
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 9751.000 -310.645 9073 1093 9774 1248 10429 1093
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 9073 1093 10453 1093 10453 1339 9073 1339 9073 1093
--6
-6 9073 1520 10453 1767
-5 1 0 1 0 38 49 0 1 0.000 0 1 0 0 9751.000 136.223 9073 1520 9774 1677 10429 1520
-2 2 0 1 0 38 50 0 6 0.000 0 0 7 0 0 5
-	 9073 1520 10453 1520 10453 1767 9073 1767 9073 1520
--6
--6
-2 4 0 1 0 7 50 0 -1 0.000 0 0 3 0 0 5
-	 10959 1843 10959 1035 10734 1035 10734 1843 10959 1843
-2 4 0 1 0 43 50 0 9 0.000 0 0 3 0 0 5
-	 7442 1880 7442 960 7141 960 7141 1880 7442 1880
-2 4 0 1 0 43 50 0 9 0.000 0 0 3 0 0 5
-	 11354 1880 11354 960 11053 960 11053 1880 11354 1880
-2 4 0 1 0 43 50 0 27 0.000 0 0 3 0 0 5
-	 10922 1787 10922 1523 10771 1523 10771 1787 10922 1787
-2 2 0 1 0 42 53 0 15 0.000 0 0 7 0 0 5
-	 7065 923 11411 923 11411 1937 7065 1937 7065 923
--6
-2 2 0 1 0 7 49 -1 20 0.000 0 0 -1 0 0 5
-	 7065 945 7965 945 7965 1440 7065 1440 7065 945
-4 0 0 40 -1 16 20 0.0000 4 240 735 7155 1305 BMC\001
--6
-2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
-	 6390 3150 4770 3150
-2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
-	 3690 3150 2115 3150
-2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
-	 7065 2700 6390 2700
-2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
-	 7065 1665 6390 1665
-2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 2
-	 7065 3330 6390 3330
-2 1 0 3 0 7 50 -1 -1 0.000 0 0 -1 0 0 4
-	 7065 1170 6390 1170 6390 4185 7065 4185
-2 1 0 3 0 7 50 -1 20 0.000 0 0 -1 0 0 3
-	 6390 4185 6390 4635 7065 4635
-4 0 0 50 -1 16 24 0.0000 4 300 1395 495 4185 Internet\001
-4 0 0 50 -1 16 24 0.0000 4 300 2040 135 4635 or site LAN\001
-4 0 0 50 -1 16 24 0.0000 4 300 795 5130 2925 eth0\001
-4 0 0 50 -1 16 24 0.0000 4 375 3435 2610 4320 Portable Computer\001
-4 0 0 50 -1 16 24 0.0000 4 300 2475 3015 4770 MAAS Server\001
-4 0 0 50 -1 16 24 0.0000 4 300 1065 2385 2880 wlan0\001
-4 0 0 50 -1 16 24 0.0000 4 300 1275 2295 2385 eth1 or\001
-4 0 0 50 -1 16 24 0.0000 4 300 1170 11610 1620 SUT 1\001
-4 0 0 50 -1 16 24 0.0000 4 300 1170 11610 3060 SUT 2\001
-4 0 0 50 -1 16 24 0.0000 4 300 1170 11610 4545 SUT 3\001
-4 0 0 50 -1 16 24 0.0000 4 300 2070 8100 5670 MAAS LAN\001

=== removed file 'documentation/images/maniac-network.png'
Binary files documentation/images/maniac-network.png	2015-07-17 19:42:06 +0000 and documentation/images/maniac-network.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/secure_id.png'
Binary files documentation/images/secure_id.png	2015-07-17 19:42:06 +0000 and documentation/images/secure_id.png	1970-01-01 00:00:00 +0000 differ
=== removed file 'documentation/images/some_tests.png'
Binary files documentation/images/some_tests.png	2015-07-17 19:42:06 +0000 and documentation/images/some_tests.png	1970-01-01 00:00:00 +0000 differ
=== removed directory 'documentation/styles'
=== removed file 'documentation/styles/cert-doc.style'
--- documentation/styles/cert-doc.style	2015-07-17 19:42:06 +0000
+++ documentation/styles/cert-doc.style	1970-01-01 00:00:00 +0000
@@ -1,603 +0,0 @@
-
-  # List any fonts you would like to embed in the PDF here
-  embeddedFonts: [ ["Ubuntu-R.ttf", "Ubuntu-B.ttf", "Ubuntu-RI.ttf",
-                    "Ubuntu-BI.ttf" ],
-                   ["UbuntuMono-R.ttf", "UbuntuMono-B.ttf",
-                    "UbuntuMono-RI.ttf", "UbuntuMono-BI.ttf"] ]
-  # Default page setup.  Can be overridden by including other
-  # stylesheets with -s
-
-  pageSetup:
-    size: letter
-    width: null
-    height: null
-    margin-top: 2cm
-    margin-bottom: 2cm
-    margin-left: 2cm
-    margin-right: 2cm
-    margin-gutter: 0cm
-    spacing-header: 5mm
-    spacing-footer: 10mm
-
-    # The first template is one of the 'pageTemplates"
-    # (See next section)
-
-    firstTemplate: coverPage
-
-  # pageTemplates can be accessed with the .. raw:: pdf PageBreak command
-
-  pageTemplates:
-    coverPage:
-        background: images/cover-background.png
-        frames: []
-            [0cm, 0cm, 100%, 100%]
-        showHeader : false
-        showFooter : false
-
-    emptyPage:
-        frames: []
-            [0cm, 0cm, 100%, 100%]
-        showHeader : false
-        showFooter : false
-
-    oneColumn:
-        frames: []
-            [0cm, 0cm, 100%, 100%]
-        showHeader : true
-        showFooter : true
-
-    twoColumn:
-        frames: []
-            [0cm, 0cm, 49%, 100%]
-            [51%, 0cm, 49%, 100%]
-        showHeader : true
-        showFooter : true
-
-    threeColumn:
-        frames: []
-            [2%, 0cm, 29.333%, 100%]
-            [35.333%, 0cm, 29.333%, 100%]
-            [68.666%, 0cm, 29.333%, 100%]
-        showHeader : true
-        showFooter : true
-
-    cutePage:
-        frames: []
-            [0%, 0%, 100%, 100%]
-        showHeader : true
-        showFooter : true
-        defaultFooter : ###Page###
-        defaultHeader : ###Section###
-
-  fontsAlias:
-    stdFont: Ubuntu-R
-    stdBold: Ubuntu-B
-    stdItalic: Ubuntu-RI
-    stdBoldItalic: Ubuntu-BI
-    stdSans: Ubuntu-R
-    stdSansBold: Ubuntu-B
-    stdSansItalic: Ubuntu-RI
-    stdSansBoldItalic: Ubuntu-BI
-    stdMono: UbuntuMono-R
-    stdMonoItalic: UbuntuMono-RI
-    stdMonoBold: UbuntuMono-B
-    stdMonoBoldItalic: UbuntuMono-BI
-    stdSerif: Times-Roman
-
-  linkColor: #606060
-
-  styles:
-    base:
-      parent: null
-      fontName: stdFont
-      fontSize: 12
-      leading: 15
-      leftIndent: 0
-      rightIndent: 0
-      firstLineIndent: 0
-      alignment: TA_LEFT
-      spaceBefore: 0
-      spaceAfter: 0
-      bulletFontName: stdFont
-      bulletFontSize: 12
-      bulletIndent: 0
-      textColor: #303030
-      backColor: null
-      wordWrap: null
-      borderWidth: 0
-      borderPadding: 0
-      borderColor: null
-      borderRadius: null
-      allowWidows: false
-      allowOrphans: false
-      hyphenation: false
-      kerning: false
-      underline: false
-      strike: false
-      commands: []
-
-    normal:
-      parent: base
-
-    aubergine:
-      textColor: 6c0149
-
-    aubergine-right:
-      textColor: ff0050
-      alignment: TA_CENTER
-
-    title-reference:
-      parent: normal
-      fontName: stdItalic
-
-    bodytext:
-      parent: normal
-      spaceBefore: 6
-      alignment: TA_LEFT
-      hyphenation: true
-
-    toc:
-      parent: normal
-
-    blockquote:
-      parent: bodytext
-      leftIndent: 20
-
-    lineblock:
-      parent: bodytext
-
-    line:
-      parent: lineblock
-      spaceBefore: 0
-
-    toc1:
-      parent: toc
-      fontName: stdBold
-
-    toc2:
-      parent: toc
-      leftIndent: 20
-
-    toc3:
-      parent: toc
-      leftIndent: 40
-
-    toc4:
-      parent: toc
-      leftIndent: 60
-
-    toc5:
-      parent: toc
-      leftIndent: 80
-
-    toc6:
-      parent: toc
-      leftIndent: 100
-
-    toc7:
-      parent: toc
-      leftIndent: 100
-
-    toc8:
-      parent: toc
-      leftIndent: 100
-
-    toc9:
-      parent: toc
-      leftIndent: 100
-
-    toc10:
-      parent: toc
-      leftIndent: 100
-
-    toc11:
-      parent: toc
-      leftIndent: 100
-
-    toc12:
-      parent: toc
-      leftIndent: 100
-
-    toc13:
-      parent: toc
-      leftIndent: 100
-
-    toc14:
-      parent: toc
-      leftIndent: 100
-
-    toc15:
-      parent: toc
-      leftIndent: 100
-
-    footer:
-      parent: normal
-      fontSize: 32
-      alignment: TA_RIGHT
-      backColor: 6c0149
-
-    header:
-      parent: normal
-      fontSize: 24
-      alignment: TA_LEFT
-      backColor: black
-
-
-    attribution:
-      parent: bodytext
-      alignment: TA_RIGHT
-
-    image:
-      parent: bodytext
-      alignment: TA_CENTER
-
-    figure:
-      parent: bodytext
-      alignment: TA_CENTER
-      commands: []
-             [VALIGN, [ 0, 0 ], [ -1, -1 ], TOP ]
-             [ALIGN, [ 0, 0 ], [ -1, -1 ], CENTER ]
-      colWidths: [100%]
-
-    figure-caption:
-      parent: bodytext
-      fontName: stdItalic
-      textColor: 6c0149
-      alignment: TA_LEFT
-
-    figure-legend:
-      parent: bodytext
-
-    bullet-list:
-      parent: bodytext
-      spaceBefore: 0
-      commands: []
-             [VALIGN, [ 0, 0 ], [ -1, -1 ], TOP ]
-             [RIGHTPADDING, [ 0, 0 ], [ 1, -1 ], 0 ]
-      colWidths: ["20", null]
-
-    bullet-list-item:
-      parent: bodytext
-
-    item-list:
-      parent: bodytext
-      commands: []
-             [VALIGN, [ 0, 0 ], [ -1, -1 ], TOP ]
-             [RIGHTPADDING, [ 0, 0 ], [ 1, -1 ], 0 ]
-      colWidths: [25pt,null]
-
-    item-list-item:
-      parent: bodytext
-
-    definition-list-term:
-      parent: normal
-      fontName: stdBold
-      spaceBefore: 4
-      spaceAfter: 0
-      keepWithNext: false
-
-    definition-list-classifier:
-      parent: normal
-      fontName: stdItalic
-
-    definition:
-      parent: bodytext
-      firstLineIndent: 0
-      bulletIndent: 0
-      spaceBefore: 0
-      colWidths: [20pt,null]
-      commands: []
-                    [VALIGN, [ 0, 0 ], [ -1, -1 ], TOP ]
-                    [LEFTPADDING, [ 0, 0 ], [ -1, -1 ], 0 ]
-                    [BOTTOMPADDING, [ 0, 0 ], [ -1, -1 ], 0 ]
-                    [RIGHTPADDING, [ 0, 0 ], [ -1, -1 ], 0 ]
-                    
-    fieldname:
-      parent: bodytext
-      alignment: TA_RIGHT
-      fontName: stdBold
-
-    fieldvalue:
-      parent: bodytext
-
-    rubric:
-      parent: bodytext
-      textColor: darkred
-      alignment: TA_CENTER
-
-    italic: