From patchwork Wed Oct 31 10:35:19 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michael-Doyle Hudson X-Patchwork-Id: 12629 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 196FA23EF7 for ; Wed, 31 Oct 2012 10:35:23 +0000 (UTC) Received: from mail-ia0-f180.google.com (mail-ia0-f180.google.com [209.85.210.180]) by fiordland.canonical.com (Postfix) with ESMTP id 935FAA191C3 for ; Wed, 31 Oct 2012 10:35:22 +0000 (UTC) Received: by mail-ia0-f180.google.com with SMTP id f6so869320iag.11 for ; Wed, 31 Oct 2012 03:35:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-forwarded-to:x-forwarded-for:delivered-to:received-spf :content-type:mime-version:x-launchpad-project:x-launchpad-branch :x-launchpad-message-rationale:x-launchpad-branch-revision-number :x-launchpad-notification-type:to:from:subject:message-id:date :reply-to:sender:errors-to:precedence:x-generated-by :x-launchpad-hash:x-gm-message-state; bh=vbZtFO4Q8nW4ICeqIMfy9tHt4nHyIIx3YBqm4zCi+Ys=; b=TXhPQWOv0g+ZVCYflf+vwUl9xsClDG47iIRIpH69k/NtYD3Y2lXsoJKNNQJhsdxXGo 3VoPtWzP3rdC68CJbUSIr011Eh6PohmMO8MrmN9zWfyIIfP0npjvM8O2DHqfqWlgbxIK beYTplOzECqqkzwUh/Y+AWK1dxacuDdocS93o55m3D+A7h4BUEegHSr5dYZm/bJB6YOF S1cjx75vYq2tvX/qgxSqVsFReN1gES+A41fAKPd7Kf+x1YR8vqaxwnVP3RP0kEJBv/JX Y9mkX9ENBhHJai5m62CXzyYV7m0YMWgAoGpQgyGJKw5aLAM/3RFtWNoG39/pghMm1IzJ JWrQ== Received: by 10.50.140.97 with SMTP id rf1mr869296igb.70.1351679721884; Wed, 31 Oct 2012 03:35:21 -0700 (PDT) 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.50.67.148 with SMTP id n20csp598038igt; Wed, 31 Oct 2012 03:35:21 -0700 (PDT) Received: by 10.180.7.197 with SMTP id l5mr1639554wia.13.1351679720478; Wed, 31 Oct 2012 03:35:20 -0700 (PDT) Received: from indium.canonical.com (indium.canonical.com. [91.189.90.7]) by mx.google.com with ESMTPS id t52si1835690wed.73.2012.10.31.03.35.19 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Oct 2012 03:35:20 -0700 (PDT) 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 1TTVdn-0005bT-L6 for ; Wed, 31 Oct 2012 10:35:19 +0000 Received: from ackee.canonical.com (localhost [127.0.0.1]) by ackee.canonical.com (Postfix) with ESMTP id 90072E00F3 for ; Wed, 31 Oct 2012 10:35:19 +0000 (UTC) MIME-Version: 1.0 X-Launchpad-Project: lava-server X-Launchpad-Branch: ~linaro-validation/lava-server/trunk X-Launchpad-Message-Rationale: Subscriber X-Launchpad-Branch-Revision-Number: 402 X-Launchpad-Notification-Type: branch-revision To: Linaro Patch Tracker From: noreply@launchpad.net Subject: [Branch ~linaro-validation/lava-server/trunk] Rev 402: there is only one way to install lava Message-Id: <20121031103519.5057.52434.launchpad@ackee.canonical.com> Date: Wed, 31 Oct 2012 10:35:19 -0000 Reply-To: noreply@launchpad.net Sender: bounces@canonical.com Errors-To: bounces@canonical.com Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="16218"; Instance="launchpad-lazr.conf" X-Launchpad-Hash: 27dbe4c4f3e994276faacb2090313b3fa7fb55d7 X-Gm-Message-State: ALoCoQk2RRVhxK7RG64bqJ9YlCBbP0FCHdpl2UCiDGUXLrxU2rd4oaedyz78YMQd4Fk4y/cobjeR ------------------------------------------------------------ revno: 402 committer: Michael Hudson-Doyle branch nick: trunk timestamp: Wed 2012-10-31 11:34:30 +0100 message: there is only one way to install lava modified: doc/installation.rst --- lp:lava-server https://code.launchpad.net/~linaro-validation/lava-server/trunk You are subscribed to branch lp:lava-server. To unsubscribe from this branch go to https://code.launchpad.net/~linaro-validation/lava-server/trunk/+edit-subscription === modified file 'doc/installation.rst' --- doc/installation.rst 2012-09-04 20:53:49 +0000 +++ doc/installation.rst 2012-10-31 10:34:30 +0000 @@ -1,87 +1,5 @@ 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`) - - -Using LAVA Deployment Tool -************************** - -See http://launchpad.net/lava-deployment-tool/ to learn more about this method. -This is by far the most supported installation mode available. - -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-server - $ cd lava-server - $ ./setup.py 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-server - $ 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-server. - -.. todo:: - Installation instructions for production installations against - postgresql using pypi +We have a tool for installing the various components that make up +LAVA. See http://lava-deployment-tool.readthedocs.org/ to learn more.