From Academic To Business Grids Lessons Learnt at

From Academic To Business Grids Lessons Learnt at PSNC Jarek Nabrzyski Applications Deparment Manager naber@man. poznan. pl

Outline § PSNC § Barriers to Grid Adoption in Business (based on last week’s EU Challengers workshop in Pisa) § Licensing Issues § Towards Business Grids at PSNC 2

R&D Center PSNC was established in 1993 (staff: 180) and is an R&D Center in: § New Generation Networks § POZMAN and PIONIER networks § 6 -NET, SEQUIN, ATRIUM, MUPBED projects § HPC and Grids § 5 FP: GRIDLAB, CROSSGRID, GRIDSTART § 6 FP (20/4): HPC-Europa, Inteli. Grid, Grid. Coord, Core. Grid, EGEE, BREIN, Be. In. Grid, ACGT, Qo. SCo. SGrid, Challengers, OMII-Europe, Phosphorus, Baltic. Grid, g-Eclipse, int. eu. grid, GN 2, EXPRe. S, Qualipso, MUPBED, MAGIX, § 2 CELTIC Projects § Sun Center of Excellence and Microsoft Innovation Center § Portals and Content Management Tools § Grid. Sphere Portal Framework support and development § Grid. Sphere team (6 persons) led by Michael Russell now at PSNC § Digital Libraries 3

Motivations for this topic at PSNC § PSNC plays many roles in various R&D Gridrelated projects § PSNC’s ambition is to transfer Grid and other related technologies to industry and commerce § PSNC is now working on the incubator programme for SMEs to exploit and support Grid technologies § ROI is important to us § First spin-offs to be launched in coming months 4

Problem § Usually the business idea comes first, then a solution is chosen § In Grids we are looking for a business idea, while the Grid idea is known and many (pilot, but also production) implementations exist § Of course there are many other barriers for commercial Grid adoption 5

Barriers for Grid Adoption § § § Legal barriers Technical barriers Economic/communication barriers Business and organisational barriers Vision barrier 6

„pharma firm stopped doing drug discovery on a grid as results not „Bank stopped panaccepted by FDA” § Specific legal frameworks of vertical markets european grid project as auditors warned (banking/finanse/health/…) would not be able to tell § Intensified by country barriers: privacy, security, „where large financial where all transactions on-line commerce, tax, digital rights services companies processed and management, export controls etc. said that they'd never therefore risked being deploy Grids beyond § e. g. Different policies about treatment of personal liable for VAT in more their organizations' data than one country” boundaries. From a § Trust of grid applications by users needs to be regulatory point of view improved they can't - they're legally not allowed to do so” Legal barriers 7

Technological Barriers „The creation of the Open Grid Forum from GGF and EGA should advance the „The complexity of the technological standards. However, it is § A need for one evolving standards roadmap Grid technologies is necessary that OGSA and W 3 C Web for Grids with emphasis on SOA, semantics identified as one of the Services are kept strictly in step to and trust/security. ensure interoperation. At present the factors that makes § The technologies to be standardised are unclear architecture appears too complex, too product managers do not much at middleware software developer given the lack of business models. The use it as the basis of their level (not end‐user level) and lacks technological core at low levels of the architecture products solutions. ” Eduardo many required features for self‐*. can be standardised, but how much of the Oliveros, Telefonica More R&D is needed involving both management layers will remain proprietary academics and industry, the latter both depends on the business models. IT vendors and end‐users. ” Keith Jeffrey § Along with standardization comes the interoperability, or lack of it. „Grid is still in its infancy. More R&D is still needed” Many authors § Interface to the Grid 8

Economic and Communication Barriers § Will GRID enable major new market – or will existing markets grow? Many doubt about it. § Will new ecosystem disturb established players? § License issues § Academic vs. business objectives. Open or not open source? Lack of clear business models is a problem. § The current model of software application license based on CPU/machine utilization is a model that clearly blocks the use of certain applications on Grid § Fragmentation of effort, including sponsored. 9

Business and Organization Barriers § Enterprises are still afraid of exposing internal resources, § Scepticism over virtualization of the service levels § Grid implies large number of suppliers/users with no previous reference § Lack of clear business models § Fragmentation of effort, including sponsored… § Is is easier to buy (cheap) hardware, if extra resources are needed 10

Open or Not Open? (your source) § Open source often causes many problems to adopt the software by commercial companies, due to: § software quality (or the lack of it) § the availability of commercial support; § deliberately disseminated fear, uncertainty and doubt; § license issues and IPR § Depending on a business model the companies choose the right scheme for them 11

Open or Not Open? (your source) § For doing science it is often a good solution: Recommended Reading § Collaborative work: many institutions working on same problem/project „Grid Licensing: Life in the § But here many options are available. Which one is best for me? Middleware Jungle” By § Globus incubator program and other similar Owen Appleton, CERN programs require very often to giving up the copyright and IPR from their contributors. In: Grid Today 12

Vision Barriers § Social and other „soft” benefits § Sharing, recycling § The current (used) commercial software offerings are very conservative and dominantly concern cluster computing. We need intra‐ and inter‐ERP GRIDs; § Many do not believe that building open grid for business is possible even by 2020 § Open Grid does not mean that we all use the same middleware! 13

Academic Grids at PSNC EGrid Testbed Cactus worm Dynamic grid computing 12 sites Presented at SC 2000 A basis for Grid. Lab project later Winning Grand Challenge Competition in 2002 (extended to other centers including US and Korea) 14

Other examples of academic Grids at PSNC § § § § § Clusterix Progress (bioinformatics) ACGT (cancer research and bioinformatics) Vlab (virtual laboratory) Inteli. Grid (semantic Grid for engineering) EGEE Cross. Grid Baltic Grid HPC-Europa 15

Transfering Grids to Industry § More business oriented projects at PSNC (e. g. Inteli. Grid, BREIN, Be. In. Grid, Qo. SCo. SGrid, ACGT) § PSNC’s incubator program underway § Microsoft Innovation Center activities § Wielkopolska Center of Advanced Technologies § Using structural funds to help SMEs § CELTIC projects (strong business models) 16

Towards Commercial Grids: Gridge and Fed. Stage § § § § § Based mostly on Grid. Lab and Progress, productized over last 18 months) Open Source (Apache 2) Fully Integrated with GT 2 and 4 Services based bussines model (free for EU projects) Mostly addressed to academia Proposed to many Grid deployment projects as a basic Grid infrastructure New requirements/features coming mostly from research projects Fully documented Temporarily at: fury. man. poznan. pl/gridge/ § § § § § Developed from scratch Codes available only for some pieces (DRMAA Service Provider available at Source. Forge) Uses federated services specifications (Liberty Alliance, OASIS, IETF, W 3 C, OGF) Globus independent Strong business security and interoperability requieremnts Mostly addressed to commerce Integrated with Sun Grid Market system (Singapore) Integration with e. Xludus’s solutions Available (with support) soon through Fed. Stage Systems Inc. 17

Building Grid § § infrastructures and § applications with Gridge § § § More than just a prototype! Integrated, almost complete Grid solution. Supports new dynamic scenarios. Fully open source! Productization by PSNC with commercial support. Being deployed and extended in more than 20 other projects! Compliant with GGF standards (GRM, SAGA, GSA, …). Grid. Sphere is 100% JSR 168 compliant Many advanced Grid scenarios implemented using Gridge 18

Fed. Stage § § Nowadays, loosely coupled software systems, platforms and computing/data services need to be integrated, linked and coordinated over networks in a standardized way. Standardization bodies such as Liberty Alliance, WS-I, OASIS, GGF, IETF, W 3 C, etc. have released recently a set of open ready-to-implement standards and protocols that can be used to enable and improve the interoperability among distributed services and computing resources. Taking into account strong security and trust requirements, we have developed production quality Fed. Stage* solutions to help service integrators, providers and consumers to take advantage of sharing computing and data services across company borders and domains within a circle of trust We facilitate the design and deployment processes of new-generation enterprises based on computing and storage services-on-demand accessible through Identity-based Web Services over the Intra/Internet. * Fed. Stage services have been developed from scratch based on our experiences and lessons learnt from previous projects (including PROGRESS and Grid. Lab) 19

§ § Fed. Stage generic architecture Interoperability, Peformance, Security are the key issues and therefore Fed. Stage AAA-based solutions are of primary importance for the crossorganization sharing of applications, data, and computational services in a collaborative business environment today. Fed. Stage products follow Liberty Alliance and WS-I standards as well as other industry standards § W 3 C standards: XML, SOAP § OASIS standards: WS-Notification, WS-Reliability, WS-Security, SAML 2. 0 § OGF/GGF standards: DRMAA, JSDL § IETF standards: SSL/TLS to enable the interoperability among Fed. Stage and various vendors products. 20

Available Fed. Stage products/services (IVQ 2006) § § § Fed. Stage Identity Provider/Manger Fed. Stage Authorization Provider/Manager Fed. Stage Accounting Provider Fed. Stage Computing Provider is able to handle more than 20 job Fed. Stage Notification Provider requests per second, around 2. 000 job requests per day, up to 1000 users requests over Web Fed. Stage Computing Provider Services and message level security mechanisms. Remote Interfaces/protocols: Web Services over SSL / SAML 2. 0 / WS-Security, IDWSF 2. 0 support, JSDL 1. 0, WS-Notification, DRMAA 1. 0 Built in support for Authentication, Authorization, and Accounting Distributed Resource Managers: Sun Grid Engine (SGEv 6 u 7), Condor 6. 8. 2 and higher), PBS/Torque Computing Nodes and Platforms: Solaris, Linux, Unix, Mac, Windows 21

Summary § Looking forward to removing the barriers for Grids (not that easy) § Go commercial if you have a bright idea and few persons willing to take a risk § Start with your business idea! § Carefully plan the steps and the technologies you want to use. § Use industry approved standards where possible. § Be carefull, technolgy is not the only limitation! 22

Thank you! 23