ElasticBox's Ravi Srivatsav at DevOps Summit, East
•Download as PPTX, PDF•
0 likes•919 views
http://elasticbox.com Learn how ElasticBox empowers enterprises to develop DevOps culture without having to have the DevOps role by removing friction between the Developers and Operations teams.
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
ElasticBox's Ravi Srivatsav at DevOps Summit, East
- 1. Ravi Srivatsav CEO and Co-founder
- 3. DevOps DevOps is a software development method that stresses communication, collaboration and integration between software developers and IT operations professionals. Source: Wikipedia
- 4. DevOps Approaches 1.IaaS 2.PaaS 3.DevOps Engineer 4.Collaborative Approach Infrastructure Approaches
- 5. The Infrastructure Approach Data Data Data Applications Applications Applications Runtime Runtime Runtime Middleware Middleware Middleware O/S O/S O/S Virtualization Virtualization Virtualization Servers Servers Servers Storage Storage Storage Networking Networking Networking Source: Microsoft Traditional IT IaaS PaaS IT Operations IT Operations IT Operations Developers Developers Developers Infrastructure Infrastructure + Middleware Communication Communication Communication
- 6. The Traditional IT Approach Data Applications Runtime Middleware O/S Virtualization Servers Storage Networking IT Operations Developers Communication Prescriptive Manual Repetitive Error-prone
- 7. The IaaS Approach Data Applications Runtime Middleware O/S Virtualization Servers Storage Networking IT Operations Developers Infrastructure Communication • Solves the procurement problem but… • Only a small step towards DevOps • Still prescriptive • Repeatable but not scalable or reusable
- 8. The PaaS Approach • Achieves repeatable and scalable deployments by imposing restrictions • NoOps approach • Widens the gap and stifles innovation with more layers “fixed” Data Applications Runtime Middleware O/S Virtualization Servers Storage Networking IT Operations Developers Infrastructure + Middleware Communication
- 9. The DevOps Engineer Approach Source: http://inkjot.files.wordpress.com/2010/02/two-heads.jpg Solves the problem but not scalable
- 11. The ElasticBox Approach O/S Virtualization Servers Storage Networking IT Ops Dev RuntimesPlatforms Deployment Profile Create Edit/use during deployment Communication/Collaboration Create Create /Use Dev Dev Infrastructure Config Mgmnt
- 12. Key Takeaways Infrastructure is changing just as fast as software Developer feedback is key for cloud success Agility is the new stability
Editor's Notes
- I’m preaching to the choir but there are so many different reasons for DevOps. For me, the most important reason is to not curtail innovation coming from both side of the devops coin. Devs and ops are invaluable and by not enabling them to work together we’re losing out.
- Wikipedia definition (insert joke) Method, not a tool For me, communication and collaboration are key
- Set the agenda for the talk
- The infrastructure approach looks something like this – from traditional IT to PaaS, it locks down layers to achieve PaaS
- Starting with the traditional IT approach
- Locking down the infrastructure layers
- Locking down more layers. Developers get no input into the infra and middleware layers Curbs innovation that could happen in any of those layers
- To solve these problems more recently, we’ve seen the rise of devops departments with a devops persona. They are either developers who get interested in deployment and network operations, or sysadmins who have a passion for scripting and coding, and move into the development side where they can improve the planning of test and deployment. The DevOps Report which was recently published reported that 16% of their respondents were part of a devops department. But 90% of these worked for companies the size of 20-499. Therein is the problem – this approach doesn’t scale.
- I think collaboration is the answer to the problem of repeatable and scalable deployments at scale
- The EB approach -it ops on one side and devs on one side -the goal is communication and collaboration both ways -service catalog where IT ops creats config mgmt -developers also create platforms and runtimes -deployment profile created by IT, but can be modified by developers
- Key is to enable more innovation through both software and infra Devops approaches should break down the walls rather than make the gap wider IT has to be agile to keep up