InfoQ Homepage Infrastructure as Code Content on InfoQ
-
Interview With Luke Kanies on $40 Million Funding of Puppet Labs
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.
-
The Birth of Continuous Delivery and DevOps
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).
-
New Gem Creates Test Boilerplate for Chef Cookbooks
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.
-
FutureOps with Immutable Infrastructures and Built-in Failure Recovery
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.
-
Latest Technology Trends on the Radar
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.
-
S is for Security
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.