Difference: IgiEmi (63 vs. 64)

Revision 642012-10-25 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IGIGuides"

IGI (based on EMI) Installation and Configuration

Line: 453 to 453
 
# yum clean all
Changed:
<
<
The CREAM CE Services were tested with gLite WN SL5 x86_64 and also with ig_WN SL5 x86_64.
  • Please remember that the TORQUE Server and Client work only if the CE and the WNs are SL5 x86_64 and the MAUI version is the same in the server and client nodes. Please update the WN if you have an old installation.
>
>
The CREAM CE Services were tested with gLite WN SL5/SL6 x86_64 and also with ig_WN SL5/SL6 x86_64.
 

CREAM CE Prerequisites

Line: 663 to 662
 

WN Installation and Configuration

Changed:
<
<
Have a look to the section Repository Settings and ensure that you have the common repo files.
Before starting the installation procedure remember to clean all yum cache and headers:
>
>
  • Supported platforms: SL5/x86_64 & SL6/x86_64
 
Changed:
<
<
# yum clean all
>
>
  • Have a look to the section Repository Settings and ensure that you have the common repo files.
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all
 

WN Prerequisites

Line: 680 to 678
 

CAs installation:

Changed:
<
<
  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core
>
>
  • Install CAs on ALL profiles:
    # yum install ca-policy-egi-core
 

Service installation

Changed:
<
<
  • Have a look to the WN documentation before starting the installationl: WN Guide.
  • Install the WN metapackages, containing all packages needed:
# yum install <metapackage> emi-version;
  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of these (see table bellow)
>
>

  • Install the WN metapackage:
    • EMI 1:
      # yum install <metapackage> emi-version openldap-client python-ldap 
    • EMI 2:
      # yum install <metapackage> 

  • IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster (see table bellow)
 
    • IGI customizations:
      • unique metapackages & configurations for WNs with support for the batch systems Torque & LSF
Changed:
<
<
      • contains the "LCG Applications Dependency Metapackage" - HEP_OSLib, compat-gcc-34-g77, compat-libgcc-296, compat-libstdc++-296, gcc-c++, ghostscript lapack, ncurses, openafs, openafs-client, openldap-clients
      • contains yaim-addons - new configuration package with IGI-custom configuration functions and files (replaces ig-yaim)
>
>
      • contains (where available) the "LCG Applications Dependency Metapackage" - HEP_OSLib, compat-gcc-34-g77, compat-libgcc-296, compat-libstdc++-296, gcc-c++, ghostscript lapack, ncurses, openafs, openafs-client, openldap-clients
      • contains yaim-addons - new configuration package with IGI-custom configuration functions and files (replaces ig-yaim), like - "ssh passwordless"
 
Line: 711 to 713
 
IMPORTANT NOTE:
Changed:
<
<
Name are case sensitive, both for metapackages installation and notetype configuration, you have to use the ones in the table above.
>
>
Metapackages & Notetypes Names are case sensitive, both for metapackages installation and notetype configuration, PLEASE use the ones in the table above.
 

IMPORTANT NOTE FOR TORQUE:
Changed:
<
<
After the Torque installation you should have the version 2.5.7-7.
Please remember to copy the munge key from the batch master to the WN just installed
# scp <batch master host>:/etc/munge/munge.key /etc/munge 
>
>
After the Torque installation you should have the version 2.5.7-7 (SL5) or 2.5.7-9 (SL5)
Please remember to copy the munge key from the batch master to the WN just installed
# scp <batch master host>:/etc/munge/munge.key /etc/munge 

For more details please read Deployment Notes of TORQUE WN config - it applies to all versions >= 2.5.7-1
 

Service Configuration

Line: 728 to 730
 
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the WN profiles (WN_torque, WN_torque_noafs, WN_LSF, WN_LSF_noafs)
Changed:
<
<
For Torque:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque 
>
>
  • For Torque:
    # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_torque 
 or
Changed:
<
<
# /glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_torque_noafs 
>
>
# /glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_torque_noafs 
 
Changed:
<
<
For LSF:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF
>
>
  • For LSF:
    # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_LSF
 or
Changed:
<
<
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN_LSF_noafs
>
>
# /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN_LSF_noafs
 
Changed:
<
<
For Other Batch System:
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  WN
>
>
  • For Other Batch System:
    # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  WN
 
Changed:
<
<
You can find in this documentation: YAIM WN Variables all mandatory variables.
>
>
You can find all mandatory variables in this documentation: YAIM WN Variables
 
Changed:
<
<
If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.
>
>
If no errors are reported during verification you can proceed with the configuration, otherwise correct them before continuing.
 

YAIM Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
>
>
  • For your convenience you can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.
 
IMPORTANT NOTE:
Changed:
<
<
All the nodetypes name are case sensitive, you have to write it as described above.
>
>
All the nodetypes name are case sensitive, you have to write them as described above.
 
Changed:
<
<
  • For Torque:
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
  • For Torque:
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  WN_torque_noafs 2>&1 | tee /root/conf_WN_torque_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

IMPORTANT NOTE:
SL6/x86_64 first configuration with yaim presents the following WARNING:
 WARNING: /var/lib/torque/mom_priv/config already exists, YAIM will not touch it
 WARNING: Batch server defined in BATCH_SERVER variable is different 
 WARNING: from the batch server defined under /var/lib/torque/mom_priv/config
 WARNING: Remove /var/lib/torque/mom_priv/config and reconfigure again to use the new value! 

this is due to the presence of the file /var/lib/torque/mom_priv/config, provided by the SL6 torque-mom package, torque-mom-2.5.7-9.el6.x86_64. Remove the file as recommended and reconfigure
 
Changed:
<
<
  • For LSF:
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
  • For LSF:
     # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def> -n  WN_LSF 2>&1 | tee /root/conf_WN_LSF`.hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 or
Changed:
<
<
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  WN_LSF_noafs 2>&1 | tee /root/conf_WN_LSF_noafs.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 
  • For Other Batch System:
Changed:
<
<
 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
>
>
 /opt/glite/yaim/bin/yaim -c -d 6 -s    -n  WN 2>&1 | tee /root/conf_WN.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to Service WN Reference Card. In this page you can found what daemons are running after installation and any other useful WN issue information.
>
>
After service installation you could have a look at WN - Service Reference Card. In this page you can find information on what daemons are running, log files, cron jobs, etc.
 

WN Documentation References:

Added:
>
>
 
Deleted:
<
<
 
Changed:
<
<
  • Other Documentation available here
>
>
 

UI Installation and Configuration

Added:
>
>
  • Supported platforms: SL5/x86_64 & SL6/x86_64
 
  • Have a look to the section Repository Settings and ensure that you have the common repo files
Changed:
<
<
  • Before starting the installation procedure remember to clean all yum cache and headers:
# yum clean all
>
>
  • Before starting the installation procedure remember to clean all yum cache and headers:
    # yum clean all
 

CAs installation:

Changed:
<
<
  • Install CAs on ALL profiles:
# yum install ca-policy-egi-core
>
>
  • Install CAs on ALL profiles:
    # yum install ca-policy-egi-core
 

Service installation

  • Have a look to the UI documentation before starting to install: UI Guides.
Changed:
<
<
  • Install the UI metapackages, containing all packages needed.

# yum install emi-ui
>
>
  • Install the UI metapackages, containing all clients available:
    # yum install emi-ui
 

Service Configuration

YAIM Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the UI profile

 # /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  UI 
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for the UI nodetype:
     # /opt/glite/yaim/bin/yaim -v -s <your-site-info.def> -n  UI 
 
Changed:
<
<
You can find in this documentation: YAIM UI Variables all mandatory variables.
>
>
You can find all mandatory variables in this documentation: YAIM UI Variables
 
Changed:
<
<
If no errors are reported during the verification you can proceed to the configuration, otherwise correct them before continuing.
>
>
If no errors are reported during verification you can proceed with the configuration, otherwise correct them before continuing.
 

YAIM Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations.

 /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
>
>
  • For your convenience yo can save all the configuration information in a log file for each configuration separately, different from the default yaimlog, that contins all the history of all configurations:
     /opt/glite/yaim/bin/yaim -c -d 6 -s  <your-site-info.def>  -n  UI 2>&1 | tee /root/conf_UI.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log 
 

Service Testing - Reference Card

Changed:
<
<
After service installation to have a look if all were installed in a proper way, you could have a look to UI Reference Card or User Troubleshooting Guide. In this page you can find some commonl errors and other useful service information.
>
>
After service installation you could have a look at the UI Reference Card or User Troubleshooting Guide. In this page you can find some common errors and other useful service information.
 

UI Documentation References:

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback