How to install DevOps into your organisation?
One of the early performances where Dev and Ops presented how they got the lead time together was when Flickr held their epic presentation at the Velocity conference in San Francisco. Patrick Dubois is usually mentioned as the one who coined the concept of DevOps, which thus is a wordplay of Developer and Operations.
Why, what’s the problem?
The underlying phenomena as DevOps (IAF early) addresses that Dev-side (development) of an IT organization from the business side hears: “Developers give us the news more often, earlier, faster…”
Ops-side (operations) is, in turn from the business side: “The systems must be available 24/7, stable without any interruption.” Thus we have a conflict in how often we want to update our systems: Ops as seldom as possible so we have stable operations, and Dev as often as possible so we can quickly come out with new (or adjusted) functionality.
What is the solution?
The solution is obviously to tear down the wall between departments. Simplified need Dev ensure that what you want to be to zone Ops is good adapted from Ops perspective, and Ops Dev need help with this! Anyone who wants to describe how it looks from side could say “they have automated everything goes, everything is under version control, and before it goes into production, it is already automatically tested”. I.e. installation, smoke testing, set of environments such as OS and third-party, load balancing, backup job … – everything is automated and version controlled. The slightest change in any environment is fully traceable. We cannot afford to let people make computers work!
The challenges are many
The list of obstacles to cross tends not to be short. To automate is not free, especially not the first time. These costs consist of the new tools, new procedures, new errors, and new lessons to be learned. This applies not only Ops without as much Dev. getting them to sit together requires often that management and organization, creating common goals and circumstances. Of course, it should be business drivers that drive the organization towards DevOps – there should be business benefits to be achieved. When it is clearly expressed and becomes concrete down to-day work, work will go toward DevOps culture become much easier.
How do you do it then?
Continuous Integration is now mainstream – there are few development organizations that do not have a building machine running centrally build and test every code check. The next step towards reducing fear during commissioning are getting Continuous delivery in place. How to automate their environments, build their pipelines and testing are naturally highly variable depending on the organization and product. In the course Continuous delivery as we go through an implementation with a single product. We also show a zero-downtime deployment patterns (Blue / Green) with load balancing in the cloud. We use modern tools and no cheating. From 0 to 100 in a few hours, with a complete version controlled environment, product and pipeline!
Learn more about DevOps by participating in the new Tieturi courses DevOps Master Class >>
You cand find more DevOps -courses on tieturi.fi >>
Andrey Adamovich
