Having the same problem as quoted below. I'm even using autosign for the
time-being while trying to solve this. Leej, did you solve this?
notice: Waiting for SSH response ... Done
notice: Installing Puppet ...
notice: Puppet is now installed on:
blahblah.eu-west-1.compute.amazonaws.com
On Tuesday, 3 July 2012 02:28:28 UTC+5:30, Leej wrote:
*Hello, new user here. I'm trying to bootstrap an aws instance and need
to change the server setting in puppet.conf on the client/instance that is
created. Is there anyway to do this beyond modifying hosts post-hoc?*
You can create a
Here's another option for people who are not using Puppet Cloud
Provisioner, but for example EC2's autoscaling or launching test-instances
by hand.:
Ubuntu and Amazon Linux images include a tool called CloudInit, which makes
it easy to perform bootstrapping tasks on a new instance. It's built
Hi Lee,
I am also new with Puppet, and I am facing the same problem.
Did you get how to solve it? I am starting to feel that I am hitting a
wall...
Thanks,
On Tuesday, July 3, 2012 3:12:38 PM UTC+2, Leej wrote:
So I've cracked the initial problem and I can deploy an instance and auto
So I've cracked the initial problem and I can deploy an instance and auto
configure puppet but I am still missing something, possibly a conceptual
misunderstanding on my part.
I spin up an aws instance with :
puppet node_aws bootstrap --image ami-e1e8d395 --keyname puppet --login
ubuntu
And 5 minutes later I read the man page
docs.puppetlabs.com/pe/2.0/cloudprovisioner_man_node_aws.html *Note that
any configuration parameter that's valid in the configuration file is also
a valid long argument, although it may or may not be relevant to the
present action. For example, server
