From patchwork Wed Jan 23 15:55:15 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Andy Doan X-Patchwork-Id: 14247 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 3446E23E39 for ; Wed, 23 Jan 2013 16:00:43 +0000 (UTC) Received: from mail-ve0-f173.google.com (mail-ve0-f173.google.com [209.85.128.173]) by fiordland.canonical.com (Postfix) with ESMTP id A2403A18D16 for ; Wed, 23 Jan 2013 16:00:42 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id b10so1024399vea.32 for ; Wed, 23 Jan 2013 08:00:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-forwarded-to:x-forwarded-for:delivered-to:x-received :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=oQbivkQYWt3JvBduzS197gwvk4kn/I32X+6j6FOf5xA=; b=UVRVl7C3a+9t8TVLj06DX5zznUgsNP4CKfnBizSA5WFRD/7MdXXKHOz1x6rIo0fj88 jjasue3EiLN+FeT6f8XK6gtfol2mqx4wjmjtzu52RHc2MoAs2PLuOLEEs/9khzu+SffF Df69KuMpu6uFxu/N63OpwolL/SlGK/u/bBtsynRDqr9R03qOGuKmf6DsXxxhXQ09qKLS r01N8w1cNW2qq+TB2G1piRr97puV1xAAww5finaWh6OLNfU//FjJ+UvD7tv0QyJMgjFJ MazPbK3zc7omTMllOBuuwolaq+qD2IJAuS+XJz1hSawGvrXS1BAFFBtGQBmrDjycQ9tI 5XKw== X-Received: by 10.220.209.74 with SMTP id gf10mr1886574vcb.10.1358956842152; Wed, 23 Jan 2013 08:00:42 -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.58.145.101 with SMTP id st5csp18022veb; Wed, 23 Jan 2013 08:00:41 -0800 (PST) X-Received: by 10.180.95.200 with SMTP id dm8mr3501949wib.16.1358956841023; Wed, 23 Jan 2013 08:00:41 -0800 (PST) Received: from indium.canonical.com (indium.canonical.com. [91.189.90.7]) by mx.google.com with ESMTPS id bm3si7582881wjb.218.2013.01.23.08.00.40 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 23 Jan 2013 08:00:41 -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 1Ty2kh-000412-My for ; Wed, 23 Jan 2013 16:00:39 +0000 Received: from ackee.canonical.com (localhost [127.0.0.1]) by ackee.canonical.com (Postfix) with ESMTP id C3A29E0955 for ; Wed, 23 Jan 2013 15:55:15 +0000 (UTC) MIME-Version: 1.0 X-Launchpad-Project: lava-scheduler X-Launchpad-Branch: ~linaro-validation/lava-scheduler/trunk X-Launchpad-Message-Rationale: Subscriber X-Launchpad-Branch-Revision-Number: 238 X-Launchpad-Notification-Type: branch-revision To: Linaro Patch Tracker From: noreply@launchpad.net Subject: [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> Date: Wed, 23 Jan 2013 15:55:15 -0000 Reply-To: noreply@launchpad.net Sender: bounces@canonical.com Errors-To: bounces@canonical.com Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="16445"; Instance="launchpad-lazr.conf" X-Launchpad-Hash: 29fdc96a975510ae2b9d87f0ac6f0a27f35101dc X-Gm-Message-State: ALoCoQm0BkBiRmjhb+olLstFPHjDKJqPwwDPAY2tgl6e3xMB7d6JorXRvqmwwp5NZCsr4Vlk4g/6 ------------------------------------------------------------ revno: 238 committer: Andy Doan 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 === 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 `_ +