Standard Model of Open Computing Linuxcon North America - August 19Th, 2015

Towards a Standard Model of Open Computing LinuxCon North America - August 19th, 2015

Adam Jollans, Cross-IBM Linux and Open Virtualization Strategy, IBM

• Molecules • Atoms • Electrons and Nucleus • Protons and Neutrons • Quarks Ø Standard Model of Particle Physics

• Stacks • eg LAMP, Linux Distributions

• Foundations • eg Apache Foundation

• Projects • eg Hadoop

• Sub-projects • eg OpenStack Nova

• Innovation • Individual • Small group • University • IT Vendor • Customer

• Existing Community • Starting new project or subproject • Splitting of project

• Open sourcing of existing code • Contribution to open source community

• Same Project • eg Linux

• Same Community • eg Apache, Eclipse

• Default Usage • eg LAMP Stack

• Open Source

• Forking • eg MySQL => MariaDB

• Acquisition • eg Xen => Citrix

• Change of Leadership • eg resignation of “Benevolent Dictator for Life”

• Technology Shifts • eg Symbian => Android

• Can multiple projects occupy the same niche ? • Gnome & KDE • MySQL & MariaDB • OpenStack & CloudStack

• Industry Forces • Concurrent Innovations • Forking • Critical mass of Community • Ecosystem support

• Size of Community • Developers • Corporate Members • Openness • 0 – single organization controlling • ½ - open community with multiple contributors • 1 – foundation with open governance • Spin • 0 – no marketing • ½ - single vendor marketing • 1 – open marketing community • Market Adoption • Downloads • Usage

• 2010 study by Henrik Ingo into popular open source projects, comparing governance models vs size of community

• 9 projects (Linux, KDE, Apache, Eclipse, Perl+CPAN, Mozilla +Addons, Gnome, Drupal and GNU) stood out as significantly larger - roughly 10 times - than any others

• All of these projects, categorized as "XtraLarge", were developed as collaborative community projects governed by non-profit foundations

• There appears to be a glass ceiling limiting the growth of the Large single-vendor projects (MySQL, Qt, OpenOffice, Mono, JBoss)

Henrik Ingo - http://openlife.cc/blogs/2010/november/how-grow-your-open-source-project-10x-and-revenues-5x

Perl • Popular solution stack for dynamic web applications Python ½ PHP ½ ½ ½ ½ • Built out of fundamental components 17 members ½ 17 members • Linux 17 members • Apache HTTP server MySQL • MySQL Database 0 ½ • PHP / Python / Perl Scripting language ? developers

• All open source building blocks Apache ½ • Various forces linking components together ½ 114 committers • Components are interchangeable Linux

• Python, Perl, MariaDB,… 1 1 • Evolved rather than designed 249 members

• Operating System Kernel

• Active Development Contributions Linux • Over 3,500 individual developers • Over 200 companies 1 • Linux Foundation 1 • Board of Directors 3597 contributors • 249 Corporate Members • Professional Team • Marketing Activities - events, publications, blogs • Independent Technical Leadership • Fellows • Market Adoption • 51.6% market share – new physical servers “Linux Kernel Development - How Fast is it Going, Who is Doing It, What Are They Doing and Who is Sponsoring the Work” – Linux Foundation

• Web Server

• Development Contributions Apache • 8 original core contributors • Today - contributors, committers, PMC 1 • Apache Software Foundation 1 • Board of Directors 31 contributors • Volunteer Leadership • Consensus, collaborative approach • Events subcontracted to Linux Foundation • Independent Technical Leadership • Project Management Committees • Market Adoption • 37.5% cumulative market share – 327 million servers “August 2015 Web Server Survey” – Netcraft - http://news.netcraft.com/archives/category/web-server-survey/

• Relational Database

• Development Contributions MySQL • Originally developed by MySQL AB 0 • Ownership • Copyright held by vendor ½ • Dual licensing – GPL and proprietary ? contributors • MySQL AB acquired by Sun • Sun acquired by Oracle • MySQL 5.5 forked into MariaDB (GPL only) • Market Adoption • Second most popular relational database

“DB-Engines Ranking” - http://db-engines.com/en/ranking

• Goal: to spread the collaborative DNA of Linux to new fields to enable innovation and access for all.

• Criteria: that must be met in order for the Linux Foundation to host a Collaborative Project:

1. The use of open source governance best practices including license and contribution agreement choices in keeping with the ideals of Linux

2. The project must have the potential to fuel innovation in an industry through collaborative software development

Linux Foundation Collaborative Projects - http://collabprojects.linuxfoundation.org

Framework for Platform-as-a-Service

Server-side Runtime Environment

Open Virtualization built on Linux

Software Defined Networking

Open Virtualization Hypervisor

Framework for Big Data processing

Framework for IaaS Cloud computing

Document-oriented NoSQL database

Cluster computing framework

Distributions Hypervisors Languages Runtimes Management Database Analytics

Framework for IaaS Cloud computing

Tools for packaging and deploying applications in containers

Relational database, forked from MySQL

Document-oriented NoSQL database

Distributed NoSQL database

Configuration management tools

Orchestration for Docker containers

Open Compute Project – sharing designs of data center projects

Open Hardware

• Software for IaaS Clouds

• Active Development Contributions OpenStack • Over 2,000 individual developers • Over 500 companies 1 • OpenStack Foundation 1 • Board of Directors 2157 contributors • Technical Committee • User Committee • 25 Corporate Members • 117 Corporate Sponsors • 393 Supporting Organizations • Professional Team • Marketing Activities - events, publications, blogs

• Open Technical Community based on the POWER architecture • Chip Design • System Design OpenPOWER • Open Source Software 1 • OpenPOWER Foundation 1 • Board of Directors 140 members • Technical Steering Committee • Work Groups • Marketing Committee • Advisory Group • 140 Corporate and Academic Members and Associates

Management

Programming

Database

App Server

Hardware

CloudStack OpenShift Puppet OpenStack CloudFoundry Chef 1 ½ ½ Kubernetes Management 1 1 1 ½ ½ ½ ½ 1 1 139 contribs 147 contribs ½ 147 contribs ½ 2157 contribs 950 contribs 139 contribs 457 contribs Perl Python 1 PHP Eclipse Programming 1 1 ½ 1 1 85 contribs ½ 52 contribs 1 210 contribs 126 contribs

MariaDB Cassandra MySQL PostgreSQL Hadoop Spark MongoDB Database ½ 1 0 ½ ½ 1 1 ½ 1 ½ ½ 1 66 members 1 ½ 109 contribs ? contribs 20 contribs 86 contribs 587 contribs 115 contribs Apache JBoss node.JS App Server 1 ½ 1 1 ½ 1 31 contribs 126 contribs 120 contribs

Xen Linux KVM Docker OpenDaylight 1 1 1 1 ½ 1 OS 1 1 ½ 1 120 contribs 3597 contribs 357 contribs 627 contribs 364 contribs OpenPower OCP Hardware 1 1 1 1 23 140 members ? members © 2015 IBM Corporation Future Directions

• Rise of Open Foundations • Best practice governance • Avoids decay or single vendor lock-in • Architectural considerations • Currently mainly point-to-point • Multi-directional within Foundations • Gaps • Open x86 hardware • Business applications • Further work • Refining “quantum numbers” • Feedback invited • Are the layers correct, what projects are missing ? • [email protected]