[Puppet Users] Re: IIS / ASP.Net Module for Windows 2003 / windows 2008

[Rakesh Kathpal]

Can someone please help me out with this issue?

On Thu, Feb 7, 2013 at 6:39 PM, Rakesh Kathpal  wrote:

> Please see.. if you can help me out in this issue...
>
> Appreciate your efforts..
>
> -- Forwarded message --
> From: Rakesh Kathpal 
> Date: Thu, Feb 7, 2013 at 4:48 PM
> Subject: IIS / ASP.Net Module for Windows 2003 / windows 2008
> To: puppet-users@googlegroups.com
>
>
> Hi,
>
> I am looking for IIS and asp.net module for windows 2003 & windows 2008,
> can anyone please help ?
>
> I came across the module https://github.com/puppetlabs/puppetlabs-dismbut it 
> works only for windows 2008 R2
>
> Also I had a look at the module https://github.com/simondean/puppet-iisbut 
> not sure what should I put it in my nodes.pp for it to work.
>
> Thanks & Regards,
>
> Rakesh K.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] issue storing facts values in mysql on puppet master 3.0.2

[Heena]

Hi,

   Version of puppet master - 3.0.2
   Version of puppet client- 3.0.2
   I have declared in [master] section.

On Saturday, February 9, 2013 7:59:06 AM UTC+5:30, denmat wrote:
>
> Hi, 
>
> Couple of questions: 
> What version of puppet? 
> What section of the puppet conf do you have those options declared (should 
> be in [master])? 
>
> Den 
>
> On 08/02/2013, at 20:24, Heena > wrote: 
>
> > inventory_active_record 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Download and unzip to install a webapp

[Brendan O'Bra]

+1 for packaging natively (deb, rpm, etc) and using the Puppet "package"
resource to deliver/install it. Life will be much better this way ;)


On Sun, Feb 10, 2013 at 2:18 PM, Jakov Sosic  wrote:

> On 02/10/2013 11:09 PM, Andreas Hilboll wrote:
>
>> Hi,
>>
>> I would like to install Piwik [*], which is a PHP webstatistics package,
>> on some of my nodes, using Puppet. The underlying servers are running
>> Debian Squeeze. Piwik is distributed as a .zip or .tar.gz file, which is
>> available at their website. They provide a constant URL always pointing
>> to the latest release:
>>
>> http://builds.piwik.org/**latest.zip
>>
>> How can I download and unzip this package to a defined location on my
>> nodes, changing the UID/GID of the unzipped files from root to www-data?
>>
>> Your help is greatly appreciated!
>>
>
> Although this task can be done with puppet, puppet is not designed to do
> it. It simply is not deploy/installation tool. It would be best if you
> could package up piwik in the OS native packages (deb). That way you could
> set up exact permissions, pre/post scripts, and then use puppet's "package"
> resource to install it.
>
> If you instead try to do the whole fetch/untar/chmod with puppet, you'll
> find yourself in a world of grief ...
>
>
> --
> Jakov Sosic
> www.srce.unizg.hr
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 
> puppet-users+unsubscribe@**googlegroups.com
> .
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at 
> http://groups.google.com/**group/puppet-users?hl=en
> .
> For more options, visit 
> https://groups.google.com/**groups/opt_out
> .
>
>
>


-- 
GVoice: 707.410.0371
LinkedIn: http://www.linkedin.com/in/brendanobra

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Download and unzip to install a webapp

[Jakov Sosic]

On 02/10/2013 11:09 PM, Andreas Hilboll wrote:

Hi,

I would like to install Piwik [*], which is a PHP webstatistics package,
on some of my nodes, using Puppet. The underlying servers are running
Debian Squeeze. Piwik is distributed as a .zip or .tar.gz file, which is
available at their website. They provide a constant URL always pointing
to the latest release:

http://builds.piwik.org/latest.zip

How can I download and unzip this package to a defined location on my
nodes, changing the UID/GID of the unzipped files from root to www-data?

Your help is greatly appreciated!


Although this task can be done with puppet, puppet is not designed to do 
it. It simply is not deploy/installation tool. It would be best if you 
could package up piwik in the OS native packages (deb). That way you 
could set up exact permissions, pre/post scripts, and then use puppet's 
"package" resource to install it.


If you instead try to do the whole fetch/untar/chmod with puppet, you'll 
find yourself in a world of grief ...



--
Jakov Sosic
www.srce.unizg.hr

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Download and unzip to install a webapp

[Andreas Hilboll]

Hi,

I would like to install Piwik [*], which is a PHP webstatistics package,
on some of my nodes, using Puppet. The underlying servers are running
Debian Squeeze. Piwik is distributed as a .zip or .tar.gz file, which is
available at their website. They provide a constant URL always pointing
to the latest release:

   http://builds.piwik.org/latest.zip

How can I download and unzip this package to a defined location on my
nodes, changing the UID/GID of the unzipped files from root to www-data?

Your help is greatly appreciated!

Cheers, Andreas.



[*] http://piwik.org/

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Fedora going to be ansible ?

[yersinia]

http://lists.fedoraproject.org/pipermail/devel/2013-January/176011.html

https://fedorahosted.org/formulas/wiki/WikiStart

Hmm, difficult to tell. Perhaps someone here know more.

Best

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Re: warnings for those shifting from puppet kick to mcollective

[R.I.Pienaar]

- Original Message -
> From: "Ellison Marks" 
> To: puppet-users@googlegroups.com
> Sent: Sunday, February 10, 2013 10:05:25 PM
> Subject: [Puppet Users] Re: warnings for those shifting from puppet kick to 
> mcollective
> 
> We use mco puppet runall 1 (our master is slightly anemic) in an every hour
> cron job. We have few enough hosts that they can all run within the hour.
> It's not quite as nice as the commander, as the commander would start
> running them all immediately after the last one was done, but it works for
> our purposes.

We'll soon release a new commander :) the runall logic is in a utility
class we'll pretty much just call it in a loop

I am looking for some big sites using the new agent to get some feedback on
the new runall logic so we can be sure it's logic doesnt have the same issues
as the previous commander

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: warnings for those shifting from puppet kick to mcollective

[Ellison Marks]

We use mco puppet runall 1 (our master is slightly anemic) in an every hour 
cron job. We have few enough hosts that they can all run within the hour. 
It's not quite as nice as the commander, as the commander would start 
running them all immediately after the last one was done, but it works for 
our purposes.

On Friday, February 8, 2013 10:44:51 AM UTC-8, Jo wrote:

> 3. There's no documented best way to run puppet from cron.
>
> I suspect PL hasn't put down a recipe for this since Puppet Commander 
> hasn't been updated to work with Puppet 3 yet. That's probably the answer, 
> but it's not available yet. This might be a good reason to wait.
>
> We settled on the many-year-old version of running it from cron with 
> fqdn_rand(30). Given the numerous problems with the cron resource, we did 
> this in a separate cron.d file like so:
>
>  # two variables to control puppet run time
> $first_minute  = fqdn_rand(30)
> $second_minute = $first_minute + 30
> file { "/etc/cron.d/puppet":
> owner   => root,
> group   => root,
> mode=> 0444,
> content => template('puppet/cron-puppet'),
> require => Package['puppet'],
> }
>
> There might be a better way, but I couldn't find it. I'd really like to 
> see a "best practice" recommendation from PuppetLabs.
>
> -- 
> Jo Rhett
> Net Consonance : net philanthropy to improve open source and internet 
> projects.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet dashboard stuck pending jobs

[Jagga Soorma]

Looks like that was actually the problem.  Searched google and came across 
the fix.  Had to change the type of the messages column to mediumtext and 
the pending jobs started finishing.  Did this by:

alter table report_logs change column message message VARCHAR(65536);

Just in case someone runs into this issue.  Thanks.

On Sunday, February 10, 2013 10:56:14 AM UTC-8, Jagga Soorma wrote:
>
> Thanks for pointing me to the log location.  Looks like this might be the 
> cause of the problem:
>
> --
> ..snip
> 2013-02-10T10:40:35-0800: [Worker(delayed_job.3 host:ssfpcond01 
> pid:25048)] Report.create_from_yaml_file failed with 
> ActiveRecord::StatementInvalid: *Mysql::Error: Data too long for column 
> 'details' at row 1: INSERT INTO `delayed_job_failures` *(`summary`, 
> `read`, `updated_at`, `backtrace`, `details`, `created_at`) 
> VALUES('Importing report report-18121-1179.
> yaml', 0, '2013-02-10 18:40:35', '--- \n- 
> /usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/a
> ..snip..
> --
>
> I am managing my passwd & group file via puppet which at times have huge 
> amount of changes especially in the group file.  This could possibly be 
> causing this error.  Is there a way to increase the size of the details 
> column to enable it to accept larger data?
>
> Has anyone seen this issue before?
>
> Thanks again for your help with this.
>
> On Friday, February 8, 2013 1:53:02 PM UTC-8, Jagga Soorma wrote:
>>
>> Hi Guys,
>>
>> I am a new puppet user and wanted some type of monitoring for puppet so 
>> deployed puppet-dashboard.  It has been working very well for a few days 
>> not, but all of a sudden I start getting pending tasks and they never 
>> finish even after restarting all processes.  They keep accumulating and 
>> never seem to finish even though the clients are running fine.  I have the 
>> puppet-dashboard running on a different server than my puppetmaster.  Is 
>> there any way to troubleshoot what seems to be stuck and how to I get it 
>> going without having to destroy the dashboard mysql db and recreating it 
>> again?  That is the only way I have got it working again but that is not 
>> the correct way of doing this :)  Any help would be appreciated.
>>
>> Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] hiera query yaml parameters

[roadtest]

Thanks Steven,  I uploaded my code 
to https://github.com/roadtest/plm-accounts and I will study your code in 
the mean time.

cheers,

carl

On Sunday, February 10, 2013 12:07:15 AM UTC-5, Steven wrote:
>
>  I'm not noticing the problem, but maybe it would help to see some other 
> code.
> I just uploaded my mounts module to github. It has one place that uses a 
> function from Example42, but that can be replaced with a normal hiera call.
>
> https://github.com/snemetz/Puppet_mounts
>
> I have a few modules that use this method, but I need time to document and 
> clean them up a bit, before releasing them.
> Mounts is one of the simpler ones.
>
> Steven
>
>
> --
> Date: Sat, 9 Feb 2013 20:15:55 -0800
> From: rai...@gmail.com 
> To: puppet...@googlegroups.com 
> Subject: Re: [Puppet Users] hiera query yaml parameters
>
> When trying to separate user information in a yaml file, I encounter two 
> issues. 
>
> 1. when I use the yaml file in init.pp under my user account module,  it 
> gives following errors. ssh_user_hash is the assigned in class  as 
>  "$ssh_user_hash = hiera(ssh_users)"
> ===
> root@vm1:/etc/puppet/manifests# puppet apply --verbose nodes.pp
> Info: Loading facts in 
> /etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
> Info: Loading facts in 
> /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
> Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
> Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
> Warning: Could not retrieve fact fqdn
> Warning: Unrecognised escape sequence '\!' in file 
> /etc/puppet/manifests/nodes.pp at line 12
> Warning: Host is missing hostname and/or domain: vm1
> Error: *ssh_user_hash is not an hash or array* when accessing it with 
> user1 at /etc/puppet/modules/plm-accounts/manifests/init.pp:41 on node vm1
> Error: *ssh_user_hash is not an hash or array *when accessing it with 
> user1 at /etc/puppet/modules/plm-accounts/manifests/init.pp:41 on node vm1
> ===
>
> 2.if I move the hiera output to node.pp, it can run on host vm1, which is 
> my puppet master with yaml file on it. But it can't run on other puppet 
> client server as it says can't find yaml file.
> ===
> Error: Could not find data item ssh_users in any Hiera data file and no 
> default supplied at /etc/puppet/manifests/nodes.pp:1 *on node vm2*
> ===
>
> Here is my yaml file and init.pp in my user module file.
> #more /var/lib/hiera/OpsUser.yaml
> ---
> ssh_users:
> user1 :
> FullName : "User1"
> additional_groups : "adm"
> shell : "/bin/bash"
> gid : 1003
> uid : 1003
> pwhash : "$1$E7OvghG0$OmZMtTbQ2uYf5GA5u7RSH1"
> ssh_key : 
> type : "ssh-rsa"
> key : 
> "B3NzaC1yc2EBJQAAAIBqOaxEVoWs69JM1H5jpzW7JvIwuanN4VW7F+uDVI1sii6BjROmYgYCvVoH+9/c3K5MNxqk35DHlFffgFk0b3o24Qa4RZZgxnUPTxsRIScaHQlr4/flYw643zVSwBpiEdBUfpRinc
> UiaYfy6SCPu3aiKRyFgxZ6VByExrbHLwsz5w=="
> comment : "us...@yahoo.com "
>
> root@vm1:/var/lib/hiera# more 
> /etc/puppet/modules/plm-accounts/manifests/init.pp
> class plm-accounts {
> #exec {
> #"/bin/echo user1:abc123 | /usr/sbin/chpasswd":
> #onlyif => "/bin/egrep -q '^user1:\!:' /etc/shadow",
> #}
>
> $ssh_user_hash = hiera(ssh_users)
>   $user_keys = keys($ssh_user_hash)
>   notice (" keys are $ssh_user_hash" )
>   if is_array ($user_keys) {
> add_users { $user_keys: }
>   }
>
>   define add_users {
> $user_uid = $ssh_user_hash[$name][uid] 
> $real_name = $ssh_user_hash[$name][FullName]
> notice ( "$user_uid is $real_name ")
> plm-accounts::virtual { "$name" :
>   uid => $user_uid,
>   realname => $real_name,
> }
> plm-accounts::add_ssh_key { $name :
>   key => "${ssh_user_hash[$name][ssh_key][key]}", 
>   type => "${ssh_user_hash[$name][ssh_key][type]}"
>   }
>   }
> }
>
>
>
>
> On Tuesday, February 5, 2013 12:00:25 PM UTC-5, roadtest wrote:
>
> you are right again:-) 
>
> For people who are new to puppet,  here is the installation instruction - 
> http://forge.puppetlabs.com/puppetlabs/stdlib.  stdlib is built in Puppet 
> Enterprise and needs to be installed for community version.
>
> cheers,
>
> carl
>
> On Tuesday, February 5, 2013 11:28:46 AM UTC-5, Steven wrote:
>
>  keys comes form the PuppetLab's stdlib module
> So does is_array and a bunch of other nice functions
>
>
> Steven
>
>  
> --
> Date: Tue, 5 Feb 2013 07:12:45 -0800
> From: rai...@gmail.com
> To: puppet...@googlegroups.com
> Subject: Re: [Puppet Users] hiera query yaml parameters
>
> Steven, thanks for your reply!  You are right. It is unnecessary using 
> create_resource to query yaml parameters. It can be done directly as 
> following:
>
> $sshd_hash = hiera(os_users)
> $server_ssh_keys = $sshd_hash[$username][ssh_keys][key]
>
> format of my os_users yaml file was not correct, that is why it failed me. 
>
> Btw

Re: [Puppet Users] how to implement cascading defaults based on puppet classes

[Roman Shaposhnik]

On Sun, Feb 10, 2013 at 9:32 AM, Keith Burdis  wrote:
> Have you looked at using hiera [1] for your configuration? It is very good
> for cascading defaults with more specific config at the top of the hierarchy
> and the least specific at the bottom. It is part of Puppet 3 and an add on
> for 2.7.

Yes, I have looked at it. My problem with Hiera is that it resides completely
outside of Puppet's DSL and is arguably pretty orthogonal to the parameterized
classes API. I like parameterized classes precisely because they are
dynamic. IOW, I can have my ENC instantiate classes with particular
parameters depending on any criteria I want *without* affecting anything
else on the system. If I want my cluster instantiated during odd numbered
hours to have auth => 'simple' and the rest auth => 'kerberos' -- that's
just ENC's job. If I want to pull off that same trick with Hiera --
I'm essentially
signing up to change a bunch of global variables that can potentially
affect my entire site.

That said, I'm starting to suspect that any solution to my problem that can
be hidden inside of parsing step has to either be parsing order dependent
(yuk!) or it has to rely on some global state that is guaranteed to be
consistent
before the parser takes over. Hiera fits that description, but it is too global.
Perhaps I can simply teach my ENC to spew out the top-level parameter
called cascading_defaults which would be a hiera-like hash for looking up
those very same values. Then my params class could be made rewritten as:
 class cluster::hdfs::params {
  auth = hlookup('auth', $::cascading_defaults, ['cluster',
'hdfs'], 'simple')
      }

Does it make sense?

Thanks,
Roman.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Re: Puppet dashboard stuck pending jobs

[Jagga Soorma]

Thanks for pointing me to the log location.  Looks like this might be the 
cause of the problem:

--
..snip
2013-02-10T10:40:35-0800: [Worker(delayed_job.3 host:ssfpcond01 pid:25048)] 
Report.create_from_yaml_file failed with ActiveRecord::StatementInvalid: 
*Mysql::Error: 
Data too long for column 'details' at row 1: INSERT INTO 
`delayed_job_failures` *(`summary`, `read`, `updated_at`, `backtrace`, 
`details`, `created_at`) VALUES('Importing report report-18121-1179.
yaml', 0, '2013-02-10 18:40:35', '--- \n- 
/usr/share/puppet-dashboard/vendor/rails/activerecord/lib/active_record/connection_adapters/a
..snip..
--

I am managing my passwd & group file via puppet which at times have huge 
amount of changes especially in the group file.  This could possibly be 
causing this error.  Is there a way to increase the size of the details 
column to enable it to accept larger data?

Has anyone seen this issue before?

Thanks again for your help with this.

On Friday, February 8, 2013 1:53:02 PM UTC-8, Jagga Soorma wrote:
>
> Hi Guys,
>
> I am a new puppet user and wanted some type of monitoring for puppet so 
> deployed puppet-dashboard.  It has been working very well for a few days 
> not, but all of a sudden I start getting pending tasks and they never 
> finish even after restarting all processes.  They keep accumulating and 
> never seem to finish even though the clients are running fine.  I have the 
> puppet-dashboard running on a different server than my puppetmaster.  Is 
> there any way to troubleshoot what seems to be stuck and how to I get it 
> going without having to destroy the dashboard mysql db and recreating it 
> again?  That is the only way I have got it working again but that is not 
> the correct way of doing this :)  Any help would be appreciated.
>
> Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard stuck pending jobs

[Felipe Salum]

Are you having the problem after running 'puppet agent --test' a few times 
or it just happens without any manual run ?

I was having the same problem some days ago, in my case because I was 
running 'puppet agent --test', more specifically the --show_diff that is 
used in --test was automatically generating a lot of output and causing the 
puppet dashboard workers to fail and increase the processing queue.

Look at /usr/share/puppet-dashboard/log/delayed_job.log (or whatever your 
dashboard location is) and check what error it is giving.

You can clean the queue manually without reinstalling everything:

service puppet-dashboard-workers stop
cd /usr/share/puppet-dashboard
rm -f spool/*
rake jobs:clear RAILS_ENV=production
service puppet-dashboard-workers start

Regards,
Felipe

On Saturday, February 9, 2013 7:11:04 PM UTC-8, Jagga Soorma wrote:
>
> Anyone out there run into this issue before or have any idea about how to 
> troubleshoot such a problem?  Any help would be appreciated.  I can't keep 
> rebuilding puppet dashboard every time this happens.
>
> Thanks
>
> On Friday, February 8, 2013 2:37:55 PM UTC-8, Jagga Soorma wrote:
>>
>> Yes, the workers are definitely running and I have tried restarting 
>> puppet-dashboard-workers a few times as well as rebooting the vm completely 
>> without any luck.  Something seems to be stuck somewhere but I can't figure 
>> out what.  This has happened a few times now and I have just been 
>> recreating from scratch to get it functional again.  Are there any logs for 
>> the workers that might tell us why these pending jobs are stuck or not 
>> finishing?
>>
>> Thanks.
>>
>> On Fri, Feb 8, 2013 at 2:27 PM, Jo Rhett 
>> 
>> > wrote:
>>
>>> Make sure that your dashboard workers are running. If you are using 
>>> CentOS then "service puppet-dashboard-workers status" will tell you.
>>>
>>> On Feb 8, 2013, at 1:53 PM, Jagga Soorma wrote:
>>>
>>> I am a new puppet user and wanted some type of monitoring for puppet so 
>>> deployed puppet-dashboard.  It has been working very well for a few days 
>>> not, but all of a sudden I start getting pending tasks and they never 
>>> finish even after restarting all processes.  They keep accumulating and 
>>> never seem to finish even though the clients are running fine.  I have the 
>>> puppet-dashboard running on a different server than my puppetmaster.  Is 
>>> there any way to troubleshoot what seems to be stuck and how to I get it 
>>> going without having to destroy the dashboard mysql db and recreating it 
>>> again?  That is the only way I have got it working again but that is not 
>>> the correct way of doing this :)  Any help would be appreciated.
>>>
>>> Thanks!
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to puppet-users...@googlegroups.com .
>>> To post to this group, send email to puppet...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>>
>>>  -- 
>>> Jo Rhett
>>> Net Consonance : net philanthropy to improve open source and internet 
>>> projects.
>>>
>>>
>>>  
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Puppet Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to puppet-users...@googlegroups.com .
>>> To post to this group, send email to puppet...@googlegroups.com
>>> .
>>> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] how to implement cascading defaults based on puppet classes

[Keith Burdis]

Have you looked at using hiera [1] for your configuration? It is very good
for cascading defaults with more specific config at the top of the
hierarchy and the least specific at the bottom. It is part of Puppet 3 and
an add on for 2.7.

  - Keith

[1]
http://www.devco.net/archives/2011/06/05/hiera_a_pluggable_hierarchical_data_store.php
 On 10 Feb 2013 06:00, "Roman Shaposhnik"  wrote:

> Hi!
>
> suppose my puppet recipes are deploying a configuration
> for the entire cluster (lets say Hadoop) consisting of quite a
> few distributed systems (lets say distributed file-system --
> HDFS, scheduler -- YARN, coordinator -- zookeeper). Each
> of these distributed systems in turn consists of a few agents
> (e.g. in HDFS there's a NameNode, DataNode, etc.).
>
> My biggest concern is how to make it possible to cascade
> defaults in such a way that they can be specified at each
> of the levels: entire cluster, subsystem, an agent that
> is part of the subsystem.
>
> To be more explicit, suppose I have a node description
> that looks like this:
> -
> class { "cluster::hdfs::datanode":
>namenode_uri => "hdfs://foo.company.com",
> auth => "kerberos"
> }
> class { "cluster::hdfs::secondary_namenode":
> namenode_uri => "hdfs://foo.company.com",
>auth  => "kerberos"
> }
> class { "cluster::zookeeper::server":
> ensemble => "zoo1.company.com",
> auth => "kerberos"
> }
> -
>
> What would be the ideal way for me to not repeat myself
> and set auth as a cluster-level default, while having
> namenode_uri as an HDFS-level default?
>
> Really, what I need should look something like:
> --
> class { "cluster":
>auth => kerberos
> }
> class { "hdfs":
>namenode_uri => "hdfs://foo.company.com"
> }
> class { "cluster::hdfs::datanode": }
> class { "cluster::hdfs::secondary_namenode": }
> class { "cluster::zookeeper::server":
> ensemble => "zoo1.company.com",
> }
> 
>
> Any ideas on how this could be implemented? I've tried
> a couple of things, but so far no luck. The natural way
> of solving it via inheritance (e.g. cluster::hdfs inherits cluster
> and cluster::hdfs::datanode inherits cluster::hdfs, etc.)
> seems to be of no help at all. Another thing I was considering
> was something along the lines of:
>   class cluster::hdfs::datanode (
>   $auth = $cluster::hdfs::params::auth
>   ) inherits cluster::hdfs::params {...}
>   ..
>   class cluster::hdfs::params {
>   if defined(Class['cluster::hdfs']) {
>   $auth = $cluster::hdfs::auth
>   } elsif defined(Class['cluster']) {
>   $auth = $cluster::auth
>   } else {
>   $auth = 'simple'
>   }
>   }
>
> seems to be pretty ugly and worse yet  dependent on the parsing
> order.
>
> Am I missing something obvious here?
>
> Thanks,
> Roman.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] dashboard permission issue

[Vitaliy Gladkevitch]

On 2/6/2013 1:18 PM, Moses Mendoza wrote:

On Tue, Feb 5, 2013 at 1:15 AM,   wrote:

I'm having trouble getting puppet dashboard (1.2.21) to run on apache.

i installed puppetmaster-passenger and puppet-dashboard package. It didn't
create user puppet-dashboard automatically as stated in the installation
guide,
so i created one manually and chowned all files under /puppet-dashboard.
when testing with webrick everything works fine (as root).
when i try with other users this is what happens:

root@puppetmaster:/usr/share/puppet-dashboard/script# sudo -u
puppet-dashboard ./server -e production
=> Booting WEBrick
=> Rails 2.3.14 application starting on http://0.0.0.0:3000
./../config/../vendor/rails/railties/lib/initializer.rb:926:in `read':
Permission denied - /usr/share/puppet-dashboard/config/database.yml
(Errno::EACCES)
from ./../config/../vendor/rails/railties/lib/initializer.rb:926:in
`database_configuration'
from ./../config/../vendor/rails/railties/lib/initializer.rb:437:in
`initialize_database'
from ./../config/../vendor/rails/railties/lib/initializer.rb:141:in
`process'
from ./../config/../vendor/rails/railties/lib/initializer.rb:113:in `send'
from ./../config/../vendor/rails/railties/lib/initializer.rb:113:in `run'
from /usr/share/puppet-dashboard/config/environment.rb:14
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from
/usr/share/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in
`require'
from
/usr/share/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:547:in
`new_constants_in'
from
/usr/share/puppet-dashboard/vendor/rails/activesupport/lib/active_support/dependencies.rb:182:in
`require'
from
/usr/share/puppet-dashboard/vendor/rails/railties/lib/commands/server.rb:84
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from ./server:3

When running with apache, passneger gives the same error:
Permission denied - /usr/share/puppet-dashboard/config/database.yml
Application root: /usr/share/puppet-dashboard

I tried changing ownerships, giving 777 rights on files etc..
First run with webrick might have been as root. Could this be an issue? If
so, is it fixable or am i due for a reinstallation?

Thanks a million for any help on this!!


/usr/share/puppet-dashboard/config/database.yml is actually a symlink
to /etc/puppet-dashboard/config/database.yml, and the same with
settings.yml, respectively. Check if the permissions in
/etc/puppet-dashboard allow read by the puppet-dashboard user. You're
correct about the package not creating the user, this is a known issue
that needs to get fixed - http://projects.puppetlabs.com/issues/18135.
Thanks for the link to the bug -- I was the one who submitted it. Just 
posted a fix on my blog over at http://serverinferno.com/?p=40



--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Puppet Users] Integration testing puppet

[gareth rushgrove]

Bryan Berry gave a talk at FOSDEM a couple of days ago about
integration testing for infrastructure
(https://speakerdeck.com/bryanwb/dont-shrug-integration-testing-for-infrastructure-with-ruby-frameworks).
He talked about a tool that's
come out of the Chef community called Test Kitchen, and pointed out it
should be possible to use it to test Puppet code too.

I've put together a quick demo of doing that here:

https://github.com/garethr/tk-demo-puppet

The demo brings up two virtual machines, applies a set of puppet
manifests and then runs some tests to assert things worked - all in
one command and with limited configuration.

The open issue on test kitchen for the multi provisioner support is
ere https://github.com/opscode/test-kitchen/issues/36

Any feedback welcome.

At the moment it's a proof of concept, but I'd like to see it exist
for real.

Or if anyone has a good approach to this problem already I'd love to see it?

Cheers

Gareth

--
Gareth Rushgrove
Web Geek

morethanseven.net
garethrushgrove.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Puppet Users] Puppet dashboard stuck pending jobs

[Esther Hanko]

Try looking in /usr/share/puppet-dashboard/log/.
Did you update the dashboard or puppet master recently? I have ran into 
similar problems after updates, since I run the dashboard on a different 
port than the external_nodes script uses. The DASHBOARD_URL in 
/usr/share/puppet-dashboard/bin/external_node got changed back into 
localhost:3000 and as a result, all my nodes were seen as unresponsive.


On 02/10/2013 04:11 AM, Jagga Soorma wrote:
Anyone out there run into this issue before or have any idea about how 
to troubleshoot such a problem?  Any help would be appreciated.  I 
can't keep rebuilding puppet dashboard every time this happens.


Thanks

On Friday, February 8, 2013 2:37:55 PM UTC-8, Jagga Soorma wrote:

Yes, the workers are definitely running and I have tried
restarting puppet-dashboard-workers a few times as well as
rebooting the vm completely without any luck.  Something seems to
be stuck somewhere but I can't figure out what.  This has happened
a few times now and I have just been recreating from scratch to
get it functional again.  Are there any logs for the workers that
might tell us why these pending jobs are stuck or not finishing?

Thanks.

On Fri, Feb 8, 2013 at 2:27 PM, Jo Rhett mailto:jrh...@netconsonance.com>> wrote:

Make sure that your dashboard workers are running. If you are
using CentOS then "service puppet-dashboard-workers status"
will tell you.

On Feb 8, 2013, at 1:53 PM, Jagga Soorma wrote:

I am a new puppet user and wanted some type of monitoring for
puppet so deployed puppet-dashboard.  It has been working
very well for a few days not, but all of a sudden I start
getting pending tasks and they never finish even after
restarting all processes.  They keep accumulating and never
seem to finish even though the clients are running fine.  I
have the puppet-dashboard running on a different server than
my puppetmaster.  Is there any way to troubleshoot what seems
to be stuck and how to I get it going without having to
destroy the dashboard mysql db and recreating it again?  That
is the only way I have got it working again but that is not
the correct way of doing this :)  Any help would be appreciated.

Thanks!

-- 
You received this message because you are subscribed to the

Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to
puppet-users+unsubscr...@googlegroups.com
.
To post to this group, send email to
puppet-users@googlegroups.com
.
Visit this group at
http://groups.google.com/group/puppet-users?hl=en
.
For more options, visit
https://groups.google.com/groups/opt_out
.




-- 
Jo Rhett

Net Consonance : net philanthropy to improve open source and
internet projects.



-- 
You received this message because you are subscribed to the

Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to puppet-users+unsubscr...@googlegroups.com
.
To post to this group, send email to
puppet-users@googlegroups.com
.
Visit this group at
http://groups.google.com/group/puppet-users?hl=en
.
For more options, visit
https://groups.google.com/groups/opt_out
.



--
You received this message because you are subscribed to the Google 
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to puppet-users+unsubscr...@googlegroups.com.

To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.