• Save
Dev ops presentation @ beingagile2013
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Dev ops presentation @ beingagile2013

  • 3,163 views
Uploaded on

Presentation on Dev Ops which I had presented in Being Agile 2013 Conference in McKinsey&Co, Gurgaon

Presentation on Dev Ops which I had presented in Being Agile 2013 Conference in McKinsey&Co, Gurgaon

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • for more information on continuous delivery and devops in the enterprise, checkout the whitepaper http://xebia.com/sites/default/bestanden/ContinuousDeliveryPaperXEBIA27112012.pdf
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,163
On Slideshare
3,142
From Embeds
21
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
1
Likes
4

Embeds 21

https://twitter.com 21

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. DevOps Demystified Anirudh Bhatnagar Senior Consultant, Xebia India. abhatnagar@xebia.com 9650573087
  • 2. Amazon’s web infrastructure guru James Hamilton uses Facebook’s recently released energy data to make an educated guess for how many servers Facebook now has: potentially 180,000. That’s up from an estimated 30,000 in the winter of 2009, and 60,000 by the Summer of 2010. google has more than one million servers 10 releases per day! ● 3 engineers ● over 14 million users ● no hardware ● +100 instances on Amazon EC2
  • 3. Agile : Responding to change.. - Less time to Market. - Low release cycle time. - Huge amount of servers on cloud. - Zero downtime. - Increasing traffic and user base.
  • 4. From Idea to Product
  • 5. The initial step: From Waterfall to Agile! - Continuous Integration - Test Automation
  • 6. But what about Release? The Last Mile !
  • 7. The next step : From CI to Continuous Delivery
  • 8. Impediments
  • 9. The Division Wall!
  • 10. The Dev world Write Code Write Unit Test Cases
  • 11. The Ops World IT buying Installation of server hardware and OS Configuration of servers, networks, storage, etc… Monitoring of servers Respond to outages IT security Managing phone systems, network Change control Backup and disaster recovery planning Manage active directory Asset tracking Software deployments Application support
  • 12. Developer vs IT Operations
  • 13. Bridging the gap!
  • 14. Introducing Mr. DevOps Mr. Sacha Noam Baron Cohen Designation : Senior DevOps Engineer
  • 15. its a culture... its a movement.. Started as devOps days in Belgium in 2009. Developers interested in cloud, clusters, servers, deployments, databases learn to write code to maintain them. Ops people evolve and start developing the code to maintain infrastructure. And they are all in one same dev team trying to achieve one goal!
  • 16. Collaboration -> Best practices Ops learn from developers - > Coding principles, managed code, versioning. Dev learn from Ops -> Insights of environment and deployments, their problems.
  • 17. Continuous delivery cont... Deployment Pipelines
  • 18. example: Build pipelines using Jenkins
  • 19. Automated Acceptance Gates
  • 20. Next Hurdle : Configuration Management Lets Automate : We had Perl... We had shell scripts.. ● How soon can you write this script? ● How maintainable is it? ● Can you write test cases for it? ● Can you have versioning? ● Can you have reusability? ● Risk???? ● Idempotency
  • 21. Phoenix Test
  • 22. Infrastructure as code Evolving from Scripts to code "a flexible model for reuse by enabling users to model infrastructure as code to easily and consistently configure and deploy infrastructure across any platform. Create a blueprint of your infrastructure that enables you to build or rebuild, automatically in minutes or hours – not weeks or months."
  • 23. Tools of the game Chef Puppet! vFabric .... ...
  • 24. What is Chef? Chef is a configuration management tool. Using its cookbooks and recipes we can provisions VMs, environments. Community maintained code, almost everything is prebuilt (cookbooks and recipes), need not reinvent the wheel, just modify as per the need.
  • 25. Chef Server, Chef node ,Knife, Cookbook and Recipes Chef Server : Central hub which keeps the nodes in sync. A cookbook is the fundamental unit of configuration and policy distribution in Chef. Recipes reside inside a Cookbook. Written in Ruby. Configurations , Policies and Attributes. Example CookBook of MySQL will contain 2 recipes 1. For MySql Server 2. For MySql Client Sample : http://community.opscode.com/cookbooks/mysql https://github.com/opscode-cookbooks/mysql Using your workstation you write/modify cookbooks and using knife (a tool) you sync it with chef repo and chef server.
  • 26. Chef Overview
  • 27. The complete picture..
  • 28. Small Demo: Using Vagrant Provision a VM and put Redis (a key-value based noSql Database) on an Ubuntu machine. .1) Provision VM 2.)Install Ubuntu 3.)Get the machine Up 4.)Download installer for Redis 5.)Install redis 6.)Start the service
  • 29. Cloud Support : EC2 $ knife ec2 server create "role[Demo] -N "demo.example. net" -i ami -3e02f257
  • 30. Thanks!