On Fri, Nov 25, 2011 at 08:53:43AM +0100, Kenneth Holter wrote:
Hi all,
When our LDAP users log into a server for the first time, PAM creates
their home directory. We use Puppet to define which groups of users
(i.e. LDAP groups) than may log into the server, by setting a
parameter
Hi Greg,
There are some problems with SSL and ruby 1.9.2. Please visit the
link below for solving the issue.
http://urgetopunt.com/puppet/2011/09/14/puppet-ruby19.html
Hope it helps.
Regards,
Kevin
On Nov 24, 12:56 pm, Greg Sutcliffe greg.sutcli...@gmail.com wrote:
Hi all,
I'm having
On 25 November 2011 12:18, linuxbsdfreak linuxbsdfr...@gmail.com wrote:
Hi Greg,
There are some problems with SSL and ruby 1.9.2. Please visit the
link below for solving the issue.
http://urgetopunt.com/puppet/2011/09/14/puppet-ruby19.html
Hi Kevin,
Thanks for the reply. As I stated in my
Hi,
difficult problem. I've made an (anti-)pattern for server-side
concatenation, but so far I haven't found an *easy* way to do it with
puppet.
In your case, you may find it easier to just use variables. Please don't
use node inheritance (or, in you use case, class inheritance, either).
class
Hi,
we want to install the ruby-gem package on a Debian system using puppet.
package { 'ruby1.9.1': ensure = present }
In another manifest we want to use the gem provider to install a ruby gem.
package { 'bundler': ensure = present, provider = gem }
On the first run the puppet
I came across a similar chicken/egg scenario when I was writing a
custom package provider which needed to leverage a gem that I knew did
not exist on the system. Here's how I solved it in my provider:
def gem_dependency(name, package =
nil)
raise Puppet::Error, Required 'name' argument must
I believe this is covered in Feature #6907, which has had a bit of
activity of late so may be coming soon. Feel free to Watch the issue
for it to gain priority.
On 25/11/11 14:21, Martin Alfke wrote:
Hi,
we want to install the ruby-gem package on a Debian system using puppet.
package
Looking into deploying puppet in work environment only thing which i
am trying to work out is a good directory structure which we can use
and then commit changes into subversion (cant use git need to use our
existing source control system).
To make things complicated we have multiple data
Hi all,
Just signed onto the mailing lists, so apologies if this has already
been addressed, but can't seem to find much relevant content online.
We're just in the process of upgrading some of our test systems (server
agent) from 2.6.4 to 2.7.5 - and we're experiencing some odd behaviour
Hi All,
I've started with Puppet recently. So maybe it is a simple problem, but
could not find out up to now the solution. I just want to print out the
debug/log message in client report.
The only way I found is to use notify for this purpose like:
class repo {
notify {The log message:}
}
On Fri, Nov 25, 2011 at 4:03 AM, Jasper Hargreaves
jasper.hargrea...@m-w.co.uk wrote:
Hi all,
Just signed onto the mailing lists, so apologies if this has already been
addressed, but can't seem to find much relevant content online.
We're just in the process of upgrading some of our test
I have this module with the following structure.
adminscripts
├── facter
├── files
│ └── getVPSNodes.pl
├── lib
│ └── puppet
│ ├── parser
│ ├── provider
│ └── type
├── manifests
│ ├── classes
│ ├── defines
│ ├── getvpsnodes.pp
│ └── init.pp
└── templates
The file
Hello,
First of all thanks for such a great software and that too for no
cost.
I'm describing the problem below along with my Environment Details:
1. LDAP: openDS
2. Puppet: Version 2.7.3 (Both clients and servers)
3. Certificates being used: Signed by cacert.org
4. Node Definitions: in openDS
5.
On Fri, Nov 25, 2011 at 11:59 AM, Peter Berghold salty.cowd...@gmail.comwrote:
I have this module with the following structure.
adminscripts
├── facter
├── files
│ └── getVPSNodes.pl
├── lib
│ └── puppet
│ ├── parser
│ ├── provider
│ └── type
├── manifests
│
On Fri, Nov 25, 2011 at 3:32 PM, Nigel Kersten ni...@puppetlabs.com wrote:
As an aside, this was an awesome way to post a module autoload problem
Peter, showing the filesystem layout and the manifest content.
the tree command is a beautiful thing! :-D
Do you perhaps have another
Hi,
The following will fail wont it? The source path is wrong.
source = puppet://puppet/syscripts/getVPSNodes.pl,
I can't check the class myself but do the .pp files parse correctly? Use the
--parseonly or the validate command to check. It maybe failing to parse one of
the files.
Cheers,
- Original Message -
As an aside, this was an awesome way to post a module autoload
problem Peter, showing the filesystem layout and the manifest
content.
the tree command is a beautiful thing! :-D
seconded, good information up front makes it all easier.
I couldn't spot
ran and got:
puppet --debug -v --parseonly init.pp
debug: importing
'/home/peter/src2/puppet-cfg/modules/adminscripts/manifests/getvpsnodes.pp'
debug: importing
'/home/peter/src2/puppet-cfg/modules/adminscripts/manifests/init.pp'
On Fri, Nov 25, 2011 at 3:45 PM, Denmat tu2bg...@gmail.com wrote:
On Fri, Nov 25, 2011 at 12:03:05PM +, Jasper Hargreaves wrote:
Hi all,
Just signed onto the mailing lists, so apologies if this has already
been addressed, but can't seem to find much relevant content online.
We're just in the process of upgrading some of our test systems (server
OK: ran the master in verbose debug mode and the behavior changed. (!)
Seems the real problem was some stuff in the earlier stages (just updated
my puppet master the other day) was and the messages were masking the
problem.
I had some statements in my templates.pp file such as
class {
I take that back. Seems I was running the wrong master. Started running
the proper master and the problem is back:
Here is what I'm seeing in the logged output:
debug: importing '/etc/puppet/modules/adminscripts/manifests/init.pp' in
environment production
debug: importing
Hi,
I don't use ldap myself so I may be of limited value.
First it would also useful to confirm that ldap works as expected over ssl by
performing a ldapsearch -vx -ZZ whatever you need to test your search from
your puppetmaster using the credentials you need.
It would also be good to see the
On Fri, Nov 25, 2011 at 12:46 PM, Peter Berghold salty.cowd...@gmail.comwrote:
On Fri, Nov 25, 2011 at 3:32 PM, Nigel Kersten ni...@puppetlabs.comwrote:
As an aside, this was an awesome way to post a module autoload problem
Peter, showing the filesystem layout and the manifest content.
class foo { ... } - modulepath/foo/manifests/init.pp
class foo::bar { ... } - modulepath/foo/manifests/bar.pp
and then you should be able to remove all the import *.pp statements.
There's been a bit of grief expressed over this bug, so I'd like to
reiterate that this wasn't a deliberate
24 matches
Mail list logo
