Changes between Version 94 and Version 95 of client_installation_guide_rpm

Show
Ignore:
Timestamp:
10/03/12 10:34:48 (12 years ago)
Author:
piontek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • client_installation_guide_rpm

    v94 v95  
    1 = QCG Broker Client Installation = 
     1= QCG-Client Installation = 
    22 
    33[[PageOutline]]  
     4 
     5'''The QCG-Client is the command-line java based client to the QCG-Broker service.''' 
    46 
    57 
    68= Requirements = 
    79* '''PL-Grid LDAP integration''' - the machine where the client is to be installed has to be configured to allow users to log in to the their "plg*" accounts. 
    8 * '''Packages requirements''' - all packages required by the QCG-Broker client will be automatically installed by YUM during the installation of qcg-broker-client package. 
     10* '''Packages requirements''' - all packages required by the QCG-Client will be automatically installed by YUM during the installation of qcg-broker-client package. 
    911 * ''Java (>= 1.6)''\\ 
    10 * '''gridFTP server''' - the gridFTP server providing access to user's data for staging them in/out. It can be installed on the client machine (see Optional steps) or be any other instance of server having access to the data.  
     12* '''GridFTP server''' - the GridFTP server providing access to user's data for staging them in/out. It can be installed on the client machine (see Optional steps) or be any other instance of server having access to the data.  
    1113 
    1214= Mandatory steps = 
    13 The installation and configuration of QCG-Broker client consists of two mandatory steps: 
     15The installation and configuration of the QCG-Client consists of two mandatory steps: 
    1416* installation of set of trusted Certificate Authorities certificates, 
    1517* installation of the client itself. 
     18 
    1619== Certificate authorities == 
    17  
    18 To enable mutual authentication and secure communication between client and QCG-Broker service set of trusted CA certificates must be copied either into the /etc/grid-security/certificates directory or configured for every user.  
     20To enable mutual authentication and secure communication between the client and the QCG-Broker service set of trusted CA certificates must be copied either into the /etc/grid-security/certificates directory or configured individually for every user.  
     21 
    1922=== EGI IGTF CAs === 
    2023Install EGI Accepted CA certificates (this also install the Polish Grid CA) 
     
    4548 
    4649=== PL-Grid Simpla-CA certificate (not part of IGTF) === 
    47 * Add appropriate YUM repositories 
     50* Add appropriate YUM repository 
    4851{{{ 
    4952#!div style="font-size: 90%" 
     
    103106}}} 
    104107 
    105 * Install cron job for it 
     108* Install cron job for fetching CRLs 
    106109{{{ 
    107110#!div style="font-size: 90%" 
     
    125128 
    126129 
    127 == QCG-Broker client == 
     130== QCG-Client == 
     131 
    128132=== Software repositories === 
    129 The packages are designed for Scientific Linux 5.x 
     133'''The packages are designed for Scientific Linux 5.x 
     134 
    130135The installation process requires root privileges. 
    131  
    132 * Install PL-Grid or/and QCG repositories: 
    133  * Official PL-Grid repository 
     136''' 
     137 
     138* Add PL-Grid or/and QCG repositories: 
     139 * Official PL-Grid repository (recommended) 
    134140{{{ 
    135141#!div style="font-size: 90%" 
     
    138144}}} 
    139145}}} 
    140  * !QosCosGrid testing repository 
     146 * Official !QosCosGrid repository 
    141147{{{ 
    142148#!div style="font-size: 90%" 
     
    151157}}} 
    152158}}} 
    153  * !QosCosGrid developing repository (not recommended - only for testing purposes) 
     159 * !QosCosGrid developing repository (not recommended - mainly for developers and testers) 
    154160{{{ 
    155161#!div style="font-size: 90%" 
     
    166172 
    167173=== Installation === 
    168 * install QCG-Broker client using YUM Package Manager: 
     174* install QCG-Client using YUM Package Manager: 
    169175{{{ 
    170176#!div style="font-size: 90%" 
     
    193199* QCG_URL_DEFAULT - the URL of QCG-Broker service 
    194200* QCG_DN_DEFAULT - the Distinguished Name of the QCG-Broker service 
    195 * QCG_CLIENT_LOCATION_DEFAULT - the location ot the client. This value is set during the installation procedure and  
    196  
    197 Optionally it is possible to configure the host and port of GridFTP service which will be used by client to staging input/output files 
    198 * GFTP_HOSTNAME - hostname of the host where the gridFTP server is installed. If the property is not set the default value is hostname of the host where the client is installed, 
    199 * GFTP_PORT - port which the gridFTP server is listening on. If the property is not set the default value is "2811". 
     201* QCG_CLIENT_LOCATION_DEFAULT - the location of the client. This value is set during the installation procedure and shouldn't be modified. 
     202 
     203Optionally it is possible to configure the host and port of the GridFTP server which will be used by client for staging input/output files 
     204* GFTP_HOSTNAME - hostname of the host where the GridFTP server is installed. If the property is not set the default value is hostname of the host where the client is installed, 
     205* GFTP_PORT - port which the GridFTP server is listening on. If the property is not set the default value is "2811". 
    200206 
    201207Additionally it is possible to configure also the settings responsible for defining the policy for creation and refreshing of user's proxy. 
    202 * QCG_PROXY_DURATION_DEFAULT - default length in hours of the created proxy  
    203 * QCG_PROXY_DURATION_MIN - minimal acceptable lifetime of the proxy. If the remaining lifetime of the proxy is smaller then the value, the proxy will be automatically recreated. 
     208* QCG_PROXY_DURATION_DEFAULT - default length in hours of the proxy created by QCG-Client, 
     209* QCG_PROXY_DURATION_MIN - minimal acceptable lifetime of the proxy. If the remaining lifetime of the proxy is smaller then the given value, the proxy is automatically recreated. 
    204210 
    205211 
     
    222228 
    223229'''IMPORTANT:''' 
    224 To configure the client to contact the official, production instance of QCG-Broker service deployed on PLGrid infrastructure please use the following values: 
     230To configure the client to contact the official, production instance of the QCG-Broker service deployed on PLGrid infrastructure please use the following values: 
    225231{{{ 
    226232#!div style="font-size: 110%" 
     
    232238 
    233239== Site configuration == 
    234  
    235240* Configure the site to display "the message of the day" for QCG-Client. 
    236241 The path to the motd file is ''/usr/share/qcg/qcg-broker-client/doc/motd''. 
    237242* Configure the site for "nightly yum updates" to automatically install new versions of the client. 
     243 
     244 
    238245= Optional steps = 
    239  
    240 The optional steps consider installation and configuration of gridFTP server as well installation and configuration of the !GridMapFileGenerator tool being responsible for periodic creation of grid-map-file used by the server for authorisation and mapping users to physical accounts. 
    241  
    242 The steps are for the case when there is no other gridFTP server providing access to user's data on the client machine and the dedicated instance of the server has to be installed. 
    243  
    244 '''IMPORTANT:''' In most cases it should be possible to configure QCG-client to use the gridFTP server installed on the QCG-Computing site. Such configuration is recommended as it reduces number of software components that have to be maintained.  
     246The optional steps consider installation and configuration of the GridFTP server as well installation and configuration of the !GridMapFileGenerator tool being responsible for periodic creation of grid-map-file used by the server for authorisation and mapping users to physical accounts. 
     247 
     248The steps are for the case when there is no other GridFTP server providing access to user's data on the client machine and the dedicated instance of the server has to be installed. 
     249 
     250'''IMPORTANT:''' In most cases it should be possible to configure QCG-client to use the GridFTP server installed on the QCG-Computing site. Such configuration is recommended as it reduces number of software components that have to be maintained.  
     251 
    245252== GridFTP server == 
    246 For the user convenience QCG client is able to stage in input data accessible from the host where it is installed and also to stage out output data there. The functionality requires the data to be accessible via gridFTP server. The gridFTP server can be installed on the client machine or it can be any gridFTP server having access to the data on client machine. The simplest and the most popular solution is to mount the same shared network file system on both machines. The mount point must be exact the same. Paths to data have to be exactly the same on both machines. 
     253For the user convenience QCG-client is able to stage in input data accessible from the host where it is installed and also to stage out output data there. The functionality requires the data to be accessible via GridFTP server. The GridFTP server can be installed on the client machine or it can be any GridFTP server having access to the data on client machine. The simplest and the most popular solution is to mount the same shared network file system on both machines. The mount point must be exact the same. Paths to data have to be exactly the same on both machines. 
    247254 
    248255 
     
    255262}}} 
    256263 
    257 The grid-ftp server requires the X.509 certificate and key to be present in following locations 
     264The grid-ftp server requires the X.509 certificate and key to be present in the following locations 
    258265* ''/etc/grid-security/hostcert.pem'' 
    259266* ''/etc/grid-security/hostkey.pem'' 
    260267 
    261 The gridFTP server has to be configured to know the range of opened ports for connections. 
     268The GridFTP server has to be configured to know the range of opened ports for connections. 
    262269Please edit the /etc/xinetd.d/gsiftp file and set the GLOBUS_TCP_PORT_RANGE environment variable. 
    263270 
     
    305312 
    306313== Grid Mapfile == 
    307 To have access do data every authenticated user must be authorized by gridFTP server against the `grid-mapfile`. This file can be created manually by an administrator (if the service is run in "test mode") or generated automatically based on the LDAP directory service. 
     314To have access do data every authenticated user must be authorized by GridFTP server against the `grid-mapfile`. This file can be created manually by an administrator (if the service is run in "test mode") or generated automatically based on the LDAP directory service. 
     315 
    308316=== Manually created grid mapfile (for testing purpose only) === 
    309317{{{ 
     
    314322}}} 
    315323}}} 
     324 
    316325=== LDAP generated grid mapfile === 
    317 * Create the ''qcg-dev'' group - this grou is allowed to read the configuration and log files. 
     326* Create the ''qcg-dev'' group - this group is allowed to read the configuration and log files. 
    318327{{{ 
    319328#!div style="font-size: 90%" 
     
    352361 
    353362After installing and running this tool one can find three files: 
    354  * /etc/grid-security/grid-mapfile.local - here you can put list of DN and local unix accounts name that will be merged with data acquired from local LDAP server 
    355  * /etc/grid-security/grid-mapfile.deny - here you can put list od DN's (only DNs!) that you want to deny access to the QCG-Computing service 
     363 * /etc/grid-security/grid-mapfile.local - here you can put list of DNs and local unix account names that will be merged with data acquired from the local LDAP server 
     364 * /etc/grid-security/grid-mapfile.deny - here you can put list od DN's (only DNs!) that you want to deny access to the GridFTP server 
    356365 * /etc/grid-security/grid-mapfile - the final gridmap file generated using the above two files and information available in local LDAP server. Do not edit this file as it is generated automatically! 
    357366