Upload
sandra4211
View
433
Download
7
Tags:
Embed Size (px)
Citation preview
NextGRID Open Source Software
Mike Surridge and Colin Upstill,IT InnovationJoan Masso and Toni Arbona,Grid Systems
© University of Southampton IT Innovation Centre and Grid Systems S.A. 20082
Overview
What is Open Source Software (OSS)? Business models and OSS Pre-existing open source middleware
GRIA IG V
Open source results from NextGRID Exploitation opportunities Open source products and support
© University of Southampton IT Innovation Centre. 20083
Software Licensing Gives permission to do things that Copyright
would otherwise prevent licensee from doing Defines what licensee can do
for what purpose the software can be used – e.g. is it restricted to evaluation or research?
how the software can be used – e.g. is it restricted to an individual, can it be used over a network?
if access to the source code is guaranteed? if the software be altered, or combined with other
software, and under what conditions? if the software be supplied to others, and on what
terms?
© University of Southampton IT Innovation Centre. 20084
Open Source Licences
Typically guarantee access to source code, and allow it to be adapted and/or supplied to others
Open Source Software (OSS) can’t be used or extended in any way a recipient wants originator has copyright licensee gains specific rights defined by the licence
Open Source is not the same as Public Domain OSS is not usually Public Domain
© University of Southampton IT Innovation Centre 20085
Software Licence FlavoursLicence flavour
Access to source?
Redistribute original?
Modify and redistribute?
Aggregate and redistribute?
Proprietary Usually
NO
NO NO NO
GPL YES Only under same licence
Only under same licence
Only under same licence
LGPL YES Only under same licence
Only under same licence
YES
BSD-type YES YES YES YES
PERMISSIVE LICENCES
CONTROLLEDLICENCES
RESTRICTIVELICENCES
TERMS USUALLY AFFECT DISTRIBUTION NOT USE
© University of Southampton IT Innovation Centre 20086
Open Source PoliticsThe Free Software Movement
Free Software: should let you run the software, for any
purpose study how it works and adapt it
to your needs redistribute copies to help your
neighbor improve the software, and
distribute the result
Requires access to source free software is open source
““Free software is a matter of liberty, not price. To understand the concept,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’.”you should think of ‘free’ as in ‘free speech’, not as in ‘free beer’.”
Gnu Philosophy.Gnu Philosophy.
© University of Southampton IT Innovation Centre 20087
Open Source and Business
Reduce development costs Professional services Other business models
© University of Southampton IT Innovation Centre 20088
Reduce Development Costs
Share costs among many stakeholdersusers, software developers and maintainerspackagers, documenters, etc
Motivated by common interestsshared development objectivesshared user requirements
Often involves commercial participantsApache, Debian, IBM, Oracle, OSDL, Sun …
© University of Southampton IT Innovation Centre 20089
Professional Services
Distribute OSS for free (as in beer) Charge for support services
installation/user supportmay also include security update services
Charge for training services training coursesskills assessment and accreditation
Charge for customisation services
© University of Southampton IT Innovation Centre 200810
Other OSS Business Models
Marketing strategy provide ‘lite’ version free as OSS encourage take-up of proprietary version includes dual licensing model
Value add-on to existing products open source distribution of drivers, utilities, plug-ins enhance value of hardware or proprietary software
Value enhancing software products core software is OSS and free enhancements are proprietary and cost money
© University of Southampton IT Innovation Centre 2008
11
Open Source Secure B2B Middleware
• Based on a service-oriented architecture• Focus on business relationships and trust
– business-to-business accounting and service level agreements– dynamic trust and security
• Functionality– distributed file transfer, storage and processing– distributed database access using OGSA-DAI– distributed inter-domain workflow composition, enactment and
publication using Taverna/Freefluo
• Easy to use– cross-platform, running on Windows, Vista and Linux distributions– simple installation wizard for all components– developers kit for new managed application services
© University of Southampton IT Innovation Centre 2008
12
• Off-the-shelf security components– Web Services technology and Public Key Infrastructure– transport and message level security– dynamic authorisation linked to business processes and trust– firewall and network friendly
• Standards compliance– WSRF Profile, WS-Notification, WS-Federation, WS-I Basic Profile and WS-I
Basic Security Profile– operational security policies (ISO/IEC 17799:2005)
• Supported at no cost on a best-endeavours basis and on a commercial basis
• Available free and open source from http://www.gria.org
Open Source Secure B2B Middleware
27-28 February 2007
© University of Southampton IT Innovation Centre. 2006
13
© University of Southampton IT Innovation Centre 2008
14
Why GRIA is LGPL
• Original goal: reduce risks for adopters– the original GRIA project ran 2001-2004– business Grids were then of unknown value– adopters needed a self-support option
• Today: forms part of our service business strategy– to protect code from closure by IT vendors (so not BSD)– to allow use of third party OSS code during development (so not
proprietary)– to allow OSS and proprietary “value add-on” and “value
enhancement” by business partners (so not GPL)
© University of Southampton IT Innovation Centre 2008
15
GRIA 5 Architecture Related to NextGRID
Static Orchestration(discovery, workflow, invocation, etc)
AutomatedSLAs
Data-centricApplication
Functionality
DynamicTrustand
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)
DynamicSLAs
27-28 February 2007 © Grid Systems S.A. 2007 16
Background
Since 2000, GridSystems concentrated on the “IntraGrid” market (Grids within a single administrative domain)
vision was the “ExtraGrid” market was not maturethis is changing quickly since 2005we have detected significant growth in customer interest
Most research in publicly funded Grid projects has been about ExtraGrids
important stock of (mostly unused in practice) available components for building ExtraGridswe intend to take advantage of this to extend our commercial offer into the ExtraGrid market.
27-28 February 2007 © Grid Systems S.A. 2007 17
Products
Until now, GridSystems has developed and commercialized a closed source IntraGrid middleware known as InnerGridThe new version Fura is an open source Grid middleware distributionAlready available
http://sourceforge.net/projects/furaUnder dual license
GPLCommercial
27-28 February 2007 © Grid Systems S.A. 2007 18
Why Fura is GPL
Goal: product marketing strategypromote take-up of IG technologycreate opportunities for proprietary licensing and support services
Dual licensing approach usedsimilar to MySQL
Why use the ‘controlled’ GPL licenceavoids undermining alternative proprietary licencecustomers have to choose early on which terms they want
27-28 February 2007 © Grid Systems S.A. 2007 19
Relationship to NextGRID
The components in Fura, the open source distribution, come from three sources:
Components from InnerGrid V, the previous version of our Grid middlewareNextGRID key components
SecurityWorkflow
Other projects supported by the EU (e.g. GRIA, SIMDAT, …)
© University of Southampton IT Innovation Centre and other members of the NextGRID consortium, 2008
20
Open Source Software from NextGRID
(C) Univeristy of Southampton IT Innovation Centre and other NextGRID participants, 2007 20Client Application
AdaptiveAPI
Supplier ManagementConsumer
Management
OtherGrounding
Advertiser
Offer Management
ApplicationManagement
PE
P
Operational Management
MID
Business Management
AppServices
ServiceFactory
AppServices
Evaluator
Negotiator
SLA TemplateEditor
Accounting/Billing
ServiceRegistry
SLA AuthZPDP
SLA/Policy Template Store
deploy SLApolicies
bizactions
bizevents
appevents
authZ checksfor the SLA
create SLA andpolicy templates
get “SLA” EPRinit SLA
Message headers includesecurity and SLA context
Application aspects shouldconform to Data-* and VIM
models
manageaccess
BusinessSupervisor
getavailableservices
QoS HistoryQoS
Analyser
QoSreportsget
usage/charges
VIMEnactor
VIMGrounding
Discovery
SLARegistry
ServiceRegistry
UsageMonitor
MembershipSTS
Sign-OnSTS
QoEAnalyser QoE History
negotiatenew SLAs
Prioritisation
UDAPProvider
AAASTS
SecureService PDP
Allocator
Deployer
UDAPAdvertiser
RightsManagement
Security Selection Negotiation
get SLAs
findservices
registernew SLA
QoE logs
gettokens
get recommendation
match SLAtemplate
WorkflowEditor
ActivityRegistry
Service Provider
Customer
advertise SLA templates
PolicyTemplate
Editor
appactions
NegotiatorClient
SLABroker
System Admin
Supervisor
Consumer
© University of Southampton IT Innovation Centre and other members of the NextGRID consortium 2008
21
Business Actors Addressed
Advertisers/brokers Service providers
service level agreement (some OSS) business-level management (some OSS)
Service customers service procurement (some OSS) user management (all available as OSS)
Application developers client application framework (all available as OSS) service framework components (some OSS)
© University of Southampton IT Innovation Centre and Grid Systems S.A. 200822
Exploiting NextGRID Results
NextGRID specifications can be usedas input to standardisation initiativesas input to Grid/SOA middleware design
NextGRID OSS components can be used in existing OSS middleware to extend other middleware to directly support applications
Many OSS components are available in GRIA and/or Fura
© University of Southampton IT Innovation Centre 2008
23
Roadmap
• GRIA 5.0 released Jun’06 Modular SOA– used to prove NextGRID security protocols– contained components from other projects
• GRIA 5.1 released May’07 Usability Enhanced– full implementation of NextGRID security model
• GRIA 5.2 released Dec'07 Advanced Applications– uses additional base standards from NextGRID
• GRIA 5.3 for release Apr'08 Barriers to Adoption– includes home-domain authentication based on NextGRID STS
• GRIA 6 (release tbd) Dynamic SOA Platform– will support fully dynamic applications and SLA terms
27-28 February 2007 © Grid Systems S.A. 2007 24
Release Calendar
2007: Fura v1.xBased on InnerGrid, without a relevant impact from NextGRIDIntraGrid components
2008: Fura v6 EnterpriseSecurity extensions from NextGRIDCompatibility with the NextGRID SLA architecture
© University of Southampton IT Innovation Centre and Grid Systems S.A. 200725
Service ProviderCustomer
Fura/GRIA Experiment in NextGRID
Controller+
Client
DB-AccessService
Job Service FURA
Billing Service MID
ServiceRegistry
MonitorGUI
EvaluatorQoS Data Collector
EvaluatorQoS Enforcer
Membership STS
Agents
DynamicSecurity
DynamicSecurity
DynamicSecurity
DynamicSecurity
DynamicSecurity
DynamicSecurity
DynamicSecurity
DynamicSecurity
Dynamic Security
Dynamic Security
© University of Southampton IT Innovation Centre and Grid Systems S.A. 200826
Commercial Offers
Fura and GRIA are both Open Source products Developments compliant with the NextGrid
architecture We are looking for business partners providing
consultancy and added value We already have growing partner communities Fura + GRIA may be bundled as an IntraGrid +
ExtraGrid product GridSystems and IT Innovation offer training,
support, maintenance, customisation and enhancements