Microsoft PowerPoint - Tutorial.ppt

UNICORE Tutorial outline Seamless Grid Computing with UNICORE • • • • • • Introduction & History The UNICORE approach Architecture and implementation details UNICORE Client GUI & Application Support UNICORE Projects & Future Availability GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Uniform Interface to COmputing Resources UNICORE Tutorial outline Universität-GH Paderborn Research Center Jülich Pallas GmbH German Weather Forecast Konrad-Zuse- Center for Scientific Computing Berlin Technical University of Dresden • • • • • • Introduction & History The UNICORE approach Architecture and implementation details UNICORE Client GUI & Application Support UNICORE Projects & Future Availability University of Karlsruhe Computing Center University of Stuttgart GFK Workshop, Seoul 2003 Peggy Lindner Leibniz – Computing Center Munich GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Approach Approach • Provide a uniform and seamless working environment for end–users – access and authentication mechanisms (client, certificates, …) – platform details (commands, data archives, batch systems, …) – user–level resource and job model (task graph, …) – job monitoring and controlling • Intended UNICORE users – end–users in a specific domain – general HPC end–users – NOT application developers • Intended usage modes – batch execution – interactive steering – NOT general purpose interactive GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Approach Approach • Security mechanisms – user authentication by X.509 certificates – authorization handled by the sites – data integrity and confidentiality by reliance on SSL/https • Implementation technique – emphasize portability, rely on standards – use Java for client and server components – build protocols on top of SSL/https – use of XML for storing jobs • System integration and deployment – fit into common firewall configurations – integrate into existing system administration procedures – preserve site autonomy (authorization, quotas, billing, …) • Extensibility – provide GUIs for particular applications (plugin mechanism) – extend set of supported resources, incarnation rules – configure third–party file transfers GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart UNICORE Tutorial outline UNICORE Resource Model Unicore Client • UNICORE site (Usite) • • • • • • Introduction & History The UNICORE approach Architecture and implementation details UNICORE Client GUI & Application Support UNICORE Projects & Future Availability • Virtual site(s) (Vsite) • User submits jobs to a Vsite • Resources – Capacity – Capability • Resources are advertised to the client GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart HLRS NEX SX5 NEC AzusA Volvox Processors CPU Time Memory Permanent disk MPI version VampirTrace version ≤20 ≤172800 sec ≤ 20000 Mbyte ≤ 100 Mbyte 1.2 2.0 LRZ Munich VPP 7000 SR8000 UNICORE Job Model • Directed acyclic graph of – tasks (computational or data transfer) – sub–jobs (to be executed at another Vsite) – temporal dependencies DNS Job VOLVOX Import Model Data If Success Execute LM Model Transfer Data Data Model – File Types • Attach resource requests to tasks – capacity (CPU time, disk, …) – capability (MPI–2, profiling, …) Notify user – can do static tests of jobs – can do resource brokering … Process-DNS Zampano Postprocess Export Data • Nspace (or Local): a local file space on the users workstation or on a local file server. As these file spaces are not controlled by the UNICORE Vsites they have been labelled as Nspaces (No UNICORE Space). • Xspace: the file space on the actual execution system where the home directory of the user’s account resides. As originally only UNIX file systems has been addressed by UNICORE this kind of file space has been named as Xspaces (UniX file space). • Uspace: a temporary working file space. For each (sub-)job a dedicated temporary working directory is created which is named Uspace (Unicore File Space). All tasks of a (sub)-job are executed in the corresponding Uspace. GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart Architecture (I) Overview Client UPL (Unicore Protocol Layer) authentication Architecture (II) NJS and TSI NJS initiate NJS <-> TSI Protocol control/data Gateway UPL Abstract Gateway TSI Shepherd fork NJS incarnation authorisation UUDB NJS IDB NJS (brokering) IDB Non-abstract NJS <-> TSI Protocol USpace TSI TSI USite USite Batch Scheduling System (NQS, PBS, LSF, fork) VSite VSite – virtual site Uspace – Unicore space GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart TSI – Target System Interface IDB – Incarnation Database Usite – UNICORE site NJS – Network Job Supervisor UUDB – UNICORE User Database GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart Job submission and execution JPA (Job Preparation Agent) SSL Multi-site Jobs Site Information Unicore Client GUI [Plug-In] Trusted CAs UUDB User Cert signed by trusted CA? HTTP HTTP Site Information Gateway Socket/SSL SSL Unicore Server Map CERT to Unix Login Unicore Server Gateway SSL Gateway Network Job Supervisor NJS (Network Job Supervisor) Socket Network Job Supervisor TCP/IP IDB TSI Make generic job machine specific TCP/IP Batch subsystem via TSI Batch subsystem via TSI Batch subsystem via TSI USpace Job Storage Space Batch subsystem via TSI Batch subsystem via TSI Batch subsystem via TSI UNICORE Site n Supercomputer GFK Workshop, Seoul 2003 UNICORE Site 1 GFK Workshop, Seoul 2003 Peggy Lindner Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Open architecture JPA (Job Preparation Agent) SSL UNICORE File Transfer - FTM Other client (e.g. NIFTI) Trusted CAs UNICORE Server NIFTI client SSL Gateway Socket/SSL XSpace SSH Storage Server RSH/SSH with suexec TSM Proprietary XSpace RSH Storage Server XSpace TSM Storage Server XSpace HPSS Storage Server Gateway SSH Accesor SAFE server Other servers (e.g. SAFE) RSH Accesor TSM Accesor HPSS Accesor Network Job Supervisor (NJS) UUDB HPSS shell Batch subsystem via TSI GFK Workshop, Seoul 2003 Peggy Lindner Target system access mechanism (e.g. SSH) GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Technical Details FTM Security Model • Architecturally integrated with the rest of the UNICORE software • Protocol is also based on serialized Java Objects • Due to different nature of file transfer commands the protocol is a multi stage protocol (not UPL) • Will use the same Gateway • Authentication – Gateway requires user certificate to initiate SSL communication – pass (permanent) user certificate along with job description • Authorization – Vsite maps certificate to local userid – authorization based on local userid – accommodate site–specific procedures • Job and request integrity – each DAG is signed with the user’s private key – the Vsite executing a sub–job can verify authenticity • Trust required – the user protects his/her private key – the CA is not compromised – NO transitive trust between Usites GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart Technology Details (I) Technology Details (II) • The protocol is implemented in two layers: • Vertically integrated architecture • Client and server components are implemented in Java 2, Perl used for Target system integration • Authentication using X.509 certificates, no delegation • Coexistence with firewalls – Unicore Protocol Layer (UPL) Simple Request/Response Protocol realized with serialized Java Objects – Abstract Job Objects (AJO) model Jobs such as a Script Task in a generic way are transmitted as serialized Objects within UPL Requests • Carries a workflow of jobs • Jobs described in an abstract form • Workflow can also contain some control constructs Deserialize Serialize Script Task Signature 10010010001111110... SSL TCP/IP Peggy Lindner Script Task Signature UPL Request GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 High Performance Computing Center Stuttgart UPL Request High Performance Computing Center Stuttgart Technology Details (III) UNICORE Tutorial outline • Supported target platforms (TSI interfaces) – Sparc and IA32 machines running Solaris – IA32 and Itanium machines running Linux – IBM SP running AIX 4.3 and 5.x – Cray T3E running Unicos/mk, SV–1 running Unicos – Hitachi SR8000 running hiux – SGI WS/Origins running Irix 6.x – HP Alpha running Tru64 – Apple Macintosh running OS X – NEC SX5 running Super-UX • Supported execution systems – CCS, LL, LSF, NQE, NQS, PBSPro GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart • • • • • • Introduction & History The UNICORE approach Architecture and implementation details UNICORE Client GUI & Application Support UNICORE Projects & Future Availability GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart The Application Front-end The UNICORE Client • Create GUIs that support important applications – UNICORE client has a plugin interface – GUI simplifies data entry for application – GUI can support application–specific resources – GUI constructs (complicated) job chains automatically • GUI will use UNICORE client to – submit the application job – monitor and control the application job • Helpful features – end–users concentrate on applications – extended consistency checks GFK Workshop, Seoul 2003 Peggy Lindner The UNICORE Client enables the end–user to • Construct UNICORE jobs • Check whether a job under construction is correct and can be run on the intended target site • Submit a completely constructed UNICORE job including Flow control constructs • Save/load partially or completely constructed jobs to/from disk • Inspect the status of all jobs known to the UNICORE system (scheduled, running, completed) • Control jobs that are scheduled or running • Retrieve the results for jobs or tasks that have been completed GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Supported Tasks Supported Tasks cont. • Script Task: – the script text can be edited in a text pane, or imported from a local or remote dataset – Input and output files can be specified • Command Task: – execute a command or application – Input and output files can be specified • Import/Export Task: – import a dataset from the (local) file space accessible to the UNICORE user into the Uspac – export a dataset from the Uspace into the (local) file space – handle storage and archive servers by specifying storage resources GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart • Transfer Task: – transfers files from the execution space of a job group to another job group – Files to be transferred can be selected from a menu, and the target job group is specified using a menu – operates in a “push” mode: the target job group is started only after all files have been transferred • File Operations Task: – Copy, rename, or delete files at run time – Create directories or modify file or directory permissions. • Compile Task: – combines the steps of compiling and linking of Fortran programs – The compiler and linker options are entered in abstract terms, supporting optimisation and debug level, data type sizes etc. GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart The UNICORE client GUI Keystore Editor Import Select Certificates Certificate Creates CSR JMC – Job Monitor Controller JPA – Job Preparation Agent Supports multiple CAs and Identities GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Creating a simple Script Job Resource Sets and Displays Site information Software resources Capacities resources Storage resources Performance indicator GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Resource Sets and Displays cont. Job Monitoring List defined resource sets Association to tasks Standard Out/Error Display and edit resource sets Job Details Log Information GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Job Flow Control Job Flow Control cont. • Simple dependency model was not sufficient – Repeated executions of tasks – Job-chains – Applications start after a certain time – Possibility for checking the success of tasks within a job chain – Checking if files are present, readable,… • Job Control constructs – Loop constructs: DoN – Group, DoRepeat - Group – Conditional constructs: IfThenElse - Group – Hold constructs: HoldJob – Task GFK Workshop, Seoul 2003 Peggy Lindner • DoN - Group – A task or sub-job is repeated N times – N is constant, predefined by the user – useful for tasks, which are able to store their provisional results and load these results on the next call to continue calculation GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Job Flow Control cont. Job Flow Control cont. • DoRepeat - Group – A task or sub-job is repeated as long as a certain condition is fulfilled / not fulfilled – useful for tasks, which are able to store their provisional results and should be repeated until a certain result or condition is reached – 3 types of conditions: • Return code • File Test • Time Test GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart • IfThenElse - Group – A task or sub-job will be executed only if a certain condition is fulfilled / not fulfilled – The „Then-Group“ is executed if the result of the test is true, otherwise the „Else-Group“ is executed – useful for tasks, which depend on any conditions GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart Job Flow Control cont. Extend the User Interface – The UNICORE Plug-In mechanism • • HoldJob - Task A HoldJob-Task will not be scheduled until – a certain time/date is reached – the user manually releases that task useful for jobs, which need resources available only on certain time interval or jobs, which execution should be checked by the user • Use the plugin interface to add components to the client – new task types (with menu entries, dialog panels, icons) – new services (extension plugins) • Plugins can – access site information and resources – construct UNICORE jobs in containers – containers encapsulate AJOs and UI information – use the remote file selector and editor – access and process the job outcome (results) Application specific support GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart The UNICORE Plug-In concept The UNICORE Plug-In concept • Plugins are separate modules that are loaded into the main software at runtime • These modules come as signed Jar archives that have the ending Plugin.jar • The client scans two directories for plugins – The installation directory ($INSTALLPATH/lib) – The user defined directory • Currently supported plug-in: - CPMD - Fluent - STAR-CD - Nastran - Gaussian - Metacomputing and Vampirtrace • On the following slides – Example Scenario – CPMD GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart The Plug-In concept – Look and Feel Menu options The Plug-In concept – Look and Feel (II) Menu options Representation In Job Editor GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart The Plug-In concept – Look and Feel (III) Menu options Representation In Job Editor Special GUI in JPA The Plug-In concept – Look and Feel (IV) Menu options Representation In Job Editor Special GUI in JPA Wizards assists in parameter settings GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart The Plug-In concept – Look and Feel (V) Menu options Representation In Job Editor Special GUI in JPA Wizards assists in parameter settings Representation In Job Monitor The Plug-In concept – Look and Feel (VI) Menu options Representation In Job Editor Special GUI in JPA Wizards assists in parameter settings Representation In Job Monitor Visualization of results GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart The Plug-In concept – How to use? The Plug-In concept – How to use? (II) Client Software Plugin XY 1. Download plugin jar archive and store in plugin directory. Client Software Plugin XY 2. Decide whether to trust a Plug-In Plugin Jar Archive Website Website GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart The Plug-In concept – How to use? (III) The Plug-In concept – How to use? (IV) Client Software Plugin XY 3. Edit the Plug-In Parameters Client Software Plugin XY 4. Will the selected virtual site support the plugin? Request Software Resource: Plugin XY Virtual Site (Vsite) GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart The Plug-In concept – How to use? (V) Plug-In Development Client Software Plugin XY 5. Submit a job • • • • Write a Java Plugin (once) Low effort for plugin writers Up to 3 classes to implement as signed Jar archive Reusable client components – FileImportPanel, FileExportPanel, RemoteTextEditor, SelectorDialog, DirectConnection, ResourceManager Submit Job containing Plugin task • Example plugins as templates at http://www.unicore.org Tutorials, Howtos, Javadoc, Support available, for instance the “UNICORE Client Plugin Programmer‘s Guide” describes the classes which have to be implemented Virtual Site (Vsite) GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Plug-In Development cont. Plug-In Development cont. • Two types of Plug-Ins – Extension Plugins (add any other new functionality to the client) -> e.g. Small Services or Resource Broker – Task Plugins (add new types of tasks to the standard client tasks) -> e.g. CPMD or Fluent • Extension Plugin: – Main Plugin Class (ExtensionPlugable): • Responsible for loading, starting and finalizing the plugin • Offers the general methods to do (e.g. inserts plugin specific menu items or attaches a toolbar to the virtual site list, or enables special features for a Vsite) • Task Plugin has to provide : – Main Plugin Class (TaskPlugable) • Responsible for loading, starting and finalizing the plugin • the general methods to do (e.g. inserts plugin specific menu items) – task icon – method to construct the container (hides AJO action graph from user) – method to construct the JPA panel (Implements the graphical representation of the application-specific parameters, and allows adding panels to the Job Monitor (e.g. for the visualization components)) GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Plug-In Development – UNICORE Container hierarchie Plug-In Development - Constructing AJO in UserContainer To be used: setFileImports() addFileImport() ImportGroup ExecuteGroup To be implemented: buildExecuteGroup() To be used: setFileExports() addFileExport() ExportGroup GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Plug-In Development – Incarnation • • Add an entry to the Incarnation Data Base (IDB) Software Resource contains paths to binaries, configuration files, etc. Example on SR8000: SOFTWARE_RESOURCE [Car-Parrinello Molecular Dynamics] CPMD V3.4.1 Plug-In Development – Resources Batch Sub-System ResourceSet Memory (64, 128, 32000) SoftwareResource XY ... • UNICORE Client UNICORE Job ResourceSet PluginTask XY PluginTask XY SoftwareResource XY SoftwareResource XY UNICORE Server INVOCATION CPMD-V3.4.1 [ export JOBTYPE=8E8; /usr/mpi/bin/mpiexec –p IAPAR -n $UC_PROCESSORS /usr/local/bin/cpmd.x $CPMD_FILE $PP_LIBRARY Memory (64, 128, 32000) SoftwareResource XY ... IDB MEMORY DEFAULT [64] … … SOFTWARE_RESOURCE XY INVOCATION XY [ /usr/bin/xy –param1 … ] Plugin XY GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart UNICORE Tutorial outline UNICORE based projects • The original UNICORE and follow on project UNICORE+, have completed end of 2002 Current projects : – EUROGRID (11/2000 – 10/2003) – OpenMolGrid (09/2002 – 11/2004) – GRIP (01/2002 – 12/2003) – NaReGI project (Japan) • • • • • • Introduction & History The UNICORE approach Architecture and implementation details UNICORE Client GUI & Application Support UNICORE Projects & Future Availability • GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart EUROGRID EUROGRID cont. • European Test Bed for Grid Applications – Seamless access to HPC resources: – Multi-site jobs • Application GRIDS: application-specific interfaces, evaluation of GRID solutions – Bio-GRID – Meteo-GRID – CAE-GRID • Industrial applications and GRID usage scenarios – ASP services for engineers – Intranet solutions for distributed organizations • Development of new GRID middleware – E.g. resource broker, efficient data transfer, . . . • Development and integration of new components efficient data transfer ASP infrastructure resource broker application coupling interactive access GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Bio–GRID Meteo-GRID • Create a bio–molecular PSE • Integrate existing biological and chemical codes http://biogrid.icm.edu.pl • Develop a relocatable version of DWD‘ s weather prediction model • Goal: ‘Weather prediction on-demand‘ as an ASP solution • Works from regular prediction data, topography and soil database GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart CAE – GRID (I) • • • Support standard engineering and scientific applications: Nastran, LS–Dyna, Gaussian, Amber, ... Provide UI including cost prediction Integrate accounting and billing CAE – GRID (II) • Run coupled aerospace simulations (electromagnetism) • Use CORBA as coupling substrate • Provide internal portal for Airbus engineers GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart OpenMolGRID OpenMolGRID • Development of middleware for management of large, geographically distributed chemical and biomedical databases OpenMolGRID enhance UNICORE by adding Plugins for – Applications for molecular calculations – Workflow support (problem solving environment) – Database access Application ‘Database Access Tool’ – Interface between UNICORE and database – Flexible output formats (XML, XSLT) • • GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart GRIP - GRid Interoperability Project The TSI interface to Globus 2 NJS • … To realize the interoperability of UNICORE and Globus and to work towards standards for interoperability in the Global Grid Forum - Establishing common ground between the two Grid environments/systems - Focus on Applications - Good contributions made to the activities of the GGF • Two strands of development work : - Brokering of UNICORE and Globus resources - Accessing Globus resources through UNICORE GFK Workshop, Seoul 2003 Peggy Lindner initiate NJS <-> TSI Protocol control/data TSI Shepherd creates Message translation Globus proxy GASS Server GRAM Client TSI Workers Globus protocols Globus 2 creates GRAM Gatekeeper GASS Client GRAM Job Manager Batch Scheduling System GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Open Grid Services - Infrastructure/ Architecture UNICORE Future Web Services • Based on XML and XML Schema • Web service model used for standardized interface description and communication • Web services provide a kind of stateless RPC / messaging • OGSA also makes web services stateful – useful for the kind of services which make up a Grid • OGSA also allows construction of service interfaces from other interfaces – interface inheritance • OGSA provides service data – think of Remote Instance Variables (RIV) for web services Peggy Lindner • • • • OGSA is a natural direction for UNICORE project to take The drive towards Grid standardization through the GGF, has the consequence of enlarging the scope of the GRIP project Interoperability and not just interoperability with Globus Adoption of OGSA by UNICORE is a sound move for the future • Forms the basis of the current work in GRIP. OGSA GFK Workshop, Seoul 2003 GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Proposed Integration of OGSA and UNICORE UPL porttype UNICORE Tutorial outline Client Gateway Resource Broker porttype Gateway NJS IDB NJS <-> TSI porttype UUDB porttype NJS IDB UUDB NJS (brokeri ng) TSI TSI USite USite • • • • • • Introduction & History The UNICORE approach Architecture and implementation details UNICORE Client GUI & Application Support UNICORE Projects & Future Availability Note: Not all interfaces will be implemented in 2003. GFK Workshop, Seoul 2003 Peggy Lindner = OGSA interface GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Install packages Availability • Components: – Client (for Windows and for Unix like systems) – Gateway – UUDB (UNICORE User Data Base) – NJS (Network Job Supervisor) – TSI (Target System Interface) • Required certificates: – User certificate (client) – Server certificates (NJS, Gateway) • Last version from project: 4.0 – UNICORE is available as Open Source and can be used free of charge in research projects – Software available at: http://www.unicore.org/downloads.htm • Licensing: – The software is provided under the terms of the UNICORE Forum Community License →UNICORE is available as Open Source and can be used free of charge in research projects →Protocol will be publicly available GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart UNICOREpro UNICOREpro • The Pallas Grid solution package UNICOREpro is aimed at: – Industrial corporations wanting to combine their distributed computing resources to make them available to more of their engineers and other users – Computing centers wanting their mobile users to access their platforms in a secure yet easy-to-use way – Research centers and universities wanting to pool computing resources and enhance scientific problem solving environments • Provides a free UNICOREpro Client and a UNICOREpro Test Grid environment to run real examples • The Pallas Grid solution package UNICOREpro consists of – the industrial-quality implementation of the UNICORE system – administrator support for installation and maintenance – user support and training – consulting services for analysis and choice of the right Grid configuration • More information at: http://www.pallas.com/e/products/unicore-pro GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart Further information … and now good luck! • WWW pages http://www.fz-juelich.de/unicoreplus http://www.unicore.org http://www.eurogrid.org http://www.grid-interoperability.org UNICORE Test Grid http://www.fz-juelich.de/unicore-test UNICORE Plus Project UNICORE Forum EUROGRID Project GRIP project • In case of any questions: lindner@hlrs.de • Slides are available at: http://www.hlrs.de/people/lindner/tutorials • • Any further questions? lindner@hlrs.de GFK Workshop, Seoul 2003 Peggy Lindner GFK Workshop, Seoul 2003 Peggy Lindner High Performance Computing Center Stuttgart High Performance Computing Center Stuttgart