OSCi-Sota
OSCi Home - OSCi Documents - OSCi Workshops - OSCi State of the Art - OSCi Events
OW2 OSCI sota and competitive analysis
This page is collectively updated by participants in the OW2 Open Source Cloudware initiative. It represents an effort to assess state of the art and to start a competitive analysis.
Members of the working group
Working group coordinators
- Patrick Moreau – INRIA
- Lionel Seinturier – INRIA
Working group members
- Cédric Carbone – Talend for DOMAIN 3
- Jean-Pierre Dion – Bull for DOMAIN 1
- Jean-Pierre Laisné – Bull for DOMAIN 4
- Alexandre Lefebvre – Orange
- Jean-Pierre Lorré - Petals Link for DOMAIN 2
- Hailong Sun – BEIHANG UNIVERSITY
- Wang Wei - ISCAS
Document History
v1.0 PM Nov 6, 2010 Initial version
v1.1 LS Nov 9, 2010 Contribution on the initial version for the glossary and domains 1, 2 & 3
v1.2 PM Nov 10, 2010 format, some clarification on section 3
1. Introduction
After exchanges between LS and PM, it has been decided to merge the state of the art action with the competitiveness one.
As noticed during the first OSCi workshop, OSCi does not provide stacks. It has been decided to rename it “component set”.
The objectives of this working group are:
- To establish the motivation to adopt Open source solutions for Cloud
2. To perform a macroscopic comparison of “OSCi component set” with state-of-the-art cloud stacks or component set
3. To perform a brick by brick comparison of OSCi components with state-of-the-art open source cloud components
4. To issue recommendations for an innovative roadmap
As far as we can, we try ti have a global approach but often we have to detail the analysis domain par domain.
- Domain 1: Self-sizing and green PaaS
- Domain 2: Massively distributed services
- Domain 3: BI4Cloud
- Domain 4: Massively distributed cloud
2 Glossary / Taxonomy
Definition
- several (UC Berkeley, Burton Group, Gartner, McKinsey, Deloitte) but NIST is emerging
- SaaS, PaaS, IaaS
Deployment types : private, public, hybrid, community
Related technologies :
Grid comp, utility comp, virtualization, autonomic computing, IoT, SOA
Non functional aspects of clouds :
Elasticity, reliability, QoS support, agility, adaptability, availability
Taxonomy (from Cloud Computing Use Case Discussion)
3 Motivation to adopt Open source solutions for Cloud
From an user point of view
- data and Application Interoperability (freedom)
- data and Application Portability
- transparency / Privacy / Security
From a technology provider / integrator point of view
- confidentiality / security
- general consensus on reduction of costs and barriers to adoption
- open APIs for pragmatic reasons
- interoperability: OSS and open standards
Proposal: to write a specific white paper on this subject.
4 Macroscopic comparison of “OSCi component set” with state-of-the-art cloud stacks or component set
The first required step Is to identify what to compare. The following table list the stacks or component set and identify which functions is implemented.
The above taxonomy is used for this analysis.
Table to be included !!
Once this cartography has been performed and the perimeter of each component set identified, the comparison can start.
The following list of the functions / qualities / features will be used to process the comparison.
- Open source or not
- Elasticity / Scalability (Storage/CPU)
- reliability
- QOS support and tools + metering + billing
- agility
- adaptability (possiblity to add functions)
- confidentiality/security
- tooling: deployment + API / programming model + development tools
- energy savings
The result will be presented on the table below:
Table to be included !!
5 Brick by brick comparison
This comparison needs to be performed for each domain.
Domain 1: Self-sizing and green PaaS
Domain 2: Massively distributed services
Domain 3: BI4Cloud
Domain 4: Massively distributed cloud
6 Recommendations for an innovative roadmap
TBC