Difference: CreamTestsP4543 (1 vs. 4)

Revision 42010-12-13 - SaraBertocco

Line: 1 to 1
 

PATCH 4543

Line: 49 to 49
 yum install glite-CREAM wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/glite-TORQUE_utils.repo -O /etc/yum.repos.d/glite-TORQUE_utils.repo wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/glite-TORQUE_server.repo -O /etc/yum.repos.d/glite-TORQUE_server.repo
Changed:
<
<
yum install glite-TORQUE_utils glite-TORQUE_server
>
>
wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/lcg-CA -O /etc/yum.repos.d/lcg-CA.repo yum install glite-TORQUE_utils glite-TORQUE_server lcg-CA
 /opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils
Changed:
<
<
  • View the log of yum for a clean installation
  • View the log of yaim for a clean installation (TORQUE is used)
>
>
  • View the log of metapackage installation using yum for a clean installation
  • View the log of yaim configuration for a clean installation (TORQUE is used)
 
  • Installation issues
Changed:
<
<
    • Due to a malfunctioning of the ufficial jpackage mirrors the following repository has been used:
>
>
    • Due to a malfunctioning of the official jpackage mirrors the following repository has been used:
 [jpackage5-generic] name=JPackage 5, generic baseurl=http://devel12.cnaf.infn.it:7444/repository/jpackage-free/ enabled=1 protect=1
Added:
>
>
    • Due to a malfunctioning of the official dag mirrors the following repository has been used:
      ### Name: RPMforge RPM Repository for RHEL 4 - dag
      ### URL: http://rpmforge.net/
      [rpmforge]
      name = RHEL $releasever - RPMforge.net - dag
      baseurl = http://apt.sw.be/redhat/el4/en/$basearch/rpmforge
      mirrorlist = http://apt.sw.be/redhat/el4/en/mirrors-rpmforge
      #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge
      enabled = 1
      protect = 0
      gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
      gpgcheck = 1
      
      [rpmforge-extras]
      name = RHEL $releasever - RPMforge.net - extras
      baseurl = http://apt.sw.be/redhat/el4/en/$basearch/extras
      mirrorlist = http://apt.sw.be/redhat/el4/en/mirrors-rpmforge-extras
      #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-extras
      enabled = 1
      protect = 0
      gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
      gpgcheck = 1
      
      [rpmforge-testing]
      name = RHEL $releasever - RPMforge.net - testing
      baseurl = http://apt.sw.be/redhat/el4/en/$basearch/testing
      mirrorlist = http://apt.sw.be/redhat/el4/en/mirrors-rpmforge-testing
      #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge-testing
      enabled = 0
      protect = 0
      gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
      gpgcheck = 1
      
    • This repository has been obtained following the procedure below:
wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el4.rf.i386.rpm
rpm -ihv rpmforge-release-0.5.1-1.el4.rf.i386.rpm
yum update
enable = 1 for [rpmforge-extras] repository in /etc/yum.repos.d/rpmforge.repo
 

Upgrade from production

  • Upgrade steps:
Changed:
<
<
wget ohttp://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_4543_1/etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
>
>
wget http://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_4543_1/etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
 yum update /opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n LSF_utils
Changed:
<
<
    • View the log of yum for an upgrade
    • View the log of yaim for an upgrade (LSF is used)
>
>
    • View the log of yum for an upgrade
    • View the log of yaim for an upgrade (LSF is used)
 

-- SaraBertocco - 2010-12-07

Added:
>
>

META FILEATTACHMENT attachment="yaim_installation_log.txt" attr="" comment="yaim configuration log" date="1292251735" name="yaim_installation_log.txt" path="yaim_installation_log.txt" size="60450" stream="yaim_installation_log.txt" tmpFilename="/usr/tmp/CGItemp15102" user="SaraBertocco" version="1"
META FILEATTACHMENT attachment="yum_installation_log.txt" attr="" comment="yum metapackage installation log" date="1292252028" name="yum_installation_log.txt" path="yum_installation_log.txt" size="56172" stream="yum_installation_log.txt" tmpFilename="/usr/tmp/CGItemp14975" user="SaraBertocco" version="1"
META FILEATTACHMENT attachment="yum_update_log.txt" attr="" comment="yum update log" date="1292255665" name="yum_update_log.txt" path="yum_update_log.txt" size="7971" stream="yum_update_log.txt" tmpFilename="/usr/tmp/CGItemp15010" user="SaraBertocco" version="1"
META FILEATTACHMENT attachment="yaim_update_log.txt" attr="" comment="yaim configuration after update" date="1292255699" name="yaim_update_log.txt" path="yaim_update_log.txt" size="41125" stream="yaim_update_log.txt" tmpFilename="/usr/tmp/CGItemp15087" user="SaraBertocco" version="1"
META FILEATTACHMENT attachment="reports_patch_4543.tar.gz" attr="" comment="Testsuite reports for patch 4543" date="1292256159" name="reports_patch_4543.tar.gz" path="reports_patch_4543.tar.gz" size="260045" stream="reports_patch_4543.tar.gz" tmpFilename="/usr/tmp/CGItemp14935" user="SaraBertocco" version="1"
META FILEATTACHMENT attachment="infotest1.txt" attr="" comment="infotest1" date="1292257370" name="infotest1.txt" path="infotest1.txt" size="4248" stream="infotest1.txt" tmpFilename="/usr/tmp/CGItemp14757" user="SaraBertocco" version="1"
META FILEATTACHMENT attachment="infotest2.txt" attr="" comment="infotest2" date="1292257393" name="infotest2.txt" path="infotest2.txt" size="32455" stream="infotest2.txt" tmpFilename="/usr/tmp/CGItemp14949" user="SaraBertocco" version="1"

Revision 32010-12-13 - SaraBertocco

Line: 1 to 1
 

PATCH 4543

Line: 32 to 32
 

Checked bugs

  • Bug #75369: [yaim-cream-ce] Reconfiguration with yaim produces garbled sudoers file
Changed:
<
<
    • Configured from scratch and than re-configure a cream-ce using files [[https://gus.fzk.de/pages/windownload.php?attid=ATT6877][users.conf] and groups.conf attached to GGUS ticket 64189
    • Verified that re-configuration does not spoil /etc/sudoers file
>
>
    • Reproduced the bug configuring from scratch and then re-configuring a cream-ce using files users.conf and groups.conf attached to GGUS ticket 64189
    • Applied the fix, cleaned the sudoers file, verified that re-configuration does not spoil /etc/sudoers file
 
  • Bug #75029: Error when GLITE_LOCATION_LOG is differet from default FIXED
    • set GLITE_LOCATION_LOG=/tmp/test

Revision 22010-12-07 - SaraBertocco

Line: 1 to 1
 

PATCH 4543

Line: 31 to 31
 

Checked bugs

Added:
>
>
  • Bug #75369: [yaim-cream-ce] Reconfiguration with yaim produces garbled sudoers file
    • Configured from scratch and than re-configure a cream-ce using files [[https://gus.fzk.de/pages/windownload.php?attid=ATT6877][users.conf] and groups.conf attached to GGUS ticket 64189
    • Verified that re-configuration does not spoil /etc/sudoers file
 
  • Bug #75029: Error when GLITE_LOCATION_LOG is differet from default FIXED
    • set GLITE_LOCATION_LOG=/tmp/test
    • create /tmp/test as root

Revision 12010-12-07 - SaraBertocco

Line: 1 to 1
Added:
>
>

PATCH 4543

Automatic tests

  • report #1:
    • CREAM UI version: 1.12.1; CREAM testsuite version: 1.0.7
    • Used direct polling for monitoring and BUpdater/BNotifier for status change detection
    • Batch system: both TORQUE and LSF. Two different CEs one submitting to Torque (cream-33) and one submitting to LSF (cream-26)
    • All tests have been performed successfully (see the report from the testsuite)

Information service checks

Tested that the BDII is operational

ldapsearch -x -h cream-33.pd.infn.it -p 2170 -b o=infosys

Output is here

Checked the Glue 1.3 root entry:

ldapsearch -x -h cream-33.pd.infn.it -p 2170 -b mds-vo-name=resource,o=grid

Output is here

Checked bugs

  • Bug #75029: Error when GLITE_LOCATION_LOG is differet from default FIXED
    • set GLITE_LOCATION_LOG=/tmp/test
    • create /tmp/test as root
    • verify that yaim stops with message "ERROR: GLITE_LOCATION_LOG directory /tmp/test exists but it is not writable by tomcat user"
    • chown tomcat:tomcat /tmp/test
    • verify that yaim complete configuration without errors

Clean installation

  • Installation steps:
    wget http://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_4543_1/etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
    yum install glite-CREAM
    wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/glite-TORQUE_utils.repo -O /etc/yum.repos.d/glite-TORQUE_utils.repo
    wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.1/glite-TORQUE_server.repo -O /etc/yum.repos.d/glite-TORQUE_server.repo
    yum install glite-TORQUE_utils glite-TORQUE_server
    /opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils
    
  • View the log of yum for a clean installation
  • View the log of yaim for a clean installation (TORQUE is used)

  • Installation issues
    • Due to a malfunctioning of the ufficial jpackage mirrors the following repository has been used:
      [jpackage5-generic]
      name=JPackage 5, generic
      baseurl=http://devel12.cnaf.infn.it:7444/repository/jpackage-free/
      enabled=1
      protect=1
      

Upgrade from production

  • Upgrade steps:
    wget ohttp://etics-repository.cern.ch/repository/pm/registered/repomd/name/patch_4543_1/etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
    yum update
    /opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n LSF_utils 
    
    • View the log of yum for an upgrade
    • View the log of yaim for an upgrade (LSF is used)

-- SaraBertocco - 2010-12-07

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