yum install -y yum-conf-epel.noarch yum install -y octave hdf5-devel glpk fftw3 yum install -y libgomp blas-devel gsl-devel gmp-devel
The following is a possible TAG to be published by theophys compliant sites:
GlueHostApplicationSoftwareRunTimeEnvironment: VO-theophys-gcc41 ??
Mpi-start is the way to start MPI jobs:
Al least openMPI should be installed:
Shared home is recommended, but file distribution is supported by MPI-start:
MPI_SHARED_HOME | MPI_NO_SHARED_HOME
Remote Start-up of MPI job can be achieved via password-less SSH:
Infiniband is recommended, but Gbit (or 10Gb) Ethernet can be used:
MPI-Infiniband | MPI-Ethernet
At the moment CpuNumber is not used at all for match making. Temporary solution in the JDL: CPUNumber=n other.GlueCEInfoTotalCPUs >= CPUNumber
JobType = "Normal" ; CpuNumber = 8 ;
SMPGranularity = 8; WholeNodes = True;
Multithread support is desirable and it should be integrated in the middleware as soon as possible.
CREAM and BLAH: see https://twiki.cern.ch/twiki/bin/view/EGEE/ParameterPassing ?? WMS: included in WMS 3.3
VOMS Roles can be used to limit the access to Parallel queues.
site-info.def: PARALLEL_GROUP_ENABLE="/infngrid/ROLE=parallel" /opt/glite/yaim/defaults/ig-site.pre: FQANVOVIEWS=yes groups.conf: "/infngrid/ROLE=parallel":::: voms-proxy-init -voms infngrid:/infngrid/Role=parallel voms-proxy-info -all >.... >attribute : /infngrid/Role=parallel/Capability=NULL >attribute : /infngrid/Role=NULL/Capability=NULL >...
MPI and multi-thread programs can be combined to exploit the upcoming multicore architectures. The hybrid mutlithread/MPI programming leads to a request of N CPUs with a smaller number of MPI processes (N/thread_num). Actually this programming model is not supported in EGEE. Possible solution: modify the value type of WholeNodes from boolean to integer. Example:
SMPGranularity = 8; WholeNodes = 4;
This syntax would lead to
qsub -l nodes=4:ppn=GlueHostArchitectureSMPSize
where ppn is a number >=8. WholeNodes value should be passed to mpi-start as the number of MPI processes. Mpi-start should be modified accordingly.
Mixed mpi/mutithread programs require thread safe MPI implementations. Thead safety can be easily verified:
MPI_Init_thread(&argc, &argv, 3, &prov); printf("MPI_Init_thread provided:%d\n", prov);
The third parameter (number 3) means a request of full thread safety support ( MPI_THREAD_MULTIPLE ). If returned value for prov is 0 thread support is not provided (MPI_THREAD_SINGLE).
MPI sites with at least 2 queues sharing the same pool of WNs: