I have seen many DevOps initiatives at various levels of maturity. One common pattern in successful ones is that they have made progress in automating the build process or the provisioning of environments. Both of these accomplishments are necessary and worthy of focus, but the efforts don’t stop there. The following is a list of things to consider that can take your DevOps initiative to the next level.
DevOps is gaining serious momentum within enterprises as of late. The big business driver is the pursuit of agility and improved reliability and quality. Adopting DevOps can be challenging because it often requires drastic changes in culture, process, and technology. Those companies that have had success with DevOps often discover some hidden benefits that they may not have anticipated when they started their journey.
HashiCorp, a San Francisco–based start-up founded in 2012, has recently released its first commercial product, called Atlas. HashiCorp is known by many people as the creator of a number of open-source tools that assist in developing, deploying, and maintaining applications. One major challenge for IT shops is that so many tools are required to automate the building and delivery of software that engineers spend far too much time trying to tie all of these tools together, which takes away time from working on business requests. In many shops, one or more people may be dedicated to managing the complexities of the DevOps tool chain, which includes integration, patching, upgrading, and many other non–value added tasks. With Atlas, engineers can leverage a single tool for managing infrastructure and builds with a common workflow and a central dashboard.
HashiCorp takes a page from the Atlassian playbook. Atlassian focuses on integrating a collection of open-source tools for agile development, such as JIRA, Confluence, HipChat, and others. HashiCorp brings together a collection of open-source tools to aid in the delivery and management of applications and infrastructure. Atlas is made up of five major functions, as represented in the following image:
Vagrant, Packer, Terraform, and Consul are all open-source projects that you can download and use for free today. Atlas provides a common platform that makes all of these open-source solutions work together seamlessly and is delivered as SaaS. In addition, Atlas handles the integrations with various CI/CD tools (Maven, Jenkins, etc.), containers and VMs (Docker, VMware, VirtualBox, and eventually Rocket), version control (GitHub and Bitbucket), configuration management (Chef, Puppet, Ansible, and Salt), public cloud providers (AWS, Google, Rackspace and Azure), and private cloud providers (OpenStack and SoftLayer). Doing these integrations yourself would require a significant amount of time and money, and it would be a never-ending task to keep everything current. Atlas provides these capabilities out of the box and will continue to add integrations as the demand for new tools arises.
Many organizations live in a multicloud world. I have seen where engineers have written thousands upon thousands of lines of code in Chef or Puppet, trying to manage the many permutations of cloud endpoints, applications stacks, and containers and VMs. Tools like Atlas to allow you to build a common workflow that can deliver a Docker container to AWS in the same way in which you could deliver a VM to a private cloud without major development. The goal of Atlas is to simplify the process of getting code from development to production by making infrastructure management and application delivery easier.
The company also announced $10 million in Series A funding from Mayfield, GGV Capital, and True Ventures.
I am starting to get annoyed with the direction of all the DevOps discussions that fly across my Twitter feed each day. I think people are focusing way too much on culture and not taking a pragmatic approach to solving business problems. I’ll be the first to admit that embracing the DevOps movement can be transformational and in some cases a major culture shock to large organizations. But there is much more to DevOps than culture.
DevOps and ITIL are like oil and water to many pundits. Some people hold that the two cannot coexist in today’s modern-day IT shops, advising companies to move away from ITIL as they start embracing the DevOps movement. I argued against this recommendation in a post called Unicorns, Horses, ITIL, and Enterprise DevOps. Continue reading DevOps and ITIL Revisited
“DevOps” is one of those buzzwords that means everything and nothing at the same time. It is like the words “cloud,” “architecture,” and “Internet of Things”—terms so vague they lead to endless debates between IT people. DevOps seems to take this verbal sparring to a new level. On top of arguing over what it means, people also debate the proper method for delivering DevOps. Notice that “method” is singular, as if there were only one way to do it.
Join my Circle on Google+
Plugin by Social Author Bio