cloud-test: Using Chef to Automate Google Compute Engine

Google Cloud Platform Blog

Using Chef to Automate Google Compute Engine

Monday, April 14, 2014

recently publishedChef is betting on Compute Enginecoded businessWhy customers love using Chef and Google Compute EngineCloud-based delivery“Prior to deploying Hosted Chef,” said Meyer, “we did everything manually. It generally took me a couple of weeks to get access to the servers I needed and at least a day to add a new developer. With Chef, I can now add a couple of developers within 20 minutes. Additionally, when we set up a new ad serving system with data bags, the set-up time goes from two to three days to an hour. This is simply one of those tools that you need regardless of what your environment is.” Speed & ScaleFlexibility Community featured partner at this year’s ChefConfChef and Compute Engine: Under the Hoodobtained a Compute Engine accounChef workstationknife-google plugingem install knife-google
knife google setupknife'gcutil'Cloud SDK

knife google server create jenkins1 -Z us-central1-a -m n1-highcpu-2 -I centos-6-v20140415 -r 'java,jenkins::master' -x $USER -i $HOME/.ssh/google_compute_engine

Creates a CentOS VM instance in Compute Engine's us-central1-a zone with machine type n1-highcpu-2

Registers it as a node named ‘jenkins1’ with the Chef Server

Configures the node’s run_list attribute as ‘java,jenkins::master’

Uses the ssh protocol to run chef-client with that ‘master’ recipe from the Jenkins community cookbook on the new system.

Chef Client finished, 19/21 resources updated in 40.207903203 secondssearch# Commands like this destroy unneeded nodes
knife google server delete tester1 -y --purgeGCE page