AWS and Open Cloud, All Things Open, 10/25/2013, Raleigh NC
3 likes861 views
The document discusses the evolution and competition in the cloud ecosystem, particularly focusing on AWS and open source alternatives like Eucalyptus and OpenStack. It emphasizes the dominance of Linux as the operating system for cloud computing and the potential benefits of an open cloud approach to prevent vendor lock-in. The presentation includes insights into cloud automation, the significance of continuous integration for developers, and the importance of creating an alternative cloud ecosystem to challenge AWS's market position.
AWS and Open Cloud, All Things Open, 10/25/2013, Raleigh NC
- 1. AWS and the open cloud ecosystem 24 October 2013 All Things Open Raleigh NC USA
- 2. @gregdek – tweet me up :)
- 3. ( Why are you here? Do use use AWS? Are you looking at private cloud? Just want to be entertained? Let's go around.) Q+A (And I have a lot of questions myself.)
- 4. (Why cloud?) MTBIAMSH (nat friedman's new toys | the sysadmin's lament | testing at scale )
- 5. Can anyone catch AWS? ( gartner magic quadrant | why? | infrastructure | real SOA | revealing the need for scale )
- 6. private cloud, srsly??? ( regulatory | leverage legacy | price | fight lock-in | NIST definition | the victory of open )
- 7. Follow AWS API || Compete w/AWS API ( why openstack competes | why eucalyptus co-opts | what the pundits think )
- 8. Would Linux have been a success... ...if Linus had rewritten POSIX? ( the GNU tools ecosystem on UNIX | the power of the de facto standard | 1000x50 or 50x1000 )
- 9. (And let's do questions again.) Q+A
- 12. Fun Fact! The first four leaders of the Fedora Project left Red Hat to work for cloud companies. Michael Johnson rPath (now SAS) Cristian Gafton Amazon Greg DeKoenigsberg Eucalyptus Max Spevack Amazon
- 13. ? Why the rush to cloud? Startups and cloud Shadow IT and cloud Automation and cloud Low MTBIAMSH
- 14. Why the rush to cloud? Startups and cloud Shadow IT and cloud Automation and cloud Low MTBIAMSH (snip... go read the whole post) http://nat.org/blog/2011/06/instant-company/
- 15. Why the rush to cloud? Startups and cloud Shadow IT and cloud Automation and cloud Low MTBIAMSH (snip... go read the whole article) http://www.wired.com/insights/2013/04/bringing-amazon-web-services-out-of-corporate-its-shadow/
- 16. Why the rush to cloud? Startups and cloud Shadow IT and cloud Automation and cloud ...because if you develop software, you have no excuse for not doing continuous integration. Low MTBIAMSH
- 17. Why the rush to cloud? Startups and cloud Shadow IT and cloud Automation and cloud Low MTBIAMSH
- 18. Cloud computing has created the lowest ever value for MTBIAMSH in the history of computing. That's why everyone is using it. (special thanks to Adrian Cockroft of Netflix for this amazing acronym)
- 19. ? What does this mean for open source? Open source has won Linux is the dominant cloud operating system Thus, cloud is where the opportunities are
- 20. What does this mean for open source? Open source has won Linux is the dominant cloud operating system Thus, cloud is where the opportunities are
- 21. What does this mean for us? Open source has won FIXME: count of AMIs across all AWS regions showing the massive number of Linux AMIs of all flavors Amazon, Google, Rackspace, and everyone else all use Linux hosts underneath, because why wouldn't you? Linux is the dominant cloud operating system Thus, cloud is where the opportunities are
- 22. What does this mean for us? Open source has won FIXME: amazing picture of all the Awesome Opportunities! Open source IaaS Open source Paas Open source SaaS? The opportunity: build SaaS based on open source components? Cloud is a way to monetize open source software Linux is the dominant cloud operating system Thus, cloud is where the opportunities are
- 23. ? Does cloud freedom matter? The fear: lock-in The opportunity: the open cloud Approach #1: create a new cloud ecosystem Approach #2: open the AWS ecosystem
- 24. Does cloud freedom matter? The fear: AWS lock-in FIXME: Gartner magic quadrant Ultimately, relying on a single vendor is bad! The opportunity: the open cloud Approach #1: create a new cloud ecosystem Approach #2: open the AWS ecosystem
- 25. Does cloud freedom matter? The fear: AWS lock-in The opportunity: the open cloud FIXME: image of the Rackspace open cloud billboards It is both intuitive and desirable to create an open cloud. We need an open cloud. And remember: Everyone is looking for any way to compete with AWS. Approach #1: create a new cloud ecosystem Approach #2: open the AWS ecosystem
- 26. Does cloud freedom matter? The fear: AWS lock-in The opportunity: the open cloud FIXME: talk about how the alternate API for Rackspace here Approach #1: create a new open cloud ecosystem Approach #2: open the AWS ecosystem
- 27. Does cloud freedom matter? The fear: AWS lock-in The opportunity: the open cloud Approach #1: create a new cloud ecosystem Approach #2: open the AWS ecosystem
- 28. ? Creating a new cloud ecosystem: is it working? OpenStack: huge brand OpenStack: huge community AWS: way ahead in features AWS: way ahead in users OpenStack doesn't help AWS users
- 29. Creating a new cloud ecosystem: is it working? FIXME: OpenStack trends on Google OpenStack: huge brand OpenStack: huge community AWS: way ahead in features AWS: way ahead in users OpenStack doesn't help AWS users
- 30. Creating a new cloud ecosystem: is it working? FIXME: numbers from Ohloh, other places OpenStack: huge brand OpenStack: huge community AWS: way ahead in features AWS: way ahead in users OpenStack doesn't help AWS users
- 31. Creating a new cloud ecosystem: is it working? FIXME: numbers from Ohloh, other places OpenStack: huge brand OpenStack: huge community AWS: way ahead in features AWS: way ahead in users OpenStack doesn't help AWS users
- 32. Creating a new cloud ecosystem: is it working? FIXME: numbers from Ohloh, other places OpenStack: huge brand OpenStack: huge community AWS: way ahead in features AWS: way ahead in users OpenStack doesn't help AWS users
- 33. Creating a new cloud ecosystem: is it working? FIXME: numbers from Ohloh, other places OpenStack: huge brand OpenStack: huge community AWS: way ahead in features AWS: way ahead in users OpenStack doesn't help AWS users
- 34. ? So who is Eucalyptus? We care about open AWS Eucalyptus is an acronym The GPL and why it still matters
- 35. So who is Eucalyptus? We care about open AWS Eucalyptus is an acronym The GPL and why it still matters
- 36. So who is Eucalyptus? We care about open AWS Eucalyptus is an acronym The GPL and why it still matters
- 37. So who is Eucalyptus? We care about open AWS Eucalyptus is an acronym The GPL and why it still matters
- 38. ? How can you compete with OpenStack? Not a competition Loose vs. tight integration Focus yields efficiency Competing for attention
- 39. How can you compete with OpenStack? Not a competition Somewhere we must include: https://twitter.com/dendrobates/st atus/367760606457126912 Loose vs. tight integration Focus yields efficiency Competing for attention https://twitter.com/dendrobates/st atus/367760606457126912/phot o/1
- 40. How can you compete with OpenStack? Not a competition Loose vs. tight integration Focus yields efficiency Competing for attention
- 41. How can you compete with OpenStack? Not a competition Loose vs. tight integration Focus yields efficiency Competing for attention
- 42. How can you compete with OpenStack? Not a competition Loose vs. tight integration Focus yields efficiency Competing for attention
- 43. How can you compete with OpenStack? Not a competition Loose vs. tight integration Focus yields efficiency Competing for attention
- 44. We compete by doing one thing very well, better than anyone else in the world. (Thanks to Jim Collins for the Hedgehog concept. Now go read Good to Great.)
- 45. ? Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 46. Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 47. Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 48. Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 49. Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 50. Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 51. Does Eucalyptus work? Better today than yesterday Embrace the ecosystem Today's services Tomorrow's services The Netflix example
- 52. ? Can I see for myself? Eucalyptus Virtual Cloud Faststart
- 53. Can I see for myself? Eucalyptus Virtual Cloud Faststart
- 54. Can I see for myself? Eucalyptus Virtual Cloud Faststart
- 55. BUT WHO IS THE LINUX OF CLOUD???!!?! !!?!11!!!??!one
- 56. Hello everybody out there using minix I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones. This has been brewing since april, and is starting to get ready. I’d like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things). I’ve currently ported bash(1.08) and gcc(1.40), and things seem to work. This implies that I’ll get something practical within a few months, and I’d like to know what features most people would want. Any suggestions are welcome, but I won’t promise I’ll implement them :-) Linus ([email protected])
- 57. Hello everybody out there using AWS I’m doing a (free) cloud (just a hobby, won’t be big and professional like AWS) for Linux. This has been brewing since april, and is starting to get ready. I’d like any feedback on things people like/dislike in AWS, as my cloud resembles it somewhat (same physical layout of the API (due to practical reasons) among other things). I’ve currently ported EC2 and S3, and things seem to work. This implies that I’ll get something practical within a few months, and I’d like to know what features most people would want. Any suggestions are welcome, but I won’t promise I’ll implement them :-) Rich Wolski ([email protected])
- 58. q+a and thanks we're hiring [email protected] @gregdek