loading...

A Well-defined Path To DevOps Success

pavanbelagatti profile image Pavan Belagatti ・2 min read

The article is originally published on DevOpsCube

Enterprises are going through a digital transformation and for years and years delivering software is being a bit of a challenge, we see a lot of friction and because of this, a lot of firms have tried to be agile but everybody has adapted to agile in a local fashion. If you take a look at the total lifecycle of how an application goes from a developer’s machine all the way into a production server, and then to the end customer, that entire workflow is anything but Agile.

Since from many years, organizations have struggled to adopt Agile and become Agile.

DevOps is here to the rescue.

A systematic map on how to achieve DevOps success

DevOps success

You must always remember, zero-touch automation is the goal, that doesn’t mean that you have to be deploying straight to production but if you want to do it, you should be able to do it. It should be so easy that even an operation guy can do it with just a push of a button and not going SSH’ing bunch of servers.

DevOps is broken into 4 different blocks,

1. Provisioning

2. Build, CI and Packaging

3. Testing

4. Release and Deploy

Along with 4 stages, this has to go through all environments as shown in the image.

The goal here should be moving the automation in your organization as far to the right as possible.

DevOps key pillars

The automation is built on these 4 core pillars,

  1. Job run-time: All your complete enterprise should be using a common image format, or a common image on which all your applications are getting built. This pillar is more of a making sure of packaging & what versions to be installed across the enterprise.

  2. State: Just running a particular task is not enough, you need to know what are all the other tasks are running, when was it last run, stable version, artifacts like IP addresses in automation, docker container tags etc all of these things should be systemically available.

  3. Visibility: You need to know how entire workflow is going on and not required to go to each thing to get the idea. You need to be able to see everything in a single pane. This helps visually get an overview of your application automation process & status.

  4. Operations: This is more of explaining how do you do deployments, how do you do scale etc

This DevOps automation process is very well explained practically by Shippable CEO, Avi Cavale in his Webinar

Start figuring out the critical processes you can automate and do DevOps the right way to succeed big.

Posted on Jan 3 by:

Discussion

markdown guide
 

What doesn't make sense to me is the coupling with agile here. DevOps is just bringing a documented, visible process, using a few Tools usually on the Engineering side of things.

Visibility and automation are probably the key concepts here, the rest is implementation detail.