Build, Release, Run & Repeat. Enterprises are raving about the agile and perfect fusion between IT Development and IT Operations. The fusion would revolutionize the transition, de-risk IT deployments, eliminate the excuse “but-it-works-on-my-system”, and break the silos between developers, testers, release managers, and system operators.
The Development to Operations (DevOps) promise is Big. It would significantly reduce the outages in live caused by changes introduced; according to estimates, 80% of the outages are due to application changes and/ or new application developments.
But there is a problem. IT vendors have been very quick in providing new products and services under the label “DevOps inside”. However, with the growth in product choices, conflicting definitions and competing services, customers often encounter confusion, while making complex purchase decisions, they are often unsure about how to deploy DevOps and get the most out of the solution.
DevOps is not just a tool set. DevOps includes tools, process and people aspects, with ‘people’ being the critical element of the equation.
DevOps’s main aim is to maximise automation, increased visibility, and tighter control of the pre-production and non-production environments and deployment/promotion of code through diverse environments. It also tries to reduce the “wall of confusion” between development and operations personnel by harmonizing the development and operations tools (allowing feedback from operations to development) as well as re-aligning objectives and incentives.
DevOps People Aspect
This is a prime aspect that garners a lot of attention. A single tool or a combination of tools that allows for a simple or fully automatic deployment. It should be able to create, operate, and destroy any type of pre-production or non-production environments and should include infrastructure related as well as middleware and application related components.
The aim should be to accelerate the transition through environments in an efficient and cost-effective manner. The result would be more testing in an early testing phase leading to higher quality. A number of IaaS tools as well as middleware and applications based process tools are available today.
While Docker, Puppet, Chef, and ControlTier are examples of existing tools, VMWare Codestream is a new entrant. Traditional enterprise vendors provide a host of toolsets. For instance, Microsoft offers Team Foundation Server/Visual Studio Online along with Microsoft System Centre and Azure. They sync with tools like Docker and Chef and also integrate with social media through UserVoice, Azuqua, etc.
Follow Part 2 to follow the topic of DevOps more closely.