Looks like this is a some problem with ruby/dependencies
[root@ndb2r0 ~]# cat 1.rb
#!/usr/bin/ruby
#
require 'digest/sha1'
require 'base64'
require 'digest/sha2'
puts Digest::SHA256.hexdigest(123)
[root@ndb2r0 ~]# ruby 1.rb
Illegal instruction
But this version looks good:
[root@ndb2r0 ~]# cat
I have a puppet module that configures samba3 with network shares and adds
samba users. If the server crashes and I configure a new server with
puppet, the samba User SID of the users will be different and I suspect all
users will get another profile on their windows client. I think I will have
Hello,
Out of a large-ish estate of systems I want only some of those systems to
send reports elsewhere to be processed by Foreman/Dashboard etc. Whilst the
others carry on sending their reports to the general puppet master.
Is this possible from the client side using reportserver = option and
Hi
I am very new to puppet and wants to implement something like this in my
puppet template (erb file)
the logic i am trying to do is :
sssd_count=`rpm -qa | grep 'sssd' | wc -l`
% if sssd_count =2 -%
session optional sss.so
% else %
session optional pam_ldap.so
% end -%
I am very new to puppet and wants to implement something like this in my
puppet template (erb file)
the logic i am trying to do is :
sssd_count=`rpm -qa | grep 'sssd' | wc -l`
% if sssd_count =2 -%
session optional sss.so
% else %
session optional pam_ldap.so
% end
Forgot to enable email notification here. Decided to go back to 3.1.1 a
week ago. Will upgrade again to provide more specific load information. Thx!
You have to be a little bit more specific. Is load only CPU related, or
I/O? Also, what do the log say? 3.2 pushes lots of notices about syntax
Hi all,
I'm testing puppet as my new deployment manager.
I need to create a manifest that does the following on Windows servers:
1. Changes a registry key - I'm using the puppet-registry module
2. Sleeps for an hour - I've been trying to use the sleep module with no
success
3. Stops a certain
Hello puppet-users,
Puppet Enterprise 3.0 is now available now. You can download it now here:
http://puppetlabs.com/misc/pe-files/
This major release introduces the following new capabilities:
* Enhanced performance and scalability: 200% performance boost and 100%
increase in scalability helps
I'm going to heartily +1 this.
Ideally, we would be able to specify only those facts that we know we need
and have the ability to blacklist facts that are harmful to our systems.
Also, custom facts that are removed from the server should be purged from
the clients and server cache at the next
Hi,
this does look potentially helpful. Thanks for sharing!
On 06/24/2013 03:26 PM, Jens Braeuer wrote:
Hi everyone,
In my environment, we heavily rely on Hiera to parametrize our modules.
Like the Puppet code, I would like to version-control the Hiera .yaml
files. However committing
Hello List,
I´ve tried to switch from md5 checksum to md5lite within all my
configuration to spare a few cpu cycles on my master,
but it didn´t work at all :-(
Then I´ve found out about bug #13199, but the bugs lists only 2.7x as
affected.
can anybody confirm this issue on 3.x?
funny that
On 24/06/13 12:22, David Sandilands wrote:
We are working on a replacing our current build set by ksh scripts with
puppet manifests and I'm having some difficulty setting umask in
/etc/sysconfig/init for RHEL 6
Ideally I would like to just do
augeas { 'augsysconfiginitumask':
Given the manifest:
$a = 1
$b = 1 + 0
$c = 1.1
$d = 1.1 + 0
$result = inline_template(
a %= @a.class % %= @a %
b %= @b.class % %= @b %
c %= @c.class % %= @c %
d %= @d.class % %= @d %
)
notify {
$result:
}
The output is:
a String 1
b Fixnum 1
c String 1.1
d Float 1.1
I forgot to clarify that this was tested on versions 3.2.1 and 3.2.2.
On Tuesday, June 25, 2013 1:06:21 PM UTC-3, Claudio wrote:
Given the manifest:
$a = 1
$b = 1 + 0
$c = 1.1
$d = 1.1 + 0
$result = inline_template(
a %= @a.class % %= @a %
b %= @b.class % %= @b %
c %= @c.class % %= @c
Is it possible to tell facter to ignore certain facts? Couldn't find a
config file for it and not sure how puppet tells it to gather facts.
There's no configuration right now. I think you have a pretty reasonable
case, and you should file a feature request at
Hi Everyone;
I was wondering if anyone has created ot knows of a module that can be used
to assign static IP addresses to hosts post build. The addresses will be
static but, need to be assigned based on MAC address.
Essentially, we have a file with a list of hostnames/mac addresses. I need
to
You are describing DHCP reservations .
That would be something to do with a DHCP server, not necessarily with Puppet
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin Hobbes)
-
Yes, but we will not be able to use DHCP in this case. This is why I was
aksing if anyone had any suggesting for leveraging Puppet to do this
On Tue, Jun 25, 2013 at 2:30 PM, Dan White y...@comcast.net wrote:
You are describing DHCP reservations.
That would be something to do with a DHCP
I can think of several ways puppet can do this, I was just wondering if the
group might have any ideas/suggestions as to best approaches. Obviously,
we are unable to use DHCP in this particular case, or we would.
On Tue, Jun 25, 2013 at 2:30 PM, Dan White y...@comcast.net wrote:
You are
Wouldn't you want to do this on the provisioning side?
---
Jerald M. Sheets jr.
On Tue, Jun 25, 2013 at 3:04 PM, Worker Bee beeworke...@gmail.com wrote:
Yes, but we will not be able to use DHCP in this case. This is why I was
aksing if anyone had any suggesting for leveraging Puppet to do
Thanks, Ken. It will be a secondary interface and it will 'hopefully' be a
one-time fix.
I appreciate the feedback and will take a look at this!
Jerald; you are absolutely right, this should be a provisioning task but,
we I have an OPS team who needs to make a one-tme correction on exisiting
I have been watching this thread grow and metastasize and I would like to offer
my opinions:
The wonderful thing about standards is that there are so many of them to
choose from. Grace Hopper (maybe)
There are at least two very different directions to approach this from, IMHO.
The first is
On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote:
On Monday, June 24, 2013 9:12:17 AM UTC-5, Alessandro Franceschi wrote:
On Monday, June 24, 2013 3:57:55 PM UTC+2, jcbollinger wrote:
None of my modules have any parameterized classes, but I am not at
liberty to publish
If you are managing sssd* package(s) via puppet, you can try this:
module.pp -
if defined(Package['sssd']) and defined(Package['sssdxx'])
{
$session_variable = sss.so
}
else
{
$session_variable = pam_ldap.so
}
template.erb -
session optional %= session_variable -%
-
On Tue,
On Tuesday, June 25, 2013 10:10:13 PM UTC+2, Ygor wrote:
I have been watching this thread grow and metastasize and I would like to
offer my opinions:
The wonderful thing about standards is that there are so many of them to
choose from. Grace Hopper (maybe)
There are at least two very
On Tuesday, June 25, 2013 11:49:49 PM UTC+2, Alessandro Franceschi wrote:
On Tuesday, June 25, 2013 9:16:20 PM UTC+2, jcbollinger wrote:
On Monday, June 24, 2013 9:12:17 AM UTC-5, Alessandro Franceschi wrote:
On Monday, June 24, 2013 3:57:55 PM UTC+2, jcbollinger wrote:
None of my
Hey Gang,
I've been asked to explore the landscape of network device management via
puppet.
in particular, I'm looking to support cisco, and force10 switches.
I know about the network device system, I'm wondering if that's the way to
go for both cisco and force10, or if there's a better way for
27 matches
Mail list logo
