AN EMPIRICAL EVALUATION OF YEAR 1

���1

!

Anees Shaikh

A YEAR AGO AT ONS

���2

Inder GopalBoard Chairman, OpenDaylight ProjectOpen Networking Summit, Apr 2013

FOCUS OF THIS TALK

• Outside-in look at OpenDaylight — using real data where possible

• Some self-evaluation — successes and shortcomings

���3

HOW TO MEASURE SUCCESS?• OpenDaylight goals: Code, Adoption, and Community

• Code — projects and the Hydrogen release

• Adoption — vendor products, user deployments, industry perception

• Community — diverse, thriving group of developers

• “You’ll know it when you see it”

���4

OPENDAYLIGHT PROJECT CREATION

���5

Ope

nDay

light

app

rove

d pr

ojec

ts

0

4

8

12

16

April May June July August September October November December January February

1616151515141312

322

5 new project proposals pending

OPENDAYLIGHT PLATFORM

���6

OPENDAYLIGHT CODE VOLUME (OHLOH.NET)

���7

Java

C++

C

Python

0 200000 400000

33,539

146,115

291,849

461,768

PROJECT COMPARISONS (OHLOH.NET)

���8

LOC contributors

OpenStack 1.67M 1,974

CloudStack 1.5M 250

Eclipse platform 2.67M 404

OpenDaylight 1.05M 154

Floodlight 97K 52

contrail-vrouter contrail controller

19K 258K

15 53

MEMBERSHIP — WHO WANTS TO PLAY

���9

5

13

20

28

35

April 8 launch June 3 June 5 June 15 October 3 January 16 February 4

18

23 22

2629

3133

VENDOR ADOPTION — PRODUCTS BUILT WITH OPENDAYLIGHT

���10

3Q 2013

1Q 2014

NON-VENDOR USERS OF OPENDAYLIGHT

• University of Kentucky (OVSDB project)

• ITRI — Taiwan (SNMP4SDN project)

• CableLabs (PCMM/ COPS prototype and proposal)

• Individual users / developers (dlux project, python client proposal, …)

���11

INDUSTRY PERCEPTION

���12

In the beginning … A New Hope!

INDUSTRY PERCEPTION

���13

In the middle … The Skeptics Strike Back

���14

first release — Return of the Jedi ?

INDUSTRY PERCEPTION

PROJECT ANALYSIS

• Stackalytics analysis

• project code submissions

• code reviews

• mailing list activity

• lines of code

• originally developed for monitoring OpenStack, adapted for OpenDaylight (in a hurry — use these numbers for trends, not absolutes)

���15

DISTRIBUTION OF COMMITS — MAY ’13 TO JAN ‘14

���16

Total to date

individual graphs in ‘Additional Material’

DISTRIBUTION OF COMMITS (OS AND ODP)

���17

OpenDaylight Hydrogen

OpenStack Diablo

DISTRIBUTION OF CODE (LOC)

���18

May 2013

January 2014

PROJECT COMMITTER DIVERSITY — GOOD

���19

integration openflowplugin ovsdb

PROJECT COMMITTER DIVERSITY— NOT SO GOOD

���20

controller opendovebgpcep

these are just examples — there are other projects with similar distributions

MAILING LIST ACTIVITY DISTRIBUTION

���21

Jan ‘14

May ‘13

SUMMARY — HOW DID WE DO?• Code 😎

• OpenDaylight community has produced a tremendous amount of code in a short period, steady increase

• Adoption • vendor products based on OpenDaylight announced or shipping 😃 • non-vendor use and extensions to OpenDaylight 😊 • industry perception still mixed 😕

• Community • large set of formal and non-affiliated members 😃 • overall committer number and diversity increasing 😊 • project-level committer diversity needs more work 😕

���22

ADDITIONAL MATERIAL

���23

DISTRIBUTION OF COMMITS

���24

May 2013

DISTRIBUTION OF COMMITS

���25

June 2013

DISTRIBUTION OF COMMITS

���26

July 2013

DISTRIBUTION OF COMMITS

���27

August 2013

DISTRIBUTION OF COMMITS

���28

September 2013

DISTRIBUTION OF COMMITS

���29

October 2013

DISTRIBUTION OF COMMITS

���30

November 2013

DISTRIBUTION OF COMMITS

���31

December 2013

DISTRIBUTION OF COMMITS

���32

January 2014

���33

Total to date