DevOps and Automation

DevOps and Automation

The nice part of this time off season is that you will get time to read and research. You can take a step back and try to update your knowledge without the interruption of operational issues.

And in my posts about DevOps I have covered Culture, so the next topic in line should be based on CA(L)MS, Automation.

 

When I look at DASA (DevOps Agile Skills Association) states that you should automate everything you can. An interesting statement, but in the glossary automation is not described. If you look into more detail of the principle DASA gives two major automation areas:

·        The software development process

·        The infrastructure landscape.

The nice part is that this is in line with the following article from Lwakatare and others. They work with DevOps dimensions and deliver practices for those patterns. In the article they describe Infrastructure and deployment process automation.

 

Another article about DevOps that actually helped me towards a better understanding of automation and the use was the following article, Toward unified DevOps model. The nice part is that this article tries to set a model for DevOps. The do not state dimensions and their practices but model DevOps in three sub-models:

·        Application and data model, the what

·        Workflow execution model, the how

·        Infrastructure model, the where.

And in their workflow execution model they incorporate continuous delivery, so the automation of software development. In their infrastructure model the struck me with the reuse of the infrastructure optimization model. And the nice part is that they added a 6th maturity level which links back to infrastructure as code. And with all of the information already created on the infrastructure optimization model, we have a lot of material available to guide us in maturing the use of infrastructure.

This information in combination with all of the publications on continuous delivery can help us in automate everything, and therefore support one the pillars/dimensions of DevOps.

 

 

Used articles:

DASA: Automate everything you can

Toward Unified DevOps model

an exploratory study of DevOps extending the dimensions of DevOps with practices

To view or add a comment, sign in

More articles by Anne Plancius

  • DevOps and anarchism

    Browsing over my timeline, I got triggered to the following statement: For our first hypothesis, we discovered that…

    1 Comment
  • DevOps: Learn from others

    Interesting to read in my feed on Devops currently a discussion about DevOps and Root Cause Analysis. And I see people…

  • DevOps, a different perspective

    In my search towards knowledge about DevOps I came across an interesting article with a for me completely different…

  • What is a DevOps culture?

    Last week I spent time in a DevOps fundamentals class leading towards the DevOps Fundamentals exam of DASA and in the…

    1 Comment
  • DevOps and Hammer

    In a constant search towards knowledge I came across this video of Dean Leffingwell on value streams. During the video…

    1 Comment
  • The impact of DevOps

    Last week I was in a session where EMA presented this report: https://www.enterprisemanagement.

  • To document or not to document

    Interesting to read finally Dr. Royce his original article, “Managing the development of large software systems”.

  • DevOps a definition please?

    A new year has started, and last year we saw a lot predictions on the trends in IT. And in those predictions DevOps was…

  • DevOps or OpsDev

    In the last weeks I see a lot of posts about the label that we have placed upon the change in IT, called DevOps. And a…

    2 Comments
  • Rules and creativity

    In preparation for this event I read the following book team of teams and I have to speak there about agile leadership…

Others also viewed

Explore content categories