We typically use knife bootstrap to work on our VMs but our AWS nodes
self-register at spinup time. Multiple methods aren’t necessarily wrong.
~~ StormeRider ~~
“Every world needs its heroes […] They inspire us to be better than we
are. And they protect from the darkness that’s just around the corner.”
(from Smallville Season 6x1: “Zod”)
On why I hate the phrase “that’s so lame”… http://bit.ly/Ps3uSS
On Wed, Feb 4, 2015 at 12:44 PM, Christine Draper <
I’ll try that - was really hoping for something that came with ChefDK.
I guess this isnt a mainstream scenario? It seemed natural to want to
use one approach for both pre-provisioned and to-be-provisioned machines.
On Wed, Feb 4, 2015 at 1:15 PM, Peter Burkholder firstname.lastname@example.org
I’m taking a stab here, but SSH with
On Wed, Feb 4, 2015 at 8:22 AM, Christine Draper <
I’d like to be able to bootstrap an arbitrary existing machine with a
chef-provisioning recipe (replacing knife bootstrap). I know I can used
’chef_node’ to set node attributes (but this wont do a bootstrap), and I
can use ‘machine’ with ‘converge_only’ to do convergence (but this requires
specifying a specific driver like vagrant or aws). Is there a way to do
what I want?
Peter Burkholder — Customer Success Engineer
Availability: no travel/OOO scheduled
301-204-5767 – email@example.com – *my: *Linkedin
chef.io http://www.chef.io/ Blog http://www.chef.io/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef