Difference: IgiEmi (59 vs. 60)

Revision 602012-10-17 - CristinaAiftimiei

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

IGI (based on EMI) Installation and Configuration

Line: 554 to 554
  # yum install emi-lsf-utils
Changed:
<
<

DGAS_sensors installation NEW

>
>

DGAS_sensors installation UPDATED

  IGI Release supports the use of DGAS as accounting system - please install also DGAS sensors on the CREAM node. You can found more documentation to DGAS Sensors 4.0 guide
Line: 942 to 942
 
Changed:
<
<

HLR Server Installation and Configuration

>
>

HLR Server Installation and Configuration NEW

 

HLR Prerequisites

Line: 988 to 988
 
  • Have a look to the section Repository Settings and ensure that you have the common repo files.
  • Please use the repositories reccomended in the EMI 2 section.
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
 

HLR Server installation

Changed:
<
<
  • Install the HLR metapackages, containing all packages needed:
# yum install igi-hlr
>
>
  • Install the HLR metapackages, containing all packages needed:
    # yum install igi-hlr
 

Middleware Configuration

Verification

Changed:
<
<
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile
>
>
  • Before starting the configuration PLEASE TEST that you have defined all the mandatory variables for all the HLR profile
 
# /opt/glite/yaim/bin/yaim -v -s <site-info.def> -n  HLR 
Deleted:
<
<
 
  • If no errors are reported during verification you can proceed to the configuration, otherwise correct them before continuing.

HLR Server Configuration

Line: 1021 to 1013
 

HLR Server Configuration

  • Please use the debug flag ( "-d 6") to configure the services in order to have detailed information.
Changed:
<
<
  • 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.

>
>
  • 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.
 
 # /opt/glite/yaim/bin/yaim -c -d 6 -s  <site-info.def>  -n  HLR 2>&1 | tee /root/conf_igi-HLR.`hostname -s`.`date +%Y-%m-%d-%H-%M-%S`.log

Post installation and configuration

Changed:
<
<
After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use this command below for each CE:
# dgas-hlr-addadmin -Sa  <CE_DN>

Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"

>
>
  • After the installation and configuration of the HLR Server services, you should register all the resources of the CEs attached to your HLR Server. Please use thecommand below for each CE:
    # dgas-hlr-addadmin -Sa  <CE_DN>
  • Where <CE_DN> is something like "/C=IT/O=INFN/OU=Host/L=Padova/CN=prod-ce-01.pd.infn.it"
 

Update From a previous release (< 4.0):

  • Back up the old databases :
    • on HLR Server stop the dgas services and make a dump of the databases:
Changed:
<
<
      • Stop the services :
# /etc/init.d/glite-dgas-hlrd stop
>
>
      • Stop the services :
        # /etc/init.d/glite-dgas-hlrd stop 
 
      • Check disk space
Changed:
<
<
        • Ensure you have enough space in the disk:
# df -h
You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)
      • Make the dump :
>
>
        • Ensure you have enough space in the disk:
          # df -h
        • You should have the space to contain the hlr and hlr_tmp database dump. (Mount an external partition or NFS partition if you don't have enough free space)
      • Make the dump :
 
mysqldump --user=root --password hlr_Padova > /data/hlr.sql
mysqldump --user=root --password hlr_tmp_Padova > /data/hlr_tmp.sql
  • Installation :
    • Install again the host with SL5/x86_64 distribution or install a new host where the HLR Server will be installed.
Changed:
<
<
+ Following the instructions in the previous section install the HLR Server and configure it using yaim.
  • Stop the HLR server process:
# /etc/init.d/dgas-hlrd stop
  • Restore the dump :
>
>
    • Following the instructions in the previous section install the HLR Server and configure it using yaim.
  • Stop the HLR server process:
    # /etc/init.d/dgas-hlrd stop
  • Restore the dump :
 
# mysql -u root -p hlr_tmp < /data/hlr_tmp.sql
# mysql -u root -p hlr < /data/hlr.sql
Changed:
<
<
  • execute translate DB
]# nohup /usr/sbin/dgas-hlr-translatedb --D &
  • Start dgas services :
# /etc/init.d/dgas-hlrd start
>
>
  • execute translate DB
    # nohup /usr/sbin/dgas-hlr-translatedb --D & 
  • Start dgas services :
    # /etc/init.d/dgas-hlrd start 
 
  • Execute populateJobTransSummary:
Changed:
<
<
# /usr/sbin/dgas-hlr-populateJobTransSummary
  • Restart dgas services :
# /etc/init.d/dgas-hlrd restart
>
>
    • The new HLR version need to polulate the JobTransSummary
      # /usr/sbin/dgas-hlr-populateJobTransSummary 
  • Restart dgas services :
    # /etc/init.d/dgas-hlrd restart 
 

Post Update Procedure

Changed:
<
<
After the update of the HLR Server Services, you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE:
>
>
After the update of the HLR Server , you should register again all the resources of the CE attached to your HLR Server. Please use this command below for each CE:
 
# dgas-hlr-addadmin -Sa  <CE_DN>
 
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