HashiCorp have publicly released Atlas, a commercial platform that unites their open source tools for development and operations to create a version control system for infrastructure management. Atlas integrates HashiCorp’s Vagrant, Packer, Terraform, and Consul tooling, with the primary goal of promoting ‘automation, audit and collaboration on infrastructure changes’ across the modern datacenter.
Lindsay Holmwood, Flapjack's creator, offers advice to enable fast, with quality, feedback loops and to support small, discrete changes. Holmwood asserts that to get quality feedback there are five main issues to think about: the CAP theorem; SLA definition; SLA validation; interfaces between services; data and infrastructure immutability.
At the inaugural CoreOS Fest in San Francisco, the CoreOS team announced that the App Container specification (appc) has recently gained support from Google, Apcera, Red Hat and VMware. Google have added support for CoreOS’s appc implementation ‘rkt’ into Kubernetes, and Apcera have created a new implementation of appc, named ‘Kurma’.
At CraftConf 2015, Mitchell Hashimoto argued that current provisioning and configuration tooling is not adequate for orchestrating the ‘modern datacenter’. The modern datacenter is agile and elastic, and ‘services’ may be spread across potentially disparate vendor platforms. Hashimoto introduced Terraform and Consul, which may be used to provide automation in these challenging environments
At QCon London 2015, Dave Farley proposed that although the state of software development has been suboptimal in the past, studies are revealing that the implementation of continuous delivery leads to considerable improvement. Farley stated that continuous delivery changes the economies of software development, and provides more rapid business idea validation and reduced defect rates.
OpenStack specialists Mirantis have announced a joint project with Google to integrate the Kubernetes container management system with the OpenStack project, which will allow Docker containers to be deployed at scale on infrastructure managed by OpenStack.
The Config Management Camp featured a panel with Mitchell Hashimoto, founder of HashiCorp and creator of Terraform, Gareth Rushgrove, senior software engineer at Puppet Labs, and John Keiser, development lead at Chef, discussing creation of infrastructure from code and cloud resources and APIs.
Amazon Web Services (AWS) have released an experimental Go programming language AWS SDK via their AWS Labs Github account, which currently supports 43 AWS services including EC2, S3 and RDS.
Puppet Labs recently closed $40 million funding round. Five investors including VMware, Google Ventures and Cisco want the company invest into talent, technology and global expansion. This fifth round nearly doubles the company’s venture capital to $85.5 million. InfoQ has talked to Luke Kanies about growing his company so fast.
At GOTO Amsterdam 2014 conference, agile coach Dan North shared his experience as part of a build team employed in a client project back in 2005. The team introduced several (technical and cultural) practices that became core tenets of the Continuous Delivery book and of the DevOps movement (for instance bridging the gap between development and ops teams was critical to success in that project).
Meez is a new gem that will help get started with test-driven infrastructure for Chef cookbooks. It creates all the boilerplate necessary to assess a cookbook’s quality using tools such as Test Kitchen, Foodcritic, ChefSpec and others, allowing the user to focus on writing actual tests and infrastructure code.
Mitchell Hashimoto, creator of Vagrant, gave a talk last month at Velocity Conf London about his vision for a “FutureOps” with immutable infrastructures and built-in failure recovery.
Thoughtworks recently released a new installment of their technology radar highlighting techniques enabling infrastructure as code, perimeterless enterprises, applying proven practices to areas without, and lightweight analytics.
Frank Breedijk, security officer at Schuberg Philis, talks about the friction points between security and DevOps and how to collaborate to avoid them. Examples include automating security tests and environments, reducing scope of security audits to relevant system components only or allowing security fixes to jump the queue of changes to production.