The lessons of Open Source for the Open Cloud


Published on

Lessons learned during +25 years of Open Source and how those can be adapted to define the Open Cloud and at what we can do to see this idea materialise.

Published in: Technology, Business
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
  • Horizontal scalability is the ability to distribute the load across a cluster of machines (think CDN), as opposed to adding more resources to a single machine/cluster (think extra storage)
  • The lessons of Open Source for the Open Cloud

    1. 1. The lessons of Open Source for the Open CloudStefano Maffulli, OpenStack Community Manager2012-09-22
    2. 2. Mission accomplished
    3. 3. Mobile and cloud computing are changingthe scenario
    4. 4. Define open-ness in cloud computing
    5. 5. <1> Enabling innovation
    6. 6. We won!
    7. 7. Enabled by the Freeedom to run, study,modify, copy
    8. 8. The freedom to tinker
    9. 9. The freedom to make
    10. 10. The freedom to innovate
    11. 11. Faster, better, cheaper
    12. 12. Open Innovation
    13. 13. OpenStack, an example of Open Innovation
    14. 14. What is OpenStack ABSTRACTION BETWEEN APPS AND HARDWARE Compute Pool Network Pool Storage Pool Virtualized Servers Virtualized Networks Virtualized Storage
    15. 15. Road to the OpenStack Foundation October 2011 April 2012 Announced 19 companies July 18, 2012 plans to launch announce support Final legal Sept 19, 2012 independent for Foundation; documents OpenStack Foundation in form Drafting posted for Foundation 2012 Committee ratification Launch!July 2010 Jan/Feb 2012 June/July August 2012OpenStack Created 2012 Drafting Individual &community framework for committee Gold Directorestablished Foundation as produces and elections; first a community publishes three Board of rounds of legal Directors documents meeting
    16. 16. OpenStack monthly active developers
    17. 17. Users of OpenStack
    18. 18. </1>
    19. 19. <2>Define “Open Cloud”
    20. 20. From computing “products” to “services” Mainframe Enterprise Cloud Computing Computing Computing1960 1980 2000 2020 Disruptions
    21. 21. Evolution of computing modelsSLA 99.999 99.9 Always onScaling Vertical HorizontalHardware Custom Enterprise CommodityHA type Hardware SoftwareSoftware Centralized Decentralized DistributedConsumption Centralized Shared Self-service Mainframe Enterprise Cloud Computing Computing Computing 1960 1980 2000 2020
    22. 22. The four freedoms (computing products) 0 freedom to run for any purpose 1 freedom to study how it works 2 freedom to make copies to help you and your friends (and charge for the act of making one) 3 freedom to distribute modified copies
    23. 23. The four freedoms (computing services) 0 freedom to run for any purpose  Do you run a service? 1 freedom to study how it works  Do you need to study how the platform runs or just study its interfaces/APIs? 2 freedom to make copies to help you and your friends (and charge for the act of making one)  You dont need to really to: if you need more capacity you buy more of the service 3 freedom to distribute modified copies  Maybe, but does it make sense?
    24. 24. Open Source software is not enough
    25. 25. San Diego Super Computer Cloud Storage Service
    26. 26. Data changes everything
    27. 27. Scale changes everything
    28. 28. Defining Open Cloud Respect the users of the services  Users must be free to come in and out of clouds  Data formats must be Open Standards  Interfaces/APIs must be Open Standards Enable Open Innovation (dont reinvent the wheel)  Create vibrant communities and business friendly ecosystems
    29. 29. Whats an Open Standard subject to full public assessment and use without constraints in a manner equally available to all parties; without any components or extensions that have dependencies on formats or protocols that do not meet the definition of an Open Standard themselves; free from legal or technical clauses that limit its utilisation by any party or in any business model; managed and further developed independently of any single vendor in a process open to the equal participation of competitors and third parties; available in multiple complete implementations by competing vendors, or as a complete implementation equally available to all parties.
    30. 30. Building both for users and for businesses
    31. 31. </2>
    32. 32. <Conclusions>
    33. 33. Close to the leaders Software As A Service Platform As A Service Infrastructure As A Service
    34. 34. The tasks of OpenStack Foundation Large scale testing and continuous integration coordination Tools to help developers contribute code easily Event management (Summit & Conf, other regional events) Legal (CLA process, trademark management & defense) Educational resources to help developers, sys admins, users, CIOs, evaluate and implement OpenStack Promotion of the OpenStack brand, including webinars, case studies, TCO studies, user interviews, and press outreach for member companies to leverage when promoting their OpenStack- powered products Promotion of ecosystem building OpenStack businesses "State of OpenStack” reports covering topics like the OpenStack Jobs outlook, OpenStack economic impact
    35. 35. Thank you … Stefano Maffulli  @smaffulli on Twitter  … for supporting OpenStack!  @openstack   All text and image content in this document is licensed under the Creative Commons Attribution-Share Alike 3.0 License (unless otherwise specified). "LibreOffice" and "The Document Foundation" are registered trademarks. Their respective logos and icons are subject to international copyright laws. The use of these therefore is subject to the trademark policy.