From 7530060ab0959a6cc98f6a809c0c1369c5a0298d Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Sat, 15 Jan 2011 12:30:25 -0500 Subject: [PATCH] update the section "Installing in Virtualized Linux Environments"; --- 1.6/admin/serversideinstallation.xml | 815 +++++++++++++++++++++++------------ 1 file changed, 533 insertions(+), 282 deletions(-) diff --git a/1.6/admin/serversideinstallation.xml b/1.6/admin/serversideinstallation.xml index eccabd85e5..ffbcf7ed2d 100644 --- a/1.6/admin/serversideinstallation.xml +++ b/1.6/admin/serversideinstallation.xml @@ -20,8 +20,8 @@ Professional, Windows7), but the software can still be installed and run on Windows via a so-called virtualized Linux-guest Operating System (using, for example, - "VirtualBox", or "VMware", or - "VirtualPC" to emulate a Linux + "VirtualBox" or "VMware" + to emulate a Linux environment). It can also be installed to run on other Linux systems via virtualized environments (using, for example, "VirtualBox" or "VMware"). More information on virtualized environments can be found in @@ -145,12 +145,12 @@ In the following example, the default shell for the opensrf user is automatically set to /bin/bash to inherit a reasonable environment: - - + + # as the root user: useradd -m -s /bin/bash opensrf passwd opensrf - + Download and Unpack Latest OpenSRF Version @@ -164,13 +164,13 @@ the directory /home/opensrf then download and extract OpenSRF. The new subdirectory /home/opensrf/OpenSRF-1.4.0 will be created: - - + + # as the opensrf user: cd /home/opensrf wget http://evergreen-ils.org/downloads/OpenSRF-1.4.0.tar.gz tar zxf OpenSRF-1.4.0.tar.gz - + Install Prerequisites to Build OpenSRF @@ -185,12 +185,12 @@ distribution keywords table . For example, to install the prerequisites for Ubuntu version 10.04 (Lucid Lynx) you would enter this command: make -f src/extras/Makefile.install ubuntu-lucid . - - + + # as the root user: cd /home/opensrf/OpenSRF-1.4.0 make -f src/extras/Makefile.install [DISTRIBUTION] - + Keyword Targets for OpenSRF <application>"make"</application> Command @@ -267,13 +267,13 @@ include support for Python and Java, add the configuration options and , respectively: - - + + # as the opensrf user: cd /home/opensrf/OpenSRF-1.4.0 ./configure --prefix=/openils --sysconfdir=/openils/conf make - + This step will take several minutes to complete. @@ -282,12 +282,12 @@ user, return to the new OpenSRF build directory and use the make utility to compile, link and install OpenSRF: - - + + # as the root user: cd /home/opensrf/OpenSRF-1.4.0 make install - + This step will take several minutes to complete. @@ -300,12 +300,12 @@ new library path, then run the command ldconfig to automatically read the file and modify the system dynamic library path: - - + + # as the root user: echo "/openils/lib" > /etc/ld.so.conf.d/osrf.conf ldconfig - + Define Public and Private OpenSRF Domains @@ -324,12 +324,12 @@ Jabber - - + + # as the root user: 127.0.1.2 public.localhost public 127.0.1.3 private.localhost private - + Change File Ownerships @@ -337,11 +337,11 @@ user, change the ownership of all files installed in the directory /openils to the user opensrf: - - + + # as the root user: chown -R opensrf:opensrf /openils - + @@ -353,25 +353,25 @@ Before continuing with configuration of ejabberd you must stop that service. As the root user, execute the following command to stop the service: - - + + # as the root user: /etc/init.d/ejabberd stop - + If ejabberd reports that it is already stopped, there may have been a problem when it started back in the installation step. If there are any remaining daemon processes such as beam or epmd you may need to perform the following commands to kill them: - - + + # as the root user: epmd -kill killall beam; killall beam.smp rm /var/lib/ejabberd/* echo 'ERLANG_NODE=ejabberd@localhost' >> /etc/default/ejabberd - + Edit the <systemitem class="service">ejabberd</systemitem> configuration @@ -425,11 +425,11 @@ As the root user, restart the ejabberd service to test the configuration changes and to register your users: - - + + # as the root user: /etc/init.d/ejabberd start - + Register <systemitem class="username">router</systemitem> and @@ -462,8 +462,8 @@ for the users <systemitem class="username">router</systemitem> and <systemitem class="username">opensrf</systemitem> on each domain (remember to replace <emphasis>NEWPASSWORD</emphasis> with the appropriate password):</para> -<screen> - <userinput> + <screen> + <userinput> # as the root user: # Note: the syntax for registering a user with ejabberdctl is: # ejabberdctl register USER DOMAIN PASSWORD @@ -471,7 +471,7 @@ ejabberdctl register router public.localhost NEWPASSWORD ejabberdctl register opensrf private.localhost NEWPASSWORD ejabberdctl register opensrf public.localhost NEWPASSWORD</userinput> -</screen> + </screen> <para>Note that the users <systemitem class="username">router</systemitem> and <systemitem class="username">opensrf</systemitem> and their respective passwords will be used again in <xref linkend="serversideinstallation-passwords"/> when @@ -483,13 +483,13 @@ execute the following commands to create the new configuration files <filename>/openils/conf/opensrf_core.xml</filename> and <filename>/openils/conf/opensrf.xml</filename> from the example templates:</para> -<screen> - <userinput> + <screen> + <userinput> # as the opensrf user: cd /openils/conf cp opensrf.xml.example opensrf.xml cp opensrf_core.xml.example opensrf_core.xml</userinput> -</screen> + </screen> </step> <step xml:id="serversideinstallation-passwords"> <title>Update usernames and passwords in the OpenSRF configuration file @@ -591,7 +591,7 @@ to instead read: /tmp/persist.db Following is a sample modification of that portion of the file: - @@ -618,11 +618,11 @@ to the home directory of each user who will use srfsh. For instance, do the following for the opensrf user: - - + + # as the root user: cp /openils/conf/srfsh.xml.example /home/opensrf/.srfsh.xml - + Edit each user's file ~/.srfsh.xml and make the following changes: @@ -653,7 +653,7 @@ Following is a sample of the file: - @@ -676,30 +676,30 @@ environmental variable PATH by adding a new file path to the opensrf user's shell configuration file ~/.bashrc: - - + + # as the opensrf user: echo "export PATH=/openils/bin:\$PATH" >> ~/.bashrc - + Start OpenSRF As the root user, start the ejabberd and memcached services: - - + + # as the root user: /etc/init.d/ejabberd start /etc/init.d/memcached start - + As the opensrf user, start OpenSRF as follows: - - + + # as the opensrf user: osrf_ctl.sh -l -a start_all - + The flag forces Evergreen to use localhost (your current system) as the hostname. The flag starts the other @@ -734,19 +734,19 @@ OpenSRF using the srfsh utility and trying to call the add method on the OpenSRF math service: - - + + # as the root user: /openils/bin/srfsh - + srfsh# request opensrf.math add 2 2 - + Received Data: 4 ------------------------------------ Request Completed Successfully Request Time in seconds: 0.007519 ------------------------------------ - + For other srfsh commands, type in help at the prompt. @@ -756,11 +756,11 @@ osrf_ctl.sh again. As the opensrf user, stop OpenSRF as follows: - - + + # as the opensrf user: osrf_ctl.sh -l -a stop_all - + @@ -833,13 +833,13 @@ the directory /home/opensrf then download and extract Evergreen. The new subdirectory /home/opensrf/Evergreen-ILS-1.6.1.2 will be created: - - + + # as the opensrf user: cd /home/opensrf wget http://evergreen-ils.org/downloads/Evergreen-ILS-1.6.1.2.tar.gz tar zxf Evergreen-ILS-1.6.1.2.tar.gz - + Install Prerequisites to Build Evergreen @@ -856,12 +856,12 @@ For example, to install the prerequisites for Ubuntu version 9.10 (Karmic Koala) you would enter this command: make -f Open-ILS/src/extras/Makefile.install ubuntu-karmic. - - + + # as the root user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 make -f Open-ILS/src/extras/Makefile.install [DISTRIBUTION] - +
Keyword Targets for Evergreen <application>"make"</application> Command @@ -950,19 +950,19 @@ You will need to install several Perl modules on the other system. As the root user install the following Perl modules: - - + + # as the root user: # first, ensure the gcc compiler is installed: apt-get install gcc # then install the Perl modules: perl -MCPAN -e shell - + cpan> install JSON::XS cpan> install MARC::Record cpan> install MARC::File::XML - + For more information on installing Perl Modules vist the official CPAN site. @@ -977,13 +977,13 @@ do this by creating the new file /etc/ld.so.conf.d/osrf.conf containing a new library path, then run the command ldconfig to automatically read the file and modify the system dynamic library path: - - + + # as the root user: echo "/usr/local/lib" >> /etc/ld.so.conf.d/osrf.conf echo "/usr/local/lib/dbd" >> /etc/ld.so.conf.d/osrf.conf ldconfig - + Restart the PostgreSQL Server @@ -995,11 +995,11 @@ execute the following command (remember to replace PGSQL_VERSION with your installed PostgreSQL version, for example 8.3): - - + + # as the opensrf user: /etc/init.d/postgresql-PGSQL_VERSION restart - + Configure Evergreen @@ -1008,13 +1008,13 @@ and linked later in . As the opensrf user, return to the Evergreen build directory and execute these commands: - - + + # as the opensrf user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 ./configure --prefix=/openils --sysconfdir=/openils/conf make - + Compile, Link and Install Evergreen @@ -1022,12 +1022,12 @@ default Evergreen Staff Client. As the root user, return to the Evergreen build directory and use the make utility as shown below: - - + + # as the root user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 make STAFF_CLIENT_BUILD_ID=rel_1_6_1_2 install - + The Staff Client will also be automatically built, but you must remember to set the variable STAFF_CLIENT_BUILD_ID to match the version of the Staff Client you will use to connect to the Evergreen server. @@ -1040,12 +1040,12 @@ directory /openils/var/web/xul that points to the subdirectory /server of the new Staff Client build: - - + + # as the root user: cd /openils/var/web/xul ln -sf rel_1_6_1_2/server server - + Copy the OpenSRF Configuration Files @@ -1057,8 +1057,8 @@ to opensrf. As the root user, execute the following commands: - - + + # as the root user: cd /openils/conf cp opensrf.xml opensrf.xml.BAK @@ -1067,7 +1067,7 @@ cp opensrf_core.xml.example opensrf_core.xml cp oils_web.xml.example oils_web.xml chown -R opensrf:opensrf /openils/ - + Create and Configure PostgreSQL Database @@ -1091,25 +1091,25 @@ As the postgres user on the PostgreSQL system create the PostgreSQL database, then set some internal paths: - - + + # as the postgres user: createdb evergreen -E UTF8 -T template0 createlang plperl evergreen createlang plperlu evergreen createlang plpgsql evergreen - + Continue as the postgres user and execute the SQL scripts as shown below (remember to adjust the paths as needed, where PGSQL_VERSION is your installed PostgreSQL version, for example 8.3). - - + + # as the postgres user: psql -f /usr/share/postgresql/PGSQL_VERSION/contrib/tablefunc.sql evergreen psql -f /usr/share/postgresql/PGSQL_VERSION/contrib/tsearch2.sql evergreen psql -f /usr/share/postgresql/PGSQL_VERSION/contrib/pgxml.sql evergreen - + Create <systemitem class="username">evergreen</systemitem> PostgreSQL user @@ -1118,14 +1118,14 @@ named evergreen and assign a password (remember to replace NEWPASSWORD with an appropriate new password): - - + + # as the postgres user: createuser -P -s evergreen - + Enter password for new role: NEWPASSWORD Enter it again: NEWPASSWORD - + Create database schema @@ -1137,15 +1137,15 @@ the following commands and replace HOSTNAME, PORT, PASSWORD and DATABASENAME with appropriate values: - - + + # as the root user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config \ --service all --create-schema --create-bootstrap --create-offline \ --hostname HOSTNAME --port PORT \ --user evergreen --password PASSWORD --database DATABASENAME - + On most systems, HOSTNAME will be localhost and PORT will be 5432. @@ -1184,13 +1184,13 @@ Apache modules - - + + # as the root user: a2enmod ssl # enable mod_ssl a2enmod rewrite # enable mod_rewrite a2enmod expires # enable mod_expires - + As the commands execute, you may see warnings similar to: Module SOMEMODULE already enabled but you can safely ignore them. @@ -1201,14 +1201,14 @@ Evergreen installation directory to the Apache directory. As the root user, perform the following commands: - - + + # as the root user: cd /home/opensrf/Evergreen-ILS-1.6.1.2 cp Open-ILS/examples/apache/eg.conf /etc/apache2/sites-available/ cp Open-ILS/examples/apache/eg_vhost.conf /etc/apache2/ cp Open-ILS/examples/apache/startup.pl /etc/apache2/ - + Create a Security Certificate @@ -1219,13 +1219,13 @@ accept the warnings in the Staff Client and browser during testing and development. As the root user, perform the following commands: - - + + # as the root user: mkdir /etc/apache2/ssl cd /etc/apache2/ssl openssl req -new -x509 -days 365 -nodes -out server.crt -keyout server.key - + You will be prompted for several items of information; enter the appropriate information for each item. The new files server.crt and server.key will @@ -1250,7 +1250,7 @@ In the section <Directory "/openils/var/cgi-bin"> replace the line: - Allow from 10.0.0.0/8 + Allow from 10.0.0.0/8 with the line: Allow from all This change allows access to your configuration @@ -1293,17 +1293,17 @@ Debian Lenny, as the root user, edit the Apache configuration file and change the lines: - - + + export APACHE_RUN_USER=www-data export APACHE_RUN_GROUP=www-data - + to instead read: - - + + export APACHE_RUN_USER=opensrf export APACHE_RUN_GROUP=opensrf - + As the @@ -1313,11 +1313,11 @@ modify the value for KeepAliveTimeout and MaxKeepAliveRequests to match the following: - - + + KeepAliveTimeout 1 MaxKeepAliveRequests 100 - + Further configuration changes to Apache may be @@ -1331,7 +1331,7 @@ and modify the section related to prefork configuration to suit the load on your system: - StartServers 20 MinSpareServers 5 @@ -1350,15 +1350,15 @@ following Apache configuration commands to disable the default It Works web page and enable the Evergreen web site, and then restart the Apache server: - - + + # as the root user: # disable/enable web sites a2dissite default a2ensite eg.conf # restart the server /etc/init.d/apache2 reload - + @@ -1468,11 +1468,11 @@ Modify the permissions in the directory /openils/var/cgi-bin to make the files executable: - - + + # as the opensrf user: chmod 755 /openils/var/cgi-bin/*.cgi - + As the opensrf user, @@ -1485,12 +1485,12 @@ before the line [ -z "$PS1" ] && return . This will allow headless (scripted) logins to load the correct environment. - - + + # as the opensrf user: echo "export PERL5LIB=/openils/lib/perl5:\$PERL5LIB" >> ~/.bashrc . ~/.bashrc - + @@ -1513,21 +1513,21 @@ As the root user, start the ejabberd and memcached services as follows: - - + + # as the root user: /etc/init.d/ejabberd start /etc/init.d/memcached start - + As the opensrf user, start Evergreen as follows: - - + + # as the opensrf user: osrf_ctl.sh -l -a start_all - + The flag forces Evergreen to use localhost (your current system) as the hostname. The flag starts the other @@ -1574,12 +1574,12 @@ changes to the library hierarchy. As the opensrf user, execute the following command and review the results: - - + + # as the opensrf user: cd /openils/bin ./autogen.sh -c /openils/conf/opensrf_core.xml -u - + Updating Evergreen organization tree and IDL using '/openils/conf/opensrf_core.xml' Updating fieldmapper Updating web_fieldmapper @@ -1596,16 +1596,16 @@ Refreshing proximity of org units Successfully updated the organization proximity Done - + As the root user, restart the Apache Web server: - - + + # as the root user: /etc/init.d/apache2 restart - + If the Apache Web server was running when you started the OpenSRF services, you might not be able to successfully log into the OPAC or Staff Client until the Apache Web server has been restarted. @@ -1626,11 +1626,11 @@ srfsh commands, type help at the prompt. As the opensrf user, execute the following commands to test your Evergreen connection: - - + + # as the opensrf user: /openils/bin/srfsh - + srfsh% login admin open-ils Received Data: "250bf1518c7527a03249858687714376" ------------------------------------ @@ -1651,21 +1651,20 @@ ------------------------------------ Request Completed Successfully Request Time in seconds: 1.336568 - ------------------------------------ - - + ------------------------------------ + If this does not work, try the following: As the opensrf user, run the settings-tester.pl utility to review your Evergreen installation for any system configuration problems: - - + + # as the opensrf user: cd /home/opensrf ./Evergreen-ILS-1.6.1.2/Open-ILS/src/support-scripts/settings-tester.pl - + If the output of settings-tester.pl does not help you find the problem, please do not make any significant changes to your configuration. @@ -1693,11 +1692,11 @@ version 3.0 and later on Ubuntu and Debian distributions). As the root user, start the Staff Client as shown: - - + + # as the root user: xulrunner /home/opensrf/Evergreen-ILS-1.6.1.2/Open-ILS/xul/staff_client/build/application.ini - + A login screen for the Staff Client similar to this should appear: Logging into the Staff Client @@ -1743,11 +1742,11 @@ commands. Note the use of restart to force the new Evergreen modules to be reloaded even if the Apache server is already running. Any problems found with your configuration files should be displayed: - - + + # as the root user: apache2ctl configtest && /etc/init.d/apache2 restart - + Stopping Evergreen @@ -1756,12 +1755,12 @@ Evergreen services. As the opensrf user, stop all Evergreen services by using the following command: - - + + # as the opensrf user # stop the server; use "-l" to force hostname to be "localhost" osrf_ctl.sh -l -a stop_all - + You can also stop Evergreen services without the flag, but the osrf_ctl.sh utility must know the fully qualified domain name for the system on which it will execute. That hostname may @@ -1799,7 +1798,7 @@ You used the command openssl in an earlier step to temporarily create a new SSL key for the Apache server (see for further - information). This self-signed security certificate was adequate during + information). This self-signed security certificate was adequate during testing and development, but will continue to generate warnings in the Staff Client and browser. For a public production server you should configure or purchase a signed SSL certificate. @@ -1836,105 +1835,168 @@
Installing In Virtualized <systemitem class="osname">Linux</systemitem> Environments - This section describes the installation of Evergreen software in so-called "virtualized" - software environments. Evergreen software runs as a native application on any of several - well-known x86 (32-bit) and x86-64 (64-bit) Linux - distributions including Ubuntu and - Debian but it does not run as a native application - on the Microsoft Windows operating system. - However, it is possible to execute Evergreen on a Windows - host system by running it within a virtual Linux-guest installation, which itself executes - on the Windows system. - The Linux environment is fully emulated and acts - (within limits) just as if it were executing on a real standalone system. - This technique of emulating a Linux environment on - a Windows host is a practical way to install and run an - Evergreen system if it is not possible to dedicate a physical machine solely as a - Linux host for Evergreen. This architecture is not - recommended for large scale systems since there are performance limitations to running Evergreen - in a virtualized environment. However, it is a reasonable architecture for smaller experimental - systems, as a proof of concept, or as a conference-room pilot. - + This section describes the installation of Evergreen software in so-called + "virtualized" software environments running on the + Microsoft Windows operating system. + Evergreen software runs as a native application + on any of several well-known x86 (32-bit) and x86-64 (64-bit) + Linux distributions including + Ubuntu and + Debian, but will not run directly on + the Microsoft Windows operating system. + Instead, Evergreen executes within an encapsulated virtual + Linux "guest" installation, + which itself executes directly on Windows. + The Linux environment is fully emulated + and acts (within limits) just as if it were executing on a real standalone system. + This technique of emulating a Linux + environment on a Windows host is a practical + way to install and run an Evergreen system if it is not possible to dedicate a + physical machine solely as a Linux host, but + the architecture is not recommended for large scale systems. There are performance + limitations to running Evergreen in a virtualized environment, since the + virtualization application itself consumes memory and contributes to the CPU load on + the Windows host system. The emulated + Evergreen environment will execute more slowly than if it were a standalone system. + However, it is still a reasonable architecture for smaller experimental systems or as + a proof of concept. +
Installing Virtualization Software As described above, Evergreen can be installed on top of an emulated - Linux environment. The - Linux environment, in turn, is installed - on top of a software application such as "VirtualBox", - "VMware" or "VirtualPC" which must - first be installed on the Windows system. This - section contains step-by-step examples that show installing popular virtualization - applications on a Windows host system. Following - this section are further descriptions of installing - Linux and Evergreen systems using that - virtualization software. -
+ Linux environment which, in turn, + is installed on top of a software application such as + "VirtualBox" or "VMware" + executing on Windows. + This section contains step-by-step examples on installing popular virtualization + applications on a Windows host system. + Following this section are further descriptions of installing + Linux and Evergreen systems on top + of that virtualization software. +
Installing <application>"VirtualBox"</application> Virtualization Software This section reviews installation of the "VirtualBox" application on - WindowsXP Professional (SP2). - Download the latest edition of VirtualBox from their official website: - http://virtualbox.org - and follow the on screen instructions to install the software. + WindowsXP Professional (SP3). + Download the latest version of the + VirtualBox from the official website: + + http://www.virtualbox.org/wiki/Downloads, + then run the executable file. Continue with the steps shown in the + next five figures until the software has been successfully + installed. The following example shows the installation of VirtualBox + version 3.8.2 . +
+ Starting the Windows installation of <application>VirtualBox</application> + + + + + +
+
+ Welcome to <application>VirtualBox</application> setup wizard + + + + + +
+
+ Accept the license agreement + + + + + +
+
+ Waiting for installation to complete + + + + + +
+
+ Installation is complete; start <application>VirtualBox</application> + + + + + +
+ At this point, VirtualBox has been + installed and started for the first time. Please continue with + + for further instructions on the next step: installing the + Linux / Evergreen distribution.
- Installing VMware Virtualization Software - - virtualization software - VMware - - This section reviews installation of the - "VMware" application on - WindowsXP Professional (SP2). - Find and Download the free virtual machine software of from the VMware - official website: - http://downloads.vmware.com - and follow the on-screen instructions. + Installing <application>"VMware"</application> Virtualization Software + For instructions on installing VMware, + visit the official website + http://www.vmware.com/. Then continue with + for + further instructions on the next step: installing the + Linux / Evergreen distribution.
- - - Installing <systemitem class="osname">Linux</systemitem> / - Evergreen on Virtualization Software - After the virtualization software is installed and running, there are two ways to - continue with installing Linux and Evergreen - software in the new virtualized environment: +
+
+ Installing <systemitem class="osname">Linux</systemitem> + / Evergreen on Virtualization Software + After the virtualization software is installed and running, there are + two ways to continue with installing + Linux and Evergreen software in the new + virtualized environment: - Download and install a prebuilt software image that contains a - working Linux / Evergreen system - (see for + Download and install a prebuilt software image that + contains a working + Linux / Evergreen + system (see + for details) - Manually install a Linux - guest system, then manually install Evergreen on it. + Manually install a + Linux guest system, + then manually install Evergreen on it (see + for + details) We review each method in the following sections.
Download and install a prebuilt software image - You can download a prebuilt software image that, when installed with your - virtualization software, emulates a - Linux guest system containing a running - Evergreen distribution. The image is essentially a snapshot of a hard disk from - a fully configured, functional Linux - system with Evergreen already installed. - We recommend this approach if you wish to get Evergreen running quickly - with minimal attention to configuration. After reviewing only a few - configuration details you can have a working Evergreen system that integrates - smoothly with the rest of your network. See - for a list of prebuilt - software images that are currently available to download and install - DISCLAIMER: The following virtual images have been contributed by members - of the Evergreen community for the purposes of testing, evaluation, training, - and development. + You can download a prebuilt software image that, when installed + on your virtualization software, emulates a + Linux guest system containing + a running Evergreen distribution. The image is essentially a snapshot + of a hard disk from a fully configured, functional + Linux system with Evergreen + already installed. It is even possible to install a software image + that is preloaded with useful data, e.g., Gutenberg records. + We recommend this approach if you wish to get Evergreen running + quickly with minimal attention to configuration. After adjusting only + a few configuration details you can have a working Evergreen system + that integrates smoothly with the rest of your network. See + for a list of + prebuilt software images that are currently available to download and + install. + Evergreen servers and staff clients must match. For example, if + you are running server version 1.4.0.1, you should use version 1.4.0.1 + of the staff client. + DISCLAIMER: The following virtual images have been contributed + by members of the Evergreen community for the purposes of testing, + evaluation, training, and development.
Linux / Evergreen Virtual Images - - - - + + + + Linux Version @@ -1945,88 +2007,277 @@ - Debian lenny (5.0) + Debian "Lenny" (5.0) + 1.6.1.4 + + + download + + VirtualBox image (no preloaded data) + + + Debian "Lenny" (5.0) 1.6.0.1 - download + + download - VirtualBox image + VirtualBox image (no preloaded data) - Ubuntu karmic koala (9.10) + Ubuntu "Karmic Koala" (9.10) 1.6.0.0 - download + + download + + VirtualBox image (no preloaded data) + + + Ubuntu "Hardy Heron" (8.04) + 1.2.3.1 + + + download + + VirtualBox image (no preloaded data) + + + Debian Etch (4.0) + 1.2.2.3 + + + download + + VMware image (preloaded with 13,000 Gutenberg records) + + + Ubuntu "Gutsy Gibbon" (7.10) + 1.2.1.4 + + + download + + VMware image, contributed by + + the Hekman Library, Calvin College + + + Gentoo + 1.1.5 + + + download - VirtualBox image + VMware image on Gentoo, courtesy of + Dan Scott, + Laurentian University + (file size is 1.1GB)
+ For the following example, we have already installed the + VirtualBox application (see + for details). + Continue with the steps as shown; refer to the accompanying figures for further + information: - VirtualBox Example - - virtualization software - VirtualBox - Start VirtualBox for the first time and select FileVirtualBox Media ManagerAdd to locate the prebuilt software image just downloaded (the example shows it was extracted from the original - zip file into a temporary directory - C:\temp). + .ZIP file into a temporary directory + C:\temp). See + + for details. - After selecting the file, click 'Open' to import it. + After selecting the file, click + Open to import it (see + + for details). - Then click 'OK' to save the selection - and return to the VirtualBox Media Manager + Then click OK to save the + selection and return to the VirtualBox Media Manager (see + + for details). - Click 'New', then 'Next' - to continue and create a new virtual machine (VM). + Click New to start the "Virtual + Machine Wizard", then Next to continue + and create a new virtual machine (VM) + ). - Create a new name for the VM and set the operating system - type, then click 'Next'. + Create a new name for the VM and set the operating + system type, then click Next (see + ). - Set the memory size (at least 512Mb), - then click 'Next'. + Set the memory size (we chose the default value of + 512Mb), then click Next (see + ). Edit the Virtual Hard Disk configuration settings; click - the radio boxes Boot Hard Disk and - Use existing hard disk - and ensure that the disk name Evergreen1601_DebianLenny.vmdk - is selected. Click 'Finish' to finish the - setup. + the radio boxes "Boot Hard Disk" and "Use existing hard disk" + and ensure that the disk name "Evergreen1601_DebianLenny.vmdk" + is selected. Click Finish to finish the + setup (see + ). Install the VirtualBox Guest Additions (really a required upgrade to - VirtualBox) + VirtualBox). - Return to VirtualBox and see the summary of the VM just - created. Click 'Start' to boot the new VM. + Return to VirtualBox and see the summary of the VM just created + (see + and ). + Click Start to boot the new VM, then + log in with username root and + password evergreen to continue. + + At this point you have a running + Linux / Evergreen system. + If you need to modify the Evergreen configuration in any way, review + the sectons of the standard Evergreen installation instructions in + that deal with + configuration. +
+ Starting <application>VirtualBox</application> for the first time + + + + + +
+
+ Selecting the software image in Virtual Media Manager + + + + + +
+
+ New software image added to <application>VirtualBox</application> + + + + + +
+
+ Creating a new VM + + + + + +
+
+ Setting the VM name and OS type + + + + + +
+
+ Setting memory size + + + + + +
+
+ Setting up the Virtual Hard Disk + + + + + +
+
+ Finishing definition of new VM + + + + + +
+
+ Summary of the new VM + + + + + +
+ +
+ Manually install <systemitem class="osname">Linux</systemitem> and Evergreen + Instead of installing a pre-built, pre-configured virtual image + of Linux containing the + Evergreen software, you could also manually install a + Linux guest system, then install + Evergreen from scratch on that system. + We recommend this approach if you need to specially configure + either the Linux system or + Evergreen itself. This will require a detailed review of both + Linux and Evergreen + configuration details. You are essentially doing a normal Evergreen + installation on a Linux + system; it just happens that + Linux is running within a + virtualized environment on a Windows + system. See for + information on the normal Evergreen installation, then continue with this + section. + For the following example, we have already installed the + VirtualBox application (see + for details). + Continue with the steps as shown; refer to the accompanying figures + for further information: + - See the start of the Linux - boot sequence. Choose Debian Gnu/Linux, kernel - 2.6.26-2-686 from the startup menu and click - 'Enter' to start - Linux and Evergreen. - After some delay you should see the command line prompt - debian-lenny login:. Log in with username - root and password evergreen - to continue. + Download and install an appropriate version of the + standard Ubuntu software + distribution on "VirtualBox". + + + Start (boot) Ubuntu. + + + Install Evergreen on the + Ubuntu system.
- +
+ Summary + Whether you install a pre-built, pre-configured virtual image of + Linux already containing the + Evergreen software (see ), + or you install a plain virtual + image Linux and then install + Evergreen from scratch (see ), + your Windows system is now hosting + an Linux system, which itself is + hosting the Evergreen distribution. So far as Evergreen is concerned, + it is happily executing in a standard + Linux environment and should + behave as if it were executing on a standalone + Linux system. +
+ -- 2.11.0