From patchwork Fri Jan 27 17:58:14 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zygmunt Krynicki X-Patchwork-Id: 6425 Return-Path: X-Original-To: patchwork@peony.canonical.com Delivered-To: patchwork@peony.canonical.com Received: from fiordland.canonical.com (fiordland.canonical.com [91.189.94.145]) by peony.canonical.com (Postfix) with ESMTP id 7B8B423E0E for ; Fri, 27 Jan 2012 17:58:16 +0000 (UTC) Received: from mail-bk0-f52.google.com (mail-bk0-f52.google.com [209.85.214.52]) by fiordland.canonical.com (Postfix) with ESMTP id 51CFCA184A7 for ; Fri, 27 Jan 2012 17:58:16 +0000 (UTC) Received: by bkar19 with SMTP id r19so2132330bka.11 for ; Fri, 27 Jan 2012 09:58:16 -0800 (PST) Received: by 10.205.120.17 with SMTP id fw17mr3494835bkc.74.1327687095975; Fri, 27 Jan 2012 09:58:15 -0800 (PST) X-Forwarded-To: linaro-patchwork@canonical.com X-Forwarded-For: patch@linaro.org linaro-patchwork@canonical.com Delivered-To: patches@linaro.org Received: by 10.204.130.220 with SMTP id u28cs80352bks; Fri, 27 Jan 2012 09:58:15 -0800 (PST) Received: by 10.180.95.1 with SMTP id dg1mr12598879wib.21.1327687095199; Fri, 27 Jan 2012 09:58:15 -0800 (PST) Received: from indium.canonical.com (indium.canonical.com. [91.189.90.7]) by mx.google.com with ESMTPS id a9si7516355wiy.26.2012.01.27.09.58.14 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 Jan 2012 09:58:15 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of bounces@canonical.com designates 91.189.90.7 as permitted sender) client-ip=91.189.90.7; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of bounces@canonical.com designates 91.189.90.7 as permitted sender) smtp.mail=bounces@canonical.com Received: from ackee.canonical.com ([91.189.89.26]) by indium.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1Rqq3y-0008GZ-O2 for ; Fri, 27 Jan 2012 17:58:14 +0000 Received: from ackee.canonical.com (localhost [127.0.0.1]) by ackee.canonical.com (Postfix) with ESMTP id A525CE0801 for ; Fri, 27 Jan 2012 17:58:14 +0000 (UTC) MIME-Version: 1.0 X-Launchpad-Project: lava-dashboard X-Launchpad-Branch: ~linaro-validation/lava-dashboard/trunk X-Launchpad-Message-Rationale: Subscriber X-Launchpad-Branch-Revision-Number: 295 X-Launchpad-Notification-Type: branch-revision To: Linaro Patch Tracker From: noreply@launchpad.net Subject: [Branch ~linaro-validation/lava-dashboard/trunk] Rev 295: Merge Merge lp:~cob-olp/lava-dashboard/documentation-improvements Message-Id: <20120127175814.4943.61019.launchpad@ackee.canonical.com> Date: Fri, 27 Jan 2012 17:58:14 -0000 Reply-To: noreply@launchpad.net Sender: bounces@canonical.com Errors-To: bounces@canonical.com Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="14727"; Instance="launchpad-lazr.conf" X-Launchpad-Hash: 816ec60452a0c166778364bd92862a6e909c489d Merge authors: Adam Konarski Related merge proposals: https://code.launchpad.net/~cob-olp/lava-dashboard/documentation-improvements/+merge/89995 proposed by: Adam Konarski (cob-olp) review: Approve - Zygmunt Krynicki (zkrynicki) ------------------------------------------------------------ revno: 295 [merge] committer: Zygmunt Krynicki branch nick: trunk timestamp: Fri 2012-01-27 18:48:08 +0100 message: Merge Merge lp:~cob-olp/lava-dashboard/documentation-improvements Documentation chapter about installation was out of date and has instructed many users to install the legacy launch-control project. This cleanup allows users to just follow the pip/source method of installation and remain unchanged for a while. removed: doc/lava-dashboard-installation-0.png doc/lava-dashboard-installation-1.png doc/lava-dashboard-installation-10.png doc/lava-dashboard-installation-11.png doc/lava-dashboard-installation-12.png doc/lava-dashboard-installation-13.png doc/lava-dashboard-installation-14.png doc/lava-dashboard-installation-15.png doc/lava-dashboard-installation-16.png doc/lava-dashboard-installation-17.png doc/lava-dashboard-installation-18.png doc/lava-dashboard-installation-19.png doc/lava-dashboard-installation-2.png doc/lava-dashboard-installation-20.png doc/lava-dashboard-installation-21.png doc/lava-dashboard-installation-22.png doc/lava-dashboard-installation-23.png doc/lava-dashboard-installation-24.png doc/lava-dashboard-installation-25.png doc/lava-dashboard-installation-26.png doc/lava-dashboard-installation-27.png doc/lava-dashboard-installation-28.png doc/lava-dashboard-installation-3.png doc/lava-dashboard-installation-4.png doc/lava-dashboard-installation-5.png doc/lava-dashboard-installation-6.png doc/lava-dashboard-installation-7.png doc/lava-dashboard-installation-8.png doc/lava-dashboard-installation-9.png modified: doc/changes.rst doc/conf.py doc/installation.rst --- lp:lava-dashboard https://code.launchpad.net/~linaro-validation/lava-dashboard/trunk You are subscribed to branch lp:lava-dashboard. To unsubscribe from this branch go to https://code.launchpad.net/~linaro-validation/lava-dashboard/trunk/+edit-subscription === modified file 'doc/changes.rst' --- doc/changes.rst 2011-12-15 20:46:27 +0000 +++ doc/changes.rst 2012-01-27 17:48:08 +0000 @@ -1,6 +1,19 @@ Version History *************** +Unreleased +========== + +* Remove outdated installation documentation and replace it with basic + instructions for using pip or direct source code (Thanks to Adam Konarski) + +* Built documentation will now include TODO markers (Thanks to Adam Kornacki) + +.. _version_0_11_0: + +Version 0.11 +============ + .. _version_0_10_1: Version 0.10.1 @@ -38,7 +51,7 @@ ============= * Merge for bug LP:#877859: add measurement information to the json output. - This change is used by the Android build service. + This change is used by the Android build service. .. _version_0_6: === modified file 'doc/conf.py' --- doc/conf.py 2011-06-28 11:42:54 +0000 +++ doc/conf.py 2012-01-24 20:00:06 +0000 @@ -25,6 +25,9 @@ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.intersphinx', 'sphinx.ext.todo', 'sphinx.ext.coverage'] +# Configuration for sphinx.ext.todo +todo_include_todos = True + # Add any paths that contain templates here, relative to this directory. templates_path = [] === modified file 'doc/installation.rst' --- doc/installation.rst 2011-06-29 22:00:20 +0000 +++ doc/installation.rst 2012-01-25 15:45:31 +0000 @@ -1,349 +1,76 @@ .. _installation: Installation -============ - -This guide shows you how to setup a LAVA Dashboard instance running on Ubuntu -Lucid Server (LTS). The installation was performed using Virtualbox -4.0.10-72479~Ubuntu~natty running on a Ubuntu Natty Narwhal host. - -.. note:: - Currently LAVA server-side installations support Ubuntu Lucid Lynx Server - *only*. Usually everything works on a more recent Ubuntu release, such as - Maverick Meerkat, Natty Narwhal and even Oneiric Ocelot however we cannot - guarantee that is the case. We welcome bug reports though, please let us - know. - - - -Getting Ubuntu Server -^^^^^^^^^^^^^^^^^^^^^ - - -You can get Ubuntu Server from http://www.ubuntu.com/download/server/download -Please ensure you get 10.04 LTS version. Feel free to use either 32bit or 64bit -version, depending on your hardware needs. - - -Installing Ubuntu Server -^^^^^^^^^^^^^^^^^^^^^^^^ - - -The installation is rather straightforward. For the purpose of this -installation we selected ``English`` - -.. image:: lava-dashboard-installation-0.png - -You need to make the same choice a moment later: - -.. image:: lava-dashboard-installation-1.png - -For country, territory or area we selected the default which is ``United -States``. You can safely choose other values. - -.. image:: lava-dashboard-installation-2.png - -A few moments later the installer will allow you to configure networking. Here -we selected `lava`. It does not matter much but if you have multiple Ubuntu -installations it's a good idea to give each an unique host name. - -.. image:: lava-dashboard-installation-3.png - -A moment later you will have to create the initial user. This user will have -administrative access to the system. For our demo we created an user called -``Lava Admin``: - -.. image:: lava-dashboard-installation-4.png - -You also need to select a user name, we selected ``lava-admin``. - -.. image:: lava-dashboard-installation-5.png - -After that the installation is really up to you. You can partition the disk -anyway you like. There is no need to select anything different from the -defaults offered by the installer as far as LAVA is concerned. - -Once the installation is done login with the username and password you selected - - -Adding the Lava Dashboard PPA -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -Currently LAVA is packaged in a PPA maintained by Zygmunt Krynicki. There is an -official PPA being prepared (owned by the Linaro Validation group) but it is -not ready as of 28th of June 2011. - -Usually PPAs are added using the very useful tool called -``add-apt-repository``. It is not installed by default on server installations -so we'll need to get it manually. Let's install the package that has this tool -``python-software-properties``, using the following command:: - - $ sudo apt-get install python-software-properties - -You should see an output similar to the one below: - -.. image:: lava-dashboard-installation-6.png - -Now we can add the PPA using the following command:: - - $ sudo add-apt-repository ppa:zkrynicki/lava - -You should see an output similar to the one below: - -.. image:: lava-dashboard-installation-7.png - -After the PPA is added we need to update the cache of packages that APT knows about. This step is mandatory:: - - $ sudo apt-get update - -.. image:: lava-dashboard-installation-8.png - -This command does produce a lot of output. After it finishes we can finally install launch-control. - - -Installing Lava Dashboard Package -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -To install the dashboard you need to install a package called -``launch-control``. - -.. note:: - Lava Dashboard used to be called Launch Control. The old name is being - transitioned but we have not prepared a packaged release of the new - codebase just yet. - -You can install this package using the following command:: - - $ sudo apt-get install launch-control - -.. image:: lava-dashboard-installation-9.png - -Running this command will make APT ask you for confirmation. It will display a -list of packages that will be installed to fulfill the dependency chain of the -dashboard. Here it required over 20 megabytes of additional packages. - -.. image:: lava-dashboard-installation-10.png - -Just confirm the selection and let it download all the packages. - - -Setting Up The Dashboard Database -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -The installer will ask you several questions. Most of the questions come from a -Debian subsystem used by the Dashboard to setup a database. This subsystem is -called ``dbconfig-common``. The first question it asks if whether you wish you -use dbconfig-common with launch-control. - -.. image:: lava-dashboard-installation-11.png - -Select ```` here please. If you select ```` instead you will have to -manually create and configure a database. This is only recommended for advanced -users and is not described in this guide. - -The next question is about the database back-end that the Dashboard should use -to store test results and other data. The dashboard supports two back-ends: - -#. SQLite -#. PostgreSQL - -.. image:: lava-dashboard-installation-12.png - -We recommend PostgreSQL for all installations. Some of the features, such as -data mining and reporting, may have database-specific queries and those queries -would not run on SQLite. - -.. note:: - It is possible to provide custom data mining queries specific to a database - back-end so it's possible to have a query that would work on both SQLite - and PostgreSQL but the users are not required to provide such fall-backs. - -The final question is displayed only when using PostgreSQL. - -.. image:: lava-dashboard-installation-13.png - -Here ``dbconfig-common`` asks you about the password you would like to use for -the database account that will be used by the dashboard to connect to -PostgreSQL server. By default a random password will be generated for you, just -leave this field blank and continue. - -After those questions the interactive part will finish and the dashboard will -be installed and configured automatically. There is very little output, usually -it looks like this: - -.. image:: lava-dashboard-installation-14.png - -There is much more details about what is happening but it is being redirected -to ``syslog``. To have a look at that immediately after the installation you -can use a command such as:: - - $ less /var/log/syslog - -Just scroll down to the end of the file (using page down key) to see the -verbose installation details. If you have any questions about that please ask -us. - -.. note:: - Asking questions is good. It let's us know what we did wrong and let's us - build a FAQ for other users. You can find us in the #linaro channel on - irc.freenode.net. Usually we're up during EU and US timezones. You can also - use https://answers.launchpad.net/lava-dashboard - - -Creating the admin user -^^^^^^^^^^^^^^^^^^^^^^^ - -The dashboard has a user account system separate from the system it is running -on. To control it you need to have a administrator, super-user account. Create -one now using this command:: - - $ sudo -u www-data /usr/lib/launch-control/manage.py createsuperuser - -.. image:: lava-dashboard-installation-15.png - -Answer the questions asked by the program. For the purpose of the guide we used -``admin`` for both user name and password. - -.. image:: lava-dashboard-installation-16.png - - -Powering off the virtual machine -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -We are almost ready to get started with the dashboard. Since we use VirtualBox -and, by default, it is using NAT networking we are unable to connect to the -dashboard from our host operating system. Let's turn off the virtual machine -and reconfigure VirtualBox networking. - -To power off the virtual machine use the following command:: - - $ sudo poweroff - -.. image:: lava-dashboard-installation-17.png - - -Reconfiguring virtual machine network -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -After the machine shuts down, go to the main VirtuaBox window (you may need to -stat VirtualBox again if you closed it earlier). Next, click on the name of the -virtual machine you created. This will change the pane on the right to display -the configuration of your virtual machine. Locate network settings and click on -the icon next to the label. This should bring up a dialog window similar to the -one below. - -.. image:: lava-dashboard-installation-18.png - -As you can see the network adapter is attached to the ``NAT`` network. Let's -change that to to ``Bridged Adapter``. If you have multiple network adapters -available (such as wired networking and wireless networking) make sure to -select the one you are connected with right now. We used ``wlan0`` which is the -name of the wireless connection on the host computer. - -The settings should look like this: - -.. image:: lava-dashboard-installation-19.png - -Click okay to close the dialog window and start the machine again. - - -Booting the virtual machine again -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -If you left the Ubuntu Lucid Server installation CD in the virtual machine as -we did please select the option called ``Boot from first hard disk`` and continue. - -.. image:: lava-dashboard-installation-20.png - -After a moment the machine will be up and running. Let's log in to see the IP -address it got from the DHCP server on your network. - -.. image:: lava-dashboard-installation-21.png - -Login with the user you created during operating system installation. As you -remember we used the ``lava-admin`` user. - -.. image:: lava-dashboard-installation-22.png - -We now need to check the IP address of our virtual server. Use the following command now:: - - $ ifconfig - -.. image:: lava-dashboard-installation-23.png - -Here our IP address is ``10.155.3.51``, the value you'll see will most likely differ. - - -Accessing the dashboard for the first time -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -Now we are ready to connect to the dashboard. From your host computer open a -web browser of your choice (we used Firefox that came with Ubuntu Natty) and go -to this address:: - - http://10.155.3.51/launch-control/ - -Substitute the value above with the IP address of your server. You should see a screen like this: - -.. image:: lava-dashboard-installation-24.png - -Let's sign in with the admin user we created. Click on the sign in button in -the top-right corner now. - -.. image:: lava-dashboard-installation-25.png - -.. note:: - The dashboard supports two kinds of user accounts. You can create a local - account, like the one we did with ``createsuperuser`` or use an existing - launchpad.net account. For general use we recommend launchpad accounts as - that will not require creating yet-another password for you to remember. - This time, however, you need to sign in as the ``admin`` user with the - ``admin`` password we created earlier. This account is special and has - access to the administration panel, more such accounts can be created if - necessary. - -After signing in go click on the link that reads ``Bundle Stream``. It will -lead you to a page that contains a list of all the streams in your dashboards. -There are no streams yet so let's create one. Please follow the link on the -page to go to the admin panel, directly to a place that allows you to create -additional bundle streams. - -.. image:: lava-dashboard-installation-26.png - -.. note:: - The dashboard uses the term ``stream`` but you can think of it as a - directory. It's just a directory in the system that can be used to store - test results in. - -You will see a form like the one on the screen shot below, make sure to select -the ``admin`` from the ``Ownership`` section. This will make you the owner of -the data stored in that stream. Also make sure to select the ``is public`` and -``is anonymous`` check-boxes below in the ``Access Rights`` section. Finally -click save. - -.. image:: lava-dashboard-installation-27.png - -.. note:: - The dashboard has a simple ownership and access control system. It is not - described here but the settings you selected a moment ago will allow anyone - to upload and download test results to the bundle stream you just created. - - -Now click on the address bar of your browser and go to this URL:: - - http://10.155.3.51/launch-control/dashboard/streams/ - -As before, please replace the IP address with the IP address of your server. -You should be able to see the ``/anonymous/`` bundle stream. - -.. image:: lava-dashboard-installation-28.png - -Congratulations, you have now correctly installed and configured the Lava -Dashboard. You can now use lava-test and lava-dashboard-tool to upload data to -your system. +^^^^^^^^^^^^ + +To install LAVA Dashboard, you will first need to install LAVA Server. +For more information about LAVA Server, see +http://lava-server.readthedocs.org + +Using virtualenv +**************** + +Python Virtualenv is a useful tool for creating a sandbox for working +with python modules. In Ubuntu, you can get it by installing +*python-virtualenv* using apt-get. For source and pypi installations of +non-production systems, it is highly recommended. + +Example usage :: + + $ virtualenv sandbox + $ cd sandbox + $ . bin/activate + +Once activated, the environment for that session will be set up so that +subsequent commands will use the virtual environment settings. + +Installation from source +************************ + +This is the most complicated and error prone installation method. It requires +the user to download source release tarballs. Unpack them and install them in +the correct order. Depending on the exact set of components that are installed +(especially client or server side components) some additional steps are +necessary. This may include setting up the web application host (one of many +possible configurations here), setting up the database (again multiple possible +options, our recommendation is to use the latest stable version of PostgreSQL). + +For installing from source, it's normally much simpler to install from +pypi first, then update using the source. This is useful if you want +to use it for development against your own branch. For instance, after +installing from pypi (see directions below) you could do the following. + +Updating in a virtualenv using source :: + + $ bzr branch lp:lava-dashboard + $ cd lava-dashboard + $ ./setup develop + +Installation from PypI +********************** + +PyPi is the python package index (http://pypi.python.org/pypi). It is +maintained by the python community and is the preferred distribution method +used by many open source projects written in the python programming language. + +Here a front-end program, such as pip (http://pypi.python.org/pypi/pip) is used +to install packages, and their python dependencies. Pip finds the required set +of packages, downloads their source releases and does the hard work of figuring +out the right way to put them together. + +This is the best compromise between wide system support (any flavour of Linux, +OS X and Windows), simplicity, upgrade and availability. The downside is that +it does not handle, by itself, the last mile. This method does not handle +things like setting up and running the application server. It also requires the +user to have additional development packages, such as python header files, +database server header files, the C compiler and more. + +To install using pypi (For development only, not for production):: + + $ pip install lava-dashboard + $ lava-server manage --development syncdb + $ lava-server manage --development migrate + +You will need to answer a few questions during the syncdb step. This +will use a simple sqlite database, and should normally only be used for +testing or hacking on LAVA. === removed file 'doc/lava-dashboard-installation-0.png' Binary files doc/lava-dashboard-installation-0.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-0.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-1.png' Binary files doc/lava-dashboard-installation-1.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-1.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-10.png' Binary files doc/lava-dashboard-installation-10.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-10.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-11.png' Binary files doc/lava-dashboard-installation-11.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-11.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-12.png' Binary files doc/lava-dashboard-installation-12.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-12.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-13.png' Binary files doc/lava-dashboard-installation-13.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-13.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-14.png' Binary files doc/lava-dashboard-installation-14.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-14.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-15.png' Binary files doc/lava-dashboard-installation-15.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-15.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-16.png' Binary files doc/lava-dashboard-installation-16.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-16.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-17.png' Binary files doc/lava-dashboard-installation-17.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-17.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-18.png' Binary files doc/lava-dashboard-installation-18.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-18.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-19.png' Binary files doc/lava-dashboard-installation-19.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-19.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-2.png' Binary files doc/lava-dashboard-installation-2.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-2.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-20.png' Binary files doc/lava-dashboard-installation-20.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-20.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-21.png' Binary files doc/lava-dashboard-installation-21.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-21.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-22.png' Binary files doc/lava-dashboard-installation-22.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-22.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-23.png' Binary files doc/lava-dashboard-installation-23.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-23.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-24.png' Binary files doc/lava-dashboard-installation-24.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-24.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-25.png' Binary files doc/lava-dashboard-installation-25.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-25.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-26.png' Binary files doc/lava-dashboard-installation-26.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-26.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-27.png' Binary files doc/lava-dashboard-installation-27.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-27.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-28.png' Binary files doc/lava-dashboard-installation-28.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-28.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-3.png' Binary files doc/lava-dashboard-installation-3.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-3.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-4.png' Binary files doc/lava-dashboard-installation-4.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-4.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-5.png' Binary files doc/lava-dashboard-installation-5.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-5.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-6.png' Binary files doc/lava-dashboard-installation-6.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-6.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-7.png' Binary files doc/lava-dashboard-installation-7.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-7.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-8.png' Binary files doc/lava-dashboard-installation-8.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-8.png 1970-01-01 00:00:00 +0000 differ === removed file 'doc/lava-dashboard-installation-9.png' Binary files doc/lava-dashboard-installation-9.png 2011-06-28 16:28:57 +0000 and doc/lava-dashboard-installation-9.png 1970-01-01 00:00:00 +0000 differ