Enterprise Adoption of Open Source


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Open Sauce is not a condiment Open Source was coined by Netscape to free themselves of the ideological and confrontational connotations of the term free software The term was given a big boost at an event organized by Tim O’Reilly titled Freeware Summit - where assemblied developers including big names such as Linus Torvalds and Larry Wall voted to use Open Source software - the conference is now the “Open Source Summit”
  • In 1998, a group of individuals advocated [1] that the term free software be replaced by open-source software (OSS) In his 1997 essay The Cathedral and the Bazaar[2], open-source evangelist Eric S. Raymond suggests a model for developing OSS known as the Bazaar model. Raymond likens the development of software by traditional methodologies to building a cathedral, "fully crafted by individual wizards or small bands of mages working in splendid isolation"[2]. He suggests that all software should be developed using the bazaar style, which he described as "a great babbling bazaar of differing agendas and approaches.” In the Bazaar model Gregorio Robles[3] suggests that software developed using the Bazaar model should exhibit the following patterns: Users should be treated as co-developers The users are treated like co-developers and so they should have access to the source code of the software. Furthermore users are encouraged to submit additions to the software, code fixes for the software, bug reports, documentation etc. Having more co-developers increases the rate at which the software evolves. Linus's law states that, "Given enough eyeballs all bugs are shallow." This means that if many users view the source code they will eventually find all bugs and suggest how to fix them. Note that some users have advanced programming skills, and furthermore, each user's machine provides an additional testing environment. This new testing environment offers that ability to find and fix a new bug. Early Releases The first version of the software should be released as early as possible so as to increase one's chances of finding co-developers early. Frequent Integration New code should be integrated as often as possible so as to avoid the overhead of fixing a large number of bugs at the end of the project life cycle. Some Open Source projects have nightly builds where integration is done automatically on a daily basis. Several Versions There should be at least two versions of the software. There should be a buggier version with more features and a more stable version with fewer features. The buggy version (also called the development version) is for users who want the immediate use of the latest features, and are willing to accept the risk of using code that is not yet thoroughly tested. The users can then act as co-developers, reporting bugs and providing bug fixes. The stable version offers the users fewer bugs and fewer features. High Modularization The general structure of the software should be modular allowing for parallel development. Dynamic decision making structure There is a need for a decision making structure, whether formal or informal, that makes strategic decisions depending on changing user requirements and other factors.
  • Would this quote go better with the Trends slide, w/ Greg’s quote? Actually the point I was driving at here was that you must treat open source as something real - not just something to leverage
  • Enterprise Adoption of Open Source

    1. 1. Before We Begin… <ul><li>To listen </li></ul><ul><ul><li>Streaming audio is available via your computer </li></ul></ul><ul><ul><li>You can also join the teleconference by clicking on the ‘Info’ tab at the top-left of the presentation window and following the login instructions </li></ul></ul><ul><li>Questions? </li></ul><ul><ul><li>Please type any questions into the Q&A window at the bottom-right of your screen </li></ul></ul><ul><ul><li>We will answer as many questions as time permits at the end of the session and follow up in a few days with a Q&A document via e-mail </li></ul></ul><ul><li>Thank you for joining, we will begin shortly </li></ul>
    2. 2. Roadmap for Enterprise Open Source Adoption
    3. 3. Agenda <ul><li>Introductions </li></ul><ul><li>Defining Open Source </li></ul><ul><li>Understanding the Current Open Source Landscape </li></ul><ul><li>Adopting Open Source in the Enterprise </li></ul><ul><li>Summary </li></ul><ul><li>Q & A </li></ul>
    4. 4. What is Open Source?
    5. 5. What is Open Source? <ul><li>‘ Open Source’ originally coined in a strategy session to position and explain Netscape’s 1998 announcement to give away the source code for its browser </li></ul><ul><li>Open source has evolved to describe the principles and methodologies that promote open access to the production and design process for various goods, products and resources </li></ul><ul><li>Today, Open Source Software (OSS) has become the most recognized form of open source </li></ul>
    6. 6. Open Source Software <ul><li>OSS was advocated to replace “Free Software’ </li></ul><ul><ul><li>Less ambiguous term </li></ul></ul><ul><ul><li>Higher comfort in the corporate world </li></ul></ul><ul><li>OSS follows the “Bazaar” vs. “Cathedral” Development Model: </li></ul><ul><ul><li>Users as Co-Developers </li></ul></ul><ul><ul><li>Early Releases </li></ul></ul><ul><ul><li>Frequent Integration </li></ul></ul><ul><ul><li>Multiple Versions </li></ul></ul><ul><ul><li>High Modularization (SOC) </li></ul></ul><ul><ul><li>Dynamic Decision-Making Structures </li></ul></ul>
    7. 7. Open Source Software: Process and Projects <ul><li>Open Source Processes </li></ul><ul><ul><li>Proven to be very successful </li></ul></ul><ul><ul><li>Community-oriented and widely distributed </li></ul></ul><ul><ul><li>Highly agile </li></ul></ul><ul><ul><li>Organized through multiple governance models </li></ul></ul><ul><li>Open Source Projects </li></ul><ul><ul><li>Vast range from Linux to Apache to Eclipse </li></ul></ul><ul><ul><li>Available in all layers of the technology stack </li></ul></ul><ul><ul><li>Initially a commoditization of technology </li></ul></ul><ul><ul><li>Now leading technology innovation </li></ul></ul>
    8. 8. Open Source Software: Current Landscape <ul><li>Web Services (SOAP Stack) </li></ul><ul><ul><li>Apache Axis </li></ul></ul><ul><ul><li>Codehaus xFire </li></ul></ul><ul><ul><li>Objectweb Celtix </li></ul></ul><ul><li>Message-oriented Middleware </li></ul><ul><ul><li>Apache ActiveMQ </li></ul></ul><ul><ul><li>Jboss Messaging </li></ul></ul><ul><ul><li>Objectweb JORAM </li></ul></ul><ul><li>Enterprise Service Bus (JBI) </li></ul><ul><ul><li>Apache ServiceMix </li></ul></ul><ul><ul><li>Codehaus Mule </li></ul></ul><ul><ul><li>ObjectWeb Petals </li></ul></ul><ul><li>Enterprise Portal </li></ul><ul><ul><li>Apache Jetspeed </li></ul></ul><ul><ul><li>Liferay </li></ul></ul><ul><ul><li>Objectweb eXo </li></ul></ul><ul><li>J2EE App Server </li></ul><ul><ul><li>Apache Geronimo </li></ul></ul><ul><ul><li>Jboss AS </li></ul></ul><ul><ul><li>Objectweb JOnAS </li></ul></ul><ul><li>Build Tools </li></ul><ul><ul><li>Apache Ant </li></ul></ul><ul><ul><li>Apache Maven </li></ul></ul><ul><li>Source Code Management </li></ul><ul><ul><li>SVN </li></ul></ul><ul><ul><li>CVS </li></ul></ul><ul><ul><li>Mercurial </li></ul></ul><ul><li>Continuous Integration </li></ul><ul><ul><li>LuntBuild </li></ul></ul><ul><ul><li>Apache Continuum </li></ul></ul><ul><ul><li>CruiseControl </li></ul></ul><ul><li>IDEs </li></ul><ul><ul><li>Eclipse </li></ul></ul><ul><ul><li>Java.net NetBeans </li></ul></ul><ul><ul><li>Sun JSE </li></ul></ul><ul><li>Code Testing Tools </li></ul><ul><ul><li>JUnit </li></ul></ul><ul><ul><li>Cactus </li></ul></ul><ul><ul><li>Selenium </li></ul></ul><ul><li>Network Management </li></ul><ul><ul><li>OpenQRM </li></ul></ul><ul><ul><li>Cacti </li></ul></ul><ul><ul><li>OpenNMS </li></ul></ul><ul><li>Application Management </li></ul><ul><ul><li>LiveTribe </li></ul></ul><ul><ul><li>Nagios/GroundWork </li></ul></ul><ul><ul><li>OpenNMS </li></ul></ul><ul><li>Performance Management </li></ul><ul><ul><li>JMeter </li></ul></ul><ul><ul><li>Seige </li></ul></ul><ul><ul><li>OpenSTA </li></ul></ul>Enterprise Systems Management Enterprise Integration And SOA Enterprise Application Development
    9. 9. Open Source Software: Future Proprietary Stacks Hybrids Enabled (Platform + Marketplace) Vendor Dependent Independent Incumbents Disruptors <ul><li>OSS penetration in G2000 continues to grow </li></ul><ul><ul><li>Productized OSS (Distributions) -- continues to challenge incumbents: IBM, Oracle, BEA and Sybase are responding with “hybrids” </li></ul></ul><ul><ul><li>New OSS buying pattern – ‘long tail’ components require new sellers </li></ul></ul><ul><ul><li>OSS Governance -- IT/IS organizations piecing together their own solutions </li></ul></ul><ul><ul><li>OSS-style Development - IBM is rapidly putting together a strategy around Jazz </li></ul></ul>
    10. 10. Enterprise Adoption of Open Source
    11. 11. Enterprise Open Source Adoption: Trends <ul><li>“ By 2010, Open Source will be included in mission-critical software portfolios within 75% of G2000 companies.” </li></ul><ul><li>By 2010, 90 percent of Global 2000 organizations will have formal open-source acquisition and management strategies (0.8 probability) </li></ul><ul><li>By 2008, OSS solutions will directly compete with closed-source products in all software infrastructure markets (0.8 probability) </li></ul><ul><li>“ We're going to utilize the way the community develops software for E*Trade proprietary development... and make E*Trade more nimble.” </li></ul>- Gartner - ETrade
    12. 12. Enterprise Open Source Adoption: Benefits <ul><li>Open Standards </li></ul><ul><ul><li>Projects are built on established standards (JCP, RCF) </li></ul></ul><ul><ul><li>Multiple implementations against established standards offers choice to users </li></ul></ul><ul><ul><li>Reference implementations of standards driven by OSS </li></ul></ul><ul><li>Community Support </li></ul><ul><ul><li>Broad user base around OSS projects </li></ul></ul><ul><ul><li>Expert consulting/development experience available for major projects </li></ul></ul><ul><ul><li>Community forums/mailings lists helps users get started </li></ul></ul>
    13. 13. Enterprise Open Source Adoption: Benefits <ul><li>Extensibility </li></ul><ul><ul><li>Access to source provides extensibility </li></ul></ul><ul><ul><li>Many projects driven to design for extensibility </li></ul></ul><ul><ul><li>OSS frameworks and platforms offer technology leadership </li></ul></ul><ul><li>Licensing </li></ul><ul><ul><li>Less restrictive deployment licensing </li></ul></ul><ul><ul><li>Ability to embed OSS technologies into products </li></ul></ul><ul><ul><li>Enables massive deployments (Grid/Farm) </li></ul></ul>
    14. 14. Enterprise Open Source Adoption: Challenges <ul><li>Governance </li></ul><ul><ul><li>Licensing </li></ul></ul><ul><ul><li>Delivery Mechanisms </li></ul></ul><ul><ul><li>Intellectual Property </li></ul></ul><ul><ul><li>Indemnification </li></ul></ul><ul><li>Community </li></ul><ul><ul><li>Diversity </li></ul></ul><ul><ul><li>Infrastructure </li></ul></ul><ul><ul><li>History </li></ul></ul><ul><ul><li>Flexibility </li></ul></ul><ul><li>Support </li></ul><ul><ul><li>Availability </li></ul></ul><ul><ul><li>Enterprise-readiness </li></ul></ul><ul><ul><li>Vendors </li></ul></ul><ul><li>Integration </li></ul><ul><ul><li>Change velocity </li></ul></ul><ul><ul><li>Lack of road maps </li></ul></ul><ul><ul><li>Missing “Enterprise” features </li></ul></ul><ul><ul><li>Highly Componentized </li></ul></ul>
    15. 15. Enterprise Adoption &quot;CIOs can't afford to treat open source as a throwaway, and they can't afford to do without support for the open source that becomes a vital component of their infrastructures.” Christopher Koch Exec Editor, CIO Magazine
    16. 16. Open Source Adoption: Guidelines for Success <ul><li>Look Beyond OSS Code </li></ul><ul><ul><li>Licensing </li></ul></ul><ul><ul><li>Community Statistics and Health </li></ul></ul><ul><ul><li>Real-time Engineering Infrastructure </li></ul></ul><ul><li>Evaluate Vendor Offerings </li></ul><ul><ul><li>Distributions </li></ul></ul><ul><ul><li>Support Subscriptions/SLAs </li></ul></ul><ul><ul><li>Add-ons </li></ul></ul><ul><li>Understand and Leverage the OSS Process Model </li></ul><ul><ul><li>Distributed development </li></ul></ul><ul><ul><li>Modular, re-usable components </li></ul></ul><ul><ul><li>Incremental development based on rapid iterations </li></ul></ul>
    17. 17. Open Source Adoption: Enterprise Planning IP Verification Indemnification Support Enterprise Repository License Compliance Enterprise Developers Community Developers
    18. 18. Open Source Adoption: Enterprise Planning <ul><li>What are you using? </li></ul><ul><ul><li>Identify the OSS and versions in your Enterprise </li></ul></ul><ul><ul><li>Understand the dependencies your organization has </li></ul></ul><ul><li>What licenses can you use? </li></ul><ul><ul><li>Determine licenses you’ll allow in your Enterprise </li></ul></ul><ul><ul><li>Gather information on OSS licenses </li></ul></ul><ul><li>How are you managing IP Verification? </li></ul><ul><ul><li>Track your source to ensure Cut and Paste violations are occurring </li></ul></ul>
    19. 19. <ul><li>Do you need support? </li></ul><ul><ul><li>Don’t forget that support is available for many OSS projects </li></ul></ul><ul><ul><li>Investigate these support subscriptions and determine what you need </li></ul></ul><ul><li>Are you indemnified? </li></ul><ul><ul><li>Determine your legal requirements </li></ul></ul><ul><ul><li>Build a policy and structure for contributions </li></ul></ul>Open Source Adoption: Enterprise Planning
    20. 20. <ul><li>Artifact-driven Engineering </li></ul><ul><ul><li>Born of modularization and community development </li></ul></ul><ul><ul><li>Offers a place to store binary artifacts, associated source and metadata </li></ul></ul><ul><ul><li>Extended to store </li></ul></ul><ul><ul><ul><li>License information </li></ul></ul></ul><ul><ul><ul><li>IP Verification Reports </li></ul></ul></ul><ul><ul><ul><li>Community resources </li></ul></ul></ul><ul><ul><ul><li>Dependencies </li></ul></ul></ul><ul><li>Centralized Store for Artifacts </li></ul><ul><ul><li>Bridges OSS communities and internal use </li></ul></ul><ul><ul><li>Allows for internal projects to share </li></ul></ul><ul><ul><li>Promotes Community-Oriented Development </li></ul></ul>Open Source Adoption: Artifact Management
    21. 21. Open Source Adoption: Enterprise Development Processes <ul><li>Leveraging the Open Source Model of Development </li></ul><ul><ul><li>Artifact & Dependency Management </li></ul></ul><ul><ul><li>Continuous Integration </li></ul></ul><ul><ul><li>Build and Release Standardization </li></ul></ul>
    22. 22. Open Source Adoption: Enterprise Development Processes <ul><li>Artifact & Dependency Management </li></ul><ul><ul><li>Managing project integration at the deliverable </li></ul></ul><ul><ul><li>Visualize interdependencies </li></ul></ul><ul><ul><li>Share snapshots of on-going development </li></ul></ul>
    23. 23. Open Source Adoption: Enterprise Development Processes <ul><li>Continuous Integration </li></ul><ul><ul><li>Continuous Integration provides Test Driven Development (TDD) </li></ul></ul><ul><ul><li>Can work with Artifact Repositories to provide building for “Blessed” platforms </li></ul></ul>
    24. 24. Open Source Adoption: Enterprise Development Processes <ul><li>Build Standardization </li></ul><ul><ul><li>Leverage new build technologies (Apache Maven) </li></ul></ul><ul><ul><li>Standardize the creation of artifacts </li></ul></ul><ul><ul><li>Create a standard way to build artifacts </li></ul></ul><ul><ul><li>Laying the foundations for SOA artifacts </li></ul></ul>
    25. 25. Summary <ul><li>Open Source: </li></ul><ul><ul><li>Projects and Process </li></ul></ul><ul><li>Enterprise Benefits and Challenges in adopting OSS </li></ul><ul><li>Strategies to Leverage OSS </li></ul>
    26. 26. Thank You for Joining the “Enterprise Open Source Adoption” Presentation! If you have questions, please call: +1 310 437 4870 or visit www.simulalabs.com