Tags:
, view all tags

Notes about Installation and Configuration of myproxy (DRAFT)

  • These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
  • This document is addressed to site administrators responsible for middleware installation and configuration.
  • The goal of this page is to provide some hints and examples on how to install and configure an IGI myproxy service based on UMD middleware.

NB: The myproxy service is a CORE service, it should not be installed at Resource Center level. The official endpoint provided by IGI is myproxy.cnaf.infn.it and MUST be used by all Resource Centers and Services part of the IGI infrastructure.

References

  1. About IGI - Italian Grid infrastructure
  2. About IGI Release
  3. IGI Official Installation and Configuration guide
  4. Troubleshooting Guide for Operational Errors on EGI Sites
  5. Grid Administration FAQs page

Reccommendations

  • The service needs at least:
    • 3 cores
    • 3 GB RAM
    • 10 GB disk space.
A full virtualized machine based on KVM has been used in the following notes.

O.S. and Repos

  • Starts from a fresh installation of Scientific Linux 5.x (x86_64).
# cat /etc/redhat-release 
Scientific Linux SL release 5.7 (Boron) 
  • Install the additional repositories: EPEL, Certification Authority, UMD
# wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# rpm -ivh epel-release-5-4.noarch.rpm 
# wget http://repository.egi.eu/sw/production/umd/1/sl5/x86_64/updates/umd-release-1.0.2-1.el5.noarch.rpm
# rpm -ivh umd-release-1.0.2-1.el5.noarch.rpm 
# cd /etc/yum.repos.d/
# wget http://repo-pd.italiangrid.it/mrepo/repos/egi-trustanchors.repo
# yum install yum-priorities yum-protectbase
  • Be sure that SELINUX is disabled (or permissive). Details on how to disable SELINUX are here:
# getenforce 
Disabled
  • Check the repos list (sl-*.repo are the repos of the O.S. and they should be present by default).
# ls /etc/yum.repos.d/
EGI-trustanchors.repo  
epel.repo  epel-testing.repo  
sl-contrib.repo  sl-debuginfo.repo  sl-fastbugs.repo  sl.repo  sl-security.repo  sl-srpms.repo  sl-testing.repo  
UMD-1-base.repo  UMD-1-updates.repo

Update host and perform the installation of package(s) (DRAFT)

# yum clean all
Loaded plugins: downloadonly, kernel-module, priorities, protect-packages, protectbase, security, verify, versionlock
Cleaning up Everything

# yum install ca-policy-egi-core SOMETHING

Service configuration

The configuration file for this service is really basic:
# cat site-info.def 
????

YAIM check

#  chmod -R 600 /root/siteinfo

# /opt/glite/yaim/bin/yaim -v -s /root/siteinfo/site-info.def -n ??????

Know Issue and Workaround

YAIM config

Please use the debug flag ( "-d 6") to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog defulat one.
# /opt/glite/yaim/bin/yaim -c -d 6 -s /root/siteinfo/site-info.def -n ??????
  

Service checks

Revision

-- PaoloVeronesi - 2011-12-28

Edit | Attach | PDF | History: r11 | r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r2 - 2011-12-28 - PaoloVeronesi
 
  • Edit
  • Attach
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