sign in sign up
<<
Home , User interface

PoS(EGICF12-EMITC2)044 http://pos.sissa.it/ ∗ [email protected] [email protected] [email protected] Speaker. Many Grid infrastructures aretures nowadays are serving routinely the accessed scientific throughInstalling communities. some and client configuring Those software such generally infrastruc- Grideven called: clients today. is a Miramare (UI). challengingmostly Interoperable task this Lite kind for of non User users expert by Interfacemultiple scientific providing clients (MILU), them users for a is accessing Plug&Play a theveloped line gLite, software and interface ARC which which evolved and contains significantly targets GT4 during .considered time. the The package incoming Through has users’ this beenstrategy evolution requests de- provides as the we natural evident have requisites always benefitwhich, for of in the having MILU, future a is development. software tofoundation which for allow This more better a complex accomplish concurrent scientific its gateways. usageThis purpose, of paper different provides Grid a infrastructures and completeered create overview in the of the MILU EU-IndiaGrid and andenvironment. reports e-NMR on communities, its and usage as experiences a gath- production UI in our local Grid ∗ Copyright owned by the author(s) under the terms of the Creative Commons Attribution-NonCommercial-ShareAlike Licence. c

EGI Community Forum 2012 / EMI26-30 Second March, Technical 2012 Conference, Munich, Germany Riccardo Murri Grid Computing Competence Center, Organisch-Chemisches Institut, University of Zurich, E-mail: Stefano Cozzini CNR-IOM Democritos, Trieste, Italy, E-mail: Tyanko Aleksiev Grid Computing Competence Center, Organisch-Chemisches Institut, University of Zurich, E-mail: Milu, the three PoS(EGICF12-EMITC2)044 Tyanko Aleksiev ] for a recent overview 1 2 : MILU is easily configurable either for single user and for multi- user environment. No experience inrequired. installing Grid Using the services installer nor script, about includedin their less in configuration than the is a tarball, minute. MILU’s installation is completed Easy to use and configure create an usable software which does not require too muchtake expertise. into account the requirements thatsoftware came was out actively during used. various training activities where the use the provided byware. the users who autonomously downloaded and tried the soft- GARUDA and gLite users are using different methods to access and use resources belonging to This approach allows us to meet the actual needs of the users and satisfy some real use cases. The establishment of different Production Grid Infrastructure (PGI) in the past few years has As an example we could consider the fact that in order to access a gLite computational Grid Direct access to different middlewares from the user’s host, enabling a sort of low level inter- MILU was developed within the EU-IndiaGrid projects (see reference [ • • • • ] in order to make available a portable gLite UI . From this basic task MILU evolved in order 2 the two different infrastructures. To avoid thisas burden simple and as to make possible the the usageallows MILU of , both seamless infrastructures was usage further of developed andimportant different enhanced to Grid becoming note a infrastructures that tool fromexperiences which MILU coming the has from same its developed user over communities. workstation. For thedevelopment this procedure years reason, on we It taking the have following is mainly into concepts: based account our software the requests and As a result, the following is a list of requirements that have successfully been turned into features: of the activity of projects)(see and http://eforge.escience-lab.org/gf/project/milu/). is The currently package maintained is based on onthe within and ICTP_UI the is and an SISSA/CNR EGRID_UI evolution eforge , of that platform [ were developed a few years agoto within the cope EGRID with project the requestIndian coming GRID from infrastructure users (GARUDA) of as well. the EU-IndiaGrid project to facilitate the access to raised a new problem: how tosystems exploit are the often aggregate not computing power. interoperable,sets Since of users different commands are middleware in forced order to to access install and and use those maintain PGIs. severalinfrastructure, independent a dedicated hostrunning working should as be UI is alsosome needed. properly hardware configured. resources The and The system on naturalto administration use which skills consequence the are this of same required. service machine these to And is two interoperate what facts with if more is a than user that one wants middleware? operation is one of thebetween possible the solutions. final The user basic and idea the behind installation and MILU configuration approach of is the to most fill popular the middlewares. gap MILU 1. Introduction PoS(EGICF12-EMITC2)044 Tyanko Aleksiev ]) which provide Graphical 4 ] which is actually a metascheduler which pro- 8 ]. All of them are available for download and 3 7 ]. 3 ], both preconfigured to access different Virtual Organization in 6 : Installing the three different UI separately on your host can pollute the host : MILU has been tested on different GNU/Linux distributions. We target three ] and the CERN TAR_UI [ the flexibility in enabling the access to different PGIs fromthe the , by same offering Linux an host. easy toing install the and command configure set environment of and the by three trying middlewares. to unify- All in one environment with tens ofproblem environment variables by and just path addinguser’s components. some $HOME. Removing/updating lines MILU the in software solves is your this thus .bashrc simple and file easy. Portable and two configuration filespopular distributions in (CentOS, the and Mandriva) and MILUSome is additional fully tested settings against and them. packagesfunctionality may which be are necessary duly indescribed listed order in MILU in to User guarantee the Guide the [ installation correct instructions. The known issues are 5 So, we mention here three similar projects, which were developed keeping in mind theTwo easiness of them are being developed within the gLite developer community: the INFN UI Plug & These three solutions are sharing the same idea: to make the gLite and ARC UIs portable on We also mention here the GridWay project [ The rest of this paper is organized as follows: section 2 will discuss some related works in MILU has been developed in order to offer a basic command level access to different PGIs. • • • • vides interoperability among different Grid middleware. This tool is actually fully compatible with of installing and managing the package. Play [ UI (GUI); despite the easiness of usage,the such CLI portals approach. remain always Thus, less for flexible ourthe and users, scriptable interaction the than with command the level Linux access Clusters remains and the Farms. preferred method for the EGI production infrastructure.implementation The for third accessing one the is the NorduGrid ARC [ Standalone UI, which is the client Linux platforms without the burdentages to of reinstall MILU from over those scratch solutions a are: new machine. The evident advan- installation as tar files. the area of portable and interoperabledetails UI the at package command itself line and level.tool in In for section section accessing 3 4 different we we describe PGImiddleware. discuss in Finally, based some how some on conclusions MILU and Advanced can future Resource be perspective are Connector used illustrated (ARC) as in and interoperability the final GARUDA section. 2. Related work Our specific aim was towho provide routinely a use command Plug&Play line Command-Linework as Interface with working (CLI) Portals environment. software and/or We for Gateways do (like users not for therefore instance compare Pgrade here portals our [ MILU PoS(EGICF12-EMITC2)044 Tyanko Aleksiev ] which should bring the MILU tool to a higher 17 4 ”MILU for Interoperability Usage/Testing.”. This makes 4.2 distribution [ ], mainly known for powering the NorduGrid collaboration infrastructure 7 ] is also present at version 4.0.8. The relatively old web-service based GT4 2 Matterhorn 11 ]. The ARC UI consists of a small set of well-behaved command-line clients, 16 graphically describes the main idea behind MILU. ] middleware originally developed by the Enabling Grids for E-sciencE (EGEE), an 1 9 The necessity of unifying allrequisite the more available than middleware 2 UIs yearsMILU has ago, has been when actually realized the started. to workMILU be of as gathering Thus, a a the valid pioneer the in different necessary its softwares field. scientific inside recognition shouldAdding the be Unicore given as to aone supported at middleware the in same MILU operational would level. render our UI and the EMI The main result obtained by MILU is to make usage of three different middleware clients ARC version 1.0.0 [ Globus Toolkit [ Figure As last remark in this section we would like to clarify how is currently MILU related with MILU package is created by gathering together pieces of software from thegLite three [ different Our challenge in the future development of MILU, thus, remains the integration with the • • ] makes available from technology providers within the EGI Community. Two facts are to be 17 transparent to the final users: thisenables has an been abstract achieved layer by between the the usage user of and a the wrapping three mechanism different which middlewares. is also supported. The supportCenter was (GC3) added [ in collaborationwhich with are the fully-supported Grid in Computing MILU. Competence EU project, provides acomputing framework and for storage building resources Grid acrossversion applications the 3.2, using Internet. for the 64-bit At available x86x86 the distributed architectures architectures. moment which is MILU Previous now supports versions deprecated enabled only because no also gLite releases the have gLite been done 3.1 since for 2010. 32-bit clients are actually provided dueIndian Production to Grid the Infrastructure. fact this GT version is still3.1 in Architecture use within GARUDA, the The Unified Middleware Distribution (UMD), the[ integrated set of software components that EMI middlewares (gLite, ARC and GT4)unique UI one. implementations and by making them work together as a MILU a good candidate for thetific base gateway. component in a layered implementation of a cross-grid scien- level of interoperability and give to the final users all the advantages of using3. our UI. The MILU software package considered as important here: recently-released EMI MILU MILU as discussed later in Section PoS(EGICF12-EMITC2)044 Tyanko Aleksiev 5 ), on the user’s . As briefly mentioned before Version MILU architecture: see text for discussion. MILU- Figure 1: The distribution directory layout is first created. All the configuration files arethe then first copied step. to the specific locations that have beenA created recursive in inspection is performed ofcutable the binaries different or middleware bash directories script looking commands. for exe- Two symbolic link are then created:the one wrapper linking script. the We explain real this executable part and with another more one details linking The in script the next is paragraph. then performingrectly some linked by basic the checks binaries whether and all prints a the brief required report. At libraries this are point cor- testing procedures can be initialized on the new distribution. Once the testing procedures are finished on the different Linux distributions a new MILU MILU has been created by taking the three different middleware UIs andBasically, all by the making stand-alone UIs their are initially downloaded and placed in a specific location so • • • • • • release can be done. MILUin is a being single distributed directory as (named ain single the “tar” heart file; of MILU all functionality its isunderstand contents the this are wrapping functionality of unpacked we the post real some executable lines binaries. of In the order script to bellow: better components work together asscript. a We provide unique here one. some technical details This of how process exactly is this task almostthat is the fully accomplished. generating automated script by caneffects: recognize a them. bash The execution of the script will have the following MILU PoS(EGICF12-EMITC2)044 command has Tyanko Aleksiev * glite-wms- so that the middleware-specific version 6 commands in the code above it can be considered as a * LD_LIBRARY_PATH lcg- is supposed to be set like: and 1 commands request the libraries distributed with gLite, thus, ) * −∗ LD_PRELOAD ...... ;; ;; export LD_LIBRARY_PATH=$MILU_INSTALL_DIR/sw/ external / usr / lib64 : . . . source $MILU_INSTALL_DIR/sw/ etc / profile .d/common.sh lcg exec "$MILU_INSTALL_DIR/ bin /. lnk /$PROG" "$@" LD_LIBRARY_PATH of a compatible libraryglite-wms is found first bythe the Linux runtime linker. For example: all the been invoked. LD_LIBRARY_PATH=$MILU_INSTALL_DIR/sw/glite/lib64... so that the linker will first check this directory when a Sources the Run Time Environment (RTE) of the currently supportedDetermines VO. the name ofdifferent the middlewares. command being called, which is generallyGiven the unique name, across the the MILUby loading generic environment wrapper variables from creates a an middlewaresome configuration appropriate specific file middleware execution and, environment if environment variables. needed, set-up The wrapper script can now execute theon real the command command with line. the arguments passed by the user Some of the difficulties into making three versioning different and incompatibilities; middlewares these working canvariables together be overcome are by related setting the environment In the rare cases when it is not, the commands have the same functionality and purpose so we can just use the more Although we referenced the 1 • • • • • ...... source $HOME/.VO. sh c a s e $PROG i n advanced/compatible version. Although conceptually simple, this approachfeatures has are proved worthy to of be note: very flexible and extensible. Some valid example of the MILU’s core functionality which performs the following tasks: MILU PoS(EGICF12-EMITC2)044 Tyanko Aleksiev Loading the RTE of the command unnecessarily (1) env 7 Older version of the Globus Toolkit and gLite used a custom version (3) variant of this option is also provided. The integrated help facilitates the usage A typical gLite installation for the Large Hadron Collider (LHC) VOs requires setting verbose; the confinement technique used byhidden MILU from the allows user. users to keep all the Grid settings of the OpenSSL libraries: running systemGrid commands commands with with the those, system-provided or OpenSSL —conversely— libraries running The would lead confinement to technique program crashes. used inwith Grid MILU commands, allowed and to keep the use system the libraries modified forFinally, the OpenSSL note rest. libraries that the technique isdifferent easily version extensible: of the MILU apurpose. could, middleware e.g., and be used use to them install concurrently for testing and comparison Although most commands only relyrequire on additional the special correct treatment settingthese (e.g., of can be placing environment handled a variables, on a some configuration case-by-caseration/cleanup file basis actions. by in having the a wrapper fixed script run location): specific prepa- Environment variable values from the Grid setupas do not they pollute are the normal only user loaded environment, executed. when We needed give and three act examples just where in this the is scope advantageous. of the Grid command being currently supported VO only duringset-up command and execution offers prevents thus of the(2) having major persistent flexibility VO of managingtens different of VOs environment from variables, the which same makes host. the output of the In order to check the correct installation and operation MILU comes with a self-test script. It The package contains also some other tools to help user in installing, testing and managing The rest of the software included in the MILU package consists of the real software compo- • • • runs test cases for allconfiguration the (e.g., main missing reverse gLite DNS and entries, ARC whichproblems can commands, (e.g., confuse and clock GridFTP checks clients) skew and for with potential common respect to signs well-known of NTP mis- servers). An effort has been made to an gives an overview of all the available options. it. The top-level MILU directory containsexecution the modes: installation script, for which example, offers differentous single- options description or and of multi-user MILU’s installation architecture, it canMILU is be and clear stored chosen. that in all From MILU’s configuration directoryby the is the tree. previ- already installation So, distributed script with basically, is the toThis only replace helps paths work in in that keeping configuration the has installation files to quickality. to be and The reflect simple, performed installation the and script installation focus also location. on checks if providing-dry-run user-level all function- the necessary software is present on the target host. A nents (e.g., binary executable files,selection libraries) has included been in done the ingathered, different tested order middlewares. and to reorganized An reduce inside the accurate the MILU size directory of tree. the3.2 final Milu package. tools At the end they are all MILU PoS(EGICF12-EMITC2)044 euindia, Tyanko Aleksiev . A step by step tutorial which replaces all the Virtual Organization ]. 3 8 ] for writing configurations for VOs not currently supported 3 milu_change_VO ] project was actively promoting the MILU development: as we already 1 Finally, MILU allows switching from one Virtual Organization to another. This is performed Switching between different VOs is made possible because of the wrapper-based architecture In this section we describe some of the use cases where MILU has been successfully deployed MILU, in its previous versions was made available and presented in several eventsMILU has and been we then actively used by EU-IndiaGrid and e-NMR VOsThe during EU-IndiaGrid various [ training discussed EU-IndiaGrid’s purpose is toinfrastructure, allow and interoperability the between the Indianthe gLite-based “GARUDA” infrastructure package European is based permanently on used GT4.day-to-day not only use; for Inside we training are this and getting community ments. “Grid some The schools”, very continuous but collaboration useful also with feedback for the and EU-IndiaGrid production community requests during for the various some training future improve- with a single command, called of MILU: since all configurationswitch is command loaded at has command to execution do,variables time, is to all to the be change work loaded that achoice, by the link among VO- the to the wrapper the ones script. set supported of by configuration Each MILU, files user which, and can at environment independently the select time a of VO writing of are: her and used. They represent the mostcapabilities. typical usage These of significant the results have software been giving achieved thuswith mostly a because the global of end overview the of users active its collaboration and theof constant such feedback kind they of give development to isneeds the in and development giving making team. the the final software The more users added usable. exactly value what they want,4.1 meeting MILU their as real portable UI configured for specific user communities and as productionreceived UI requests to officially include and distribute severalenmr.eu Virtual etc.) Organizations (compchem, within eela, the EGI communities. events or just as an alternative way for users to access their Grid infrastructures. (VO)-dependent configuration files with a versionmand appropriate is for also the script-based, new selected and VO.to like This the the com- final previously user: seen installation listing all script, the offers supported variety VOs, of checking options the currently used one, etc. gilda, enmr.eu, gridseed,is available in elab, the MILU compchem, User Guidein [ MILU. gridats Finally it is worthy to underlineproxy should that be when created a in switch order to toMILU permit a can future VO do. interaction, has but been this falls accomplished outside a the new scope VOMS of what 4. MILU at work MILU test the commands in dependency ordererror and has to been make user-friendly detected reports and that stepsavailable point to and out take discussed what to in exact correct the it. MILU A User large Guide number [ of test cases are additionally PoS(EGICF12-EMITC2)044 Tyanko Aleksiev ] VO. They were interested in using MILU 15 ] Virtual Environment. The main idea of GRID- 9 10 ) at disposal of our local users. A system-wide installation has been ]. The purpose of the exercise was to provide a training facility where 12 the HADDOCK tutorial whereEMBO MILU global has exchange been lecture used courseTaiwan during in (May Beijing two 2, (April 2011) different 27 workshops: to May the 6, 2011)the and HADDOCK the WeNMR workshops one in in Istanbul and Frankfurt. MILU is also integrated in the GRIDSEED [ Finally MILU is also deployed as standard UI on the SISSA/eLab Portal UI We report in this subsection where MILU has been the crucial ingredient inMILU solving was a firstly Grid used as a single interface to both gLite and ARC within the GRIDSEED Another major user community is the e-NMR [ • • portal.grid.sissa.it users could learn howinteroperability two issues. similar Grid The middleware UIusers can from are interact both enabled and middleware to have have usefront-ends. been a same Both unified LCG_CE first credential and in knowledge as ARC_CE the were well on Both MILU configured as to gLite UI access same and where the VOMS same ARC proxy computing resources. are to using interact with the both same CE LFC file catalog as well as the same storage element. ( interoperability problem. Itevolution is of the worth package and to motivate note further its that development. this real-worldtraining case environment studies [ drove the recent and make it available toaccessing the the user e-NMR community Grid asand an Infrastructures. the alternative, experience preconfigured They gained Plug&Play provide with toolactivities us around the for constant the UI. world. feedback MILU We about mention was some the also of being usage them actively below: used during their training SEED is to provide aon simple Virtual . tool to Within setup GRIDSEED,Two MILU a different Virtual is portable Machines actually (VMs) and serving (a interoperable 32-bit aspreinstalled Grid and a and a infrastructure configured. standard 64-bit based Depending User one) on are Interface. the availabletructure, hardware with and more MILU the already MILU number VM of people User usinghave Interfaces the a (UIs) infras- set can of be predefined accounts added,being with up widely a to used script a during to maximum several create Grid Grid of training certificates 10. activities on around Such the the fly. UIs world. This solution is done but users canone switch Grid between infrastructures different from Virtual the Organizationsolution same allows and host. to have significantly From access reduce the to theof systems the maintenance more administrator’s users and point than this upgrade provide of time. an view uniqueportal From this point machine of the does submission point allow for of infact both view local to resources submit and on GRID our ones: local the 4.2 High Performance Computing MILU resources. for Interoperability Usage/Testing MILU activities and schools organized locally permitsinteraction us and to occasional gain “user even testing” moresoftware - useful more an experience usable doing essential for live step thethis for specific positive improving interaction needs and is of making the the this integrationwe MILU of community. discuss the in An metascheduler next as important subsection. part recent of example the of MILU distribution as PoS(EGICF12-EMITC2)044 Tyanko Aleksiev ], and on the results of the above 13 10 Interoperability between Globus Toolkit 4 and gLite Figure 2: depicts the basic idea for this interoperability issue. 2 In the scenario described in the picture the main role is played by the GridWay metascheduler Very recently MILU, jointly with GridWay metascheduler was a key software package to en- which uses MILU as underlyingpoint software here to is connect that with MILU differentGridWay. provides Grid on The infrastructures. the Gridway The same package key hostby is all MILU therefore the and compiled low this and level implementationduction software linked allows Grid which against cross-submission Infrastructures is from the in needed the libraries a by samethen provided transparent host appropriately way toward configured for both in the Pro- all finalsources, the users. to components Gridway accomplish for metascheduler data gathering was transfer information about across the EU-IndiaGrid Grid resources re- in EGI Grid and GARUDA example, the project interoperability team ofnario the based project on lined-out production a resources completeresources available interoperability from and sce- both GT4-WS Grid GARUDA infrastructures resources ascompleted exploited CREAM-CE with simultaneously EGI Gridway from scheduler. achosen MILU to In installation facilitate this the regard, end-usersFigure in the spawning GridWay their meta-scheduler jobs has transparently been on the also resources available. able interoperation between theinteroperability GARUDA study and exploiting the EGI virtual environment Grid ofa GRIDSEED infrastructures. Globus involving an toolkit LCG-CE Starting 4 and with web a service basic flavour computing element [ MILU The above services are complemented byThat a work fake represented Certification a Authority first providedthe by possibility attempt of GRIDSEED. to facing Grid setup interoperability a featuresEuropean and training Grid issues facility middleware when solutions. using that quite While would widelyrience using provide deployed different MILU to levels and end of GRIDSEED users users interoperability:access are middleware level. able level, to scientific expe- gateways level, application PoS(EGICF12-EMITC2)044 Tyanko Aleksiev 11 ]. The GridWay scheduler, properly configured to access both GARUDA and 14 MILU Grid and finally to executeand jobs the simultaneously GARUDA Grid. on EU-IndiaGrid Submissionas VO of reported resources MPI in in jobs [ the wasgLite also EGI infrastructure, enabled Grid is for now both availablethe Grid for site infrastructures the hosting MILU the 1.2. MILUcient project. It interoperability User is tool communities to distributed have use as therefore boththis a at infrastructures approach disposal separate at a can plug-in the simple now on same and easily time.downloading effi- the implemented We software stress on and here any installing the it Linux fact by host that themselves. at disposal to the users by simply PoS(EGICF12-EMITC2)044 Tyanko Aleksiev 12 To provide a smooth transitionsoftware still between needs different to middleware be around systems,when as two e.g., the infrastructures new with when one different the is access too old methods have immature to to be completely bridged. replaceTo it, provide or a preconfigured environmentuser, that used can to satisfy the play needs withdetails of command and only the line needs average interface a scientific and tool that who "just does works". not care about the technical it provides a portable Plug&Play Grid environment for Linux boxes, it enables the usage of different middlewares all at the same time. Future developments of the package, in addition to the standard update ofWe the finally mention middleware that MILU is an open project made available to the community and we MILU is also an important tool towards interoperability. In this context we successfully ex- The positive feedback received by several users and user communities makes us confident We also believe that MILU can have an impact for the users and developers belonging to Details about implementation and some practical use cases have been presented as valid In this paper, the MILU software project, has been presented addressing its two main important • • • • supported, will be in therequired direction by the of user providing community on which the is steadily top increasing. of MILU usefulencourage tools interested and people software as tointeresting play to community with developers, it in addition and tothe non-technical contribute target users, audience to who of have it. been MILU. historically Indeed,access We MILU on think can a be that the Linux MILU idealtest/debug machine, could instances tool of for be for running quickly services. the enabling Grid purpose client of rapid prototyping a new tool, or for deploying ploited interoperation among the Indian productionone Grid by GARUDA means and of the GridWay. European gLite-based that MILU software facilitates thecomplexity access of to installing the and configuring differentfrom Grid Grid the intricate UI. infrastructures details This of and Grid allows hides middleware installation MILUto the and learn users configuration high how and to therefore to be to use dedicate largely the Grid shielded and not how to installemerging the communities, middleware. as a lower-levelnisms tool can upon be which built. There more is sophisticated a Grid clear access need mecha- for a tool like MILU: demonstration proofs. The package,support together is with freely available detailed and instructions atof about the the time its MILU of installation software. this and writing, we registered more than 2600 downloads features: MILU 5. Conclusions PoS(EGICF12-EMITC2)044 , paper Tyanko Aleksiev EU-IndiaGrid , IFIP International , Concurrency and Computation: , Future Generation Computing Systems 23 , appeared in Computational Methods in Multiagent and Grid Systems, An International 13 , 1st International Workshop on Grid Technology for A modular meta-scheduling architecture for interfacing GRIDSEED: A Virtual Training Grid Infrastructure available as pdf file at Applications exploiting e-infrastructures across Europe and India within the invited contribution into the book: ‘”Grid Computing", ISBN Programming the Grid with gLite The new EGRID infrastructure P-GRADE portal family for grid infrastructures MILU user Guide Globus Toolkit Version 4: Software for Service-Oriented Systems Science and Technology, 2006 , Pacini and F. Prelz and J.Craig White and and A. M. Di Barroso Meglio and andand P. Buncic A. A. and Djaoui Edlund R. and and Byrom F. A. Giacomini and MaraschiniWalk and L. and and J. Cornwall A. R. Hahkala and Wilson, Middleton and M. and F. M. Hemmer Sgaravatto and and S. M. Hicks Steenbakkers and J. ’http://eforge.escience-lab.org/gf/project/milu/docman/?subdir=2’ with pre-WS and WS Grid resource(2): management services 252-261, 2007 Financial Modeling and , Palermo, Italy, February, 2006. Practice & Experience. Volume 23, Issue 3, pages 235-245, 10 March 2011 accepted to the CLCAR2011 conference, Colima5-9 Mexico Colima, September Mexico. 2011 CLCAR 2011, September Conference on Network and , Springer-Verlag LNCS 3779, pp 2-13, 2006. testcase“ Demo session during the 5threference: EGEE http://gridseed.escience-lab.org/uploads/Main/GridSeed-poster.pdf User forum at Uppsala (Sweden) April 15 2010. Poster EU-IndiaGrid project 979-953-307-540-1, InTech - Open Access Publisher, to be published. Alessio Terpin, interoperability experiments using GridSeed tool Journal 6 (2010) 261-269 Network, Grid infrastructure and Interoperability: state-of-the-artEUIndiaGrid2 between Deliverable Europe D3.1, and available India at http://www.euindiagrid.eu/index.php/pubblications- doc/doc_download/520-eu-indiagrid2-deliverable-d31 [3] T. Aleksiev [1] A. Masoni, S. Cozzini, [2] Ezio Corso, Stefano Cozzini, Angelo Leto, Antonio Messina, Riccardo Murri, Riccardo Di Meo, [4] Peter Kacsuk, [9] E. Laure and C. Gr and S. Fisher and A. Frohner and P. Kunszt and A. Krenek and O. Mulmo and F. [5] The package is available at: https://gilda.ct.infn.it/UIPnP/ [6] The package is available at: https://twiki.cern.ch/twiki/bin/view/LCG/TarUIInstall [7] http://www.nordugrid.org/arc/ [8] E. Huedo, R. S. Montero and I. M. Llorente. [10] I. Gregori, S. Cozzini, T. Aleksiev, [11] I. Foster, [12] ”Interoperabilty among gLite and ARC middleware in training grid infrastructures: GRIDSEED [13] B.R. Amarnath, T. Selvi Somasundaram, M. Kashif, A. Masoni and S. Cozzini MILU References [14] [15] http://www.e-nmr.eu/gLite-users [16] http://www.gc3.uzh.ch/organization.html [17] http://www.eu-emi.eu/ and http://www.eu-emi.eu/emi-2-matterhorn