Do not use this page, it has been migrated to the ARCS SVN Repository at http://www.grid.apac.edu.au/repository/trac/systems/wiki/InfoSystems/CentralIndexServiceInstall

MDS VM Deployment

This page will detail how an MDS VM should be deployed at a site. Not all partner sites will need to run an MDS VM. Only sites that want to provide redundancy to the central MDS server (mds.sapac.edu.au) can run an MDS VM. UQ has volunteered to run another MDS VM to act as a backup to mds.sapac.edu.au.

How the system used to work

The MIP is run at each site every 10min and publishes data to the Indexing Service on that sites ng2.

Each ng2 is configured to specify ng2.sapac.edu.au as the upstream server.

MDS queries (wsrf requests) are then sent to ng2.sapac.edu.au.

This doesn't provide any fault tolerance and prevents SAPAC from working on ng2.

We are working on a better deployment plan.

The Plan

  • Setup a VM dedicated to MDS at SAPAC - mds.sapac.edu.au
  • Each ng2 should specify mds.sapac.edu.au as the upstream server
    • The RPMs currently hosted at JCU should be moved to APAC with instructions updated. And /opt/vdt/globus/etc/globus_wsrf_mds_index/hierarchy.xml configured correctly.
  • Setup a generic DNS record mds.apac.edu.au.
    • Daniel sent email to David Bannon 12Apr.
  • Modify clients - iVEC Generic Grid Client to use the new address
  • Modify webmds to use the new address. Should webmds be hosted at APAC?
  • Setup at least one more MDS VM at another site. UQ site - ngmds.hpcu.uq.edu.au
    • All need to be specified in hierarchy.xml
    • Add extra A records to mds.apac.edu.au - ie. Round Robin
  • Clients will need to be modified like Myproxy to timeout quickly and resolve to try a different IP on failure

Progress

mds.sapac.edu.au is running.

Waiting on port 8443 to be opened on Adelaide Uni firewall. Requested 10Apr07. Keep trying - they may not notify.

Port 8443 on mds.sapac.edu.au is now open. -- GersonGalang 24Apr07

ngmds.hpcu.uq.edu.au is running. -- WillHsu - 31 May 2007

VM Notes

Based on VmdetailsNg2

Install/update Gbuild

Run the BuildNgMdsVdt161.sh script; this has been adapted as follows from the NG2 build script:

  • don't need Ggateway pbs-telltail xinetd perl-DBD-MySQL
  • don't need PBS_HOME or qstat tests
  • disable sudoers
  • don't need component: PRIMA-GT4 Globus-WS-PBS-Setup
  • does install MySQL? , but probably not needed? (leave it there, it will just use swap if not used)
  • starts fork job manager, but not needed!

touch /etc/grid-security/grid-mapfile

service globus-ws start

31May07 I reinstalled ng2dev without following the install steps below. It is still receiving information published by ng2 (which we enabled for testing). So maybe none of this is actually needed?

Security: /etc/grid-security/mds-grid-mapfile will need to be modified.

Install MIP: PlanResource#Install_Config_Docs

yum install APAC-mip-module-py APAC-mip-globus

/usr/local/mip/config/globus/install -l /opt/vdt/globus

  • (ignore 2 messages, hunk failed). 30May06 tested on ng2dev build, an no message shown.

Disable publishing of the MIP, comment upstream in hierarchy.xml

  • Need at least one entry, upstream or downstream, our mds specifies ng2 as downstream (which should not prevent others)
  • Will list downstream permissions one day - when it is patched to work properly
  • UPDATE: See: Securing MDS (REFACTOR Daniel, put a link here)

Disable publishing information from the local MIP. Check: /opt/vdt/globus/etc/globus_wsrf_mds_index/server-config.wsdd.

  • Strangely this was not needed on our mds even though it should have worked the same way as ng2!
  • Under DefaultIndexService
    • Delete parameter value org.globus.mds.usefulrp.rpprovider.ResourcePropertyProviderCollection
    • Delete parameter rpProviderConfigFile

We think that the APAC WebMDS interface should also be installed on the hosts running the central index services (MDS VM). WebMDS only runs on tomcat so if we install this on MDS, we'll need to deploy tomcat on it and run it together with GT4's standalone container. It will be a waste of resource running two JVMs for each of the application servers so we are suggesting that we run the GT4 container on the tomcat container on MDS as well. Instructions can be found here: DeployGT4AndWebMDSOnTomcat -- GersonGalang 26 Jul 2007

-- DanielCox - 14 Apr 2007

Do not use this page, it has been migrated to the ARCS SVN Repository at http://www.grid.apac.edu.au/repository/trac/systems/wiki/InfoSystems/CentralIndexServiceInstall

Topic attachments
I Attachment Action Size Date Who Comment
shsh BuildNgMdsVdt161.sh manage 4.3 K 14 Apr 2007 - 03:22 DanielCox  
Topic revision: r20 - 04 Dec 2007 - 00:21:44 - GersonGalang
APACgrid.MdsVMDeployment moved from APACgrid.MdsDeployment on 09 May 2007 - 03:13 by GersonGalang - put it back
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback