Thanks for your response,
No, I don't have ruby shadow installed on the clients.
but is there any other approach to set the password because if i installed
the ruby shadow package then i have to rebuild the rpm and for some
administrative reasons we have to avoid building this RPM again.
On Fri, 29 Jan 2010 06:13:44 -0600, James Cammarata j...@sngx.net wrote:
On Fri, 29 Jan 2010 09:47:05 +0800, Ohad Levy ohadl...@gmail.com wrote:
after a very long discussion about this topic in the past, we internally
decided to have a simple script which checks the yum repo for 32bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You wanted release early, release often and the Puppet team has
delivered!
The 0.25.4 release is a maintenance release (with one important
feature - pre/post transaction hooks - discussed below) in the
0.25.x branch. The release primarily addresses
James Turnbull wrote:
The release is available at:
http://reductivelabs.com/downloads/puppet/puppet-0.25.4.tar.gz
http://reductivelabs.com/downloads/gems/puppet-0.25.4.gem
http://gemcutter.org/gems/puppet
I have packages for Fedora/RHEL/CentOS at:
Thank you Ohad,
you are right, we can obtain the wanted behavior without any sort of
callback.
Using solution 3 we can have a cron job that run puppetca --list and
for each entry it query the cloud API to perform extra checks.
If the checks are OK, it does puppetca --sign .
Puppet client is
On Wed, Jan 27, 2010 at 05:59:27PM +0100, Thomas Bellman wrote:
- Each node has a copy of the entire repository of modules and classes
which makes it in my opinion a security risk.
Don't put passwords and private keys in your manifests.
Would you call this a general rule? If so, what's the
Thanks. That seems to work to set defaults when running standalone.
( I haven't yet tested it running client/server )
It would still be handy if there was a way to pass values from the
commandline.
( After I set servername, the next error was for environment, which I
also now set,
but that
hello,
- steve majewski steve.majew...@gmail.com wrote:
It would still be handy if there was a way to pass values from the
commandline.
export FACTER_foo=bar
you now have $foo in your manifests.
--
You received this message because you are subscribed to the Google Groups
Puppet
Hello,
I'm writing a plugin which make an xml-rpc call that throw an
exception if the foreign call fail (due to a bad fault-structure).
So I catch this exception in my code (I expect it to fail) :
[...]
server = XMLRPC::Client.new( host, /xmlrpc/db, 8069)
begin
result =
Running puppet 0.24.8, I'd like to make Puppet be indifferent/ignore whether a
package is installed or not. The hangup here is that I include a class that
installs the package, so I through to make a class that inherits that and
changes ensure = undef, but this doesn't seem to work. I have
I use the following plugin :
module Puppet::Parser::Functions
newfunction(:getPassword, :type = :rvalue) do |args|
clientHostname = args[0]
type = args[1]
len = args[2]
filename = /var/lib/puppet/passwords/ + clientHostname + - +
type + .pass
def newpass( len )
On Sat, Jan 30, 2010 at 12:23 AM, Peter Meier peter.me...@immerda.chwrote:
On Wed, Jan 27, 2010 at 05:59:27PM +0100, Thomas Bellman wrote:
- Each node has a copy of the entire repository of modules and classes
which makes it in my opinion a security risk.
Don't put passwords and private
Ohad Levy schrieb:
we actually created a simple datastore which is encrypted (reusing
puppet certificates and preshared key) to allow our masters to decrypt
info which is consider confidential.
This sounds interesting. Could you give a code example?
Cheers
Christian
--
Dipl.-Inf. Christian
13 matches
Mail list logo
