Open Source Development in Real Business. Yoshiya ETO Linux Development Div. Platform Business BU. Fujitsu Ltd.

Transcription

1 Open Source Development in Real Business Yoshiya ETO Linux Development Div. Platform Business BU. Fujitsu Ltd.

2 Disclaimer The opinions and views expressed here are my own, and do not reflect those of my employer or its clients. 1

3 Quick history of Fujitsu with OSS In early 90s NIC drivers GNU utils for PC 2

4 Linux Development early 2000s Fujitsu has focused on the Enterprise To recommend Linux as one of the priority OS Developing lots of features for enterprise No.16 contributor according to the KPS site Kernel + Patch + Statistics in google Touching to several core components in Linux kernel Optimizing Servers and MWs to Linux Linux runs for lots of business critical systems 3

5 OSS, what is the value for you? What is the OSS for you? Why do you use it? Most likely answer, Reduce development cost Use OSS as part of your product under the license Opened Source Software Someone developed it for themselves You may use it for another workload 4

6 OSS as Opened Source Software Someone developed for themselves Very well tested for his workload Tested for other workloads also Almost no difference against proprietary software Vendor assumes workload and test cases for it You can request lacked feature to vendor/community You can directly pay cost to make it better, if you need much better quality in feature and stability 5

7 Working together with OSS You may request lacked feature to the project Add your requirement to To-Do List in community A person who understands your business may develop it You can directly pay cost for the development Crowd Sourcing Software CSS??? open-o Sourceing Software You may develop priority things by yourself 6

8 To develop things in community Understanding IP&Licenses Managing the development: lots of differences To Understand your requirement To Educate engineers To Create indicators to understand the progress Finding out the understandings in executive 7

9 The productivity in Linux kernel 50 What does this mean? What should we manage for this? 8

10 Development style in Linux You have to adjust your development style & plan Your patch Your patch After several cleanups Not acceptable Your patch has space to be acceptable 9

11 Divergence, conflict Linux drives huge-servers and small devices This is creating the divergence in requirement Just a negative impact in development? 10

12 Fuel of Innovation at OSS Divergence, conflict Memory hotplug Started to enable high-end server capability Small embedded vendor did nt like the implementation Finally we reached the breakthrough idea w/them Collaboratively develop both requirements 11

13 Fuel of Innovation, another case Divergence, conflict Cgroup Started to isolate different characteristic workload on big enterprise server Smart-phone developer joined to the develop. Core Technology: Common to all products You are not only the developer Collaboration is the key to touch to the core May make development slower but make innovation 12

14 Productivity, again Productivity: indicates in-house development Developer: not limited in-house Your team is part of the community developer Have to look around you KPS site provides the information Employers Dir 13

15 Managing the development Traditional indicators may not work well Coding status: coded lines / planed code lines Test status: tested cases / planed test cases Maturity curve: Bugs found / bugs to be found New indicator needed to understand the progress Example of indicator: Really used in big project Patches accepted / Patches to be accepted KPS site was developed for this purpose 14

16 Maturity curve of stability AFR, Annual Failure Rate -RHEL case- Fujitsu internal statistics data

17 Fuel of maturity curve 1Make OS stable for the specific MW/application Develop strictly required feature in Linux Contribute test cases based on the incidents analysis To Linux Test Project, LTP To KVM Autotest project 2Keep workload running inside the stable code-path Educate MW/appl. developer to understand OS code Limited feature should be used in MW/appl. 3Divergence does not help... 16

18 Summary No choice other than OSS Uniqueness: Can be achieved with OSS Joining to OSS: To create your uniqueness OSS is waiting for your idea Education: In communication, Change mind set Your own progress indicator: Pseudo-productivity Business indicators/plan: To involve executives 17

19