Over a million developers have joined DZone.
Platinum Partner

Consuming Chef API from Any Script - Part 1

· DevOps Zone

The DevOps Zone is brought to you in partnership with New Relic. Improving the performance of your app is easy with New Relic's SaaS-based monitoring.

Its been more than a year since we have adopted Chef for ThoughtWorks. We use Chef not only for configuration management but also for provisioning instances.  Since most of our infrastructure is automated many of the services needs to integrate with chef programmatically.

Knife, the command line interface of chef provides easy integration via knife plugin and Knife exec. But in this post I’ll showcase how Chef can be used from any script if you have an API client configured. At bare minimum we need to set three parameters to get our script talking to a Chef server, these are Chef server url, node_name and client key. Once configured we can use Chef API to interact with chef server. Lets start with enlisting the number of nodes

require 'rubygems'
require 'chef'  

Chef::Config[:client_key]='path to client cert.pem'
Chef::Config[:chef_server_url]="http://ur chef server:4000"     

Chef::Node.list.each do |node|  
    puts node.first      

The DevOps Zone is brought to you in partnership with New Relic. Know exactly where and when bottlenecks are occurring within your application frameworks with New Relic APM.


Published at DZone with permission of Ranjib Dey , DZone MVB .

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}