[Puppet Users] Downgrading RubyGems using Package provider => gem

2011-07-08 Thread Ryan Conway
Hey everyone, I'm experiencing an issue resulting from the way RubyGems works when dealing with multiple gem versions. When managing a gem through the Package provider, setting ensure to a version lower than a currently installed version will result in Puppet installing the older version, however

[Puppet Users] Re: Using with EC2 (and auto-scaling)

2011-07-22 Thread Ryan Conway
The approach I've used is similar - automatically sign new CSRs so that new nodes can be added without human interaction. In order to then apply a configuration to the node, the hostnames for my machines all conform to a pattern, which I then match against a regular expression in the node manifest

[Puppet Users] Re: add ip address of another EC2 instance automatically in the hosts file of existing EC2 instance

2011-08-01 Thread Ryan Conway
You can indeed use Exported resources. See the first example in this documentation: http://docs.puppetlabs.com/guides/exported_resources.html The example shows how to have every host export its SSH public key, and then collect every host’s key and install it in the ssh_known_hosts file (which is

[Puppet Users] Re: Step by step guide to setting user passwords

2011-08-03 Thread Ryan Conway
One more thing - Puppet will fail to set the password unless the libshadow gem is present, as this is required to work with shadow passwords. The failures due to this being missing weren't obvious if I remember back - you only get a warning that the user provider isn't able to manage the passwords