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

1. Running Licensed Software on Grid Lauris Cikovskis (RTU ETF) Edgars Znots (IMCS UL) AHM Riga May 12-14, 2009 2nd BG-II AHM, 13.05.2009, Riga, Latvia

2. Outline • Experience with ANSYS and MATLAB • Challenges • Solutions • Best practices and suggestions 2nd BG-II AHM, 13.05.2009, Riga, Latvia

3. ANSYS • Proprietary, licensed software • Each running instance of ANSYS takes one license • A central License Server is necessary • Incomming connections from running ANSYS instances to License Server are necessary 2nd BG-II AHM, 13.05.2009, Riga, Latvia

4. ANSYS – challenges and solution • License agreenment allows ANSYS instances to be run 25 miles away from License Server • Which means – we can run ANSYS on RTU and IMCS UL clusters, but not on the entire BG-II infrastructure • Had to cut through firewalls • First approach downloaded full ANSYS installation to WNs for each job (if it was not there already) • Now we have put ANSYS in local software directory for IMCS UL cluster, and each job is sent to Grid with information about where License Server can be contacted 2nd BG-II AHM, 13.05.2009, Riga, Latvia

5. ANSYS – best practices and suggestions • Spend the time to read and understand the license agreenment! • Analyze security issues 2nd BG-II AHM, 13.05.2009, Riga, Latvia

6. RunningLicencedsoftwareonGrid:MATLAB • MATLAB gridificationissues • Licencing • Userfriendlyinterface AHM Riga May 12-14, 2009

7. Why MATLAB? • Over 1 millionpeoplearoundtheworldspeaks MATLAB! • Programming languageforscienceandengineering • Toolboxes fordifferentsciencefields • Parallelcomputingsupport • Jobexecutiononmulticore/clustersystems • MPI support AHM Riga May 12-14, 2009

8. ThirdParty 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.” AHM Riga May 12-14, 2009

9. Usualway... Mtest.m function Mtest(X,Y) ........ save rezultsA end Mtest.sh Mtest.jdl #!/bin/bash $matlab_home/bin/matlab -nodisplay -r Mtest(1,5) Executable = "Mtest.sh"; InputSandbox = {"Mtest.sh","Mtest.m"}; Stdoutput = "message.txt"; OutputSandbox = {"message.txt","rezultats.mat","stderror"}; AHM Riga May 12-14, 2009

10. Whataboutsuchway? @task <parameters> glite_UI task.m Just onecommandwithdfevalto executeyour M-file AHM Riga May 12-14, 2009

11. gLite user Interface Parallel Computing Toolbox™ TOOLBOXES BLOCKSETS MATLAB gLiteintegration User side GRID MDCS MDCS MDCS MDCS DevelopedbyEGEE&Mathworks Y MDCE- MATLAB DistributedComputing Server AHM Riga May 12-14, 2009

12. Onuserside • User requirements • Balticgrid VO certificate • MATLAB + Parallel computing toolbox (1 licence) • accountinanygLite UI • Direct access from MATLAB workspace to Grid • Passwordlesssshconnection to gLite UI needed • Puttytoolsareused - Plink,Pscp,Pageant • Automatic JDL creation • Inputandoutputfiletrasfer to storage element • resultreciviengandoutputin MATAB workspace AHM Riga May 12-14, 2009

13. Onclusterside • FLEXnet licence server • workernodesneedsacces to licence server • MATLAB DCS installationinsharedsoftwaredirectory • MPI supportneededforparallel MATLAB tasks - Stillneedstesting... • 4GB RAM/corerecommended AHM Riga May 12-14, 2009

14. Conlusions MathWorkshaschangedthelicensingconditions to complywithdistributedcomputingdemands Provideduserfriendlyaccess to Grids - no knowledge about Grids needed  MATLAB enviromentallowsfurtherdevelopment of cluster/Grid interface Integrationneedinprovmentsinerrorhandling Relatedsoftwarecanbegridifiedinsimilarmanner – Scilab, Octavia, Sage AHM Riga May 12-14, 2009

15. Thankyouforattention! AHM Riga May 12-14, 2009