Win a copy of Node.js Design Patterns: Design and implement production-grade Node.js applications using proven patterns and techniques this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Pipeline as Code: are Puppet and Chef passe now?

 
Marshal
Posts: 16598
278
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I noticed Packer and Terraform mentioned in the book's description as infrastructure-as-code tools. I'm curious why those tools and whether Puppet and Chef would be supplanted by these or are they still relevant in some way. What do Packer and Terraform have over Puppet, Chef, and other IaC tools?
 
Saloon Keeper
Posts: 24334
167
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Packer and Terraform are VM generation tools. You'd primarily use them to create the base VM images. Terraform, as I recall, gets progressively more cumbersome as you get to finer-grained provisioning. Packer commonly uses Ansible to provision, but I'm pretty sure that it can also use Puppet and Salt as well - it just has to install their respective clients first.

I'm not as gung-ho on Puppet as I used to be, because it's the equivalent of creating an Enterprise Java app versus hacking out small, simple stuff (Ansible). But I do use Puppet for my complex server configurations, even though I typically use Ansible to pre-provision (install Puppet, networking and the like). My container-based stuff isn't really the kind of thing that Puppet is designed to maintain, so the container VMs are strict Ansible provisioning - even the part that installed the container with the PuppetMaster in itself . I use Ansible to install and configure the containers.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic