2nd bg-ii ahm, 13.05.2009, riga, latvia

BalticGrid-II ProjectBalticGrid-II Project

AHM Riga May 12-14, 20092nd BG-II AHM, 13.05.2009, Riga, Latvia 1

Running Licensed Software on Grid

Running Licensed Software on Grid

Lauris Cikovskis (RTU ETF)Lauris Cikovskis (RTU ETF)Edgars Znots (IMCS UL)Edgars Znots (IMCS UL)

2nd BG-II AHM, 13.05.2009, Riga, Latvia 2

OutlineOutline

Experience with ANSYS and MATLABExperience with ANSYS and MATLAB

ChallengesChallenges

SolutionsSolutions

Best practices and suggestionsBest practices and suggestions


ANSYSANSYS

Proprietary, licensed softwareProprietary, licensed software

Each running instance of ANSYS takes one licenseEach running instance of ANSYS takes one license

A central License Server is necessaryA central License Server is necessary

Incomming connections from running ANSYS instances to Incomming connections from running ANSYS instances to License Server are necessaryLicense Server are necessary


ANSYS – challenges and solutionANSYS – challenges and solution

License agreenment allows ANSYS instances to be run 25 License agreenment allows ANSYS instances to be run 25 miles away from License Servermiles away from License Server

Which means Which means –– we can run ANSYS on RTU and IMCS UL we can run ANSYS on RTU and IMCS UL clusters, but not on the entire BG-II infrastructureclusters, but not on the entire BG-II infrastructure

Had to cut through firewallsHad to cut through firewalls

First approach downloaded full ANSYS installation to WNs First approach downloaded full ANSYS installation to WNs for each job (if it was not there already)for each job (if it was not there already)

Now we have put ANSYS in local software directory for IMCS Now we have put ANSYS in local software directory for IMCS UL cluster, and each job is sent to Grid with information UL cluster, and each job is sent to Grid with information about where License Server can be contactedabout where License Server can be contacted


ANSYS – best practices and suggestions

ANSYS – best practices and suggestions

Spend the time to Spend the time to readread and and understandunderstand the license the license agreenment!agreenment!

Analyze security issuesAnalyze security issues

Running Licenced software on Grid:MATLAB

Running Licenced software on Grid:MATLAB

MATLAB gridification issuesMATLAB gridification issues Licencing User friendly interface

AHM Riga May 12-14, 2009

Why MATLAB?Why MATLAB?

Over 1 million people around the world speaks Over 1 million people around the world speaks MATLAB! MATLAB!

PProgramming languagerogramming language for science and engineering for science and engineering

Toolboxes Toolboxes forfor different science fieldsdifferent science fields

Parallel computing supportParallel computing support Job execution on multicore/cluster systems MPI support


Third Party licenceThird Party licence

“The licensee having the MDCS installed is able to share his cluster to other non degree granting institutions in the same “country”; in this case Europe(EU). That is, others can access your cluster.”

“To get access to other clusters, the other clusters must also install MDCS with third part rights. In EGEE, a middleware is used between the MDCS locations, as the MDCS are installed on separate clusters.”


Executable = "Mtest.sh";

InputSandbox = {"Mtest.sh","Mtest.m"};

Stdoutput = "message.txt";

OutputSandbox = {"message.txt","rezultats.mat","stderror"};

Mtest.jdl

Usual way...Usual way...


function Mtest(X,Y)

........

save rezults A

end

Mtest.m

#!/bin/bash

$matlab_home/bin/matlab -nodisplay -r Mtest(1,5)

Mtest.sh

What about such way? What about such way?

Just one command with Just one command with dfeval dfeval to execute your M-fileto execute your M-file


@task <parameters> glite_UI task.m

MATLAB gLite integrationMATLAB gLite integration

Developed by EGEE&MathworksDeveloped by EGEE&Mathworks

Y Y

MDCE- MATLAB Distributed Computing Server MDCE- MATLAB Distributed Computing Server


ParallelComputing Toolbox™

gLite user InterfaceTOOLBOXES

BLOCKSETSGRID

MDCS

MDCS

MDCS

MDCS

User side

On user sideOn user side

User requirementsUser requirements Balticgrid VO certificate MATLAB + Parallel computing toolbox (1 licence) account in any gLite UI

Direct access from MATLAB Direct access from MATLAB workspace to Gridworkspace to Grid Passwordless ssh connection to gLite UI needed Putty tools are used - Plink,Pscp,Pageant

Automatic JDL creationAutomatic JDL creation

Input and output file trasfer to storage elementInput and output file trasfer to storage element

result recivieng and output in MATAB workspaceresult recivieng and output in MATAB workspace


On cluster sideOn cluster side

FLEXnet licence serverFLEXnet licence server worker nodes needs acces to licence server

MATLAB DCS installation in shared software MATLAB DCS installation in shared software directorydirectory

MPI support needed for parallel MATLAB tasksMPI support needed for parallel MATLAB tasks- Still needs testing...

4GB RAM/core recommended4GB RAM/core recommended


ConlusionsConlusions

MathWorks has changed the licensing conditions to MathWorks has changed the licensing conditions to comply with distributed computing demandscomply with distributed computing demands

Provided user friendly access to Grids - nProvided user friendly access to Grids - no o knowledge about Grids needed knowledge about Grids needed MATLAB enviroment allows further development of MATLAB enviroment allows further development of cluster/Grid interfacecluster/Grid interface

Integration need inprovments in error handlingIntegration need inprovments in error handling

Related software can be gridified in similar manner Related software can be gridified in similar manner – Scilab, Octavia, Sage – Scilab, Octavia, Sage


BalticGrid-II ProjectBalticGrid-II Project

Thank you for attention!Thank you for attention!


2nd bg-ii ahm, 13.05.2009, riga, latvia

Documents