Changes between Version 6 and Version 7 of Download/SCDB


Ignore:
Timestamp:
Oct 12, 2006, 11:35:34 PM (19 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Download/SCDB

    v6 v7  
    44[[TOC(inline)]]
    55
     6
     7== Web Server Installation ==
     8
     9The Quattor server needs to run a Web server to serve profiles, kickstart configuration files and execute the CGI script at end of installation to change PXE boot to local disk. In addition, it is recommended (but not necessary) to use this Web server for serving RPMs.
     10
     11Web server installation requires nothing specific, just the configuration of a document root with enough space if you plan to serve RPMs and the configuration of CGIs. This Web server can be shared with other usages and you can use a specific virtual host instead of a dedicated server.
     12
     13Apache is the recommended Web server (installation instuctions here refer to Apache) and it can be installed from the OS distribution.
    614
    715== Subversion Server ==
     
    7684 * Adding a script on the Quattor server that will be launched by the hook script, using ssh
    7785 * Configuring SSH keys to allow execution of the previous script as root (preferably) from the Apache account
    78  * Add a CGI script on Quattor web server used at end of installation of a machine to allow next boot from local disk.
     86 * Add a CGI script on Quattor server used at end of installation of a machine to allow next boot from local disk.
     87 * Configuration of AII
     88
    7989
    8090=== Installation of hook script and server script ===
     
    8494The other script, `build-tag.pl`, also provided as part of SCDB, in the `src/hooks` directory, must be installed (root executable) in `/root/quattor` on the Quattor server.
    8595
     96
     97=== Creation of Ssh Keys ===
     98
     99Currently, deployment of new version of the templates is done by the hook script triggered by `ant deploy` executing the server script `build-tag.pl` through ssh. There is no way to enter a password at this time, thus ssh must be configured in such a way that the Apache account on the Subversion server can do a ssh connection as root on the Quattor server, without password. The easiest is to use ssh keys to do that.
     100
     101
     102=== Post-installation CGI Script ===
     103
     104At the end of a machine installation, as part of the Kickstart post-intallation script, a CGI script is executed on the Quattor server to change PXE configuration in order for the machine to boot from local disk next time. This allows to set PXE as the first boot device in the BIOS and control re-installation via `aii-shellfe` command.
     105
     106This script, `build-tag.pl`, can be found in SCDB directory `src/cgis`. It must be placed on the Web server running on the Quattor server, in the directory for CGIs.
     107
     108
     109=== Configuration of AII ===
     110
     111This involves 2 separate steps :
     112 * Customization of `/etc/aii*.conf` files
     113 * Customization of AII related variables in templates
     114
     115To customize AII configuration files, located in `/etc` and named `aii-*.conf`, refer to the comment in each files. Main parameters to customize are the URL to use to download profiles (in `aii-shellfe.conf`) and the directory where to place kickstart configuration files produced by AII (in `aii-osinstall.conf`).
     116
     117There are a few variables to customize in site templates to reflect your Quattor and AII configuration, mainly :
     118
     119 * `QUATTOR_PROFILE_URL` : URL to use to download machine profiles.
     120 * `AII_OSINSTALL_SRV` : Name of the Web server serving kickstart configuration files and RPMs.
     121 * `AII_ACKSRV` : Name of the Web server to use for the post-installation CGI. Defaults to `AII_OSINSTALL_SRV`
     122 * `AII_ACKCGI` : post-installation CGI URL. Defaults to `/cgi-bin/aii-installack.cgi`.
     123 * `AII_OSINSTALL_TEMPLATE` : name of the Kickstart configuration template to use. Defaults to `i386_sl3_ks.conf`.
     124
     125These variables are generally defined site-wide, in the template `pro_site_global_variables.tpl` located in site directory. Look at provided examples, in SCDB distribution.
     126
     127
     128