• Save
DevOps, Cloud, and the Death of Backup Tape Changers
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

DevOps, Cloud, and the Death of Backup Tape Changers

on

  • 781 views

Talk on the state and (hopeful) future of the IT Operations industry presented at the SouthEast LinuxFest 2013. In this talk I outline how Ops is slowly killing off it's own position by not adapting ...

Talk on the state and (hopeful) future of the IT Operations industry presented at the SouthEast LinuxFest 2013. In this talk I outline how Ops is slowly killing off it's own position by not adapting to serve users/customers better and clinging to it's fiefdom.

Statistics

Views

Total Views
781
Views on SlideShare
762
Embed Views
19

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 19

https://twitter.com 19

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

DevOps, Cloud, and the Death of Backup Tape Changers Presentation Transcript

  • 1. DevOps, Cloud, and the Death ofthe Backup Tape ChangerDavid NalleyPMC Member Apache CloudStackMember, Apache Software Foundationke4qqq@apache.orgTwitter: @ke4qqq
  • 2. #whoami• Apache Software Foundation Member• Apache CloudStack PMC Member• Recovering Sysadmin• Fedora Project Contributor• Zenoss contributor• Employed by Citrix in the Open Source Business Office
  • 3. Setting expectations• Wildly opinionated• Not really a deep technical talk• Plenty of prognostications
  • 4. A bit of background• Server hugger• Cloud hater• Sudden cloudy conversion
  • 5. Status Quo in Operations• Start new project• File ticket for resources....wait....wait....wait• Get resources, that arent configured....wait...• Get network access.....get permission....wait• Get things done.
  • 6. Status Quo in Operations• What IT Ops provides is not what developers want.• IT is ever more central to the operation of the business.• Ops has used this centrality to erect a fiefdom• Constraint is worse than ever.• People hate interacting with Ops.• Maniacal focus on technology.
  • 7. Status Quo in Operations• Much of IT has become a commodity• People can now easily consume services• Bypassing IT - even on large projects has become a norm• Shadow IT competes with Ops.
  • 8. Cloud is OSSM• On Demand• Self-service• Scalable• Measurable
  • 9. Cloud Service ModelsUSER CLOUD a.k.a. SOFTWARE AS A SERVICESingle application, multi-tenancy, network-based, one-to-manydelivery of applications, all users have same access to features.Examples: Salesforce.com, Google Docs, Red Hat Network/RHELDEVELOPMENT CLOUD a.k.a. PLATFORM-AS-A-SERVICEApplication developer model, Application deployed to an elasticservice that autoscales, low administrative overhead. No conceptof virtual machines or operating system. Code it and deploy it.Examples: VMware CloudFoundry, Google AppEngine, WindowsAzure, Rackspace Sites, Red Hat OpenShift, Active State Stackato,AppfogSYSTEMS CLOUD a.k.a INFRASTRUCTURE-AS-A-SERVICEServers and storage are made available in a scalable way over anetwork.Examples: EC2, Rackspace CloudFiles, OpenStack, ApacheCloudStack, Eucalyptus, OpenNebulaSaaSPaaSIaaS
  • 10. Cloud is an automation enabler●Remove constraints - people empowered to get thingsdone.●Agility●Enforce automated process instead of manual ones.●Why are you doing things manually?
  • 11. DevOps●Create constancy of purpose toward improvement of product and service, with the aim to become competitive, stay in business and toprovide jobs.●Adopt the new philosophy. We are in a new economic age. Western management must awaken to the challenge, must learn theirresponsibilities, and take on leadership for change.●Cease dependence on inspection to achieve quality. Eliminate the need for massive inspection by building quality into the product inthe first place.● Improve constantly and forever the system of production and service, to improve quality and productivity, and thus constantly decreasecosts.● Institute training on the job.● Institute leadership The aim of supervision should be to help people and machines and gadgets do a better job. Supervision ofmanagement is in need of overhaul, as well as supervision of production workers.● Drive out fear, so that everyone may work effectively for the company.● Break down barriers between departments. People in research, design, sales, and production must work as a team, in order to foreseeproblems of production and usage that may be encountered with the product or service.● Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortationsonly create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus liebeyond the power of the work force.– Eliminate work standards (quotas) on the factory floor. Substitute with leadership.– Eliminate management by objective. Eliminate management by numbers and numerical goals. Instead substitute with leadership.– Remove barriers that rob the hourly worker of his right to pride of workmanship. The responsibility of supervisors must be changedfrom sheer numbers to quality.– Remove barriers that rob people in management and in engineering of their right to pride of workmanship. This means, inter alia,abolishment of the annual or merit rating and of management by objectives● Institute a vigorous program of education and self-improvement.● Put everybody in the company to work to accomplish the transformation. The transformation is everybodys job.
  • 12. DevOps● Culture● Automation● Measurement● Sharing– Damon Edwards and John Willis
  • 13. Theory of constraints
  • 14. A look into the future of IT
  • 15. But thats the future if we adapt● Stop building silos and fiefdoms● The focus has to change from controlling and limitingto enabling, and making people more efficient.● We must become partners, with developers, with therest of the business.
  • 16. What if we dont adapt● People will continue to avoid and work around us.● We will become irrelevant● We will become the backup tape changers of ourgeneration.