(r5) EntryDescriptionNo52 < Main

Tags: , view all tags
---+ Upgrade to OSG 1.0
We started our upgrade to 1.0:
   * stoping our gatekeeper, in our computing element
<pre>
/etc/init.d/xinetd stop
</pre>
   * In our Computing element, getting pacman
<pre>
cp -a  /opt/osg-0.8.0 /home/mdias/osg_backup0.8
cd /opt
wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-3.26.tar.gz
tar --no-same-owner -xzvf pacman-3.26.tar.gz
cd pacman-3.26
source setup.sh
</pre>
now, 
<pre>
cd /opt
mkdir osg-1.0.0
cd /opt/osg-1.0.0
vdt-control --off
export OLD_VDT_LOCATION=/opt/osg-0.8.0
pacman -get OSG:ce
source setup.sh
pacman -get OSG:Globus-Condor-Setup
</pre>
the last step install condor batch. We have to inspect
<pre>
 vim  /opt/osg-1.0.0/condor/etc/condor_config
</pre>
Managed fork issues: installing and configuring it 
<pre>
pacman -get  OSG:ManagedFork
 $VDT_LOCATION/vdt/setup/configure_globus_gatekeeper --managed-fork y --server y
</pre>
Gums server:
<pre>
pacman -get  OSG:gums
</pre>
Monalisa
<pre>
 vim /opt/osg-1.0.0/MonaLisa/Service/VDTFarm/ml.properties
$VDT_LOCATION/vdt/setup/configure_monalisa --prompt
vim  /opt/osg-1.0.0/MonaLisa/Service/CMD/ml_env
JAVA_HOME=/opt/osg-1.0.0/jdk1.5  <-------was jdk1.4
</pre>
Gums host cron
<pre>
vdt-register-service -name gums-host-cron --enable
 vdt-control --enable gums-host-cron
$VDT_LOCATION/gums/scripts/gums-host-cron
</pre>
some gums configuration
<pre>
cp /opt/osg-1.0.0/post-install/prima-authz.conf /etc/grid-security/.
cp /opt/osg-1.0.0/post-install/gsi-authz.conf /etc/grid-security/.
</pre>
We have to inspect these files
<pre>
$VDT_LOCATION/vdt-app-data/gums/config/gums.config
$VDT_LOCATION/gums/config/gums-client.properties
</pre>

Reusing the old configuration
<pre>
cd /opt/osg-1.0.0/monitoring
source ../setup.sh
export OLD_VDT_LOCATION=/opt/osg-0.8.0/
./configure-osg.py -e
vim extracted-config.ini
</pre>
we can test it and repair
<pre>
configure-osg.py -v -f ./extracted-config.ini
 cp /opt/osg-0.8.0/monitoring/grid3-user-vo-map.txt
/opt/osg-1.0.0/monitoring/.
vim /opt/osg-1.0.0/monitoring/extracted-config.ini
</pre>
installing it
<pre>
  ./configure-osg.py -c -f ./extracted-config.ini 
</pre>
removing and creating simbolic links
<pre>
unlink /OSG 
ln -s /opt/osg-1.0.0 /OSG
</pre>
Turning on services (seems to be not necessary) 
<pre>
vdt-control --on
</pre>

   * Installing RSV
<pre>
vim /opt/osg-1.0.0/monitoring/config.ini
[RSV]
 . . . 
enabled = True
 . . . 
rsv-user = mdias

</pre>
now start services
<pre>
vdt-control --on condor-cron osg-rsv apache 
</pre>
and check it
<pre>
condor_cron_q
tail -f $VDT_LOCATION/osg-rsv/logs/consumers/gratia-script-consumer.out
</pre>
   * In our nodes, in a NFS shared directory,
<pre>
cd /home/mdias
wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-3.26.tar.gz
tar --no-same-owner -xzvf pacman-3.26.tar.gz
</pre>
and then  We've created a script like that:
<pre>
source /opt/OSG-wn-client/setup.sh
vdt-control --off
cd /home/mdias/pacman-3.26
source setup.sh
mv /opt/OSG-wn-client /opt/OSG-wn-client.old
mkdir /opt/OSG-wn-client
cd /opt/OSG-wn-client
VDTSETUP_AGREE_TO_LICENSES=y
export VDTSETUP_AGREE_TO_LICENSES
VDTSETUP_INSTALL_CERTS=l
export VDTSETUP_INSTALL_CERTS
VDTSETUP_EDG_CRL_UPDATE=n
export VDTSETUP_EDG_CRL_UPDATE
VDTSETUP_ENABLE_ROTATE=y
export VDTSETUP_ENABLE_ROTATE
VDTSETUP_CA_CERT_UPDATER=n
export VDTSETUP_CA_CERT_UPDATER
pacman -trust-all-caches -get OSG:wn-client
mkdir /opt/OSG-wn-client/glite/etc
cp /OSG/glite/etc/vomses /opt/OSG-wn-client/glite/etc/.
mv /var/log/glexec /var/log/glexec.old
mv  /etc/glexec  /etc/glexec.old
mkdir /opt/glexec
cd /opt/glexec
pacman -trust-all-caches    -get http://vdt.cs.wisc.edu/vdt_181_cache:Glexec
sed -i 's/yourmachine.yourdomain/osg-ce.sprace.org.br/g'  /etc/glexec/contrib/gums_interface/getmapping.cfg
source setup.sh
vdt-control --on
</pre>
so, We start to run it in our nodes:
<pre>
/root/bin/clcmd /home/mdias/worknodeinstall.sh
/root/bin/clcmd rm -rf /opt/OSG-wn-client.old
</pre>
we have to edit one /etc/glexec/glexec.conf to put "linger" =no line in [glexec] section and copy to the other nodes. Also we have to edit our computer element , *before* reusing old configuration:
<pre>
 vim /opt/osg-1.0.0/monitoring/extracted-config.in
glexec_location = /opt/glexec/glexec-osg
</pre>
Testing glexec
<pre>
cd /opt/OSG-wn-client
source setup.sh 
voms-proxy-init -voms cms:/cms
export GLEXEC_CLIENT_CERT=/tmp/x509up_u537  
cd /opt/glexec/
glexec-osg/sbin/glexec /usr/bin/id
</pre>

A srm error can force us to upgrade our dcache to make srm compatible. So in our storage elements:
<pre>
/opt/init.d/dcache-pool stop
/opt/init.d/dcache-core stop
wget http://www.dcache.org/downloads/1.8.0/dcache-server-1.8.0-15p7.noarch.rpm
wget
rpm -Uvh dcache-server-1.8.0-15p7.noarch.rpm 
/opt/d-cache/install/install.sh
chkconfig --del dcache-core 
chkconfig --del dcache-pool 
cp /opt/d-cache/bin/dcache-pool /etc/init.d/.
cp /opt/d-cache/bin/dcache-core /etc/init.d/.
chkconfig --add dcache-core 
chkconfig --add dcache-pool 
chkconfig dcache-core on
chkconfig dcache-pool on
</pre>

interesting links
   * http://twiki.mwt2.org/bin/view/Main/DeployingOSG1d0
   * https://twiki.grid.iu.edu/twiki/bin/view/ReleaseDocumentation/ComputeElementInstall
---++Updates
---+++Fulano em dd/mm/aaaa
Coloca o que fez.
---+++Ciclano em dd/mm/aaaa
Mais comentarios


-- Main.MarcoAndreFerreiraDias - 23 Jun 2008
Topic revision: r5 - 2008-06-27 - MarcoAndreFerreiraDias
antalya escort bursa escort eskisehir escort istanbul escort izmir escort