The Open Sourcing of Infrastructure
0 likes157 views
This document discusses the history and future of open sourcing infrastructure. It describes how Linux and open source software grew from being seen as "cheap Unix" to becoming ubiquitous. Factors like the LAMP stack, concerns around vendor lock-in, and a need for greater automation drove more organizations to use open source options. Now open source powers much of modern infrastructure through tools like Docker, Kubernetes, and DC/OS. Going forward, the document advocates open sourcing entire infrastructure stacks to avoid vendor lock-in and allow for community ownership and contributions from anywhere.
![© 2017 Mesosphere, Inc. All Rights Reserved. 3
The [recent]
history of
infrastructure
(from a highly opinionated,
open source view)](https://image.slidesharecdn.com/theopensourcingofinfrastructure-allthingsopen2017-171127161242/85/The-Open-Sourcing-of-Infrastructure-3-320.jpg)
![© 2017 Mesosphere, Inc. All Rights Reserved. 12
Downtime becoming [considerably more] unacceptable
Increase in reliance upon scaling and automation
Transition from server “pets” to “cattle”
Larger focus on data (retention, speed)
Flood of changes to how we use software](https://image.slidesharecdn.com/theopensourcingofinfrastructure-allthingsopen2017-171127161242/85/The-Open-Sourcing-of-Infrastructure-12-320.jpg)
The Open Sourcing of Infrastructure
- 1. © 2017 Mesosphere, Inc. All Rights Reserved. 1 The Open Sourcing of Infrastructure All Things Open 2017 Elizabeth K. Joseph @pleia2
- 2. © 2017 Mesosphere, Inc. All Rights Reserved. ❏ Developer Advocate at Mesosphere working on DC/OS, Apache Mesos ❏ 15+ years working in open source communities ❏ 10+ years in Linux systems administration and engineering roles ❏ Founder of OpenSourceInfra.org ❏ Author of The Official Ubuntu Book and Common OpenStack Deployments Elizabeth K. Joseph, Developer Advocate
- 3. © 2017 Mesosphere, Inc. All Rights Reserved. 3 The [recent] history of infrastructure (from a highly opinionated, open source view)
- 4. © 2017 Mesosphere, Inc. All Rights Reserved. 4 “To make a server, first add…”
- 5. © 2017 Mesosphere, Inc. All Rights Reserved. 5 With proprietary Unix and Windows-based platforms, the stage was set for the golden age of proprietary software in the 1990s and into the 2000s. And so rose the proprietary world of software
- 6. © 2017 Mesosphere, Inc. All Rights Reserved. 6 Linux was an upstart, at best seen as “cheap Unix” Lots of FUD around open source
- 7. © 2017 Mesosphere, Inc. All Rights Reserved. 7 I liked it anyway.
- 8. © 2017 Mesosphere, Inc. All Rights Reserved. 8 So I got a junior Linux systems administrator job!
- 9. © 2017 Mesosphere, Inc. All Rights Reserved. 9 ● What is Free/Open Source Software (FOSS)? ● How & Why Linux and FOSS can Deliver Business Results ● Managing FOSS: Thousands of Alternatives - How To Choose? ● Using Open Source Web Applications to Produce Business Results Some of the topics during a seminar I spoke at in the 00s
- 10. © 2017 Mesosphere, Inc. All Rights Reserved. 10 Turning point: LAMP stack
- 11. © 2017 Mesosphere, Inc. All Rights Reserved. 11 Reluctance to be locked-in by a vendor Greater concern over security Wanted the ability to fix bugs ourselves Learned that innovation is stifled when software is developed in isolation Flood of changes to how we interact with software
- 12. © 2017 Mesosphere, Inc. All Rights Reserved. 12 Downtime becoming [considerably more] unacceptable Increase in reliance upon scaling and automation Transition from server “pets” to “cattle” Larger focus on data (retention, speed) Flood of changes to how we use software
- 13. © 2017 Mesosphere, Inc. All Rights Reserved. 13 Open source is now ubiquitous
- 14. © 2017 Mesosphere, Inc. All Rights Reserved. 14 Source: “The state of the Octoverse 2016” https://octoverse.github.com/
- 15. © 2017 Mesosphere, Inc. All Rights Reserved. 15 Developers are using, developing on, contributing to, and sharing open source software! Operations is using and developing on open source software.
- 16. © 2017 Mesosphere, Inc. All Rights Reserved. 16 When I left my ops job, I left my tools behind CC BY 2.0 https://www.flickr.com/photos/90692443@N05/8239219385/
- 17. © 2017 Mesosphere, Inc. All Rights Reserved. 17 Time to open source ops stuff!
- 18. © 2017 Mesosphere, Inc. All Rights Reserved. 18 Configuration management Puppet Modules Chef Cookbooks Ansible Playbooks Open application definitions DC/OS Universe Catalog Juju Charms Full disk images Dockerhub and other container registries Done!
- 19. © 2017 Mesosphere, Inc. All Rights Reserved. 19 Welcome to the present!
- 20. © 2017 Mesosphere, Inc. All Rights Reserved. 20 Open Sourcing Infrastructure: PHASE 2 What were some of the reasons for going open source in the first place? ● Security ● Ability to diagnose and fix bugs without vendor intervention ● Increased control over our data and services ● Avoiding vendor lock-in
- 21. © 2017 Mesosphere, Inc. All Rights Reserved. 21 The Cloud. Including IaaS, PaaS, SaaS...
- 22. © 2017 Mesosphere, Inc. All Rights Reserved. 22 “Most people just consume the cloud without thinking ... many users are sinking cost into infrastructure that is not theirs, and they are giving up data and information about themselves without thinking.” Edward Snowden, OpenStack Summit, May 9, 2017
- 23. © 2017 Mesosphere, Inc. All Rights Reserved. 23 Let’s think.
- 24. © 2017 Mesosphere, Inc. All Rights Reserved. 24 Is the service I’m using adhering to open standards, or am I locked in?
- 25. © 2017 Mesosphere, Inc. All Rights Reserved. 25 What is my recourse if the service vendor goes out of business ...or is bought by a competitor?
- 26. © 2017 Mesosphere, Inc. All Rights Reserved. 26 Does the vendor have a history of communicating clearly and honestly with their customers about downtime, security, etc?
- 27. © 2017 Mesosphere, Inc. All Rights Reserved. 27 Does the vendor respond to bugs and feature requests?
- 28. © 2017 Mesosphere, Inc. All Rights Reserved. 28 Will the vendor use our data in a way that I’m not comfortable with? (or worse, isn’t allowed by your own customer agreements)
- 29. © 2017 Mesosphere, Inc. All Rights Reserved. 29 Initial costs may be low, but do you have a plan to handle long term, growing costs?
- 30. © 2017 Mesosphere, Inc. All Rights Reserved. 30 You could consider all these things and acknowledge them as acceptable risks. Many organizations do! Just make sure you are actually, seriously considering them
- 31. © 2017 Mesosphere, Inc. All Rights Reserved. 31 Various infrastructure technologies are available: ● OpenStack ● Kubernetes* and Docker swarm mode* ● DC/OS* ● ...more in the future! * Can be used in the cloud or on premises Or look again to Open Source!
- 32. © 2017 Mesosphere, Inc. All Rights Reserved. 32 Even further into the future CC BY 2.0 https://www.flickr.com/photos/kevinmgill/16528411470/
- 33. © 2017 Mesosphere, Inc. All Rights Reserved. 33 OpenStack OSUOSL KDE & Gnome Debian & Ubuntu Open Source the Whole Stack And more at opensourceinfra.org Infrastructure, configurations, tools, images
- 34. © 2017 Mesosphere, Inc. All Rights Reserved. 34 Contributions from anyone, anywhere Vendor independence No lock-in Community ownership What do these projects get?
- 35. © 2017 Mesosphere, Inc. All Rights Reserved. 35 Questions? Elizabeth K. Joseph Twitter: @pleia2 Email: [email protected] Slides http://princessleia.com/presentations/2017/ “Why open source should be the first choice for cloud-native environments” article https://opensource.com/article/17/8/open-sourcing-infrastructure