similar to: puppetlabs-ntp template discussion

Hi, I have been fighting this issue without success for several days. I am sure some of you have dealt with something similar: I have 2 manifest one for vim which works like a charm : class vim { if $operatingsystem == "Debian" { package {"vim": ensure => present, } package

I''m trying to get rspec-puppet working and have run into a problem. I have a VM running ubuntu lucid, have installed rubygems 1.3.5 from the apt package and have install rspec-puppet (and other required gems), and rake, using gem install. I''ve run rspec-puppet-init in the module I want to test, and have created a very basic spec file for one of the classes in my module.

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Hello! Now that we''re two weeks in it''s time for another update on what''s been going on in the module team. We focused on puppetlabs-ntp and puppetlabs-firewall as our two primary modules, but also merged in fixes to passenger, rabbitmq, mysql, apt, and apache. As a result of this work we''ve released: http://forge.puppetlabs.com/puppetlabs/apache/0.7.0

Hi, I''m not a total newbie with puppet, but I only use it for a few things and I''m not even using modules yet, mostly because I only deploy configuration files for now. I have a configuration for NTP that looks like this: class ntpd { package { "ntp": ensure => installed, } file { "/etc/ntp.conf": owner => root,

So, I''ve been looking into the params pattern for writing modules, ie. having a params.pp file that init.pp inherits from as a place to use custom logic to set variables, and it seems very useful. I do have one question that I''m hoping someone can answer. If, for example, I look at an example42 module, everything is in params.pp. On the other hand, looking at, say,

Hi, I have just started to use Foreman 1.1. I have been using Puppet for a while and have some custom modules and ones that have been dragged down from git etc. I am using nodes.pp in Puppet to assign classes and template entries to hosts. So is Foreman meant to eliminate my need for a nodes.pp? How do I manage my erb templates in Puppet without a nodes.pp? Thanks, -- You received

We need to refer to common variables across multiple modules. For example, our dns module, firewall module and monitoring module need knowledge of our radius server IP address. Is the correct approach to create a ''common'' class where these variables are defined and then reference them from each module and create a class dependancy as below. We are using a custom ENC which

hello, Till now hiera-puppet was the only way I know that allowed hiera data to be loaded from inside a module. The problem with this was that it was still subject to the site specific hierarchy which means a module author had a pretty hard time to store his data in a proper way in his module thus perpetuating the use of the params classes pattern. Now that Puppet 3 is out and it''s gem

Trying to figure out the erwbgy/system plugin and just getting stuck.. first run it did some changes, but it ignored parameters for ntp and now its not refreshing if I update the yaml at all, Im slightly lost at what I may be missing :) hiera.yaml --- :hierarchy: - %{certname} - %{environment} - global - %{environment}/common :backends: - yaml :yaml: :datadir:

Hi... I''ve been trying to set up boolean values in Hiera, but with no luck. For example, I''m using puppetlabs-haproxy module, and this is a code snippet: class haproxy ( $manage_service = true, ... ) inherits haproxy::params { ... if $manage_service { } } Now, this is how I set up values in hiera: haproxy::manage_service: false But, it seems that

According to the documentation at http://docs.puppetlabs.com/puppet/2.7/reference/lang_conditional.html#if-statements, you can test for truth with syntax like this: if $is_virtual == ''true'' { AFAICT that''s not the case. The quotes around ''true'' make the comparison always fail. Here''s my test case class users {

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

I''ve been using PuppetDB as an ENC for a while, but I haven''t really utilized it for stored configs or anything. I was mostly interested in replacing Dashboard''s reporting capabilities, but PuppetDB doesn''t yet do anything (that I can see) with reports. So I''m currently looking into setting up a separate Foreman server. I saw the script mentioned

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

I''m trying to set a global noop but it doesn''t seem possible, There are 2 bugs open about this which to me look pretty serious as the expected behaviour isn''t the case. http://projects.puppetlabs.com/issues/21286 http://projects.puppetlabs.com/issues/6549 If anyone has a work around (that doesn''t include modifying puppet.conf file) I would be very

Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

Hi guys, I don''t know how to solve this: I want ".yaml"-files in each module''s "/data"-directory. These .yaml-files should contain data, which Hiera sould pass to the module''s manifests. How can I do that? I''m using Puppet 3.3.1 Thanks in advance! -- You received this message because you are subscribed to the Google Groups "Puppet

I''m running a previously working set of modules with the Puppet master version 3.1.0-rc2. I''m getting the Error: stack level too deep Here is a chunk of the debug Debug: Scope(Class[Zabbix]): Retrieving template zabbix/zabbix.conf.php.erb Debug: template[/etc/puppet/environments/production/modules/zabbix/templates/zabbix.conf.php.erb]: Bound template variables for

I''ve been working on getting spec tests on all of my modules and am down to ones that use hiera and don''t have any reasonable defaults. It looks like there is a project on GH (https://github.com/amfranz/rspec-hiera-puppet) that is designed to fill this need, but for the life of me I cannot make it work. FriedBob helped out on the IRC channel some with his solution of including