NextGRID Open Source Software


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • COMPONENTS: GREEN = there will be an open source version YELLOW = there may be an open source version RED = likely to remain proprietary WHITE = application specific INTERFACES GREEN = there will be a public specification RED = will use a private (implementation-specific) interface BLACK = application specific
  • This diagram shows the different pieces the demo is composed of. The green ones correspond to NextGRID components reference implementations or, in the special case of the Membership STS, custom implementations which are still NextGRID compliant.
  • NextGRID Open Source Software

    1. 1. NextGRID Open Source Software Mike Surridge and Colin Upstill, IT Innovation Joan Masso and Toni Arbona, Grid Systems
    2. 2. Overview <ul><li>What is Open Source Software (OSS)? </li></ul><ul><li>Business models and OSS </li></ul><ul><li>Pre-existing open source middleware </li></ul><ul><ul><li>GRIA </li></ul></ul><ul><ul><li>IG V </li></ul></ul><ul><li>Open source results from NextGRID </li></ul><ul><li>Exploitation opportunities </li></ul><ul><li>Open source products and support </li></ul>
    3. 3. Software Licensing <ul><li>Gives permission to do things that Copyright would otherwise prevent licensee from doing </li></ul><ul><li>Defines what licensee can do </li></ul><ul><ul><li>for what purpose the software can be used – e.g. is it restricted to evaluation or research? </li></ul></ul><ul><ul><li>how the software can be used – e.g. is it restricted to an individual, can it be used over a network? </li></ul></ul><ul><ul><li>if access to the source code is guaranteed? </li></ul></ul><ul><ul><li>if the software be altered, or combined with other software, and under what conditions? </li></ul></ul><ul><ul><li>if the software be supplied to others, and on what terms? </li></ul></ul>
    4. 4. Open Source Licences <ul><li>Typically guarantee access to source code, and allow it to be adapted and/or supplied to others </li></ul><ul><li>Open Source Software (OSS) can’t be used or extended in any way a recipient wants </li></ul><ul><ul><li>originator has copyright </li></ul></ul><ul><ul><li>licensee gains specific rights defined by the licence </li></ul></ul><ul><li>Open Source is not the same as Public Domain </li></ul><ul><ul><li>OSS is not usually Public Domain </li></ul></ul>
    5. 5. Software Licence Flavours PERMISSIVE LICENCES CONTROLLED LICENCES RESTRICTIVE LICENCES TERMS USUALLY AFFECT DISTRIBUTION NOT USE YES YES YES YES BSD-type YES Only under same licence Only under same licence YES LGPL Only under same licence Only under same licence Only under same licence YES GPL NO NO NO Usually NO Proprietary Aggregate and redistribute? Modify and redistribute? Redistribute original? Access to source? Licence flavour
    6. 6. Open Source Politics The Free Software Movement <ul><li>Free Software: should let you </li></ul><ul><ul><li>run the software, for any purpose </li></ul></ul><ul><ul><li>study how it works and adapt it to your needs </li></ul></ul><ul><ul><li>redistribute copies to help your neighbor </li></ul></ul><ul><ul><li>improve the software, and distribute the result </li></ul></ul><ul><li>Requires access to source </li></ul><ul><ul><li>free software is open source </li></ul></ul>“ Free software is a matter of liberty, not price. To understand the concept, you should think of ‘free’ as in ‘free speech’, not as in ‘free beer’.” Gnu Philosophy.
    7. 7. Open Source and Business <ul><li>Reduce development costs </li></ul><ul><li>Professional services </li></ul><ul><li>Other business models </li></ul>
    8. 8. Reduce Development Costs <ul><li>Share costs among many stakeholders </li></ul><ul><ul><li>users, software developers and maintainers </li></ul></ul><ul><ul><li>packagers, documenters, etc </li></ul></ul><ul><li>Motivated by common interests </li></ul><ul><ul><li>shared development objectives </li></ul></ul><ul><ul><li>shared user requirements </li></ul></ul><ul><li>Often involves commercial participants </li></ul><ul><ul><li>Apache, Debian, IBM, Oracle, OSDL, Sun … </li></ul></ul>
    9. 9. Professional Services <ul><li>Distribute OSS for free (as in beer) </li></ul><ul><li>Charge for support services </li></ul><ul><ul><li>installation/user support </li></ul></ul><ul><ul><li>may also include security update services </li></ul></ul><ul><li>Charge for training services </li></ul><ul><ul><li>training courses </li></ul></ul><ul><ul><li>skills assessment and accreditation </li></ul></ul><ul><li>Charge for customisation services </li></ul>
    10. 10. Other OSS Business Models <ul><li>Marketing strategy </li></ul><ul><ul><li>provide ‘lite’ version free as OSS </li></ul></ul><ul><ul><li>encourage take-up of proprietary version </li></ul></ul><ul><ul><li>includes dual licensing model </li></ul></ul><ul><li>Value add-on to existing products </li></ul><ul><ul><li>open source distribution of drivers, utilities, plug-ins </li></ul></ul><ul><ul><li>enhance value of hardware or proprietary software </li></ul></ul><ul><li>Value enhancing software products </li></ul><ul><ul><li>core software is OSS and free </li></ul></ul><ul><ul><li>enhancements are proprietary and cost money </li></ul></ul>
    11. 11. Open Source Secure B2B Middleware <ul><li>Based on a service-oriented architecture </li></ul><ul><li>Focus on business relationships and trust </li></ul><ul><ul><li>business-to-business accounting and service level agreements </li></ul></ul><ul><ul><li>dynamic trust and security </li></ul></ul><ul><li>Functionality </li></ul><ul><ul><li>distributed file transfer, storage and processing </li></ul></ul><ul><ul><li>distributed database access using OGSA-DAI </li></ul></ul><ul><ul><li>distributed inter-domain workflow composition, enactment and publication using Taverna/Freefluo </li></ul></ul><ul><li>Easy to use </li></ul><ul><ul><li>cross-platform, running on Windows, Vista and Linux distributions </li></ul></ul><ul><ul><li>simple installation wizard for all components </li></ul></ul><ul><ul><li>developers kit for new managed application services </li></ul></ul>
    12. 12. <ul><li>Off-the-shelf security components </li></ul><ul><ul><li>Web Services technology and Public Key Infrastructure </li></ul></ul><ul><ul><li>transport and message level security </li></ul></ul><ul><ul><li>dynamic authorisation linked to business processes and trust </li></ul></ul><ul><ul><li>firewall and network friendly </li></ul></ul><ul><li>Standards compliance </li></ul><ul><ul><li>WSRF Profile, WS-Notification, WS-Federation, WS-I Basic Profile and WS-I Basic Security Profile </li></ul></ul><ul><ul><li>operational security policies (ISO/IEC 17799:2005) </li></ul></ul><ul><li>Supported at no cost on a best-endeavours basis and on a commercial basis </li></ul><ul><li>Available free and open source from </li></ul>Open Source Secure B2B Middleware
    13. 14. Why GRIA is LGPL <ul><li>Original goal: reduce risks for adopters </li></ul><ul><ul><li>the original GRIA project ran 2001-2004 </li></ul></ul><ul><ul><li>business Grids were then of unknown value </li></ul></ul><ul><ul><li>adopters needed a self-support option </li></ul></ul><ul><li>Today: forms part of our service business strategy </li></ul><ul><ul><li>to protect code from closure by IT vendors (so not BSD) </li></ul></ul><ul><ul><li>to allow use of third party OSS code during development (so not proprietary) </li></ul></ul><ul><ul><li>to allow OSS and proprietary “value add-on” and “value enhancement” by business partners (so not GPL) </li></ul></ul>
    14. 15. GRIA 5 Architecture Related to NextGRID Static Orchestration (discovery, workflow, invocation, etc) Automated SLAs Data-centric Application Functionality Dynamic Trust and Security Base standards (http, wsdl, soap, addressing, security, etc) GRIA uses dynamic SLA but with static terms Used for dynamic relationships, but static application workflows in GRIA 5 Consistent handling of jobs, file storage and OGSA-DAI services in GRIA GRIA uses the NextGRID model to protect relationships and services Used for basic facilities and interoperability Dynamic Orchestration (discovery, workflow, invocation, etc) Dynamic SLAs
    15. 16. Background <ul><li>Since 2000, GridSystems concentrated on the “IntraGrid” market (Grids within a single administrative domain) </li></ul><ul><ul><li>vision was the “ExtraGrid” market was not mature </li></ul></ul><ul><ul><li>this is changing quickly since 2005 </li></ul></ul><ul><ul><li>we have detected significant growth in customer interest </li></ul></ul><ul><li>Most research in publicly funded Grid projects has been about ExtraGrids </li></ul><ul><ul><li>important stock of (mostly unused in practice) available components for building ExtraGrids </li></ul></ul><ul><ul><li>we intend to take advantage of this to extend our commercial offer into the ExtraGrid market. </li></ul></ul>
    16. 17. Products <ul><li>Until now, GridSystems has developed and commercialized a closed source IntraGrid middleware known as InnerGrid </li></ul><ul><li>The new version Fura is an open source Grid middleware distribution </li></ul><ul><li>Already available </li></ul><ul><ul><li>http:// </li></ul></ul><ul><li>Under dual license </li></ul><ul><ul><li>GPL </li></ul></ul><ul><ul><li>Commercial </li></ul></ul>
    17. 18. Why Fura is GPL <ul><li>Goal: product marketing strategy </li></ul><ul><ul><li>promote take-up of IG technology </li></ul></ul><ul><ul><li>create opportunities for proprietary licensing and support services </li></ul></ul><ul><li>Dual licensing approach used </li></ul><ul><ul><li>similar to MySQL </li></ul></ul><ul><li>Why use the ‘controlled’ GPL licence </li></ul><ul><ul><li>avoids undermining alternative proprietary licence </li></ul></ul><ul><ul><li>customers have to choose early on which terms they want </li></ul></ul>
    18. 19. Relationship to NextGRID <ul><li>The components in Fura , the open source distribution, come from three sources:  </li></ul><ul><ul><li>Components from InnerGrid V , the previous version of our Grid middleware </li></ul></ul><ul><ul><li>NextGRID  key components </li></ul></ul><ul><ul><ul><li>Security </li></ul></ul></ul><ul><ul><ul><li>Workflow </li></ul></ul></ul><ul><ul><li>Other projects supported by the EU (e.g. GRIA, SIMDAT, …) </li></ul></ul>
    19. 20. Open Source Software from NextGRID (C) Univeristy of Southampton IT Innovation Centre and other NextGRID participants, 2007 Client Application Adaptive API Supplier Management Consumer Management Other Grounding Advertiser Offer Management Application Management PEP Operational Management MID Business Management App Services Service Factory App Services Evaluator Negotiator SLA Template Editor Accounting/ Billing Service Registry SLA AuthZ PDP SLA/Policy Template Store deploy SLA policies biz actions biz events app events authZ checks for the SLA create SLA and policy templates get “SLA” EPR init SLA Message headers include security and SLA context Application aspects should conform to Data-* and VIM models manage access Business Supervisor get available services QoS History QoS Analyser QoS reports get usage/ charges VIM Enactor VIM Grounding Discovery SLA Registry Service Registry Usage Monitor Membership STS Sign-On STS QoE Analyser QoE History negotiate new SLAs Prioritisation UDAP Provider AAA STS Secure Service PDP Allocator Deployer UDAP Advertiser Rights Management Security Selection Negotiation get SLAs find services register new SLA QoE logs get tokens get recommendation match SLA template Workflow Editor Activity Registry advertise SLA templates Policy Template Editor app actions Negotiator Client SLA Broker Supervisor Service Provider Customer System Admin Consumer
    20. 21. Business Actors Addressed <ul><li>Advertisers/brokers </li></ul><ul><li>Service providers </li></ul><ul><ul><li>service level agreement (some OSS) </li></ul></ul><ul><ul><li>business-level management (some OSS) </li></ul></ul><ul><li>Service customers </li></ul><ul><ul><li>service procurement (some OSS) </li></ul></ul><ul><ul><li>user management (all available as OSS) </li></ul></ul><ul><li>Application developers </li></ul><ul><ul><li>client application framework (all available as OSS) </li></ul></ul><ul><ul><li>service framework components (some OSS) </li></ul></ul>
    21. 22. Exploiting NextGRID Results <ul><li>NextGRID specifications can be used </li></ul><ul><ul><li>as input to standardisation initiatives </li></ul></ul><ul><ul><li>as input to Grid/SOA middleware design </li></ul></ul><ul><li>NextGRID OSS components can be used </li></ul><ul><ul><li>in existing OSS middleware </li></ul></ul><ul><ul><li>to extend other middleware </li></ul></ul><ul><ul><li>to directly support applications </li></ul></ul><ul><li>Many OSS components are available in GRIA and/or Fura </li></ul>
    22. 23. Roadmap <ul><li>GRIA 5.0 released Jun’06 Modular SOA </li></ul><ul><ul><li>used to prove NextGRID security protocols </li></ul></ul><ul><ul><li>contained components from other projects </li></ul></ul><ul><li>GRIA 5.1 released May’07 Usability Enhanced </li></ul><ul><ul><li>full implementation of NextGRID security model </li></ul></ul><ul><li>GRIA 5.2 released Dec'07 Advanced Applications </li></ul><ul><ul><li>uses additional base standards from NextGRID </li></ul></ul><ul><li>GRIA 5.3 for release Apr'08 Barriers to Adoption </li></ul><ul><ul><li>includes home-domain authentication based on NextGRID STS </li></ul></ul><ul><li>GRIA 6 (release tbd) Dynamic SOA Platform </li></ul><ul><ul><li>will support fully dynamic applications and SLA terms </li></ul></ul>
    23. 24. Release Calendar <ul><li>2007: Fura v1.x </li></ul><ul><ul><li>Based on InnerGrid, without a relevant impact from NextGRID </li></ul></ul><ul><ul><li>IntraGrid components </li></ul></ul><ul><li>2008: Fura v6 Enterprise </li></ul><ul><ul><li>Security extensions from NextGRID </li></ul></ul><ul><ul><li>Compatibility with the NextGRID SLA architecture </li></ul></ul>
    24. 25. Fura/GRIA Experiment in NextGRID Controller + Client DB-Access Service Job Service FURA Billing Service MID Service Registry Monitor GUI Evaluator QoS Data Collector Evaluator QoS Enforcer Membership STS Agents Dynamic Security Dynamic Security Dynamic Security Dynamic Security Dynamic Security Dynamic Security Dynamic Security Dynamic Security Dynamic Security Dynamic Security Service Provider Customer
    25. 26. Commercial Offers <ul><li>Fura and GRIA are both Open Source products </li></ul><ul><li>Developments compliant with the NextGrid architecture </li></ul><ul><li>We are looking for business partners providing consultancy and added value </li></ul><ul><li>We already have growing partner communities </li></ul><ul><li>Fura + GRIA may be bundled as an IntraGrid + ExtraGrid product </li></ul><ul><li>GridSystems and IT Innovation offer training, support, maintenance, customisation and enhancements </li></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.