Comments on: Expanding DevOps With Infrastructure As Code https://www.nextplatform.com/2022/04/11/expanding-devops-with-infrastructure-as-code/ In-depth coverage of high-end computing at large enterprises, supercomputing centers, hyperscale data centers, and public clouds. Mon, 25 Apr 2022 21:54:28 +0000 hourly 1 https://wordpress.org/?v=6.5.5 By: Timothy Prickett Morgan https://www.nextplatform.com/2022/04/11/expanding-devops-with-infrastructure-as-code/#comment-188989 Sat, 23 Apr 2022 11:44:05 +0000 https://www.nextplatform.com/?p=140433#comment-188989 In reply to Brad Appleton.

Fair points all, and we have covered all of these vendors. But the expansion I spoke of was that of Perforce, which had version control and development tools but nothing like Chef or Puppet.

]]> By: Brad Appleton https://www.nextplatform.com/2022/04/11/expanding-devops-with-infrastructure-as-code/#comment-188963 Fri, 22 Apr 2022 20:40:12 +0000 https://www.nextplatform.com/?p=140433#comment-188963 IaC isn’t an expansion of DevOps. It is arguably the foundation of DevOps, starting with the ‘Agile Infrastructure’ (which later was called Infrastructure as Code).

See same titled papers by DevOps co-creators Andrew Clay Shafer and Patrick Debois, at Velocity2008, Velocity2009 & Agile2009.

Also … Chef & Puppet came about an 2005, based on Ruby. But then first such IaC tool was Mark Burgess’ CFEngine, which came out in ’93, and was the inspiration for Chef & Puppet, especially with Ruby-ish syntax instead of CFEngine’s Perl-ish syntax (there was also a Python-based IaC tool inspired by CFEngine that predates Chef & Puppet)

]]>