In our last article we discussed how to smartly select a pilot project to prove out the benefits of a DevOps organization. As you begin to put your DevOps adoption plan in place, one thing that should be included -- regardless of the project chosen -- is a Landing Zone. As you transition from a traditional Development - IT Operations framework, the Landing Zone is important as it provides needed efficiency, standardization, and governance.
Automation. It’s a word that can mean so many things depending on your context. For CIOs looking to spearhead their organization’s digital transformation, it increasingly means creating agility for their organizations through IT process automation. The implications of this are vast for enterprises, as automation touches everything from technology, to IT processes and even the corporate culture. As a result, Flux7 CEO, Dr. Aater Suleman, has written a paper discussing how CIOs can use automation to be the driving force behind tomorrow’s innovation engine.Download it here or read on for highlights from his piece.
We embrace the transformative opportunities DevOps provides and when coupled with agile practices, enables us and our customers to move quickly and drive innovation. One of the ways our team embodies agility is through remote service delivery. While this practice runs counter to how consultants have traditionally worked, we are often asked about the advantages of remote delivery and thought we’d share today the upsides of this approach and how it supports the agile DevOps model.
Continuous Delivery (CD) is a core facet of successful DevOps and as a result, a core Flux7 strategy for implementing DevOps-based IT modernization. At Flux7, we always view DevOps as streamlining the delivery of not just Code but also the delivery of Infrastructure (networking, firewalls, VMs), Server Configuration (software packages such as Apache or JAVA), and Security Rules (policies for AWS Config Rules or HashiCorp Vault). Among these, efficient delivery of infrastructure and configuration are both very critical for full stack agility. For our customers in AWS, our typical choice for infrastructure delivery is CloudFormation. We like AWS CloudFormation because it is native to AWS, follows a simple YAML or JSON syntax, and has deep integration with other AWS Services such as the AWS Service Catalog.
In the last post of this series, we discussed Docker Remote API and explored the commands specific to containers. In this post, let’s discuss commands specific to images.