[Branch,~linaro-validation/lava-scheduler/trunk] Rev 238: update install instructions to just point to lava-deployment-tool

Message ID 20130123155515.16630.22180.launchpad@ackee.canonical.com
State Accepted
Headers show

Commit Message

Andy Doan Jan. 23, 2013, 3:55 p.m.
------------------------------------------------------------
revno: 238
committer: Andy Doan <andy.doan@linaro.org>
branch nick: lava-scheduler
timestamp: Wed 2013-01-23 09:54:02 -0600
message:
  update install instructions to just point to lava-deployment-tool
modified:
  doc/installation.rst


--
lp:lava-scheduler
https://code.launchpad.net/~linaro-validation/lava-scheduler/trunk

You are subscribed to branch lp:lava-scheduler.
To unsubscribe from this branch go to https://code.launchpad.net/~linaro-validation/lava-scheduler/trunk/+edit-subscription

Patch

=== modified file 'doc/installation.rst'
--- doc/installation.rst	2012-01-28 17:56:51 +0000
+++ doc/installation.rst	2013-01-23 15:54:02 +0000
@@ -1,80 +1,6 @@ 
 Installation
 ^^^^^^^^^^^^
 
-LAVA can be installed in several different ways. As with any open source
-project that does source distribution the end user has all the freedom to do
-what they want. We support certain installation methods more than others. You
-can always ask for support using Launchpad support tracker (see
-:ref:`questions`)
-
-To install LAVA Scheduler, 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-scheduler
- $ cd lava-scheduler
- $ ./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-scheduler
- $ 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.
+The scheduler should be installed along with all other LAVA components and
+prerequisites by using the `lava-deployment-tool <http://lava-deployment-tool.readthedocs.org/en/latest/index.html>`_
+